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

Nominatim cannot find the langley boundaries #5124

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

Nominatim cannot find the langley boundaries #5124

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

Comments

@openstreetmap-trac
Copy link

Reporter: daniel[at]nadir-seen-fire.com
[Submitted to the original trac issue database at 7.57pm, Monday, 17th February 2014]

Langley has two boundaries to it:\
http://www.openstreetmap.org/relation/2031947 \
http://www.openstreetmap.org/relation/2031946

However when searching for Langley neither boundary can be found (while searching for neighbouring cities like Surrey will find their boundaries):\
http://www.openstreetmap.org/search?query=Langley%2C%20Canada#map=11/49.0984/-122.5937

Is there a way this can be fixed.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 8.07am, Tuesday, 18th February 2014]

Both relations were missing, I've forced an update now and they should be ok. Most likely a case of broken boundaries that got fixed without touching the boundary relations themselves. Nominatim doesn't catch those.

Note that it still has some trouble finding both relations because the relations only contain the full name 'township of Langely' and 'city of Langley'.

@openstreetmap-trac
Copy link
Author

Author: daniel[at]nadir-seen-fire.com
[Added to the original trac issue at 9.10am, Tuesday, 18th February 2014]

Aye, I see that other boundaries like "City of Surrey" also contain a name=Surrey. Does the fact that there are two "Langley" boundaries prevent the two Langley boundaries from having a name=Langley or short_name=Langley?

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 9.19am, Tuesday, 18th February 2014]

Not at all, you'll simply get both in the result list. I recommend adding wikipedia tags as well, so that they appear in sensitive order.

For the city of Langley you should also add the existing place node (http://www.openstreetmap.org/node/52555902) with member role 'label' to the boundary relation. That will resolve the name issue and avoid duplicate results.

@openstreetmap-trac
Copy link
Author

Author: daniel[at]nadir-seen-fire.com
[Added to the original trac issue at 10.30am, Tuesday, 18th February 2014]

Thanks for the information, I had never even strongly noticed the Edit button, so I'm new at OSM.

I added an alt_name=Langley to both, since it didn't seem correct to use name=Langley as both moving "City/Township of" to offical_name as this appears as if it would make the common name both are described by the same, and short_name appears to be meant for real abbreviations.
Was this correct?

I don't know much about the label relation though. Other city boundaries like Vancouver and Surrey don't appear to have it, so I don't have much reference to go on.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 10.51am, Tuesday, 18th February 2014]

name should generally contain what is used 'on the ground'. Though, what that exactly means may be interpreted different from region to region. Definitions are even less clear for the alternative name tags. I recommend that you ask your local community (probably the [https://lists.openstreetmap.org/listinfo/talk-ca talk-ca mailinglist] in your case) about the best use of the tags so that they are consistent within the region. They can also help with the finer details of relation mapping.

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