Geopoint field type
editGeopoint field type
editFields of type geo_point
accept latitude-longitude pairs, which can be used:
-
to find geopoints within a bounding box,
within a certain distance of a central point,
or within a polygon or within a
geo_shape
query. - to aggregate documents geographically or by distance from a central point.
- to integrate distance into a document’s relevance score.
- to sort documents by distance.
There are five ways that a geopoint may be specified, as demonstrated below:
PUT my-index-000001 { "mappings": { "properties": { "location": { "type": "geo_point" } } } } PUT my-index-000001/_doc/1 { "text": "Geopoint as an object", "location": { "lat": 41.12, "lon": -71.34 } } PUT my-index-000001/_doc/2 { "text": "Geopoint as a string", "location": "41.12,-71.34" } PUT my-index-000001/_doc/3 { "text": "Geopoint as a geohash", "location": "drm3btev3e86" } PUT my-index-000001/_doc/4 { "text": "Geopoint as an array", "location": [ -71.34, 41.12 ] } PUT my-index-000001/_doc/5 { "text": "Geopoint as a WKT POINT primitive", "location" : "POINT (-71.34 41.12)" } GET my-index-000001/_search { "query": { "geo_bounding_box": { "location": { "top_left": { "lat": 42, "lon": -72 }, "bottom_right": { "lat": 40, "lon": -74 } } } } }
Geopoint expressed as an object, with |
|
Geopoint expressed as a string with the format: |
|
Geopoint expressed as a geohash. |
|
Geopoint expressed as an array with the format: [ |
|
Geopoint expressed as a Well-Known Text
POINT with the format: |
|
A geo-bounding box query which finds all geopoints that fall inside the box. |
Geopoints expressed as an array or string
Please note that string geopoints are ordered as lat,lon
, while array
geopoints are ordered as the reverse: lon,lat
.
Originally, lat,lon
was used for both array and string, but the array
format was changed early on to conform to the format used by GeoJSON.
A point can be expressed as a geohash. Geohashes are base32 encoded strings of the bits of the latitude and longitude interleaved. Each character in a geohash adds additional 5 bits to the precision. So the longer the hash, the more precise it is. For the indexing purposed geohashs are translated into latitude-longitude pairs. During this process only first 12 characters are used, so specifying more than 12 characters in a geohash doesn’t increase the precision. The 12 characters provide 60 bits, which should reduce a possible error to less than 2cm.
Parameters for geo_point
fields
editThe following parameters are accepted by geo_point
fields:
If |
|
|
If |
Should the field be searchable? Accepts |
|
Accepts an geopoint value which is substituted for any explicit |
|
|
Defines what to do if the script defined by the |
|
If this parameter is set, then the field will index values generated by this script, rather than reading the values directly from the source. If a value is set for this field on the input document, then the document will be rejected with an error. Scripts are in the same format as their runtime equivalent, and should emit points as a pair of (lat, lon) double values. |
Using geopoints in scripts
editWhen accessing the value of a geopoint in a script, the value is returned as
a GeoPoint
object, which allows access to the .lat
and .lon
values
respectively:
def geopoint = doc['location'].value; def lat = geopoint.lat; def lon = geopoint.lon;
For performance reasons, it is better to access the lat/lon values directly:
def lat = doc['location'].lat; def lon = doc['location'].lon;