railML 3.x Advanced Example

Description

Since railML 3.x introduces new modelling concepts, documentation of the data exchange format need to enclose more detailed information, in particular for newcomers. The Simple Example Tutorial provides such a "Hello world" documentation for a very simple scenario. The Advanced Example shall be based on the Simple Example and extend its content to cover further modelling aspects and railML 3.x use cases.

Background

This ticket shall be used as a collector for requirements and needs concerning the content of the upcoming Advanced Example. It was initiated following the 3rd railML 3.1 Workshop that took place in Prague on November 15, 2018. Wishes for further content to be added to the Advanced Example can be expressed in the railML forum and/or in the meetings and conf calls of the different developer groups.

Links

• Simple Example:
• download at railML website: [https://www.railml.org/en/user/exampledata.html]
• as part of railML 3.1 final release: [https://svn.railml.org/railML3/tags/railML-3.1-final/]

Proposed solution

The Advanced Example shall contain the following elements from infrastructure domain:

1. Border (e.g. between different IM)
2. Balises and balise groups
3. Mileage changes (gaps, overlaps)
4. Electrifications implemented with version 10
5. divided station tracks within a station (several isolated sections, each with its own train number field) in connection with different stopping places at one station track implemented with version 8
6. two lines in form of an "Y" to support [train coupling and sharing](https://wiki.railml.org/index.php? title=Dev:Train_Coupling_And_Sharing) with four stations implemented with version 2
7. one stoppingPoint so that a train can pass an OCP implemented with version 2
8. different levels of topology (micro, meso, macro) implemented with version 2
9. crossing implemented with version 2
10. single switch crossing implemented with version 2
11. stabling track (siding track for storing vehicle) implemented with version 2
12. parts of stations to exemplify @ocpParentRef usage [2]
13. ETCS e.g. level transitions [2]
14. shunting signals and insulated joints to allow for shunting [1]
15. a line without switchable signals and with self-restoring points [1]
16. derailers
17. direction and speed indicators [1]
18. temporary vs. permanent speed restrictions [1] implemented with version 2
19. geoCoorginates [2]
20. stationCodes [2] implemented with version 4
21. deflecting speed of the railway switches
22. gradients [2]
23. tunnels [2] implemented with version 2
24. combination of signals where main signal and distant signal are on the same post (same location/absPos) [2]
25. routes [2]
26. tvd [2]
27. trainProtectionSystemChange [2]
28. eliminate anagrams from the names of lines
29. add full speed profiles for all of the lines

[1] Dirk Bräuer, 01.04.2020: https://www.railml.org/forum/index.php?t=msg&th=697&goto=2411&#msg_2411

[2] Torben Brand 29 August 2023 https://www.railml.org/forum/index.php?t=rview&goto=3118&th=914#msg_3118 ... to be continued ...