Home » railML newsgroups » railML.infrastructure » How to model ETCS BL2 speed restrictions and gradients, in railML v2.x (Best practice)
How to model ETCS BL2 speed restrictions and gradients, in railML v2.x [message #2027] Thu, 29 November 2018 14:56 Go to previous message
Jörgen Strandberg is currently offline  Jörgen Strandberg
Messages: 15
Registered: August 2017
Junior Member
In search of a best practice for, in railML v2.x, modeling ETCS BL2 speed restrictions and gradients (slope) for the complete track, I would like to propose these semantic restriction:

A gradientChange/speedChange shall be automatically ended at the trackBegin/trackEnd in @dir.
Rationale: To avoid unnecessary processing of connected tracks when writing and interpreting data.

Additionally I would like to point to some parts of the railML documentation on the wiki that need clarification, such as valid values for @dir and @vMax special value 999.

See attached docx-file.

Regards,
Jörgen Strandberg

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3.1] Difference between Stopping Places and Operational Point (opOperationType stoppingPoint)
Next Topic: Question towards use of @passable attribute (2.4)
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Sep 21 06:14:16 CEST 2024