You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: