From Geo Hashing
Jump to: navigation, search

Miscellaneous geohashing utilities that are known not to work any longer


This implementation IS FULLY 30W-compliant.
Geco screenshot.png
A re-implementation of the calculator above using leaflet/cloudmade and the JSON web service below. By using geo.crox as a data source, it is hopefully more reliable than the official map. It also shows the global hash on the map, which you may only notice when it comes into range anyway.



  • lat - latitude of the initial graticule
  • lon - longitude of the initial graticule
  • zoom - initial zoom level
  • date - initial date in YYYY-MM-DD format


Hackish Bitcoin-based Python Implementation[edit]

This implementation IS NOT 30W-compliant.

Implementation is broken, as far as I can see: The json service queried does not provide the "open" symbol queried. I believe MtGox does not have an opening at all.

MarkTraceur made this to test what Geohashing would look like using a different financial source. It's based on the opening price of Bitcoins in USD at Mt. Gox. You can change the site you use, the coordinates, or just about anything pretty easily. It will get nicer-looking as time goes on.

It is here:

Feel free to fork it and/or send feedback through GitHub!

Michi did some improvements and bug fixing on Marks original script:
  • Since bitcoincharts removed the "open" field in their data, the script uses the price at midnight for the calculation.
  • Support for the Globalhash.
  • 30W compliant.
  • Support for other markets than Mt.Gox.
  • More map services.
The code is in his fork. Unfortunately Mark does not respond to Pull Requests, so it looks like the fork won't get merged back.

Former geohash location suggester[edit]

No longer available as of 2012.

This implementation IS PARTIALLY 30W-compliant.
not compatible for dates before 2008-05-27

Geohash Recommender - This website doesn't seem to work as of 12-Jun-09

Yet another implementation in Python is here as well. It does the same as the ones above but also gives "validation" information. Lets you know if the geohash location is under water and thus if its a valid place to go party. Using this it attempts to suggest the "best" alternative geohash by checking all neighbouring grid locations. I'll add more terrain recognition if people like it. The code is over here Source Code


  • There are a few, it needs a few refreshes to get the whole tagging right. It also has trouble guessing the terrain type occasionally. Refreshing it makes it work but its a problem im looking into, have a look at the code and help if you can :)
  • Gives me a false location for May 28 and 29, 2008, which aren't yet known anywhere in the world according to the algorithm. --Tim P 21:29, 24 May 2008 (UTC)
    • But... thos dates aren't real yet. There is no dow result. Granted it should give an error instead of giving _something_ but...
      • As of 05:06, 26 May 2008 (UTC), this gives locations for May 27-30 west of 30W and for May 28-31 east of 30W, i.e., four days beyond what should be calculable as of that time. Beyond those dates, it gives a proper error message stating that no Dow is available. I think temporary data were added to the implementation for testing purposes; these should be removed. --Tim P
      • One could interpret the algorithm such that, for any date in the future, one is to use "the opening price from [DOW's] previous day of active trading is used", i.e., the most recent trading day. Obviously, this would lead to the location changing as the day approaches but, in a random spontaneous adventure generator, that seems almost mathematically pure. I mean, that's just what happens when you try to generate spontaneity too far into the future, yes?  ;) Ted 00:19, 30 May 2008 (UTC)
  • Electronicwar website seems to be no longer functioning. Jiml 00:29, 13 June 2009 (UTC)