Search results

encode different types of stations in "macro" infrastructure models Connection between tracks Remarks and open issues on mileage changes (planned) IS:UseCases

switch the connection between two subsequent tracks the insertion of a switch somewhere on a track a crossover between two parallel tracks a crossing of

(nicht bei DB Netz) depot a train depot crossover a connection between two tracks of a double-track line Überleitstelle junction Junction: joining/splitting

separate, connecting track element was allowed, a special attribute denoted the length of the connection. See Dev:Connection_between_tracks. id: xs:ID, required

cases the connection from tr1 to tr2 is "right" and the connection from tr1 to tr3 is "straight". Please also refer to Dev:Connection_between_tracks for information

point to the id of another <connection> Please also refer to Dev:Connection_between_tracks for information on how to use connections and switches/crossings

point to the id of another <connection> Please also refer to Dev:Connection_between_tracks for information on how to use connections and switches/crossings

refer to Dev:Connection_between_tracks for further information on how to use switches. Positive pos values describe the distance from the track's begin. The

Experienced users Guide Dev:Tracks within and between the station a way to differentiate between tracks within and between stations using railML2 IS New

trackEnd   Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]

Dev:Coding XML Components Dev:CommonDataTypes Dev:Common Concepts Dev:Connection between tracks Dev:Creating instructions Dev:Defaults Dev:Defining temporal availability

</connections> </trackTopology> </track> <track id="tr02"> <trackTopology> <trackBegin id="tb02" pos="0"> <connection id="tbcx02" ref="tecx01"/> </trackBegin>

value="crossover"> + <xs:annotation> + <xs:documentation>a connection between two tracks of a double-track line </xs:documentation> + </xs:annotation> + </xs:enumeration>

Possible values are: simpleCrossing: Two tracks are crossing without the possibility of changing between these two tracks. It allows going in 4 directions.

id="inf01"> <tracks> <track id="tr1" ... type="mainTrack"> <trackTopology> <trackBegin pos="0.0" id="tr1_b"> <openEnd id="tr1_b_oe"/> </trackBegin> <trackEnd pos="1000

radius="0"/> </trackElements> </track> In this example, the first <radiusChange> point (rC0815) is situated at the connection of the straight track segment (A)

that station. The rest of the tracks are segments. A line is a sequence of tracks “between” and “within” a station. Each track of a line sequence shall be

referenced tracks are defined under <tracks>, and their begin and end reference the OCP ocp01: <tracks> <track id="tr01" code="401" name="1"> <trackTopology>

trackBegin   Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]

a specific connection between two trains. It is used to provide information to a connection management system to track connections between trains, detect

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>