-
Notifications
You must be signed in to change notification settings - Fork 2
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
BM, BAPR and BAL aren't train prot systems #154
Comments
Some of the pink systems were indeed documented on the wiki but not tagged. We can remove them. Maybe the wiki should also be updated then, especially because the list of train protection systems in https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging#Train_protection_systems is used in the proposal https://wiki.openstreetmap.org/wiki/Proposal:Railway:train_protection for the new tag |
For example one rail line just within France (from Hagenau) is tagged with
(see https://overpass-turbo.eu/?w=%22railway%3Abapr%22%3D*+global&R). How would you propose to tag such a line? Maybe the tagging legend could be split into "train protection systems" and "block control systems". The SNCF data portal has "mode de cantonnement" (somewhat translated into partitioning mode) defined: And separately the KVB equipped lines: https://data.sncf.com/explore/dataset/lignes-equipees-de-kvb/map/?location=12,48.85997,7.57782&basemap=jawg.transports |
Part of #154 Some of these are not used at all, or are not train protection systems.
This will be cleaned up with #164. I will then convert the issue to a discussion for further display / tagging discussion. |
Part of #154 Some of these are not tagged at all, or are not train protection systems.
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
These shouldn't be shown here. Yes, there are documented tags for these, but they aren't train protection systems nevertheless, but rather a form of operation.
The text was updated successfully, but these errors were encountered: