geo-shape-query.asciidoc 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. [[query-dsl-geo-shape-query]]
  2. === GeoShape Query
  3. Filter documents indexed using the `geo_shape` type.
  4. Requires the <<geo-shape,`geo_shape` Mapping>>.
  5. The `geo_shape` query uses the same grid square representation as the
  6. geo_shape mapping to find documents that have a shape that intersects
  7. with the query shape. It will also use the same PrefixTree configuration
  8. as defined for the field mapping.
  9. The query supports two ways of defining the query shape, either by
  10. providing a whole shape definition, or by referencing the name of a shape
  11. pre-indexed in another index. Both formats are defined below with
  12. examples.
  13. ==== Inline Shape Definition
  14. Similar to the `geo_shape` type, the `geo_shape` Filter uses
  15. http://www.geojson.org[GeoJSON] to represent shapes.
  16. Given a document that looks like this:
  17. [source,js]
  18. --------------------------------------------------
  19. {
  20. "name": "Wind & Wetter, Berlin, Germany",
  21. "location": {
  22. "type": "Point",
  23. "coordinates": [13.400544, 52.530286]
  24. }
  25. }
  26. --------------------------------------------------
  27. The following query will find the point using the Elasticsearch's
  28. `envelope` GeoJSON extension:
  29. [source,js]
  30. --------------------------------------------------
  31. {
  32. "query":{
  33. "filtered": {
  34. "query": {
  35. "match_all": {}
  36. },
  37. "filter": {
  38. "geo_shape": {
  39. "location": {
  40. "shape": {
  41. "type": "envelope",
  42. "coordinates" : [[13.0, 53.0], [14.0, 52.0]]
  43. }
  44. }
  45. }
  46. }
  47. }
  48. }
  49. }
  50. --------------------------------------------------
  51. ==== Pre-Indexed Shape
  52. The Filter also supports using a shape which has already been indexed in
  53. another index and/or index type. This is particularly useful for when
  54. you have a pre-defined list of shapes which are useful to your
  55. application and you want to reference this using a logical name (for
  56. example 'New Zealand') rather than having to provide their coordinates
  57. each time. In this situation it is only necessary to provide:
  58. * `id` - The ID of the document that containing the pre-indexed shape.
  59. * `index` - Name of the index where the pre-indexed shape is. Defaults
  60. to 'shapes'.
  61. * `type` - Index type where the pre-indexed shape is.
  62. * `path` - The field specified as path containing the pre-indexed shape.
  63. Defaults to 'shape'.
  64. The following is an example of using the Filter with a pre-indexed
  65. shape:
  66. [source,js]
  67. --------------------------------------------------
  68. {
  69. "filtered": {
  70. "query": {
  71. "match_all": {}
  72. },
  73. "filter": {
  74. "geo_shape": {
  75. "location": {
  76. "indexed_shape": {
  77. "id": "DEU",
  78. "type": "countries",
  79. "index": "shapes",
  80. "path": "location"
  81. }
  82. }
  83. }
  84. }
  85. }
  86. }
  87. --------------------------------------------------