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

Wrong parenting #4185

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

Wrong parenting #4185

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

Reporter: Alibeg
[Submitted to the original trac issue database at 6.08am, Monday, 16th January 2012]

Steps to reproduce:

  1. Type in search box: "vijenica town hall".

This works both in OSM and in Nominatim - same error.

Vijenica is not in " " ("Republika Srpska"), and also, not in "Mjedenica" (another error or bug)

Vijecnica is one of the landmarks of Sarajevo, and this is quite a big mistake.

I think the reason is:

"Opina Stari Grad Sarajevo"
(http://searchindex.open.mapquest.com/details.php?place_id=2172777160)

is listed under "Parent Of (named features only):" section of

" " (which has rank: state)
(http://searchindex.open.mapquest.com/details.php?place_id=2176273152).

This isn't correct and I think this is cause for some locations in Sarajevo to have wrong "state" labels, and they appear as being in " " both on:
http://www.openstreetmap.org/
and on:
http://nominatim.openstreetmap.org/

I have tried to find that node " " but it was deleted, and I do not know how can I edit it's child nodes.

Thanks for assistance.

@openstreetmap-trac
Copy link
Author

Author: mmehl
[Added to the original trac issue at 8.13pm, Monday, 30th April 2012]

Similar problem in Germany:
Saarlouis is not in Daun (see http://nominatim.openstreetmap.org/details.php?place_id=128810352).
Daun is a city in Rheinland-Pfalz.

@openstreetmap-trac
Copy link
Author

Author: mmehl
[Added to the original trac issue at 8.20pm, Monday, 30th April 2012]

Maybe the "place=region" tag on the node Daun (#95965404) leads to this confusion...

@openstreetmap-trac
Copy link
Author

Author: datendelphin
[Added to the original trac issue at 9.05am, Sunday, 15th July 2012]

I think this is tha same issue as #4247. Not entirely reproducible, but should be fixed with next import

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