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/example-data]
• as part of railML 3.1 final release: [https://development.railml.org/railml/version3/-/tags/3.1-final]

Proposed solution

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

• Border (e.g. between different IM) implemented with version 13
• Balises and balise groups
• Mileage changes (gaps, overlaps) implemented with version 12
• Electrifications implemented with version 10
• 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
• 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
• one stoppingPoint so that a train can pass an OCP implemented with version 2
• different levels of topology (micro, meso, macro) implemented with version 2
• crossing implemented with version 2
• single switch crossing implemented with version 2
• stabling track (siding track for storing vehicle) implemented with version 2
• parts of stations to exemplify @ocpParentRef usage [2] implemented with version 13
• ETCS e.g. level transitions [2]
• shunting signals and insulated joints to allow for shunting [1]
• a line without switchable signals and with self-restoring points [1]
• derailers implemented with version 2
• direction and speed indicators [1]
• temporary vs. permanent speed restrictions [1] implemented with version 2
• geoCoorginates [2]
• stationCodes [2] implemented with version 4
• deflecting speed of the railway switches implemented with version 2
• gradients [2] implemented with version 13
• tunnels [2] implemented with version 2
• combination of signals where main signal and distant signal are on the same post (same location/absPos) [2]
• routes [2]
• tvd [2]
• trainProtectionSystemChange [2]
• eliminate anagrams from the names of lines implemented with version 12 -add full speed profiles for all of the lines
• 2025-01-27 Bane NOR Workshop add ETCS section to the Advanced example to be published as v14 (added Ne14/ETCS-Equipment everywhere in Arnau / Cranz / Dunja)
• 2025-01-27 Bane NOR Workshop add Splitting section to the Advanced example
• clearance points as a kind of trainDetectionElement
• to make cross section of stations in centre
• define names of three IM names (third for siding) to be published as v14
• Replace "part" in "station part"
• add gradient with negative value to be published as v14
• new view LPS view the same as current line view to be published as v14
• new view line view which shows which tracks belong to which line
• Remove arrows in line / LPS views -> replace with nothing or stop
• move 69C to 0,800 to be published as v14
• move 69VWC to 0,877 to be published as v14
• move 69VC to 1,500 to be published as v14
• Gradientchange to 6,800 from 12250m to 6800m to be published as v14
• new view infrastructure manager view with three managers (1: siding, 2: line 2444, 3: 8176 and 9333) -> no code only name to be published as v14
• Rename „dismantled“ to „closed“ to be published as v14
• Add register_railML to legend
• Rename „existing“ to „operational“ to be published as v14
• Future: add some „conceptual“ piece of track
• IM-Border should have an OCP called „IM border“ with the name of a relevant infrastructure manager
• Add 2 designators (one for each IM) for borderPoint OP
• Three LPS: track 3 into Cranz, re-km to double slip switch

[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 ...