Geo-polygon queryedit
A query returning hits that only fall within a polygon of points. Here is an example:
GET /_search
{
"query": {
"bool" : {
"must" : {
"match_all" : {}
},
"filter" : {
"geo_polygon" : {
"person.location" : {
"points" : [
{"lat" : 40, "lon" : -70},
{"lat" : 30, "lon" : -80},
{"lat" : 20, "lon" : -90}
]
}
}
}
}
}
}
Query Optionsedit
| Option | Description |
|---|---|
|
Optional name field to identify the filter |
|
Set to |
Allowed Formatsedit
Lat Long as Arrayedit
Format as [lon, lat]
Note: the order of lon/lat here must conform with GeoJSON.
GET /_search
{
"query": {
"bool" : {
"must" : {
"match_all" : {}
},
"filter" : {
"geo_polygon" : {
"person.location" : {
"points" : [
[-70, 40],
[-80, 30],
[-90, 20]
]
}
}
}
}
}
}
Lat Lon as Stringedit
Format in lat,lon.
GET /_search
{
"query": {
"bool" : {
"must" : {
"match_all" : {}
},
"filter" : {
"geo_polygon" : {
"person.location" : {
"points" : [
"40, -70",
"30, -80",
"20, -90"
]
}
}
}
}
}
}
Geohashedit
GET /_search
{
"query": {
"bool" : {
"must" : {
"match_all" : {}
},
"filter" : {
"geo_polygon" : {
"person.location" : {
"points" : [
"drn5x1g8cu2y",
"30, -80",
"20, -90"
]
}
}
}
}
}
}
geo_point Typeedit
The query requires the geo_point type to be set on the
relevant field.
Ignore Unmappededit
When set to true the ignore_unmapped option will ignore an unmapped field
and will not match any documents for this query. This can be useful when
querying multiple indexes which might have different mappings. When set to
false (the default value) the query will throw an exception if the field
is not mapped.