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
We've run into a bug where queries on coordinates with longitude greater than -13.5 degree all appear to be using the same (wrong) geohash to query.
We discovered that when we create an item using the putPoint method and then try and query that same point using either queryRectangle or queryRadius, it was consistently failing to find the item for the coordinates for our dataset of locations within the UK. Testing on coordinates in North America everything seems to work fine.
We investigated the issue by spying on the values sent to dynamo and discovered that the geohash generated for the query gets stuck at 9223372036854775807 when the longitude value was above -13.5 (we kept latitude at 40).
Hello,
We've run into a bug where queries on coordinates with longitude greater than -13.5 degree all appear to be using the same (wrong) geohash to query.
We discovered that when we create an item using the putPoint method and then try and query that same point using either queryRectangle or queryRadius, it was consistently failing to find the item for the coordinates for our dataset of locations within the UK. Testing on coordinates in North America everything seems to work fine.
We investigated the issue by spying on the values sent to dynamo and discovered that the geohash generated for the query gets stuck at 9223372036854775807 when the longitude value was above -13.5 (we kept latitude at 40).
I was able to chart out this divergence of the query and the put request:
Source: https://jsfiddle.net/ndefmp49/
This trend continues well into the positives
The text was updated successfully, but these errors were encountered: