Gregory's Server7/ 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:
|
3 comments
 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 |
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
#geoeducation