Geo & Visual Verification

Nominatim / OpenStreetMap Geocoding

Nominatim (OpenStreetMap) provides geocoding and reverse geocoding, but the public API has strict usage limits. This page summarises the official Nominatim usage policy, explains constraints for bulk geocoding, and outlines self-hosting and commercial alternatives recommended for product or high-volume use.

Official source

slug: nominatim-openstreetmap
priority: 74
reviewed: Apr 24, 2026

Next wavePhase 2Medium riskSensitiveAPIapproved

01overview

How this source is shaped

Useful for location normalization and map context, but the public endpoint has clear usage limits. For product use, self-hosting or a commercial geocoding provider may be better.

Source type: Geospatial
Access model: Free
Pricing model: Free Public Service With Strict Usage Policy; Self-Hosting Possible
API available: Yes
Requires account: No
Risk level: Medium
Sensitivity: Sensitive
Integration phase: Phase 2
Integration priority: 74

02scoring

Review dimensions

Each dimension is graded on a 0–10 scale. The overall score is a weighted aggregate.

overall score

7.54/10

Weighted aggregate across the eight review dimensions.

Authorityreputation and provenance of the source

8.00/10

Data qualityaccuracy, coverage, completeness

7.70/10

Usabilityhow quickly an analyst can extract value

7.20/10

APIshape, stability and cost of programmatic access

7.40/10

Documentationhow well the source is explained and referenced

7.80/10

Freshnesshow up-to-date the data stream is

7.60/10

Ethical fitalignment with our ethical OSINT posture

7.20/10

Commercial valueproduct leverage and monetisable surface

7.40/10

03application

Where this source fits

What analysts use it for, and — just as important — where it does not belong.

Primary use cases

location_context
map_enrichment
place_lookup
geo_reporting

Suitable for

researchers
journalists
developers
mapping_projects

Not suitable for

bulk_geocoding_on_public_endpoint
tracking_private_people

data types

geocodingreverse_geocodingaddresseslocationsosm_data

04opinion

Editorial take

Our qualitative read on the source — tone, framing and trust posture.

Good source, but operationally we must be careful. Great for prototypes and low-volume lookups.

05product

Integration stance

Build, buy or defer. What shape the product integration would take, and why.

Use in limited volume first. For scale, consider self-hosted Nominatim or a compliant provider.

06governance

Ethics and compliance

What to handle carefully, and what must not ship without sign-off.

Ethical notes

Location data can be sensitive. Avoid building private-person tracking workflows.

Compliance notes

Respect the official Nominatim usage policy. Cache results and avoid bulk public endpoint usage.

07technical

Metadata

Catalog-side technical footer. Values as recorded in the source row.

source owner: OpenStreetMap / Nominatim
report module: geo_context
integration candidate: true
requires usage policy review: true

Back to catalog