GeoJS vs Nominatim (OSM)
Same instrument, two spec sheets — measured, not claimed.
GeoJS vs Nominatim (OSM): common questions
Which is more reliable, GeoJS or Nominatim (OSM)?
On our scheduled checks, Nominatim (OSM) leads on measured uptime — GeoJS at 98.9% versus Nominatim (OSM) at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, GeoJS or Nominatim (OSM)?
GeoJS has the lower median latency in our checks — GeoJS responds in 62 ms versus Nominatim (OSM) at 319 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
Do GeoJS and Nominatim (OSM) need an API key?
Neither needs a paid key — GeoJS is callable with no signup, and Nominatim (OSM) is keyless with a required User-Agent header. Both are quick to prototype with; rate limits still apply.
Can I call GeoJS and Nominatim (OSM) from the browser?
Yes — both GeoJS and Nominatim (OSM) send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.
Are GeoJS and Nominatim (OSM) free for commercial use?
GeoJS has unclear commercial terms, and Nominatim (OSM) is personal/non-commercial only. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.