-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offer to connect sidewalk to service road without tagging crossing #9650
Conversation
@@ -435,6 +441,10 @@ export function validationCrossingWays(context) { | |||
|
|||
if (connectionTags) { | |||
fixes.push(makeConnectWaysFix(this.data.connectionTags)); | |||
let lessLikelyConnectionTags = tagsForConnectionNodeIfAllowed(entities[0], entities[1], graph, true); | |||
if (lessLikelyConnectionTags && JSON.stringify(connectionTags) !== JSON.stringify(lessLikelyConnectionTags)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a footway crosses a major road, it would be possible to offer a crossing=no
connection as a less likely option. However, crossing=no
doesn’t have a preset yet (openstreetmap/id-tagging-schema#548) and looks just like highway=crossing
on the map, which could be confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
offer a
crossing=no
connection
I agree that the tagging-schema would need to support this first in order to make sense. Let's keep that option in mind for a later stage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks 👍
@@ -435,6 +441,10 @@ export function validationCrossingWays(context) { | |||
|
|||
if (connectionTags) { | |||
fixes.push(makeConnectWaysFix(this.data.connectionTags)); | |||
let lessLikelyConnectionTags = tagsForConnectionNodeIfAllowed(entities[0], entities[1], graph, true); | |||
if (lessLikelyConnectionTags && JSON.stringify(connectionTags) !== JSON.stringify(lessLikelyConnectionTags)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
offer a
crossing=no
connection
I agree that the tagging-schema would need to support this first in order to make sense. Let's keep that option in mind for a later stage.
When a driveway or other service road crosses a sidewalk, offer to either connect them without any tags or connect them with
highway=crossing
. Previously, there was only one option that implied nothing about tags but addedhighway=crossing
anyways:When a service road crosses an ordinary footpath, or when a larger road crosses a sidewalk, continue to offer just the option to connect them with
highway=crossing
, but with the same icon as the crossing presets. Similarly, when a stream crosses a sidewalk, show the same icon as the Ford preset:Fixes #8463.