Home » railML newsgroups » railml.timetable » [railML3]: Code points in routes used for TMS
[railML3]: Code points in routes used for TMS [message #2770] Fri, 25 June 2021 10:26 Go to next message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 61
Registered: March 2016
Dear all,

I received a request to introduce Codepoints (and LS-Codepoints): which are fixed points on the infrastructure,
primarily associated with driving paths - thus linked to signals. A special type of LS-Codepoints are also used to
denote the place where the train identifiers will be displayed on the GUI (berths).

In the discussion it was stated the special type for display of train identifiers can be the already developed
"trainNumberField" in interlocking, which refers to "tvdSection" concerning train location.

The code points associated with driving path needs to be added in the route definition in order to identify alternative
paths (red line in attached sketch with code points "503" and "509"). The idea was to refer to "trackIL" elements as
code points from the route.

Questions to you:
1) Would this fulfil your needs? Remember "trackIL" refers to "track" in IS, which is a part of a "netElement".

2) Would you need code points at route entry and route exit, as well?

3) Would you require for the code points to refer only to a spotLocation instead of a linearLocation like "track" has?
If so, what kind of infrastructure element shall be referred to?

Your opinions on the issue are welcome.
Jörg von Lingen - Interlocking Coordinator


[Updated on: Sun, 25 July 2021 16:09] by Moderator

Report message to a moderator

Re: [railML3]: Code points in routes used for TMS [message #2794 is a reply to message #2770] Mon, 19 July 2021 19:37 Go to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 76
Registered: April 2007
Hi Jörg,

could you please point out the relation to timetable (if thats not exactly whats included in the attachment). As I understand it, we are talking about points that are static and dependend on infrastructure and interlocking, rather than varying between one train on a route and the next.

Best regards,

Milan Wölke - Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Sun, 25 July 2021 16:09] by Moderator

Report message to a moderator

Previous Topic: [railML3] supported time scopes in railML 3.2
Next Topic: [railML2] New concept LineTT
Goto Forum:

Current Time: Mon Sep 20 21:41:38 CEST 2021