You're viewing version 2.17 of the OpenSearch documentation. This version is no longer maintained. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.
Geoshape query
Use a geoshape query to search for documents that contain geopoint or geoshape fields. You can filter documents using a geoshape that is defined within a query or use a pre-indexed geoshape.
The searched document field must be mapped as geo_point
or geo_shape
.
Spatial relations
When you provide a geoshape to the geoshape query, the geopoint and geoshape fields in the documents are matched using the following spatial relations to the provided shape.
Relation | Description | Supporting geographic field type |
---|---|---|
INTERSECTS | (Default) Matches documents whose geopoint or geoshape intersects with the shape provided in the query. | geo_point , geo_shape |
DISJOINT | Matches documents whose geoshape does not intersect with the shape provided in the query. | geo_shape |
WITHIN | Matches documents whose geoshape is completely within the shape provided in the query. | geo_shape |
CONTAINS | Matches documents whose geoshape completely contains the shape provided in the query. | geo_shape |
Defining the shape in a geoshape query
You can define the shape to filter documents in a geoshape query either by providing a new shape definition at query time or by referencing the name of a shape pre-indexed in another index.
Using a new shape definition
To provide a new shape to a geoshape query, define it in the geo_shape
field. You must define the geoshape in GeoJSON format.
The following example illustrates searching for documents containing geoshapes that match a geoshape defined at query time.
Step 1: Create an index
First, create an index and map the location
field as a geo_shape
:
PUT /testindex
{
"mappings": {
"properties": {
"location": {
"type": "geo_shape"
}
}
}
}
Step 2: Index documents
Index one document containing a point and another containing a polygon:
PUT testindex/_doc/1
{
"location": {
"type": "point",
"coordinates": [ 73.0515, 41.5582 ]
}
}
PUT testindex/_doc/2
{
"location": {
"type": "polygon",
"coordinates": [
[
[
73.0515,
41.5582
],
[
72.6506,
41.5623
],
[
72.6734,
41.7658
],
[
73.0515,
41.5582
]
]
]
}
}
Step 3: Run a geoshape query
Finally, define a geoshape to filter the documents. The following sections illustrate providing various geoshapes in a query. For more information about various geoshape formats, see Geoshape field type.
Envelope
An envelope
is a bounding rectangle in the [[minLon, maxLat], [maxLon, minLat]]
format. Search for documents containing geoshape fields that intersect with the provided envelope:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "envelope",
"coordinates": [
[
71.0589,
42.3601
],
[
74.006,
40.7128
]
]
},
"relation": "WITHIN"
}
}
}
}
The response contains both documents:
{
"took": 5,
"timed_out": false,
"_shards": {
"total": 1,
"successful": 1,
"skipped": 0,
"failed": 0
},
"hits": {
"total": {
"value": 2,
"relation": "eq"
},
"max_score": 0,
"hits": [
{
"_index": "testindex",
"_id": "1",
"_score": 0,
"_source": {
"location": {
"type": "point",
"coordinates": [
73.0515,
41.5582
]
}
}
},
{
"_index": "testindex",
"_id": "2",
"_score": 0,
"_source": {
"location": {
"type": "polygon",
"coordinates": [
[
[
73.0515,
41.5582
],
[
72.6506,
41.5623
],
[
72.6734,
41.7658
],
[
73.0515,
41.5582
]
]
]
}
}
}
]
}
}
Point
Search for documents whose geoshape fields contain the provided point:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "point",
"coordinates": [
72.8000,
41.6300
]
},
"relation": "CONTAINS"
}
}
}
}
Linestring
Search for documents whose geoshape fields do not intersect with the provided linestring:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "linestring",
"coordinates": [[74.0060, 40.7128], [71.0589, 42.3601]]
},
"relation": "DISJOINT"
}
}
}
}
Linestring geoshape queries do not support the WITHIN
relation.
Polygon
In GeoJSON format, you must list the vertices of the polygon in counterclockwise order and close the polygon so that the first vertex and the last vertex are the same.
Search for documents whose geoshape fields are within the provided polygon:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "polygon",
"coordinates": [
[
[74.0060, 40.7128],
[73.7562, 42.6526],
[71.0589, 42.3601],
[74.0060, 40.7128]
]
]
},
"relation": "WITHIN"
}
}
}
}
Multipoint
Search for documents whose geoshape fields do not intersect with the provided points:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "multipoint",
"coordinates" : [
[74.0060, 40.7128],
[71.0589, 42.3601]
]
},
"relation": "DISJOINT"
}
}
}
}
Multilinestring
Search for documents whose geoshape fields do not intersect with the provided lines:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "multilinestring",
"coordinates" : [
[[74.0060, 40.7128], [71.0589, 42.3601]],
[[73.7562, 42.6526], [72.6734, 41.7658]]
]
},
"relation": "disjoint"
}
}
}
}
Multilinestring geoshape queries do not support the WITHIN
relation.
Multipolygon
Search for documents whose geoshape fields are within the provided multipolygon:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type" : "multipolygon",
"coordinates" : [
[
[
[74.0060, 40.7128],
[73.7562, 42.6526],
[71.0589, 42.3601],
[74.0060, 40.7128]
],
[
[73.0515, 41.5582],
[72.6506, 41.5623],
[72.6734, 41.7658],
[73.0515, 41.5582]
]
],
[
[
[73.9146, 40.8252],
[73.8871, 41.0389],
[73.6853, 40.9747],
[73.9146, 40.8252]
]
]
]
},
"relation": "WITHIN"
}
}
}
}
Geometry collection
Search for documents whose geoshape fields are within the provided polygons:
GET /testindex/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "geometrycollection",
"geometries": [
{
"type": "polygon",
"coordinates": [[
[74.0060, 40.7128],
[73.7562, 42.6526],
[71.0589, 42.3601],
[74.0060, 40.7128]
]]
},
{
"type": "polygon",
"coordinates": [[
[73.0515, 41.5582],
[72.6506, 41.5623],
[72.6734, 41.7658],
[73.0515, 41.5582]
]]
}
]
},
"relation": "WITHIN"
}
}
}
}
Geoshape queries whose geometry collection contains a linestring or a multilinestring do not support the WITHIN
relation.
Using a pre-indexed shape definition
When constructing a geoshape query, you can also reference the name of a shape pre-indexed in another index. Using this method, you can define a geoshape at index time and refer to it by name at search time.
You can define a pre-indexed geoshape in GeoJSON or Well-Known Text (WKT) format. For more information about various geoshape formats, see Geoshape field type.
The indexed_shape
object supports the following parameters.
Parameter | Required/Optional | Description |
---|---|---|
id | Required | The document ID of the document containing the pre-indexed shape. |
index | Optional | The name of the index containing the pre-indexed shape. Default is shapes . |
path | Optional | The field name of the field containing the pre-indexed shape as a path. Default is shape . |
routing | Optional | The routing of the document containing the pre-indexed shape. |
The following example illustrates how to reference the name of a shape pre-indexed in another index. In this example, the index pre-indexed-shapes
contains the shape that defines the boundaries, and the index testindex
contains the shapes that are checked against those boundaries.
First, create the pre-indexed-shapes
index and map the boundaries
field for this index as a geo_shape
:
PUT /pre-indexed-shapes
{
"mappings": {
"properties": {
"boundaries": {
"type": "geo_shape",
"orientation" : "left"
}
}
}
}
For more information about specifying a different vertex orientation for polygons, see Polygon.
Index a polygon specifying the search boundaries into the pre-indexed-shapes
index. The polygon’s ID is search_triangle
. In this example, you’ll index the polygon in WKT format:
PUT /pre-indexed-shapes/_doc/search_triangle
{
"boundaries":
"POLYGON ((74.0060 40.7128, 71.0589 42.3601, 73.7562 42.6526, 74.0060 40.7128))"
}
If you haven’t already done so, index one document containing a point and another document containing a polygon into the testindex
index:
PUT /testindex/_doc/1
{
"location": {
"type": "point",
"coordinates": [ 73.0515, 41.5582 ]
}
}
PUT /testindex/_doc/2
{
"location": {
"type": "polygon",
"coordinates": [
[
[
73.0515,
41.5582
],
[
72.6506,
41.5623
],
[
72.6734,
41.7658
],
[
73.0515,
41.5582
]
]
]
}
}
Search for documents whose geoshapes are within the search_triangle
:
GET /testindex/_search
{
"query": {
"bool": {
"must": {
"match_all": {}
},
"filter": {
"geo_shape": {
"location": {
"indexed_shape": {
"index": "pre-indexed-shapes",
"id": "search_triangle",
"path": "boundaries"
},
"relation": "WITHIN"
}
}
}
}
}
}
The response contains both documents:
{
"took": 11,
"timed_out": false,
"_shards": {
"total": 1,
"successful": 1,
"skipped": 0,
"failed": 0
},
"hits": {
"total": {
"value": 2,
"relation": "eq"
},
"max_score": 1,
"hits": [
{
"_index": "testindex",
"_id": "1",
"_score": 1,
"_source": {
"location": {
"type": "point",
"coordinates": [
73.0515,
41.5582
]
}
}
},
{
"_index": "testindex",
"_id": "2",
"_score": 1,
"_source": {
"location": {
"type": "polygon",
"coordinates": [
[
[
73.0515,
41.5582
],
[
72.6506,
41.5623
],
[
72.6734,
41.7658
],
[
73.0515,
41.5582
]
]
]
}
}
}
]
}
}
Querying geopoints
You can also use a geoshape query to search for documents containing geopoints.
Geoshape queries on geopoint fields only support the default INTERSECTS
spatial relation, so you don’t need to provide the relation
parameter.
Geoshape queries on geopoint fields do not support the following geoshapes:
- Points
- Linestrings
- Multipoints
- Multilinestrings
- Geometry collections containing one of the preceding geoshape types
Create a mapping where location
is a geo_point
:
PUT /testindex1
{
"mappings": {
"properties": {
"location": {
"type": "geo_point"
}
}
}
}
Index two points into the index. In this example, you’ll provide the geopoint coordinates as strings:
PUT /testindex1/_doc/1
{
"location": "41.5623, 72.6506"
}
PUT /testindex1/_doc/2
{
"location": "76.0254, 39.2467"
}
For information about providing geopoint coordinates in various formats, see Formats.
Search for geopoints that intersect with the provided polygon:
GET /testindex1/_search
{
"query": {
"geo_shape": {
"location": {
"shape": {
"type": "polygon",
"coordinates": [
[
[74.0060, 40.7128],
[73.7562, 42.6526],
[71.0589, 42.3601],
[74.0060, 40.7128]
]
]
}
}
}
}
}
The response returns document 1:
{
"took": 21,
"timed_out": false,
"_shards": {
"total": 1,
"successful": 1,
"skipped": 0,
"failed": 0
},
"hits": {
"total": {
"value": 1,
"relation": "eq"
},
"max_score": 0,
"hits": [
{
"_index": "testindex1",
"_id": "1",
"_score": 0,
"_source": {
"location": "41.5623, 72.6506"
}
}
]
}
}
Note that when you indexed the geopoints, you specified their coordinates in "latitude, longitude"
format. When you search for matching documents, the coordinate array is in [longitude, latitude]
format. Thus, document 1 is returned in the results but document 2 is not.
Parameters
Geoshape queries accept the following parameters.
Parameter | Data type | Description |
---|---|---|
ignore_unmapped | Boolean | Specifies whether to ignore an unmapped field. If set to true , then the query does not return any documents that contain an unmapped field. If set to false , then an exception is thrown when the field is unmapped. Optional. Default is false . |