Skip to content
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

Add crossing:signals field to crossing/*traffic_signals presets #1203

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

tordans
Copy link
Collaborator

@tordans tordans commented Apr 28, 2024

This is based on top of #1201 and should only be merged after that was merged. For that reason it is marked as a draft for now. I will rebase here in case #1201 changes.Update: Since #1201 was merged this is now rebased and ready for review.


This PR adds the field and add the addTags part.

This follows the conversation during the iD Community Meetup to consider adding the tag due to the usage in StreetComplete, Routers and the general impression that the crossing:signals=yes tag is widely "in use" and accepted.


Closes #1118

Note: This change was also part of https://github.com/openstreetmap/id-tagging-schema/pull/1044/files#diff-b8505be38bbc0be40512bf63c04d79f36f8826808ba4f0c06f186527eddcc7b4

@tordans tordans marked this pull request as draft April 28, 2024 20:00
Copy link

🍱 You can preview the tagging presets of this pull request here.

@tordans tordans mentioned this pull request Apr 28, 2024
18 tasks
@tordans
Copy link
Collaborator Author

tordans commented Apr 28, 2024

Testing

Looks good.

For a crossing node with just crossing=traffic_signals + highway=crossing the addTags dialogue shows up as expected:

image

Follow up

  • Cleanup the addTags to only include the tags that are not already part of tags. Which makes it a lot easier to read and maintain.

Open question…

  • Do we actually want a field for this? Because the field allows to remove the "yes" value, which triggers the yellow update box (again). I think we shoudl remove the field and rely on addTags to add a tag that is only visible in the full tags part of the sidebar.
    • image

@tordans
Copy link
Collaborator Author

tordans commented Apr 28, 2024

Next steps

@tordans tordans marked this pull request as ready for review December 19, 2024 10:30
@Dimitar5555
Copy link
Contributor

If a crossing is already tagged as crossing=traffic_signals, this implies that there are signals present at the crossing. Adding crossing:signals=yes alongside crossing=traffic_signals feels redundant, as it doesn't provide any additional valuable information.

If the goal is to eventually phase out crossing=traffic_signals and replace it with a combination of tags such as highway=crossing + crossing:signals=yes, then this should be clearly stated and discussed in a proposal.

In my opinion, the focus should be on maintaining clean and efficient tagging, and crossing=traffic_signals alone already conveys the necessary information about signal presence. Adding another tag for the same purpose could cause confusion and dilute the clarity of the tagging scheme.

@tordans
Copy link
Collaborator Author

tordans commented Dec 19, 2024

Just for reference: The draft of the proposal on this tag https://wiki.openstreetmap.org/wiki/Proposal:Crossing_signalization#Rationale


Lets see if we find any reason to go along with this at this point … – I am happy with benching it for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

crossing:signals
2 participants