Skip to content

Create AWS&TPWS legend in train_protection.yaml#922

Closed
saltywalrus-prkl wants to merge 1 commit into
hiddewie:masterfrom
saltywalrus-prkl:patch-1
Closed

Create AWS&TPWS legend in train_protection.yaml#922
saltywalrus-prkl wants to merge 1 commit into
hiddewie:masterfrom
saltywalrus-prkl:patch-1

Conversation

@saltywalrus-prkl

Copy link
Copy Markdown

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 :)

@hiddewie

hiddewie commented May 1, 2026

Copy link
Copy Markdown
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.

@hiddewie

hiddewie commented May 31, 2026

Copy link
Copy Markdown
Owner

Thanks for the pull request. Dual and multi train protection will be implemented with #976. This pull request can be closed.

@hiddewie hiddewie closed this May 31, 2026
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

Successfully merging this pull request may close these issues.

2 participants