Point field typeedit
The point
data type facilitates the indexing of and searching
arbitrary x, y
pairs that fall in a 2dimensional planar
coordinate system.
You can query documents using this type using shape Query.
As with geo_shape and geo_point, point
can be specified in GeoJSON
and WellKnown Text formats.
However, there are a number of additional formats that are supported for convenience and historical reasons.
In total there are five ways that a cartesian point may be specified, as demonstrated below:
PUT myindex000001 { "mappings": { "properties": { "location": { "type": "point" } } } } PUT myindex000001/_doc/1 { "text": "Point as an object using GeoJSON format", "location": { "type": "Point", "coordinates": [71.34, 41.12] } } PUT myindex000001/_doc/2 { "text": "Point as a WKT POINT primitive", "location" : "POINT (71.34 41.12)" } PUT myindex000001/_doc/3 { "text": "Point as an object with 'x' and 'y' keys", "location": { "x": 71.34, "y": 41.12 } } PUT myindex000001/_doc/4 { "text": "Point as an array", "location": [ 71.34, 41.12 ] } PUT myindex000001/_doc/5 { "text": "Point as a string", "location": "71.34,41.12" }
Point expressed as an object, in GeoJSON format, with 

Point expressed as a WellKnown Text
POINT with the format: 

Point expressed as an object, with 

Point expressed as an array with the format: [ 

Point expressed as a string with the format: 
Unlike the case with the geopoint field type,
the order of the coordinates x
and y
is the same for all formats above.
The coordinates provided to the indexer are single precision floating point values so
the field guarantees the same accuracy provided by the java virtual machine (typically
1E38
).
Parameters for point
fieldsedit
The following parameters are accepted by point
fields:
If 


If 
Accepts an point value which is substituted for any explicit 
Sorting and retrieving pointsedit
It is currently not possible to sort points or retrieve their fields
directly. The point
value is only retrievable through the _source
field.