java code for geohashes
An implementation of Geohashes in pure Java. The produced hashes, when using character precision (multiples of 5 bits) are compatible to the reference implementation geohash.org.
You can however also encode Geohashes down to the full available precision of a long i.e. 64 bits.
Getting the library
As of today, new releases are made available via maven Central. Thus you can use the artifacts in various build systems like maven, ivy, gradle, sbt and mayn more.
Find the current versions here:
Building/Testing the code
The geohash-java code can be built using Apache Maven.
Maven targets are the usual suspects.
- clean - compile - test - package # pack a versioned jar containing the compiled class files
This branch ditches 1.6 compatibility. If you need that look at the release-1.0 branch and artifacts in maven central. I will backport important bugfixes to the release-1.0 branch.
Current development involves getting the following things to run:
- a method to find the n closest hashes to any given point.
- refactor tests, might want to add a dependency on hamcrest and provide some custom matchers for fun and profit.
Last important changes
This version switches the license over to Apache Software License 2.0
Important fix 398d048b66e8cff1e5df8aa1a4bdc4c37ca70070 ord() would return negative longs, which is plain wrong.
Thanks to Graham Dennis and aborochoff for pointing it out.
Also: Raise source level to 1.7.
Merge this fix https://github.com/0mok/geohash-java/commit/12550a392ea974cf75c81fce2bd21fe1535715a1 It causes compareTo() of geohashes to behave similarly as comaring their base32 encoded strings
toBase32() now throws an exception if the hash precision is not a multiple of 5.
- Added a static method to obtain a geohash string in one call. Thanks to Andy Chosak.
Finally realeased to maven central.
- Added method getCharacterPrecision() to GeoHash class
- Changed the code in VincentyGeodesy not to stumble over the fact that NaN == NaN will always return false
- Added a small fix that keeps VincentyGeodesy#moveInDirection() from returning wrong values when moving large distances. [submitted by André Kischkel]
- Added next(), next(step) and prev() methods to Geohash.
- Added fromBase32() and toBase32() to TwoGeoHashBoundingBox.
- Cleaned up the entire source tree using clearly defined settings.
- Added/fixed the methods toBinaryString() and Geohash.fromBinaryString() that can encode and decode a geohash into a simple String of 0s and 1s.
- Also added test code for those methods.
- Classes containing data are now Serializable.
- Merged Kevins [ktcorby] code that yields all the geohashes in a bounding box, at a given resolution.
- Merged Chris' [cchandler] code to encode and decode geohashes from a binary string.
Fixed issue #2 from Github:
- Neighbouring hashes can be calculated by using the getAdjacent() method, which yields a hashes 8 neighbors.
- northern, eastern, western and southern neighbours can be determined using the respective methods.
Fixed issue #1 from Github:
- A bug caused different hashes to be yielded sometimes.
This code has been placed under the Apache License 2.0. See the LICENSE file for more information. Please contribute improvements and bug fixes back via github.