Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#5429 closed defect (invalid)

search returns wrong postcode, knowing it better ...

Reported by: andreas.filsinger@… Owned by: geocoding@…
Priority: critical Milestone:
Component: nominatim Version: 2.0
Keywords: postcode postal_code Cc:


The Search "q=altdorferstr, neumuenster" (de) returns postcode 24534. It should return 24539.

This is NOT an Error in the Data. Poly-Lines for both postcodes are correct (I try to attach 2 PNGs showing this).

This is NOT a Street wich goes through 2 or more postcode claims, the whole street fully is inside 24539 Poly.

It seems to me its a bug in the code checking if a point is in a Polygone or not. Or a bug in Creating placex Records while set up the Search-Basis. I do not know the path through the code adding PLZ Information to a found Street.

Maybe Info-Addition "postcode" is done by "another" Table, not by PolyLines?, based here on false Data, then please sorry - give me a hint to report this in correct manner.

:-| Andreas

Change History (3)

comment:1 Changed 3 years ago by andreas.filsinger@…

comment:2 Changed 3 years ago by Sarah Hoffmann

Resolution: invalid
Status: newclosed

Sorry to say but this is a data error after all. The postcode comes from which has a bad addr:postcode (and even a not so helpful note hinting that the addr:postcode tag is misused). As Neumünster makes up part of the address of Altdorferstrasse, the postcode is inherited. Remove the spurious addr:postcode on the town node and all will be well.

comment:3 Changed 3 years ago by andreas.filsinger@…

I made the Remove. It now works as expected.

(So my first commit to OSM is a Kill, puh)

Note: See TracTickets for help on using tickets.