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.
- 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
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.
Ethics and compliance
Access, licensing and sensitive-data considerations for this source.
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.