Search results

<controllers>, <speedProfiles>, <states> (introduced with version 2.4), <routes> (introduced with version 2.5), <operatingRules> (introduced with version

into NEST March 13th 2023 by User:RailML Coord Documentation IL IS 3.1 3.2 X Routes for timetable simulation (former: Capacity operational simulation) Fahrstrassen

IS:route   Parent: <routes> Children: <additionalName>, <switchAndPosition>, <overlapSwitchAndPosition>, <releaseGroup>, <states> [1..1] A route is a central

IS:state   Parent: <states> Children: <designator> (introduced with version 2.5), <xs:any> [1..1] This is to define disabled/enabled infrastructure pieces

IS:routes   Parent: <infrastructure> Children: <route> [0..1] Container to define routes within the infrastructure. None None Not yet described. / Noch

controlled for the route to be set. As some track sections are included to form flank protection (and are thus not part of the routes path), they have to

trains that are already planned in the timetable planning. This means that routes with corresponding travel times through the network are already planned

uses the elements in the infrastructure to ensure safety and make train routes. In Norway there are also dependencies between the infrastructure and the

alternative routes, mutually exclusive routes, etc. Consider for instance routesetting. An interlocking is required to set and lock routes. A description

primary The main path or route of the train. Der Hauptlauf des Zuges (auch "Stammfahrplan" genannt). secondary An alternative path or route of the train. "Nebenlauf"

As some switches are not part of the routes path but have to be controlled to perform flank protection for the route, they have to be included and declared

version 2.4) controller software version routeSetTime: (introduced with version 2.5) The technical time for the route to be set by the CTC and interlocking

also analyses the logical relations that exist between elements in terms of routes, flank protection<br />The result of this analysis is called a data platform

Permission/operating zones including shunting areas for temporary local operation Routes infrastructure This section serves to specify the required data regarding

5): mandatory flag for differentiation between boards and signals maskableRoute (deprecated with version 2.4) maskableATC (deprecated with version 2.4) virtual:

times on the stations, different operating days or lengths of the running routes are permissible. Please also refer to the notes section below for further

station. The size of the railML IL file grows linearly with the number of routes and exponentially with the number of network nodes. Signalling Schematic

horizon. Details: for conflict detection on micro-level of the topology, routes and route-dependancies (flank-protections) are required for both safety and capacity

for other elements based on coordinates Parameters of software elements (routes, flank protection for switches etc.) yearly monthly weekly daily very small

allow that one train (to be exactly: one train number) may have different routes or slots at different operating days. In contrast, 'Coupling & Sharing'

exchanged is bigger than in use case ETCS-a because data such as balises or routes will be added. The amount of the data to be exchanged is the same as in

bases. IL This interference to interlocking relates to the visualization of routes and their attributes (ATP device type, CTC handling, overlap/safety zone/slip

journeys, usually on the same route, in the sense of a sequence of stops and journey times (start and end on this route may be different) for easier identification

additionalName   Parent: <route> Children: None [0..∞] The element <additionalName> provides additional names with descriptions in other languages, dialects

operation, the route and trains are secured and the elements of the route are controlled by radio. The special feature is that the route elements are controlled

primary The main path or route of the train. Der Hauptlauf des Zuges (auch "Stammfahrplan" genannt). secondary An alternative path or route of the train. "Nebenlauf"

startTime, status <designator> endDate, entry, register, startDate <routes> <route> approachPointRef, approachSpeed, code, conditional, description, entryRef

operation, the route and trains are secured and the elements of the route are controlled by radio. The special feature is that the route elements are controlled

operation, the route and trains are secured and the elements of the route are controlled by radio. The special feature is that the route elements are controlled

timetable is asked for in the competition, i. e. the amount of trains, their routes and (regular) operating days and possible any other properties of the trains

occupation of route by another train running ahead für Halte wegen vorausfahrenden Zuges occupationCrossing: Kreuzung Stop caused by occupation of route by an

operation, the route and trains are secured and the elements of the route are controlled by radio. The special feature is that the route elements are controlled

If a train is not included in the railML® file with its entire itinerary and already has a midnight transition before "entering" the railML® file network

A speed change is treated as not pre-signalised if there is at least one route at which a train can pass the speed change decreasing and did not pass any

by the trainborne equipment. When an ETCS vehicle is used on a non-ETCS route this is known as Level 0. The trainborne equipment monitors the train for

This article explains basic concepts: How to encode different types of stations in "macro" infrastructure models. Dieser Artikel erklärt Grundlagen des

than one train part either in one section or in subsequent sections of its route. There may be several elements <trainPartRef> with the same position if the

departure, and run through times of the (operational) train until the end of its route are marked with arrivalDay=1 and departureDay=1. Although the <operatingPeriod>

by the trainborne equipment. When an ETCS vehicle is used on a non-ETCS route this is known as Level 0. The trainborne equipment monitors the train for

represent locations which the <trainPart> passes, the <ocpsTT> contains the route of a train through the network. Das Element <ocpsTT> als Container fasst

IS:additionalName propOther IS:additionalName radiusChange IS:additionalName route IS:additionalName serviceSection IS:additionalName signal IS:additionalName

sequence herein is supposed to be used for successive parts along the train route. This is not to be mixed up with the sequence of rolling stock inside a train

to true if the referenced track is not part of the path of the route but gives the route flank protection. ref: xs:IDREF flankProtection: xs:boolean, optional

IS:overlapSwitchAndPosition   Parent: <route> Children: None [0..∞] (introduced with version 2.5) A path for the route overlap is unambigituously defined by

buffers) on the line (especially on bridges). Typical value for the widely used route class D4 is 8.0 tonnes. Die Meterlast beschreibt die maximale Last, die das

different sections of the train’s route. The many long-distance trains which run empty before and after their published route are examples from practice for

buffers) on the line (especially on bridges). Typical value for the widely used route class D4 is 8.0 tonnes. Die Meterlast beschreibt die maximale Last, die das

is multiple stations/stopping points. This may also be useful when doing routing through a rail network. Transfer between stations that are grouped like

herein is supposed to be used for successive parts along the (pattern) train route. This is not to be mixed up with the sequence of rolling stock inside a (pattern)

Competency Management) SJN no: Strekningsbeskrivelse for jernbanenettet Bane NOR "Route description for the rail network" for the Norwegian rail network owned by

<xs:element name="routes" type="rail:eRoutes" minOccurs="0"> + <xs:annotation> + <xs:documentation>See https://wiki2.railml.org/wiki/IS:routes</xs:documentation>

timetable is asked for in the competition, i. e. the amount of trains, their routes and (regular) operating days and possible any other properties of the trains

branch line is a railway line which branches off a more important through route, usually a main line. These lines have mainly local traffic only, lower speeds

<topologyReference> element, the underlying topology used to determine the route and calculate journey times can be referenced. A <topologyReference> can

<xs:attribute name="maskableRoute" type="xs:boolean" /> - <xs:attribute name="maskableATC" type="xs:boolean" /> + <xs:attribute name="maskableRoute" type="xs:boolean">

machines, number of axle counters, number of signals, …) Network components (router, switches, cable) Power supply Technical room, number of CPU boards, Container

time a train moves from one infrastructure element (e.g. track section, route, station, train number field, timetable element) to the next. For example

of this SCWS (stationary, ETCS Level 1, ETCS Level 2) Supervision of free route in seconds Workplace data Element names Tracks Switches Regular Switches

Statement covers the requirements for access and use of the rail network (route network) of the infrastructure manager. It provides all the technical and

override sections technical control system documentation VzG protection route technical control system documentation VzG signals technical control system

altitude (polyline) Geometry: Track curvature Topology: Node-link model Route IDs Track IDs Mileposts / kilometre posts id, location Junctions id, location

Zugfolgeabstand für Halte wegen vorausfahrenden Zuges Stop caused by occupation of route by another train running ahead Zugfolgeänderung, Abwarten Zugfolgezeit occupationCrossing

timetable, but contain sufficient information about trains to identify them, route them through the infrastructure and state their validity. The infrastructure

changes speeds deflecting speeds gradients tunnel (resistance) (main)signal & route clearance operational rules*** electrification train protection system restrictions

Another use case is the exchange of changed planning data. For example, if a route cannot be travelled due to construction work and trips that were assigned

dir, distNearestDangerPoint, function, height, id, maskableATC, maskableRoute, name, ocpStationRef, pos, rail:lang, ruleCode, sigSystem, sight, signalBoxOcpRef

macroscopic railway network descriptions a detailed description of operational routing (e.g. change of driving direction) was not possible; especially within OCP

dir, distNearestDangerPoint, function, height, id, maskableATC, maskableRoute, name, ocpStationRef, pos, rail:lang, ruleCode, sigSystem, sight, signalBoxOcpRef

<xs:attribute name="switchable" type="xs:boolean" /> - <xs:attribute name="maskableRoute" type="xs:boolean" /> - <xs:attribute name="maskableATC" type="xs:boolean"

ation> + </xs:annotation> + </xs:attribute> <xs:attribute name="maskableRoute" type="xs:boolean" /> <xs:attribute name="maskableATC" type="xs:boolean"