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
Geohashes provide a structure for geospatial subdivisions by defining a hierarchical grid. This data structure supports an efficient way to filter data in a hierarchical way which should be supported by the REST API to filter points of certain cell.
Such a filter just needs a geohash that defines a cell within the grid and will be used as prefix. In result of filtering data with a geohash filter all geopoints sharing the same prefix as the defined cell must be returned. Also such a filter should allow filtering adjacent cells of the defined cell. For example the cell defined by the geohash u30 has eight adjacent cells u1r, u32, u33, u1p, u31, u0z, u2b and u2c. So this kind of filter can be used for a more efficient filtering-process than the simple bounding box filter does.
Example
The most simple setup for such a filter uses two arguments:
Since each geopoint corresponds to a single geohash it must be possible to index all prefixes of this geohash. For example the geohash u30 also corresponds to the terms u3 and u. The upper bound of the geohash length is defined by the precision defined in the mapping.
Geohashes provide a structure for geospatial subdivisions by defining a hierarchical grid. This data structure supports an efficient way to filter data in a hierarchical way which should be supported by the REST API to filter points of certain cell.
Such a filter just needs a geohash that defines a cell within the grid and will be used as prefix. In result of filtering data with a geohash filter all geopoints sharing the same prefix as the defined cell must be returned. Also such a filter should allow filtering adjacent cells of the defined cell. For example the cell defined by the geohash
u30
has eight adjacent cellsu1r
,u32
,u33
,u1p
,u31
,u0z
,u2b
andu2c
. So this kind of filter can be used for a more efficient filtering-process than the simple bounding box filter does.Example
The most simple setup for such a filter uses two arguments:
Since each geopoint corresponds to a single geohash it must be possible to index all prefixes of this geohash. For example the geohash
u30
also corresponds to the termsu3
andu
. The upper bound of the geohash length is defined by the precision defined in the mapping.The text was updated successfully, but these errors were encountered: