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

tunnel=* on a way generates inappropriate address/place #5232

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

tunnel=* on a way generates inappropriate address/place #5232

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

Comments

@openstreetmap-trac
Copy link

Reporter: skybunny
[Submitted to the original trac issue database at 8.46pm, Sunday, 21st September 2014]

Consider placeid https://nominatim.openstreetmap.org/details.php?place_id=9212214461 ...

Two issues seem evident; the first is how nominatim is handling address generation for ways with the tag tunnel=* regardless of other tagging; the second is that it is generating them for a waterway way at all.

Issue A: For ways with tunnel=* in general, the address 'West Pine Lake Road, Atkins, Forest, Wisconsin, United States of America' is generated. I would expect that a generated address in this case should be 'Atkins, Forest, Wisconsin, United States of America', as a tunnel does not necessarily have anything to do with the closest way of type 'highway'.

Issue B: Regardless of (A), above, this is a way of type waterway=, which in turn is a member of a relation of type waterway=. Generally these do not generate a placeid at all, because they are parented to the waterway relation (here, relation 172143.) In other words, that the way has the waterway tag on it should be evaluated over the fact that tunnel also does.

Thanks for the consideration!

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 4.34pm, Friday, 10th October 2014]

For issue A, I tend to disagree. There can be quite a lot of tunnels in a town and getting a more specific address that includes a street name can only help to disambiguate results.

Regarding issue B, the problem is that the name tag which actually refers to the stream is taken to belong to the tunnel. To fix that Nominatim neds to interpret bridge:name and tunnel:name. That is already covered in #4361, so closing this one as a duplicate.

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