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
  • #323
Closed
Open
Issue created Mar 12, 2018 by IS Coordination@coordination.ISMaintainer

Default values for Level Crossing (de: Default-Werte für BÜ-Modellierung)

Description

It was mentioned in the forum that the current implementation of a level crossing contains some attributes with default values that are source of errors. It is suggested to review these default values and in case of misleading information (e.g. when the information is in fact unknown) the default value should be removed.

Background

The attribute @length describes the length of the level crossing from railway perspective (default="0").

The attribute @angle describes the angle between road and railway in degrees (default="90").

The attribute @protection describes the technical protection system installed at the level crossing (default="none").

Links

  • Forum discussion:
  • Tobias Bregulla, 12.03.2018: [https://www.railml.org/forum/index.php?t=msg&th=556&start=0&]
  • Trac ticket:
  • Wiki documentation:
  • IS:LevelCrossing: [http://wiki.railml.org/index.php?title=IS:levelCrossing]

Proposed solution in railML 2.4

It is suggested to remove the default values for attributes:

  • @length
  • @angle
  • @protection

Proposed solution in railML 3.x

The topic of default values affects almost all types of elements and attributes in the railML model. For upcoming railML 3.x it is suggested to limit usage of default values to attributes where there is no doubt and no chance for misinterpretation. In all other cases, default values shall not be used/implemented in the model.

Assignee
Assign to
Time tracking

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