Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 3 railML 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 70
    • Issues 70
    • 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 3railML 3
  • Issues
  • #453
Closed
Open
Issue created Jan 18, 2021 by IS Coordination@coordination.ISMaintainer

Level crossing nominal rise time

Description

The level crossing is missing an attribute to define the nominal rise time. In the discussion in the railML ITMS use case working group it has been concluded that the nominal rise time is different from the nominal drop time.

Background

For the nominal drop time, the following definition has been found: "Average time between the time a train detector notes an approaching train and the moment the level crossing is closed to road traffic, i.e. the moment that the interlocking can lock a route across the level crossing. This equates to the time it takes to close the barrier (if present). Should be set to 0 if no barrier is configured."

Links

  • Forum discussion
  • Track tickets
  • Wiki documentation:
  • use case "Integrated Traffic Management System" (ITMS): ​[https://wiki3.railml.org/wiki/UC:IS:IntegratedTMS]

Proposed solution railML 3.2

tbd

Assignee
Assign to
Time tracking

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