Home » railML newsgroups » railML.infrastructure » [railML3] Mandatory <length> element for <track>s
Re: [railML3] Mandatory <length> element for <track>s [message #2249 is a reply to message #2244] Tue, 17 September 2019 09:38 Go to previous messageGo to previous message
Fabiana Diotallevi is currently offline  Fabiana Diotallevi
Messages: 21
Registered: October 2018
Junior Member
Dear all,
I also agree to make the track length optional.

As suggested by Christian, the position of all the involved elements should be derived from the topology layer defined by the netElements, which provide with their intrinsic coordinates a reference to the specific used positioning systems (linear or geometric).
I think that the netElements should be the "building blocks" that, alone, are able to define the link between the "logical" and the "real" world: any other element position should be derived from the reference system defined by the netElements network.

To check the stability of this assert we are currently implementing the automatic import/export of railML 3.1 data on our RaIL-AiD tool by making the intrinsic coordinate definition mandatory for all the netElements.

Report message to a moderator

[Message index]
 
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:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri May 03 02:37:50 CEST 2024