Fixed #9406: By treating aerialway=station as valid start/end point which suppresses the false warning#11675
Fixed #9406: By treating aerialway=station as valid start/end point which suppresses the false warning#11675Razen04 wants to merge 4 commits intoopenstreetmap:developfrom
Conversation
d8446da to
2acf322
Compare
There was a problem hiding this comment.
we have another preset, called Aerialway Stopping Location, which seems to be used in much the same way, and also seems to be a routing sink.
Should this logic apply to that tag as well?
There was a problem hiding this comment.
I think public_transport=stop_position && aerialway=* should be treated the same way as aerialway=station.
In both cases, the mapper is explicitly marking a boundary where pedestrian movement ends and aerial transport begins.
This is different from public_transport=stop_position for buses, trams, or trains, where pedestrian connectivity is expected to continue.
So should I add that case too in the code?
There was a problem hiding this comment.
I think so, but I would be also fine with doing it as a next PR (note: not a maintainer)
There was a problem hiding this comment.
Let's see why k-yle says. The fix is just one line more i suppose.
There was a problem hiding this comment.
@k-yle do you have by any chance time to look into that?
There was a problem hiding this comment.
it should be a trivial change, i would fix it in this PR imo, so that we have a centralised place to this discuss this topic
There was a problem hiding this comment.
appears to be done, from what I see
…t/end point which suppresses the false warning
|
I messed it up in between, lol. Anyways I think I made. the correct change, do look into it once. |
|
Yeah, this 579 changed files looked a bit suspect :) |
|
|
||
| // treat nodes inside gondola stations and ski lifts as connected | ||
| if (vertex.tags.aerialway) { | ||
| if (vertex.tags.aerialway === 'station' || vertex.tags.public_transport === 'stop_position') return true; |
There was a problem hiding this comment.
I guess it would also count say public_transport=stop_position aerialway=no ?
And public_transport=stop_position aerialway=whatever_gibberish ?
Should requiring specifically aerialway=station or public_transport=stop_position aerialway=yes be needed?
Co-authored-by: Mateusz Konieczny <matkoniecz@gmail.com>
|
I fixed this slightly differently in cd255c8: the |
Description
Currently, iD warns for paths which are not connected to any other route any is contained within a building like gondola stations which is a false positive. This has been explained in detail in Issue #9406.
Fix
The fix to this is simple, we just add an extra check in the
isConnectedVertexfunction to check if a vertex in the path hasaerialway=stationand returntruefor that, which means the path is valid to have start/end in the gandola station even if they are not connected to any other roads or highway(which they aren't supposed to).Fixes #9406
Before:
After the if statement:
References
This is similar to issue #3906 - which showed problems with foothpaths connecting two buildings.