ip=216.73.216.78
Nominatim Geocoder & Reverse Geocoder · dev-docs

Using Nominatim in a Verification Workflow

A cautious geocoding workflow that treats places and reverse-geocoded objects as candidates requiring independent geographic verification.

status
Published
slug
verification-workflow
published
Aug 22, 2026

Using Nominatim in a Verification Workflow

Geocoding is most useful when it generates a location hypothesis that can be tested independently.

Place search

If a source mentions:

Central Market, City X

Nominatim can help produce candidate coordinates.

Then verify with:

  • map context;
  • street network;
  • visible landmarks;
  • imagery;
  • local naming;
  • other geographic sources.

Reverse search

If you already have coordinates, reverse geocoding can provide a nearby named OpenStreetMap object.

The result is not necessarily the exact building or feature at those coordinates.

Nominatim's reverse endpoint returns a suitable nearby OSM object according to its indexing logic.

Do not use geocoding as proof

Bad conclusion:

Nominatim says the image was taken in Bologna.

Better:

Nominatim returned Bologna-area candidates for the location query; independent visual/geographic evidence is required to verify the media location.

Provider policy

The public OSMF Nominatim endpoint has strict usage limits and is not intended to power generic bulk geocoding services.

OSINT.dev therefore requires an explicitly configured compliant provider before enabling the native runner.

References

last published Aug 22, 2026