Home » railML newsgroups » railML.infrastructure » Defintion of is::track type attribute
Re: Defintion of is::track type attribute [message #2370 is a reply to message #2303] Thu, 05 March 2020 15:02 Go to previous messageGo to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 68
Registered: March 2008
Member
christian.rahmig wrote on Mon, 06 January 2020 15:36
I am not sure if there is such a big difference between the different types of track (usage): In particular, for "sidingTrack" and "connectingTrack" the usage is the same like the possible usage. Major physical characteristics of the track are - so far - not modelled in railML.
Let's compare the attribute descriptions in the wiki and the referenced forum thread. The best practice section in the wiki lists national usage of @type in line with the forum discussion. (Skipping connectingTrack, where there are no big differences.)

mainTrack
  • Wiki, attributes: This is a regular track a of line used for frequent passenger and freight transport.
  • Wiki, best practice: NO: hovedtogspor/hovedspor, DE: Durchgehendes Hauptgleis, de-CH: Hauptgleis/Signalisiertes Gleis, fr-CH: Voie signalée, it-CH: Binario segnalato, NL: Hoofdspoorweg, CZ: Hlavní kolej
  • Forum: Main tracks of the line and their continuation in the station.
secondaryTrack
  • Wiki, attributes: This is a track not frequently used (e. g. loops for overtaking and/or crossing in stations).
  • Wiki, best practice: NO: togspor, DE: nicht-durchgehendes Hauptgleis, NL: Lokaalspoorweg, CZ: Spojovací kolej
  • Forum: Other signalised tracks (with train routes).
sidingTrack
  • Wiki, attributes: This is a siding.
  • Wiki, best practice: NO: øvrige spor/sidespor, DE: Nebengleis, de-CH: Nebengleis/Nicht-signalisiertes Gleis, fr-CH: Voie non-signalée, it-CH: Binario non segnalato, NL: Raccordement, CZ: Manipulační koleje
  • Forum: Non-signalised tracks (without train routes, but possibly shunting rountes)
So the attribute descriptions in the wiki describes mainTrack and secondaryTrack using the frequency of use, and doesn't really explain sidingTrack. In contrast the forum consensus uses properties of the infrastructure that determine the possible use (signalised or not, straight or not).

Thomas' suggested descriptions are quite close to the previous forum consensus, but I think it is best to avoid the term "commercial" and use "signalised" or "routes" rather than "train journeys".

Best,
Thomas


Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3.1] Modelling of a double slip switch
Next Topic: Definition of track/stoppingPlace/platform infrastructure vs. timetable
Goto Forum:
  


Current Time: Fri May 03 18:44:03 CEST 2024