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

Using Connect the features with Crossing With Pedestrian Signals doesn't work as expected #9176

Closed
arch0345 opened this issue Jun 21, 2022 · 1 comment
Labels
bug A bug - let's fix this!

Comments

@arch0345
Copy link
Contributor

URL

No response

How to reproduce the issue?

  1. Add a Crossing With Pedestrian Signals way that crosses a street
  2. While selecting this new way, click on Connect the features
  3. A generic highway=crossing node is added

When using Connect the features with a Unmarked Crossing or Marked Crossing way, it adds an Unmarked Crossing or Marked Crossing node respectively. Because of this, I think it makes sense for it to add a Crossing with Pedestrian Signals node instead of just a generic highway=crossing node

Screenshot(s) or anything else?

image

image

Which iD Editor versions do you see the issue on?

Released version at openstreetmap.org/edit

Which browsers are you seeing this problem on?

Chrome

@tyrasd
Copy link
Member

tyrasd commented Jul 19, 2022

fixed in #9181

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug - let's fix this!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants