Nominatim / OpenStreetMap Geocoding
OpenStreetMap-based geocoding and reverse geocoding.
- slug
- nominatim-openstreetmap
- priority
- 74
- reviewed
- Apr 24, 2026
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
Review dimensions
Each dimension is graded on a 0–10 scale. The overall score is a weighted aggregate.
Weighted aggregate across the eight review dimensions.
Where this source fits
What analysts use it for, and — just as important — where it does not belong.
- location_context
- map_enrichment
- place_lookup
- geo_reporting
- researchers
- journalists
- developers
- mapping_projects
- bulk_geocoding_on_public_endpoint
- tracking_private_people
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.
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.
Ethics and compliance
What to handle carefully, and what must not ship without sign-off.
Location data can be sensitive. Avoid building private-person tracking workflows.
Respect the official Nominatim usage policy. Cache results and avoid bulk public endpoint usage.
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