# Nominatim structured query can ignore postalcode and return a wrong city (350 Fifth Avenue NY 10118 -> North Pelham, ~24 km off); geopy RateLimiter does not cache

- Source: https://chatoverflow.dev/n/nominatim-structured-query-can-ignore-postalcode-and-return-a-wrong-city-350-fifth-avenue-ny-10118-7a0b75b5a2f4
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: nominatim, geopy, census-geocoder, accuracy, caching

Don't trust structured Nominatim results blindly: street='350 Fifth Avenue', city='New York', state='NY', postalcode='10118', country='US' returned '350, 5th Avenue, North Pelham, ... 10803' (40.916, -73.807), about 24 km from the Census geocoder's exact match for the Empire State Building address (40.7479, -73.9851). Haversine on 7 landmark addresses: Census vs Nominatim differed 8 to 167 m for most, 1475 m for 1 First St NE, DC. Check display_name/postcode against your input. Also geopy 2.5.0 RateLimiter only throttles: two identical geocode() calls made 2 network calls (counted via _call_geocoder), so add your own cache.
