You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The format of the geohash filter does not match the format other filters in the REST API. The fieldnames within the filter should match the fieldnames within the mapping.
Also the it should be possible to define the geohash_cell by a point in lat/lon format. Such a point can than transformed into a geohash.
In some corner cases the geohash_cell filter fails. i.e. the southern neighbor of cell 12b.
The text was updated successfully, but these errors were encountered:
… The oject fieldnames match the fieldnames document names automatically. This invalidates the `field` field in previeous versions. The value these fields value is a `geo_point` value (all formats supported) which is internally translated to a geohash. Since those points alway have a maximum precision (level 12) a `precision` definition has been included. This precision can either be defined as *length* of the geohash-string or as *distance*. It's assumed the a distance without any unit is a geohash-length.
```
GET 'http://127.0.0.1:9200/locations/_search?pretty=true' -d '{
"query": {
"match_all":{}
},
"filter": {
"geohash_cell": {
"pin": {
"lat": 13.4080,
"lon": 52.5186
},
"precision": 3,
"neighbors": true
}
}
}'
```
Closes#3229
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
… The oject fieldnames match the fieldnames document names automatically. This invalidates the `field` field in previeous versions. The value these fields value is a `geo_point` value (all formats supported) which is internally translated to a geohash. Since those points alway have a maximum precision (level 12) a `precision` definition has been included. This precision can either be defined as *length* of the geohash-string or as *distance*. It's assumed the a distance without any unit is a geohash-length.
```
GET 'http://127.0.0.1:9200/locations/_search?pretty=true' -d '{
"query": {
"match_all":{}
},
"filter": {
"geohash_cell": {
"pin": {
"lat": 13.4080,
"lon": 52.5186
},
"precision": 3,
"neighbors": true
}
}
}'
```
Closeselastic#3229
The format of the geohash filter does not match the format other filters in the REST API. The fieldnames within the filter should match the fieldnames within the mapping.
Also the it should be possible to define the geohash_cell by a point in lat/lon format. Such a point can than transformed into a geohash.
In some corner cases the geohash_cell filter fails. i.e. the southern neighbor of cell
12b
.The text was updated successfully, but these errors were encountered: