Search results
Jump to navigation
Jump to search
- encode different types of stations in "macro" infrastructure models Connection between tracks Remarks and open issues on mileage changes (planned) IS:UseCases3 KB (350 words) - 19:56, 22 January 2024
- switch the connection between two subsequent tracks the insertion of a switch somewhere on a track a crossover between two parallel tracks a crossing of45 KB (5,550 words) - 18:04, 19 January 2024
- (nicht bei DB Netz) depot a train depot crossover a connection between two tracks of a double-track line Überleitstelle junction Junction: joining/splitting4 KB (602 words) - 12:22, 30 June 2023
- IS:connection crossing (section Position of connection in the XML-Tree / Position von connection im XML-Baum)separate, connecting track element was allowed, a special attribute denoted the length of the connection. See Dev:Connection_between_tracks. id: xs:ID, required2 KB (699 words) - 19:20, 22 January 2024
- IS:connection switch (section Position of connection in the XML-Tree / Position von connection im XML-Baum)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 information5 KB (1,094 words) - 19:21, 22 January 2024
- IS:connection trackEnd (section Position of connection in the XML-Tree / Position von connection im XML-Baum)point to the id of another <connection> Please also refer to Dev:Connection_between_tracks for information on how to use connections and switches/crossings211 bytes (148 words) - 16:28, 20 July 2022
- IS:connection trackBegin (section Position of connection in the XML-Tree / Position von connection im XML-Baum)point to the id of another <connection> Please also refer to Dev:Connection_between_tracks for information on how to use connections and switches/crossings215 bytes (148 words) - 11:12, 22 January 2013
- 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. The2 KB (1,151 words) - 16:06, 6 November 2022
- Experienced users Guide Dev:Tracks within and between the station a way to differentiate between tracks within and between stations using railML2 IS New8 KB (25 words) - 18:35, 5 February 2024
- trackEnd Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]4 KB (545 words) - 18:10, 22 March 2024
- Dev:Coding XML Components Dev:CommonDataTypes Dev:Common Concepts Dev:Connection between tracks Dev:Creating instructions Dev:Defaults Dev:Defining temporal availability202 bytes (229 words) - 18:26, 23 November 2020
- </connections> </trackTopology> </track> <track id="tr02"> <trackTopology> <trackBegin id="tb02" pos="0"> <connection id="tbcx02" ref="tecx01"/> </trackBegin>15 KB (1,768 words) - 18:26, 19 January 2024
- value="crossover"> + <xs:annotation> + <xs:documentation>a connection between two tracks of a double-track line </xs:documentation> + </xs:annotation> + </xs:enumeration>104 KB (9,170 words) - 10:56, 8 October 2021
- Possible values are: simpleCrossing: Two tracks are crossing without the possibility of changing between these two tracks. It allows going in 4 directions.2 KB (1,116 words) - 10:12, 28 June 2023
- id="inf01"> <tracks> <track id="tr1" ... type="mainTrack"> <trackTopology> <trackBegin pos="0.0" id="tr1_b"> <openEnd id="tr1_b_oe"/> </trackBegin> <trackEnd pos="100010 KB (1,182 words) - 19:33, 22 January 2024
- radius="0"/> </trackElements> </track> In this example, the first <radiusChange> point (rC0815) is situated at the connection of the straight track segment (A)9 KB (1,756 words) - 15:32, 25 March 2024
- 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 be20 KB (1,833 words) - 15:44, 10 October 2023
- referenced tracks are defined under <tracks>, and their begin and end reference the OCP ocp01: <tracks> <track id="tr01" code="401" name="1"> <trackTopology>9 KB (1,420 words) - 10:23, 1 February 2024
- IS:trackBegin (section Position of trackBegin in the XML-Tree / Position von trackBegin im XML-Baum)trackBegin Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]3 KB (483 words) - 10:48, 15 April 2024
- TT:connection (section Position of connection in the XML-Tree / Position von connection im XML-Baum)a specific connection between two trains. It is used to provide information to a connection management system to track connections between trains, detect25 KB (3,398 words) - 20:30, 22 January 2024
- 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 number10 bytes (579 words) - 15:58, 18 May 2020
- IS:openEnd (redirect from IS:openEnd trackBegin)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, or2 KB (511 words) - 19:44, 22 January 2024
- (IxL-data) describe the track-topology track-elements block-information speed limits in connection with specific elements of the track (especially switches)10 bytes (571 words) - 16:12, 3 February 2020
- and branching planned connection requirements with validity, source and target, minimum and maximum connection time, connection guaranteed flag, same platform10 bytes (355 words) - 16:12, 3 February 2020
- 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>398 KB (34,006 words) - 10:54, 8 October 2021
- <!-- connections --> - <!-- +- connection --> - <!----> - - <xs:complexType name="eConnectionsTT"> - <xs:sequence> - <xs:element name="connection" typ531 KB (37,474 words) - 10:55, 8 October 2021
- railway infrastructure elements that is used for logical locking connections between switches, derailers, level crossings, or other signalling components859 bytes (660 words) - 15:10, 23 May 2022
- <xs:element name="connection" type="rail:tSwitchConnectionData" maxOccurs="3" /> + <xs:element name="connection" type="rail:tSwitchConnectionData" maxOccurs="3">331 KB (27,016 words) - 10:56, 8 October 2021
- contents, for a through connection (connection without transfer for passengers), all elements <trainPart> which define a through connection shall have the same24 KB (3,449 words) - 18:37, 22 January 2024
- operational or the commercial view of the train run. Connections: The relevant connections/associations between trains at a particular operation or control point9 KB (916 words) - 12:29, 22 February 2024
- Dev:changes/2.3 (section Extend connection element)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 by20 KB (238 words) - 18:57, 22 January 2024
- 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 support108 KB (9,484 words) - 10:56, 8 October 2021
- Dev:changes/2.2 (section connection and annotationRef)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 by36 KB (103 words) - 13:54, 21 February 2022
- uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers. Maschineninterpretierbare Zeichenkette7 KB (1,167 words) - 20:40, 22 January 2024
- 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. A23 KB (104 words) - 11:10, 3 May 2022
- is supposed to be chronological. trackInfo: Textual description of station track for information purposes. The real track and platform information can and12 KB (1,526 words) - 18:09, 7 March 2024
- 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 use10 bytes (1,903 words) - 16:12, 3 February 2020
- the track network Nodes, edges Inner topology: connections between edges or marker at edges for correct routing at switches Geometry of the track network10 bytes (367 words) - 16:12, 3 February 2020
- <infrastructure>.<tracks>.<track>.<trackTopology>.<trackBegin>.<macroscopicNode>.ocpRef <infrastructure>.<tracks>.<track>.<trackTopology>.<trackEnd>.<macroscopicNode>16 KB (2,372 words) - 16:07, 12 November 2021