Home » railML newsgroups » railML.infrastructure » [railML3] Mandatory <length> element for <track>s
Re: [railML3] Mandatory <length> element for <track>s [message #2254 is a reply to message #2249] Mon, 07 October 2019 21:33 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Fabiana,

Am 17.09.2019 um 09:38 schrieb Fabiana Diotallevi:
> [...] I also agree to make the track length optional.

Thank you for your feedback!

> 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.

The answer to the question "What is the leading system for defining the
location reference?" is somewhat use case specific. There are scenarios
where the line kilometer system is the primary information and the
intrinsic coordinates are derived from this, but the other scenario
exists as well. railML shall suit all the different scenarios and
related use cases. Therefore, its syntax provides elements/attributes
for both, the intrinsic and the "extrinsic" location.

> 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.

That's a good idea! We at railML.org are interested in "real world
examples" and data sets. So, if you can show that the concept of
mandatory intrinsic coordinates works for your use case (SCTP -
Schematic Track Plan), we may cross-check this approach with other use
cases, too, and learn from the results. Probably, you can present first
experiences at the next railML Conference taking place in Brussels on
November 6, 2019?

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org


Christian Rahmig – Infrastructure scheme 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
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 18:19:10 CEST 2024