Search results

Jump to navigation Jump to search
  • horizon. Details: for conflict detection on micro-level of the topology, routes and route-dependancies (flank-protections) are required for both safety and capacity
    10 bytes (343 words) - 16:12, 3 February 2020
  • for other elements based on coordinates Parameters of software elements (routes, flank protection for switches etc.) yearly monthly weekly daily very small
    10 bytes (367 words) - 16:12, 3 February 2020
  • 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
    1 KB (1,457 words) - 21:00, 25 November 2018
  • 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
    10 bytes (441 words) - 16:12, 3 February 2020
  • 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
    9 KB (1,526 words) - 16:19, 20 May 2024
  • 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
    958 bytes (951 words) - 20:19, 13 December 2021
  • bases. IL This interference to interlocking relates to the visualization of routes and their attributes (ATP device type, CTC handling, overlap/safety zone/slip
    10 bytes (198 words) - 16:12, 3 February 2020
  • occupation of route by another train running ahead für Halte wegen vorausfahrenden Zuges occupationCrossing: Kreuzung Stop caused by occupation of route by an
    12 KB (1,375 words) - 12:14, 24 January 2022
  • 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
    1 KB (1,558 words) - 20:14, 13 December 2021
  • 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
    1 KB (1,452 words) - 14:01, 16 November 2022
  • 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
    8 KB (1,098 words) - 18:21, 19 January 2024
  • represent locations which the <trainPart> passes, the <ocpsTT> contains the route of a train through the network. Das Element <ocpsTT> als Container fasst
    1 KB (134 words) - 17:14, 24 September 2023
  • This article explains basic concepts: How to encode different types of stations in "macro" infrastructure models. Dieser Artikel erklärt Grundlagen des
    16 KB (1,299 words) - 15:29, 20 May 2024
  • 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
    2 KB (238 words) - 23:05, 25 November 2018
  • 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
    2 KB (1,354 words) - 17:25, 15 February 2021
  • 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
    443 bytes (736 words) - 22:11, 25 November 2018
  • 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>
    19 KB (2,347 words) - 18:40, 19 January 2024
  • 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
    10 bytes (1,903 words) - 16:12, 3 February 2020
  • 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
    10 KB (1,890 words) - 15:25, 25 March 2024
  • 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
    600 bytes (86 words) - 10:23, 28 March 2023
View ( | ) (20 | 50 | 100 | 250 | 500)