Talk:IS:track

From railML 2 Wiki
Revision as of 20:09, 10 April 2017 by RailML Coord Governance (talk | contribs) (Mapping of type attribute)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Semantic of type and mapping to national usage?

There is a unclear mapping for the classifications of the track in the type attribute. The usage in Germany is currently AFAIK:

  • Durchgehendes Hauptgleis; pro Betriebsstelle immer Eines bei je Eingleisiger und Zwei je zweigleisiger Strecken, mit Zugstraße
  • Hauptgleis; alle anderen Gleise mit mindestens einer Zugstraße
  • Nebengleis; alle anderen Gleise ohne Zugstraßen, nur Rangierfahrten
  • Gleisverbindung; Gleise ohne eigenen Verkehrswert, in Weichenverbindungen, Überleitungen

The mapping for mainTrack to Deutschland: durchgehendes Hauptgleis is nearby, but whats with the others:

  • secondaryTrack: This is a track not frequently used (e. g. for overtaking only).
  • connectingTrack: This is a transfer track from one to another track e. g. in branches, points or cross overs.
  • sidingTrack: This is a siding.
  • stationTrack: This is a track in a station, possibly with plattforms.
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.

Any opinions for railML® 2.x and for a refactoring in railML® 3.x? --Vasco Paul Kolmorgen (talk) 20:09, 10 April 2017 (CEST)