Nominatim

Nominatim
Ken Vermette based on https://commons.wikimedia.org/wiki/File:OpenStreetMap-Logo · CC BY-SA 3.0 · source
Name	Nominatim
Developer	OpenStreetMap Foundation
Initial release	2009
Programming language	PHP, PostgreSQL, PostGIS
Operating system	Unix-like
License	ODbL

Nominatim Nominatim is a geocoding and reverse-geocoding engine used to convert between textual addresses and geographic coordinates, powering mapping applications and spatial search across platforms. It is commonly deployed alongside mapping stacks to provide address lookup for projects, organizations, and services that require place resolution and geospatial indexing. Nominatim is often integrated with tools and infrastructures in the geospatial ecosystem to support routing, visualization, and location-based features.

Overview

Nominatim operates as a search service built on top of spatial databases and is frequently paired with map rendering systems such as OpenStreetMap, MapQuest, Mapbox, CartoDB, and Leaflet. It ingests structured and unstructured place data from projects like GeoNames, Geonames.org, and national mapping agencies including Ordnance Survey, Institut national de l'information géographique et forestière, and US Geological Survey. Deployments often interact with routing engines such as OSRM, GraphHopper, and Valhalla and with tile servers like TileStache and Mapnik. Nominatim supports integrations with web frameworks and APIs used by organizations like Wikipedia, Wikidata, Flickr, Strava, and Uber Technologies.

History

Nominatim was developed in the context of the expanding OpenStreetMap project and emerged as a dedicated search component to interpret OSM data. Early development involved contributors associated with communities including OpenStreetMap Foundation, HOT (Humanitarian OpenStreetMap Team), and mapping companies such as CloudMade and MapQuest. Over time, maintenance and feature work involved developers and institutions like Geocoding API contributors, Paul Norman, and volunteers linked to regional chapters like OpenStreetMap US, OpenStreetMap UK, and OpenStreetMap Germany. Nominatim's evolution paralleled improvements in database technologies, with migrations to PostgreSQL and PostGIS mirroring trends at organizations including Esri, QGIS, and academic groups at University of California, Berkeley and Massachusetts Institute of Technology.

Features and Functionality

Nominatim provides forward geocoding, reverse geocoding, structured search, and batch lookup capabilities used by projects such as Mapillary, OpenAddresses, Nextcloud, Mozillians, and GitLab. Its functionality supports address interpolation methods comparable to techniques employed by HERE Technologies and TomTom, and offers administrative boundary resolution akin to datasets from GADM and Natural Earth. Nominatim exposes APIs compatible with client libraries in ecosystems like Python, Ruby, Node.js, and Java, and is used by platforms such as Facebook, Twitter, and LinkedIn for location enrichment workflows. Features include geospatial ranking, fuzzy matching, multilingual name handling similar to Wikimedia projects, and POI extraction comparable to Foursquare and Yelp.

Data Sources and Coverage

Nominatim primarily indexes data from OpenStreetMap contributors worldwide but is often augmented with authoritative datasets from national agencies like Institut Géographique National, Land Information New Zealand, and Swisstopo. Third-party gazetteers such as GeoNames, GNIS (US Geological Survey), and regional sources like Nominative datasets in France are sometimes integrated in custom deployments. Coverage varies by region, with dense urban mapping in cities such as New York City, London, Tokyo, Paris, and Berlin and sparser data in remote areas documented by projects like Missing Maps and initiatives led by Humanitarian OpenStreetMap Team. Nominatim’s address parsing handles international formats from countries represented in standards and registries like ISO 3166 and administrative taxonomies used by Eurostat.

Usage and Integration

Deployers embed Nominatim in web services, mobile apps, and enterprise systems used by groups such as Mozilla Foundation, OpenLayers, Esri, GDAL, and QGIS plugins. Integration patterns include RESTful API calls consumed by clients built with React, AngularJS, and Vue.js as well as server-side consumption in stacks based on Django, Ruby on Rails, Flask, and Spring Framework. Nominatim is incorporated into data pipelines alongside ETL tools like Apache NiFi, FME, and Pentaho, and used for geocoding in analytics platforms such as Tableau, Power BI, and Jupyter Notebook environments at research centers like Scripps Institution of Oceanography and Max Planck Institute.

Performance and Scaling

Performance tuning for Nominatim typically involves database optimization strategies used in large-scale deployments by companies such as Amazon Web Services, Google Cloud Platform, Microsoft Azure, and hosting providers like DigitalOcean. Scaling techniques include replication, sharding, and load balancing approaches inspired by architectures from Cassandra, PostgreSQL clustering, and cache layers using Redis and Varnish. High-demand services mirror practices from platforms like OpenStreetMap.org and Wikimedia Foundation to manage query throughput, and benchmarking often references tools and projects such as JMeter, Locust (software), and Prometheus for monitoring. Large-scale indexing projects draw lessons from efforts by Mapillary and corporate mapping teams at Apple Inc. and HERE Technologies.

Licensing and Privacy

Nominatim’s data model and deployments must account for licensing regimes including the Open Database License used by OpenStreetMap and compatibility considerations with datasets under Creative Commons and national proprietary licenses from institutions such as Ordnance Survey and IGN. Privacy guidance aligns with regulations and frameworks like General Data Protection Regulation and practices promoted by civil society groups such as Electronic Frontier Foundation and Privacy International. Operational policies often follow norms from community organizations including OpenStreetMap Foundation and project governance examples from Wikimedia Foundation to manage acceptable use, rate limiting, and data retention.

Category:Geocoding