adresse.data.gouv.fr vs BigDataCloud Geocode
Same instrument, two spec sheets — measured, not claimed.
adresse.data.gouv.fr vs BigDataCloud Geocode: common questions
Which is more reliable, adresse.data.gouv.fr or BigDataCloud Geocode?
On our scheduled checks, adresse.data.gouv.fr leads on measured uptime — adresse.data.gouv.fr at 100% versus BigDataCloud Geocode at 53.9% 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, adresse.data.gouv.fr or BigDataCloud Geocode?
BigDataCloud Geocode has the lower median latency in our checks — adresse.data.gouv.fr responds in 853 ms versus BigDataCloud Geocode at 193 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 adresse.data.gouv.fr and BigDataCloud Geocode need an API key?
Neither needs a paid key — adresse.data.gouv.fr is callable with no signup, and BigDataCloud Geocode is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call adresse.data.gouv.fr and BigDataCloud Geocode from the browser?
Yes — both adresse.data.gouv.fr and BigDataCloud Geocode 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 adresse.data.gouv.fr and BigDataCloud Geocode free for commercial use?
adresse.data.gouv.fr allows commercial use on its free tier, and BigDataCloud Geocode has unclear commercial terms. 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.