Home » railML newsgroups » railML.infrastructure » Extension of railML's Advanced Example
Re: Extension of railML's Advanced Example [message #3113 is a reply to message #3110] Mon, 21 August 2023 07:54 Go to previous messageGo to previous message
Vasco Paul Kolmorgen
Messages: 55
Registered: November 2004
Member
Dear all,

I would like to point out that there has already been extensive advice from colleagues at the iRFP Dresden/Germany in 2020 on the Advanced Example (V07; as of 2020-03-25), which can perhaps be incorporated into the discussion that is now restarting.
The suggestions can be found at https://www.railml.org/forum/index.php?t=msg&goto=2411 and are presented again below:
  • Signal 69B1 should stay at the left side of the track?
  • 69N1/N3 do not necessarily need a switchable Zs3 but possibly a Zs7, which 69N2 surely needs.
  • 69P1 would probably need a Zs2.
  • In Kudowa, 3a should be the siding (Ladegleis) and the route to 3b should go through 1a to get a route-point in the middle of the station track ("echte Mittelweiche").
  • I guess the sidings in Kudowa would need a Flankenschutz (5, 3a) and Spitzenschutz (W01) = de-railers (Gleissperren).
  • In Kudowa, K06 would probably have a point number (W06ab/cd) and be numbered in consequence with the other's from left to right (between W02 and W03).
  • If it shall be possible to enter Kudowa track 2 with trains, it should have an So8 as at the neighbouring track 1b.
  • Sure that there would be a track circuit around Instersee W01? Why? The point can only be set by hand!
  • Why is there an insulated rail joint at 69VWc and 70A?
  • It is not possible to shunt, not even to run around with an engine in Cranz since there is no Ra10 and no insulated rail joint between any home signal and outer point.
  • The speed boards at Arnau and Cranz should be at the face of the outer points. (Arnau: km 0,5 vs. 0,8 = 300 m too far outside - why?)
  • If the speed restriction at the level crossing would be permanent - which we probably assume for it to be published in timetables - it would have to be signalled with Lf6/7 - not with Lf1/2. (We can probably make a compromise here.) But the level crossing should have no barriers to give a reason for the speed restriction of only 20 kph... and the speed restriction should be valid for head of train only (spitzenaufgelöst) to show how this is encoded in railML.
  • In Arnau, please clarify in the drawing whether platform 1 belongs to track 1 and whether track 1 has one or two platform edges.
As the posting contains a lot of abbreviations of the German signal book, here are some explanations:
  • Zs2: Direction indicator (Richtungsanzeiger)
  • Zs3: Speed indicator (Geschwindigkeitsanzeiger)
  • Zs7: substitute order as caution signal (Ersatzauftrag als Vorsichtsignal)
  • Ra10: Shunting stop board (Rangierhalttafel)
  • Lf 1/2: temporary speed change board (Langsamfahrtafel, vorübergehend)
  • Lf 6/7: permanent speed change board (Geschwindigkeitstafel, ständig)
Hope this helps.

Best regards,
--
Vasco Paul Kolmorgen - Governance Coordinator
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany

Am 18.08.2023 um 19:17 schrieb Larissa Zhuchyi:
> Dear all
>
> railML.org would like to extend the next version of an "Advanced
> example" [1] (current version 11 from 2023-07-25; without XML code). The
> Advanced example is available for free to the whole community and shows
> common elements of railway operation that are used in data management
> and data exchange.
>
> In this thread we want to collect your feedback on the proposed list and
> any other points to be added.
>
> Additionally, it appeared to railML.org, that some of the elements are
> not usually present in the schematic track plan but in other diagrams.
> As such what is your opinion on extending an "Advanced example" by e.g.
> gradient profile?
>
> List of proposed extensions:
> 1. parts of stations to examplify @ocpParentRef usage
> 2. description of ETCS e.g. balises and level transitions
> 3. input data for the runtime calculation [1], e.g. gradient changes and
> speed changes
>
> What do you think about the list? Do you have anything to add?
>
> [1] https://www.railml.org/en/user/exampledata.html
> [2] https://www.railml.org/forum/index.php?t=msg&th=906& start=0&
>
> Sincerely,
>
> Larissa Zhuchyi

[Updated on: Mon, 21 August 2023 09:36] by Moderator

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 2] <speedChange> semantic constraints revision
Next Topic: @keepsOrientation in Track object
Goto Forum:
  


Current Time: Mon May 20 19:09:36 CEST 2024