Opened 8 years ago

Closed 8 years ago

#4537 closed defect (duplicate)

Incorrect Nominatim Result

Reported by: warling Owned by: geocoding@…
Priority: major Milestone:
Component: nominatim Version: 2.0
Keywords: st. paul, minneapolis, ZIP code, 55414, 55114, Clarence Avenue, Emerald Avenue Cc: warling


  1. The query "44 Clarence Avenue Southeast, Minneapolis, MN 55414, USA" does not point directly to the house, even though the house is clearly in the system. The closest it comes is the beginning of Clarence Avenue, but the result displays the incorrect ZIP code (55114 instead of 55414; 55114 is located in St. Paul, and 55414 is located in Minneapolis; the boundary between St. Paul and Minneapolis is the north-south street Emerald Avenue, a bit to the east of the above address.)
  1. The query "44 Clarence Avenue Southeast, Minneapolis, MN 55414-3528, USA" returns no results at all; the only difference is the inclusion of the "-3528" carrier code to the ZIP code.
  1. The query "44 Clarence Avenue Southeast, Minneapolis, MN 55114, USA" DOES point directly to the correct house, even though this is the incorrect ZIP code. It seems that the ZIP code's boundaries are incorrect.

My hunch is that the problem stems from incorrect ZIP code boundaries. West of Emerald Avenue is Minneapolis (55414), while east of Emerald Avenue is St. Paul (55114).

Change History (2)

comment:1 Changed 8 years ago by warling

Cc: warling added

comment:2 Changed 8 years ago by Sarah Hoffmann

Resolution: duplicate
Status: newclosed

There was a bug in the postcode generation which has been corrected with the latest import. All examples now work now as expected.

There are still some issues with zip+4 postcodes but there is already ticket #3838 for that. Closing this one as duplicate.

Note: See TracTickets for help on using tickets.