-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Geo: incorrect neighbours computation in GeoHashUtils #8526
Labels
Comments
clintongormley
added
>bug
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
labels
Nov 18, 2014
clement-tourriere
pushed a commit
to clement-tourriere/elasticsearch
that referenced
this issue
Nov 18, 2014
We don't have to set XLimit and YLimit depending on the level (even or odd), since semantics of x and y are already swapped on each level. XLimit is always 7 and YLimit is always 3. Close elastic#8526
nknize
pushed a commit
that referenced
this issue
Nov 25, 2014
We don't have to set XLimit and YLimit depending on the level (even or odd), since semantics of x and y are already swapped on each level. XLimit is always 7 and YLimit is always 3. Close #8526
nknize
pushed a commit
that referenced
this issue
Nov 25, 2014
We don't have to set XLimit and YLimit depending on the level (even or odd), since semantics of x and y are already swapped on each level. XLimit is always 7 and YLimit is always 3. Close #8526
nknize
pushed a commit
that referenced
this issue
Nov 25, 2014
We don't have to set XLimit and YLimit depending on the level (even or odd), since semantics of x and y are already swapped on each level. XLimit is always 7 and YLimit is always 3. Close #8526
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
We don't have to set XLimit and YLimit depending on the level (even or odd), since semantics of x and y are already swapped on each level. XLimit is always 7 and YLimit is always 3. Close elastic#8526
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
We don't have to set XLimit and YLimit depending on the level (even or odd), since semantics of x and y are already swapped on each level. XLimit is always 7 and YLimit is always 3. Close elastic#8526
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GeoHashUtils.neighbor produces bad neighbours for even level geohash (when geohash length is even).
For instance :
For geohash
u09tv
:http://geohash.gofreerange.com/ (this geohash is in Paris, France).
Real neighbours for this geohash are
[u09wh, u09wj, u09wn, u09tu, u09ty, u09ts, u09tt, u09tw]
GeoHashUtils.neigbors returns
[u09qh, u09wj, u09yn, u09mu, u09vy, u09ks, u09st, u09uw]
The text was updated successfully, but these errors were encountered: