Search results

must reference one or more <trainPart>s, that all <trackElements> must have a position on the <track>, that the length of a <tunnel> is a decimal number

indicates that a track is terminated without any possibility for trains to enter or leave the track. The <connection> in other <trackBegin>s and <trackEnd>s, or

(IxL-data) describe the track-topology track-elements block-information speed limits in connection with specific elements of the track (especially switches)

and branching planned connection requirements with validity, source and target, minimum and maximum connection time, connection guaranteed flag, same platform

short and connect other tracks. Examples are short track sections connecting two tracks where switches allow to move from one track to the other. </xs:documentation>

<!-- connections --> - <!-- +- connection --> - <!----> - - <xs:complexType name="eConnectionsTT"> - <xs:sequence> - <xs:element name="connection" typ

railway infrastructure elements that is used for logical locking connections between switches, derailers, level crossings, or other signalling components

<xs:element name="connection" type="rail:tSwitchConnectionData" maxOccurs="3" /> + <xs:element name="connection" type="rail:tSwitchConnectionData" maxOccurs="3">

contents, for a through connection (connection without transfer for passengers), all elements <trainPart> which define a through connection shall have the same

operational or the commercial view of the train run. Connections: The relevant connections/associations between trains at a particular operation or control point

railML® schema changes between railML® 2.2 and railML® 2.3   This site is intended to collect the schema changes between railML® 2.2 and railML® 2.3 by

Schema differences between railML® 2.2 and railML® 2.3 This page shows schema differences between railML® 2.2 and railML® 2.3. It is intended to support

railML® schema changes between railML® 2.1 and railML® 2.2   This site is intended to collect the schema changes between railML® 2.1 and railML® 2.2 by

uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers. Maschineninterpretierbare Zeichenkette

railML® schema changes between railML® 2.3 and railML® 2.4   This site is intended to collect the schema changes between railML® 2.3 and railML® 2.4. A

is supposed to be chronological. trackInfo: Textual description of station track for information purposes. The real track and platform information can and

not allow a distinction between values which are the minimum necessity and which are planned. There may be a difference between them especially in the use

the track network Nodes, edges Inner topology: connections between edges or marker at edges for correct routing at switches Geometry of the track network

<infrastructure>.<tracks>.<track>.<trackTopology>.<trackBegin>.<macroscopicNode>.ocpRef <infrastructure>.<tracks>.<track>.<trackTopology>.<trackEnd>.<macroscopicNode>