News for hackers. Stuff that matters.
Re:Show HN: An API to encode and decode coordinates using Ge... by raimille1 on Friday October 11, 2019 @01:09PM (#21226307)
When I see services like this or W3W, I cannot understand what is the goal? What's wrong with coordinates themselves?
Re:Show HN: An API to encode and decode coordinates using Ge... by hobofan on Friday October 11, 2019 @03:21PM (#21227537)
Geohashes are incredibly useful when building geospatial software (at least at the UI layer or close to it). With them, bucketing multiple data points that are in close proximity to each other is a breeze, and you then do zooming, panning, etc. with those buckets.

W3W (or the better alternative of Plus Codes) is then essentially just a layer of human readable names to have a digestible encoding of geohashes.

Re:Show HN: An API to encode and decode coordinates using Ge... by tpaschalis on Friday October 11, 2019 @05:27PM (#21228643)
Also, if you are set on using a geocode system, geohashes and plus codes are open-source, public-domain algorithms, unlike w3w, to avoid issues like [1] which was being discussed on HN yesterday.

[1] https://justpaste.it/39hat

Re:Show HN: An API to encode and decode coordinates using Ge... by shhsshs on Friday October 11, 2019 @01:17PM (#21226395)
The point of a geohash is that it’s super short.
Re:Show HN: An API to encode and decode coordinates using Ge... by alexchamberlain on Friday October 11, 2019 @02:10PM (#21226884)
So are the coordinates, right? I thought the point was that they were easier to remember and communicate?
Re:Show HN: An API to encode and decode coordinates using Ge... by shhsshs on Saturday October 12, 2019 @07:45PM (#21237159)
A geohash is 6ish characters and coordinates are usually 10-15 digits. They are both pretty short either way, but a people can remember/communicate 6 characters way easier than 10-15.