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

Warning for emergency exit not in route or stop_areas (tagging issue?) #10

Open
double-a opened this issue Oct 5, 2021 · 1 comment

Comments

@double-a
Copy link

double-a commented Oct 5, 2021

Essentially 2 warnings for the same node:
Found 1 entrances not used in routes or stop_areas: n315269742
1 subway entrances are not in stop_area relations: n315269742
The node is just an emergency exit far away from the next stop, thus it is not part of a stop_area.
Maybe one could add it to the route, but I do not think that there is a matching role for this.

Anything wrong with the tagging of the node? (access=emergency, entrance=exit, railway=subway_entrance)

Or should the check ignore such nodes?

@alexey-zakharenkov
Copy link
Owner

As I can see, Tag:railway=subway_entrance and Key:access pages don't consider railway=subway_entrance + entrance=exit + access=emergency tagging as correct for such exits. Maybe exit=emergency is more suitable, but Key:exit only mentions it without assertion of approvement status.

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

No branches or pull requests

2 participants