- Full API docs.
- We recommend you also follow @OpenCageData on twitter and/or read our blog where all changes are announced.
Changes to OpenCage Geocoder API.
new version of the what3words library for our annotation means that we now support Afrikaans, Czech, Danish, Dutch, Greek, Japanese, Korean, Norwegian, Thai, Xhosa, and Zulu.
we have significantly improved the granularity and coverage of our timezone annotation.
previously results in
geojsonformat had not returned some of the fields (examples include
timestamp, and more) that other response formats had. This is now corrected, sorry for the oversight.
non-GET HTTP requests to the API now return
405 - Method not allowederror.
FIPSannotation for locations in the United States. See docs.
New optional parameter
proximityfor biasing results is now supported. See docs.
From 1 August 2018 non-GET HTTP requests will be treated as errors. Please see our blog post for full details.
our website moved to https://opencagedata.com.
added the Australian G-NAF dataset as one of the backend geocoders we query.
if a result is a road (ie
_typekey in the
componentsportion of the result has the value "road") if possible we now also return a
road_typewith values like those generally used in OpenStreetMap.
added the Addok geocoder as one of the backend geocoders we query.
new page to clarify GDPR/data protection
flagannotation. See the full list of annotations.
In many parts of the world roads may have names but also numbers or some sort of unique identifier code. In cases where the result for a reverse geocoding query is such a road, the
componentsportion of the response now also contains a
road_referencekey and value. In Europe some major highways may also have a national and European reference (for example "A 6" and "E 15"). In such cases we also set the
road_reference_intlkey and value.
componentsportion of the result now contains the key
ISO_3166-1_alpha-2with the corresponding code for that location if we are able to determine it. This is in addition to the two-letter
country_codewhich is also returned. This is mainly useful for places like Puerto Rico or Guadeloupe where the two codes differ.
We have launched a new account dashboard, removing the 3rd party dashboard from 3scale we had peviously used. Passwords in the old (and new) systems were encrypted, thus making it impossible for us to transfer them to the new system, so the first time you log into the new system you will have to create a new password. Sorry for the inconvenience.
new version of the what3words library for our annotation means that we now support Arabic, Finnish, Italian, Mongolian, Polish, and Swedish
some tweaks to how we calculate confidence score for some of the backend geocoders, will generally result in slightly lower confidence
requests to geocode invalid coordinates now return a response with status code 400 Blog post.
qiblaannotation. Blog post.
currencyannotation. Blog post.
map view upgraded to leaflet 1.0.1
The optional parameter
countrycodecan be a comma seperated list of 2-letter country codes See full list of optional parameters.
Previously if a road name in the components field had been a digit it had been returned as a number not a string. This was unintentional and is now fixed. The road name is always returned as a string.
new optional request parameter
no_record. See full list of optional parameters.
google-v3-jsonformat to convert our types to google types
_typekey to the
componentslist so that the type of object we geocoded to can more easily be determined. See docs.