Home » railML newsgroups » railML.infrastructure » <track>@mainDir
Re: <track>@mainDir [message #1711 is a reply to message #1710] Fri, 23 February 2018 15:33 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian,

we do not use <track>.@mainDir. We would not miss it.

We use <sectionTT>.@trackInfo with:
=1 for "regular track" (dt: Regelgleis)
=2 for "track of the opposite direction" (dt: Gegengleis).

This usage of <sectionTT>.@trackInfo is redundant to <sectionTT>.<trackRef>.@ref: If a train runs on the Gegengleis (<sectionTT>.@trackInfo='2'), it has also <sectionTT>.<trackRef>.@ref set to the proper track of the opposite direction.

This redundancy is a "short-cut" for cases if there is no full <infrastructure> at the railML file or if a reading software does not like the effort of parsing the <infrastructure>.

In spite of there is a (small) usage of "regular direction" and "wrong direction", it is rather a short-cut around the infrastructure details but not necessarily a demand for infrastructure. It could explain why somebody could want to define a regular direction of tracks. But it is not so obvious or demanding that we (iRFP) need it. So again: no opposition from us against deprecating of <track>.@mainDir.

Dirk.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: infrastructure "state"
Next Topic: Published railML extension railML2.4nor (IS)
Goto Forum:
  


Current Time: Tue Apr 30 20:57:20 CEST 2024