Gregory's Server10/ Now we pass the decimal coordinates to our geocoding API and get the location 🙌
|
6 comments
 12/ Precise geocoding might not make sense. Example: a tourist taking a picture right by the Eiffel Tower 🗼 in Paris 🇫🇷, probably wants their image geocoded as "Eiffel Tower" not the exact street address. We offer this as a service to several large image processing customers. 13/ Now you know how to turn Exif data from images into useful geographic information. You can find the javascript code example and more background info over in our guide to reverse geocoding images: 14/ Thanks for reading (and sharing), we hope you enjoyed this #geoeducation thread. We have many more threads about the #geoweirdness of specific countries, border disputes, geocoding, etc on our blog. Some still on twitter, but week by week we are moving them to mastodon (and writing new threads)  @opencage assuming you have that info in EXIF data, can you identify that the camera was pointing towards the Eiffel tower rather than away from it? Just to make sure that this is really what's in the frame. Focusing distance might be useful too. @brunogirin Yes, can be done, but a simpler solution is just provide the user with both responses (precise address and nearby POI) and let them then choose which one is appropriate for the situation |
11/ 🚨 WAIT!!! 🚨
The precision of the Exif coordinates depends on the tech (GPS, cell, etc) used to capture the location. So they may not be perfectly precise.
But also showing a precise location might not be appropriate or have privacy implications.
See our guide on how to show less precise location like just the city or neighbourhood:
https://opencagedata.com/guides/how-to-preserve-privacy-by-showing-only-an-imprecise-location
#geoeducation