-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds geo-bounding box query documentation #2134
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
9a69d6a
Adds geo-bounding box query documentation
kolchfa-aws 7442dea
Removed geoshape
kolchfa-aws 7883266
Added geohash examples
kolchfa-aws b99feea
Incorporated doc review comments
kolchfa-aws 79dbec8
Implemented editorial feedback
kolchfa-aws File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,226 @@ | ||
--- | ||
layout: default | ||
title: Geo-bounding box queries | ||
parent: Query DSL | ||
nav_order: 55 | ||
--- | ||
|
||
# Geo-bounding box queries | ||
|
||
To search for documents that contain [geopoint]({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/geo-point) fields, use a geo-bounding box query. The geo-bounding box query returns documents whose geopoints are within the bounding box specified in the query. A document with multiple geopoints matches the query if at least one geopoint is within the bounding box. | ||
|
||
## Example | ||
|
||
You can use a geo-bounding box query to search for documents that contain geopoints. | ||
|
||
Create a mapping with the `point` field mapped as `geo_point`: | ||
|
||
```json | ||
PUT testindex1 | ||
{ | ||
"mappings": { | ||
"properties": { | ||
"point": { | ||
"type": "geo_point" | ||
} | ||
} | ||
} | ||
} | ||
``` | ||
|
||
Index three geopoints as objects with latitudes and longitudes: | ||
|
||
```json | ||
PUT testindex1/_doc/1 | ||
{ | ||
"point": { | ||
"lat": 74.00, | ||
"lon": 40.71 | ||
} | ||
} | ||
|
||
PUT testindex1/_doc/2 | ||
{ | ||
"point": { | ||
"lat": 72.64, | ||
"lon": 22.62 | ||
} | ||
} | ||
|
||
PUT testindex1/_doc/3 | ||
{ | ||
"point": { | ||
"lat": 75.00, | ||
"lon": 28.00 | ||
} | ||
} | ||
``` | ||
|
||
Search for all documents and filter the documents whose points lie within the rectangle defined in the query: | ||
|
||
```json | ||
GET testindex1/_search | ||
{ | ||
"query": { | ||
"bool": { | ||
"must": { | ||
"match_all": {} | ||
}, | ||
"filter": { | ||
"geo_bounding_box": { | ||
"point": { | ||
"top_left": { | ||
"lat": 75, | ||
"lon": 28 | ||
}, | ||
"bottom_right": { | ||
"lat": 73, | ||
"lon": 41 | ||
} | ||
} | ||
} | ||
} | ||
} | ||
} | ||
} | ||
``` | ||
|
||
The response contains the matching document: | ||
|
||
```json | ||
{ | ||
"took" : 20, | ||
"timed_out" : false, | ||
"_shards" : { | ||
"total" : 1, | ||
"successful" : 1, | ||
"skipped" : 0, | ||
"failed" : 0 | ||
}, | ||
"hits" : { | ||
"total" : { | ||
"value" : 1, | ||
"relation" : "eq" | ||
}, | ||
"max_score" : 1.0, | ||
"hits" : [ | ||
{ | ||
"_index" : "testindex1", | ||
"_id" : "1", | ||
"_score" : 1.0, | ||
"_source" : { | ||
"point" : { | ||
"lat" : 74.0, | ||
"lon" : 40.71 | ||
} | ||
} | ||
} | ||
] | ||
} | ||
} | ||
``` | ||
|
||
The preceding response does not include the document with a geopoint of `"lat": 75.00, "lon": 28.00` because of the geopoint's limited [precision](#precision). | ||
{: .note} | ||
|
||
## Precision | ||
|
||
Geopoint coordinates are always rounded down at index time. At query time, the upper boundaries of the bounding box are rounded down, and the lower boundaries are rounded up. Therefore, the documents with geopoints that lie on the lower and left edges of the bounding box might not be included in the results due to rounding error. On the other hand, geopoints that lie on the upper and right edges of the bounding box might be included in the results even though they are outside the boundaries. The rounding error is less than 4.20 × 10<sup>−8</sup> degrees for latitude and less than 8.39 × 10<sup>−8</sup> degrees for longitude (around 1 cm). | ||
|
||
## Specifying the bounding box | ||
|
||
You can specify the bounding box by providing any of the following combinations of its vertex coordinates: | ||
|
||
- `top_left` and `bottom_right` | ||
- `top_right` and `bottom_left` | ||
- `top`, `left`, `bottom`, and `right` | ||
|
||
The following example shows how to specify the bounding box using the `top`, `left`, `bottom`, and `right` coordinates: | ||
|
||
```json | ||
GET testindex1/_search | ||
{ | ||
"query": { | ||
"bool": { | ||
"must": { | ||
"match_all": {} | ||
}, | ||
"filter": { | ||
"geo_bounding_box": { | ||
"point": { | ||
"top": 75, | ||
"left": 28, | ||
"bottom": 73, | ||
"right": 41 | ||
} | ||
} | ||
} | ||
} | ||
} | ||
} | ||
``` | ||
|
||
## Request fields | ||
|
||
Geo-bounding box queries accept the following fields. | ||
|
||
Field | Data type | Description | ||
:--- | :--- | :--- | ||
_name | String | The name of the filter. Optional. | ||
validation_method | String | The validation method. Valid values are `IGNORE_MALFORMED` (accept geopoints with invalid coordinates), `COERCE` (try to coerce coordinates to valid values), and `STRICT` (return an error when coordinates are invalid). Default is `STRICT`. | ||
type | String | Specifies how to execute the filter. Valid values are `indexed` (index the filter) and `memory` (execute the filter in memory). Default is `memory`. | ||
ignore_unmapped | Boolean | Specifies whether to ignore an unmapped field. If set to `true`, the query does not return any documents that have an unmapped field. If set to `false`, an exception is thrown when the field is unmapped. Default is `false`. | ||
|
||
## Accepted formats | ||
|
||
You can specify coordinates of the bounding box vertices in any [format]({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/geo-point#formats) that the geopoint field type accepts. | ||
|
||
### Using a geohash to specify the bounding box | ||
|
||
If you use a geohash to specify the bounding box, the geohash is treated as a rectangle. The upper-left vertex of the bounding box corresponds to the upper-left vertex of the `top_left` geohash, and the lower-right vertex of the bounding box corresponds to the lower-right vertex of the `bottom_right` geohash. | ||
|
||
The following example shows how to use a geohash to specify the same bounding box as the previous examples: | ||
|
||
```json | ||
GET testindex1/_search | ||
{ | ||
"query": { | ||
"bool": { | ||
"must": { | ||
"match_all": {} | ||
}, | ||
"filter": { | ||
"geo_bounding_box": { | ||
"point": { | ||
"top_left": "ut7ftjkfxm34", | ||
"bottom_right": "uuvpkcprc4rc" | ||
} | ||
} | ||
} | ||
} | ||
} | ||
} | ||
``` | ||
|
||
To specify a bounding box that covers the whole area of a geohash, provide that geohash as both `top_left` and `bottom_right` parameters of the bounding box: | ||
|
||
```json | ||
GET testindex1/_search | ||
{ | ||
"query": { | ||
"bool": { | ||
"must": { | ||
"match_all": {} | ||
}, | ||
"filter": { | ||
"geo_bounding_box": { | ||
"point": { | ||
"top_left": "ut", | ||
"bottom_right": "ut" | ||
} | ||
} | ||
} | ||
} | ||
} | ||
} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -88,6 +88,7 @@ PUT testindex1/_doc/6 | |
"point": { | ||
"type": "Point", | ||
"coordinates": [74.00, 40.71] | ||
} | ||
} | ||
``` | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change "execute" to "run" or "apply" (or another appropriate verb).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think "execute" is the best verb here. Will keep it for clarity.