Create AWS&TPWS legend in train_protection.yaml#922
Closed
saltywalrus-prkl wants to merge 1 commit into
Closed
Conversation
Owner
|
There is also an open issue #549 to render multiple train protection systems on the same line, which would also solve the same problem in a more general way. |
Owner
|
Thanks for the pull request. Dual and multi train protection will be implemented with #976. This pull request can be closed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In Great Britain, most lines are equipped with AWS, which provides information about the next signal aspect and only applies intervention braking if the driver does not acknowledge the information in time. Some lines are also equipped with the complimentary TPWS system, which provides intervention braking if a signal is passed at danger. On these lines, both AWS and TPWS work simultaneously.
At present, the AWS tag takes precedent over the TPWS tag, so in areas where both systems are installed it appears as if only AWS is installed. My pull request would create a new legend for AWS&TPWS which takes precedent over AWS, correcting this issue.
The reason for doing it this way rather than just renaming the TPWS legend to AWS&TPWS is that there are lines which use TPWS without AWS in Australia, so the existing TPWS legend needs to remain in place for use on them.
Information on AWS/TPWS:
https://www.railengineer.co.uk/tpws-a-retrospective/
Thanks :)