Credit Is Due

The OpenCage Geocoder is built from great open source products and uses equally great open data to make it all work. This is what's under the API. Most of the products and data we use have a follow up link to each product's additional data sources. It's a worthwhile exercise to click through to see just how much open geo-data there is in the world.

nominatim

Nominatim and OpenStreetMap

Data OpenStreetMap and contributors under ODbL. GPL v2.

We're proud to support OpenStreetMap by being corporate members of the OpenStreetMap Foundation.

DataScienceToolkit

DataScienceToolkit

Data contributors and licenses are on the about page. Source code dual licensed under the MIT and GPL licenses.

geonames

GeoNames

Data under CC-BY. Data sources page.

Twofishes

Twofishes

Data under CC-BY. Apache 2.0. Twofishes home page.

what3words

what3words

The what3words Server Software converts searches that are compatible with what3words into geographic co-ordinates, and converts geographic co-ordinates into what3words.

Yahoo GeoPlanet

Yahoo GeoPlanet

Data under CC-BY.

Postcodes.io

Postcodes.io

Data under OS OpenData licence. Data sources page.

Under The API

What makes the OpenCage geocoder run? We're glad you asked ...

The OpenCage geocoder is an aggregating API. For every query you shoot at the API, it makes calls to each of the back-end geocoders we have installed.

The bulk of the geocoder code is written in Perl, apart from the back-end geocoders which are written in a whole plethora of languages.

Please take a peak at the various software projects we've opensourced .

The API is served by Apache and the whole lot runs on top of servers running ubuntu, a version of Linux.

Twitter icon made by Anton Saputro, CC 3.0 BY