Geo coding took longer as the meta information about city districts etc. which needs to be mapped is different, but changing maps was easy. That said Open Cage was nice as their data was cleaner and we didn't have to manually change data as we had to do with Google.
OpenCage (https://opencagedata.com/) founder here if anybody has questions. Putting country hierarchies in a set of keys is a challenge for all geocoders and the output differs slightly (though we have a google-compat mode). Sometimes it's just road vs street or town vs city. England has parishes, Paris has arrondissements (equivalent to a city within a city), Berlin is a city, county and state (same outer boundaries) for example.
>Just pass the coordinates as a latitude and a longitude, separated by either a comma or a (URL encoded) space and the API will automagically work out that you want to reverse geocode.
Is the reverse geocoding based on
1. government-source boundary data, or
2. proximity to tagged points from OSM or other non-authoritative sources?
Both where government provides open boundary data, though in most cases that would've been imported into OpenStreetMap already https://opencagedata.com/credits
