Gregory's Server8/ Many of our users are academics, doing geocoding for research and with the need to cross reference with other datasets.
We include US FIPS codes (if in the US), NUTS codes (in the EU) and UN M49 codes to easily do the matching.
|
5 comments
 10/ Similarly, last year we added UN/LOCODEs as an annotation. These are a system of codes developed and maintained by the πΊπ³ United Nations and commonly used in logistics. 11/ Annotations are added to our API results by default, but if you don't need them you can turn them off by setting "no_annotations=1" to your API request. Here's the full list of optional API parameters: https://opencagedata.com/api#optional-params 12/ Admittedly some of the annotations are a bit niche. Are you into ham radio π»? Well, we provide the Maidenhead location reference commonly used by amateur radio operators. 13/ Thanks for reading and sharing π. If you're a user of our geocoding API please let us know ideas for annotations (or anything else) that would make your life easier. We have links to many more geothreads about our service, border disputes, exclaves, #geoweirdness of individual territories, etc listed on our blog: https://blog.opencagedata.com/geothreads |
9/ Another common category of customer is vehicle tracking πππ», so we return"roadinfo", things like what type of road has been matched, speed limits, etc
https://opencagedata.com/api#roadinfoann