Geocoding on local Nominatim Server (Geofabrik files) less effective than OpenStreetMaps search

Hello, I am new to this but I’ve been looking around the forum and can’t figure out why this is happening.

I’m running a local Nominatim (4.3) instance using the latest US files from Geofabrik.

For instance, the web server locates this location just fine:
https://nominatim.openstreetmap.org/ui/search.html?street=1128+11th+ST&postalcode=90403

But my local installation seems to only locate the street, not the house/building:

http://localhost:8080/search?street=1128+11th+ST&postalcode=90403

Local output:

[{“place_id”:9584949,“licence”:“Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",“osm_type”:“way”,“osm_id”:740887343,“boundingbox”:[“34.0207803”,“34.0214254”,“-118.4881303”,“-118.4873641”],“lat”:“34.021225”,“lon”:“-118.4878922”,“display_name”:"11th Street, Santa Monica, Los Angeles County, California, 90403, United States”,“place_rank”:26,“category”:“highway”,“type”:“tertiary”,“importance”:0.41001}]

Any constructive idea about how to fix this? I’m relying on this to reliably geocode many bulk addresses.

The public instance of Nominatim afaik still uses address (interpolation) data from TIGER to complement OSM data.

PS: imho this should probably be turned off but that’s a different discussion.

Interesting. Do they call TIGER via the web? Or do they have their own local version of TIGER? Is there a way to get TIGER locally too?

https://nominatim.org/release-docs/latest/customize/Tiger/

2 Likes