OpenSearch/docs/reference/query-dsl/geo-shape-query.asciidoc

182 lines
5.2 KiB
Plaintext
Raw Normal View History

[[query-dsl-geo-shape-query]]
=== Geo-shape query
++++
<titleabbrev>Geo-shape</titleabbrev>
++++
Filter documents indexed using the `geo_shape` or `geo_point` type.
Requires the <<geo-shape,`geo_shape` Mapping>> or the <<geo-point,`geo_point` Mapping>>.
The `geo_shape` query uses the same grid square representation as the
`geo_shape` mapping to find documents that have a shape that intersects
[Geo] Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach (#36751) * [Geo] Expose BKDBackedGeoShapes as new VECTOR strategy This commit exposes lucene's LatLonShape field as a new strategy in GeoShapeFieldMapper. To use the new indexing approach, strategy should be set to "vector" in the geo_shape field mapper. If the tree parameter is set the mapper will throw an IAE. Note the following: When using vector strategy: * geo_shape query does not support querying by POINT, MULTIPOINT, or GEOMETRYCOLLECTION. * LINESTRING and MULTILINESTRING queries do not support WITHIN relation. * CONTAINS relation is not supported. * The tree, precision, tree_levels, distance_error_pct, and points_only parameters will not throw an exception but they have no effect and will be marked as deprecated.. All other features are supported. * revert change to PercolatorFieldMapper * fix ExistsQuery for geo_shape vector strategy * add deprecation logging for tree, precision, tree_levels, distance_error_pct, and points_only * initial update to geoshape docs, including mapping migration updates * initial support for GeoCollection queries * fix docs and javadoc errors * clean up geocollection queries * set deprecated mapping tests to NOTCONSOLE * fix geo-shape mapper asciidoc mapping and test warnings * add support for point queries using LatLonShapeBoundingBoxQuery * update GeoShapeQueryBuilderTests to include POINT queries for VECTOR strategy. Other comment cleanups * add lucene geometry build testing to ShapeBuilder tests * remove deprecated prefix tree mapping from geo-shape.asciidoc * refactor GeoShapeFieldMapper into LegacyGeoShapeFieldMapper and GeoShapeFieldMapper Both classes derive from BaseGeoShapeFieldMapper that provides shared parameters: coerce, ignoreMalformed, ignore_z_value, orientation. * update docs to remove vector strategy * fix GeometryCollectionBuilder#buildLucene to return the object created by the shape builder * fix LineLength failure in GeoJsonShapeParserTests * ShapeMapper refactor changes from PR feedback * fix typo in geo-shape.asciidoc * ignore circle test in docs * update indexing-approach ref to geoshape-indexing-approach * add warnings check for LegacyGeoShapeFieldMapper to AbstractBuilderTestCase * fix deprecatedParameters setup * update indexing approach * fixing unexpected warnings failures * move orientation back to field type * remove if in LegacyGeoShapeFieldMapper#doXContent. Fix GeoShapeFieldMapper to work with double array as a point * fix indexing-approach link in circle section of geoshape docs * add strategy to deprecation warnings check * fix test failures * fix typo in QueryStringQueryBuilderTests * fix total hits to totalHits().value * fix version number * add version check to BaseGeoShapeFieldMapper * fix line length! * revert version check in BaseGeoShapeFieldMapper * Fix serialization of mappings of legacy shapes.
2018-12-18 10:54:56 -05:00
with the query shape. It will also use the same Prefix Tree configuration
as defined for the field mapping.
The query supports two ways of defining the query shape, either by
providing a whole shape definition, or by referencing the name of a shape
pre-indexed in another index. Both formats are defined below with
examples.
==== Inline Shape Definition
Similar to the `geo_shape` type, the `geo_shape` query uses
http://www.geojson.org[GeoJSON] to represent shapes.
Given the following index:
[source,console]
--------------------------------------------------
PUT /example
{
"mappings": {
"properties": {
"location": {
"type": "geo_shape"
}
}
}
}
POST /example/_doc?refresh
{
"name": "Wind & Wetter, Berlin, Germany",
"location": {
"type": "point",
"coordinates": [13.400544, 52.530286]
}
}
--------------------------------------------------
// TESTSETUP
The following query will find the point using the Elasticsearch's
`envelope` GeoJSON extension:
[source,console]
--------------------------------------------------
GET /example/_search
{
"query":{
"bool": {
"must": {
"match_all": {}
},
"filter": {
"geo_shape": {
"location": {
"shape": {
"type": "envelope",
"coordinates" : [[13.0, 53.0], [14.0, 52.0]]
},
"relation": "within"
}
}
}
}
}
}
--------------------------------------------------
==== Pre-Indexed Shape
The Query also supports using a shape which has already been indexed in
another index. This is particularly useful for when
you have a pre-defined list of shapes which are useful to your
application and you want to reference this using a logical name (for
example 'New Zealand') rather than having to provide their coordinates
each time. In this situation it is only necessary to provide:
* `id` - The ID of the document that containing the pre-indexed shape.
* `index` - Name of the index where the pre-indexed shape is. Defaults
to 'shapes'.
* `path` - The field specified as path containing the pre-indexed shape.
Defaults to 'shape'.
* `routing` - The routing of the shape document if required.
The following is an example of using the Filter with a pre-indexed
shape:
[source,console]
--------------------------------------------------
PUT /shapes
{
"mappings": {
"properties": {
"location": {
"type": "geo_shape"
}
}
}
}
PUT /shapes/_doc/deu
{
"location": {
"type": "envelope",
"coordinates" : [[13.0, 53.0], [14.0, 52.0]]
}
}
GET /example/_search
{
"query": {
"bool": {
"filter": {
"geo_shape": {
"location": {
"indexed_shape": {
"index": "shapes",
"id": "deu",
"path": "location"
}
}
}
}
}
}
}
--------------------------------------------------
==== Spatial Relations
The <<spatial-strategy, geo_shape strategy>> mapping parameter determines
which spatial relation operators may be used at search time.
The following is a complete list of spatial relation operators available when searching a field of type `geo_shape`:
* `INTERSECTS` - (default) Return all documents whose `geo_shape` field
intersects the query geometry.
* `DISJOINT` - Return all documents whose `geo_shape` field
has nothing in common with the query geometry.
* `WITHIN` - Return all documents whose `geo_shape` field
is within the query geometry.
* `CONTAINS` - Return all documents whose `geo_shape` field
contains the query geometry.
When searching a field of type `geo_point` there is a single supported spatial relation operator:
* `INTERSECTS` - (default) Return all documents whose `geo_point` field
intersects the query geometry.
[float]
==== Ignore Unmapped
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.
==== Shape Types supported for Geo-Point
When searching a field of type `geo_point` the following shape types are not supported:
* `POINT`
* `LINE`
* `MULTIPOINT`
* `MULTILINE`
==== Notes
Geo-shape queries on geo-shapes implemented with <<prefix-trees, `PrefixTrees`>> will not be executed if
<<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>> is set to false.