Email or username:

Password:

Forgot your password?
OpenCage's posts Post Back to profile
Top-level
OpenCage 👉🌍

8/ The address-formatting templates themselves can be used in any programming language, and there are now 11 different parsers. 🥳

Yeah, open source!

List of programming languages with address-formatting parsers
8 March at 13:13 | Open on en.osm.town
3 comments
OpenCage 👉🌍

9/ Most importantly we have hundreds of tests. We're always adding more, and welcome your suggestions. There is no shortage of global addressing edge cases.

You can see address-formatting in action in the "formatted" string in our geocoding API results.

Screenshot of JSON response from the OpenCage geocoding API for the coordinates 52.3877830, 9.7334394
8 March at 13:15 | Open on en.osm.town
OpenCage 👉🌍

10/ We hope you enjoyed this week's #geoeducation thread, a small peek behind the curtain 🪟 at life at a geocoding service.

We have links to many more geothreads about border disputes, exclaves, #geoweirdness of individual countries, reverse geocoding, etc listed on our blog:

blog.opencagedata.com/geothrea

Screenshot of the OpenCage blog page about geothreads
8 March at 13:18 | Open on en.osm.town
OpenCage 👉🌍

11/ Bonus address formatting toot - there have been MANY different schemes to replace or supplement addresses using various codes or word combinations: What3Words, geohashes, H3 codes, MGRS codes, UN/LOCODES, etc. Each with pros and cons.

We return many of these different codes as "annotations" to our geocoding results, see: opencagedata.com/api#annotatio

Screenshot of the OpenCage geocoding API documentation explaining the "MGRS" annotation
8 March at 13:22 | Open on en.osm.town
Go Up