Skip to main content

Is something wrong with nominatim.openstreetmap.org? It does a _lot_ of timeouts for me.

I'm currently testing a feature which relies heavily on (reverse) geocoding, so I switched to a nominatim instance from @geofabrik for now, but I can't use that one in production.

@Geofabrik
in reply to Pietervdvn :mapcomplete:

OpenCage 👉🌍
OpenCage 👉🌍
• •
happy to help if you need high volumes of reverse geocoding https://opencagedata.com/

OpenCage - Easy, Open, Worldwide, Affordable Geocoding and Geosearch

An easy-to-use forward and reverse geocoding API. Worldwide coverage. Affordable, predictable pricing. Open data.
opencagedata.com
in reply to OpenCage 👉🌍

Pietervdvn :mapcomplete:
Pietervdvn :mapcomplete:
• •

@opencage Yeah, I know! Thanks for the offer, but I'm gonna stick to the OSM-instance as long as I'm falling under 'acceptable use'

For now, it is an accessibility feature that only a handful of people will use, so it is gonna be a very small volume of lookups.

@OpenCage 👉🌍
in reply to Pietervdvn :mapcomplete:

pavi
pavi
• •
Hasnt that always been the case with nominatim and #osm main website. I wonder why despite all these years we haven't got a search engine which is stable and gave proper results. Yes it does give some detailed results and I even tweak the queries to satisfy it. But what about the end user? 👦
#OSM
in reply to pavi

Pietervdvn :mapcomplete:
Pietervdvn :mapcomplete:
• •

@pavi This is the first (technical) issue I've had in three years while using nominatim, so that's fine.

And search is really hard to get right. If you can do better, go for it!

@pavi
⇧