Home » railML newsgroups » railml.common » [railML3] Refactoring of states (e.g. infrastructure states)
Re: [railML3] Refactoring of states (e.g. infrastructure states) [message #3376 is a reply to message #3375] Fri, 25 October 2024 14:04 Go to previous messageGo to previous message
Torben Brand is currently offline  Torben Brand
Messages: 180
Registered: March 2016
Senior Member
Dear Thomas,
Jernbanedirektoratet agree with setting elementState on track instead of netElements (as they are abstract). The solution with setting start and end validity for organizationalUnit is fine for us.

Jernbanedirektoratet disagrees with not giving geometry elements like gradientCurve an elementState. This as we often have plans that have objects planned on the track, but the gradients have not been planned yet, but we need them for RTC. The gradients are thus estimated and get a state different from the track with the value "conceptual".

Furthermore the gradients can be individually defined in RailOscope and we need to exchange the information with Bane NORs new DIM tool.

Thus, we hope to have the possibility to set elementState on gradient (and horizontal) curves as an optional item in railML3.3.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Additional Attributes for Revision Management
Next Topic: RE: [railML3] Refactoring of OrganizationalUnits
Goto Forum:
  

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

Current Time: Sun May 18 22:33:09 CEST 2025