Home » railML newsgroups » railML.infrastructure » [railML3] Mandatory <length> element for <track>s
Re: [railML3] Mandatory <length> element for <track>s [message #2241 is a reply to message #2231] Thu, 29 August 2019 17:16 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 62
Registered: March 2015
Member
Dear Christian,

I haven't quite understood the background yet. Apparently the <length>
element is necessary to calculate the position of elements. But aren't
the positioning systems in the topology layer intended for this?
Apart from that, the scheme only specifies that I have to specify at
least one <length> sub-element for a <track> element, but not which one.
For example, it is possible to specify different <length> elements for
both directions or to distinguish between operational and constructional
length. This certainly makes sense for defining different operational
effective lengths of a track, but is not suitable for calculating
positions and distances.
If the <length> property must actually be mandatory, because it is
required for the calculation of positions, then it should also be forced
in the scheme that it is the structural length of the <track>, which
must also be identical for both directions.

Best regards Christian

--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 3.2] Extending enumeration for track condition areas
Next Topic: [railML 3.2] extending the <balise> element
Goto Forum:
  


Current Time: Thu May 02 22:40:57 CEST 2024