| Re: Partial Route [message #2023 is a reply to message #2017] |
Mon, 26 November 2018 06:14  |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
Dear Fabiana,
I have checked your proposal concerning <hasTvdSection> with the Norwegian model and the practise I knew from Thales.
Thus I have inserted this additional element into routes and overlap as optional, i.e. it is optional by the schema but
can be set mandatory by the use case. At least in IMED I have set it to mandatory.
The changes can be found in SVN trunk of railML3.
Regards,
Jörg v.Lingen - Interlocking coordinator
Fabiana Diotallevi wrote on 20.11.2018 11:41:
> Dear Joerg,
> it is true that the TVD sections composing the route could
> be derived from the topology: however, this would involve a
> quite complicated process, because it would mean to locate
> the starting and the end signal in the interlocking schema
> (and the switches too), find their referenced signals (and
> switches) in the infrastructure schema, find the netelements
> they belong to, link them to the trainDetectionElements and
> finally to the trackCircuits.
>
> Maybe it would be easier to add to <knowsRoute> a new
> mandatory tag <hasTvdSection> which lists all the
> TrackCircuits, and to leave the <hasReleaseGroup> tag
> optional (as it is today).
>
> What do you think?
>
> Regards,
>
> Fabiana
>
|
|
|
|
Members
Search
Help
Login
Home
