Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The stack I describe in the post is only for map tiles - Map tiles are a good fit for CDNs because the input space is small (just Z/X/Y coordinates on a square grid) and thus very cacheable.

Geocoding is a very different problem because the input space - human language - is much, much larger, and answering queries quickly to support features like autocomplete really requires a server with hot data in memory.

One of my favorite projects in this space is Pelias https://pelias.io which is an open source auto-completing geocoder based on OSM plus other open data. It's backed by a great team that also runs a business: Geocode Earth https://geocode.earth



(Co-maintainer of Pelias and co-founder Geocode Earth here)

Thanks Brandon for yet another one of your shout outs.

I'd just like to underline one thing you said, Pelias/Geocode Earth are based on OSM _plus other data_: that last part is pulling a lot of weight.

OSM data is great, in fact the POI data in OSM is best-in-class in many parts of the world. But OSM in general doesn't have great address coverage. It's very difficult to manually map low density rural or suburban areas, as is the preferred method with OSM. Bulk address imports are possible, but rare. However there are a huge number of local governments that publish up to date, relatively complete and accurate address lists, and we heavily lean on those for good address coverage.

So to anyone looking for a geocoder who has been put off from Pelias or Geocode Earth because you saw it uses OSM, give it a try anyway. OSM data is a crucial piece of the puzzle, but not the only one.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: