Date and geo types #
date
#
A date-time value. Internally stored as epoch milliseconds; accepted input
depends on the field’s
format
(default strict_date_optional_time||epoch_millis), so both ISO-8601
strings ("2024-06-15T10:30:00Z") and raw millisecond integers work. Used
by
date range,
date histogram
aggregations and sort.
Parameters for date fields
#
Support indexing multiple values #
Yes
geo_point
#
A latitude/longitude point ({"lat": 39.9, "lon": 116.4}), indexed for
geo bounding box,
geo distance and
geo polygon queries. Distances use
haversine on WGS-84 in metres.
Parameters for geo_point fields
#
Support indexing multiple values #
Yes — a field may hold multiple points.
geo_shape
#
An arbitrary geometry — point, multi-point, line string, multi-line
string, polygon (with holes), multi-polygon, envelope or geometry
collection. Written as GeoJSON ({"type": "polygon", "coordinates": [[[-73.97, 40.80], …]]}, [lon, lat] order) or a WKT string; queried
with
geo shape queries by relation
(intersects, within, contains, disjoint). Matching is exact:
each shape’s bounding box is indexed in a 4-dimensional BKD tree for
candidates, and the stored geometry verifies the relation.
The shape’s column is always maintained (it is the exact-verification
source); column: false is ignored for this type.
Parameters for geo_shape fields
#
Support indexing multiple values #
No — a field holds one shape per document.