Home » railML newsgroups » railml.infrastructure » Infrastructure data for a train path finding tool - #2, microscopic view (How to represent data required by a train path finding tool in railmL2.4?)
Infrastructure data for a train path finding tool - #2, microscopic view [message #2508] Wed, 29 July 2020 14:08
Rüdiger Ebendt is currently offline  Rüdiger Ebendt
Messages: 3
Registered: July 2020
Junior Member
Hi everyone,

this is again from Ruediger Ebendt, staff at the Institute of Transportation Systems, German Aerospace Center (DLR). This post addresses the same use case as in my previous post (https://www.railml.org/forum/index.php?t=msg&goto=2507), but looking at a different level.

Some of the pieces of data we need to represent in railML2.4 (for the purpose of an import interface of a train path finding tool) belong to a microscopic view on the infrastructure (maybe, some of these even belong to interlocking instead of infrastructure). These pieces of data are (original German terms in square brackets):

- train control system (i.e. ETCS, LZB): begin, block sign, end, clearing point [Zugsicherungstechnik: Anfang, Blockkennzeichen, Ende, Zugschlussstelle]
- route (including an exact description of all negotiated route elements, exclusions and of the overlap) [Fahrstraße (inkl. einer exakten Beschreibung der befahrenen Fahrwegelemente, der Ausschlüsse und des Durchrutschwegs)]
- route clearing point [Fahrstraßenzugschlussstelle]
- overhead line section [Oberleitungsschaltgruppe]
- signal clearing point [Signalzugschlussstelle]
- operational procedures (e.g. direct traffic control (DTC)) [Betriebsverfahren, z.B. Zugleitbetrieb]

Thank you very much for your help!

Kind regards
Ruediger Ebendt

[Updated on: Wed, 29 July 2020 14:14]

Report message to a moderator

Previous Topic: Infrastructure data for a train path finding tool
Goto Forum:

Current Time: Wed Aug 12 14:26:39 CEST 2020