Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 2railML 2
  • Issues
  • #424
Closed
Open
Issue created Oct 12, 2020 by Organisation@organisation.GOVOwner

Extend definition of <speedProfiles> and add values

Description

The challenge to solve: how to combine speed profiles of different type and how to find out which maximum speed value is spplicable for a certain train that follows several speed profiles.

Background

This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.

The element is a high-level element in railML 2.4.

In railML2.4nor, the speed for trains is modelled via speed profiles. The speed profiles are specified for different types of trains. railML2.4nor uses the railML2.4 @name attribute to indicate the speeds accordingly. The @name attribute is defined as a string in railML2.4 and the allowed string values are restricted in railML2.4nor.

For more details on the allowed elements in railML2.4nor, see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.7.

Links

  • Forum discussion:
    • Torben Brand, 16.10.2017: [https://www.railml.org/forum/index.php?t=msg&th=538&goto=1655&#msg_1655]
    • Torben Brand, 06.09.2018: [https://www.railml.org/forum/index.php?t=msg&th=605&goto=1955&#msg_1955]
    • Torben Brand: [https://forum.railml.org/userfiles/2018-07-02_jbd_speed-profile-hierachy-names-refactoring.pdf]
  • Trac tickets:
    • #424
    • #425
  • Wiki documentation:
    • IS:speedProfile: [https://wiki2.railml.org/wiki/IS:speedProfile]

Proposed solution in railML 2.5

Clearify definitions of increasing and decreasing speed profiles:

  • increasing: The speed profile increases the permitted speed. If multiple "increasing" speed profiles are applicable, select the one with the highest @vMax value.
  • decreasing: The speed profile decreases the permitted speed. If multiple "decreasing" speed profiles are applicable, select the one with the lowest @vMax value. If this value is lower than the speed of an "increasing" speed profile, it overrides that speed.

For identifying the "basic" speed profile, a new explicit boolean attribute @basicSpeedProfile (true, false) shall be defined. The basic speed profile defines a "baseline speed value" that is valid for all trains if no other specific speed restrictions are given. The basic speed profile is always linked with @influence="increasing"

The ETCS train category shall be linked with the speed profile via a new attribute @etcsTrainCategory (integer 0..15). At the same time, the attribute @etcsTrainCategory in element <speedChange> shall become DEPRECATED.

to be continued

Edited Mar 14, 2022 by IS Coordination
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany