|
Top-level
 5/ Reverse geocoding may seems simple, but there are lots of things to consider. First up, different parts of world are structured very differently, with different admin hierarchies and ways to show addresses. We format the address as expected locally. BTW - the templates we use to do it are open sourced: https://github.com/OpenCageData/address-formatting Pull requests gladly received! 5 comments
7/ One small reverse geocoding pet peeve - people often send our geocoding API ultra precise coordinates. Like nanometer level. There is no real need for more than 6 places past the decimal, see: 8/ Next issue - privacy 🕵️🕵️♂️🕵️♀️ Geocoding super precisely is technically cool, but can at times be a real privacy issue. For example a website might want to show a user's neighbourhood, not their specific home address. Here's our guide to geocoding "coarsely" https://opencagedata.com/guides/how-to-preserve-privacy-by-showing-only-an-imprecise-location 9/ But by far the hardest part about reverse geocoding is that the world changes all day, every day. There is continual new construction, demolition, address changes, changes of all kinds. #OpenStreetMap alone has 5+ MILLION edits per day (keep up the good work everyone!) 10/ If you want to play around with the ideas from this thread, we have a tutorial on writing your own reverse geocoder https://opencagedata.com/guides/how-to-preserve-privacy-by-showing-only-an-imprecise-location or of course you can just try out our API |
Gregory's Server
6/ Of course most of the world has no hierarchy as all, it's water. We handle that as well.
See our thread on geocoding the oceans: https://en.osm.town/@opencage/110207789147450417