Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

strange extra results of street with wrong postal code #4726

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

strange extra results of street with wrong postal code #4726

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

Reporter: skyper
[Submitted to the original trac issue database at 1.31pm, Friday, 28th December 2012]

Searching
http://nominatim.openstreetmap.org/search.php?q=mercystra%C3%9Fe&viewbox= returns in first place one valid result:
http://nominatim.openstreetmap.org/details.php?place_id=42638941

This is not the best choice, as I expected to get the whole street and not just a part (situation see below) but OK.

In third place I get: http://nominatim.openstreetmap.org/details.php?place_id=82189640 with a wrong postal code. Do not know where this comes from but seen this code on several search for streets around this area. Please do not show this post code as it is an individual post code for the administration and not valid for any street.

=== situation ===

  • the street has a valid associatedStreet relation with post code (79100). This should be the first hit and only valid post code.
  • the postal code is tagged in the whole city either with the admin boundary relation or if needed as an own boundary relation boundary=postal_code.

Please do not use the postal_code of nodes with place=* as this might be totally wrong.
Thanks

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 6.57am, Monday, 16th December 2013]

Postcodes on admin boundaries now work. For post codes on associatedStreet relations see #4878.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant