Skip to content
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

GeoHashing #2

Open
vdisawar opened this issue Jun 27, 2013 · 2 comments
Open

GeoHashing #2

vdisawar opened this issue Jun 27, 2013 · 2 comments

Comments

@vdisawar
Copy link

Hi,

I had a question with the geohasher class in this project. I mainly wanted to ask what is beneficial with converting LatLng coordinates to a geohash and how accurate is it?

thanks

I know this isn't an issue but I didn't know where to post the questions.

@turbomanage
Copy link
Collaborator

I believe the accuracy is a few meters for the full base 32 geohash.
However, using a geohash to query proximity is tricky since you may be near
a hash boundary. For that reason, it is actually not used in the current
project. We decided to query the most recent position updates from anywhere
in the world instead. It was used in an earlier version.

The geohash algorithm we used is this one:
http://en.wikipedia.org/wiki/Geohash

HTH,
/dmc

On Thu, Jun 27, 2013 at 2:18 PM, vdisawar notifications@github.com wrote:

Hi,

I had a question with the geohasher class in this project. I mainly wanted
to ask what is beneficial with converting LatLng coordinates to a geohash
and how accurate is it?

thanks


Reply to this email directly or view it on GitHubhttps://github.com//issues/2
.

@vdisawar
Copy link
Author

So in order to query locations on app engine, is it possible to just use lat, lng values instead of geohashing and are there any downsides to that approach, if any?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants