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

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

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

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'