Search results

Jump to navigation Jump to search
Results 1 – 13 of 13
Advanced search

Search in namespaces:

  • Dev:Semantic Constraints (category GeneralDescription)
    that it does not make sense to specify a stopOnRequest and at the same time that the train is not allowed to stop. Such rules restricting the contents, or
    4 KB (579 words) - 16:49, 13 March 2023
  • This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    522 bytes (38 words) - 21:56, 25 April 2022
  • UC:TT:TimetableInformation (category Use case (TT)) (section Description / Beschreibung)
    <baseItineraryPoint> elements with commercially relevant stops (<stop> with an <isCommercial> element). For the each stop the following data is shown: published times:
    5 KB (751 words) - 13:28, 13 March 2023
  • Logical Train Positions Subschema: Infrastructure   Related subschemas: IL TT RS  Reported by: Siemens Mobility For general information on use cases see
    16 KB (1,407 words) - 11:50, 18 July 2022
  • UC:TT:TAF/TAP TSI (category Use case (TT)) (section Description / Beschreibung)
    with a sequence of <ocpTT> elements with commercially relevant stops (<stopDescription> with commercial='true'). For the each stop the following data is
    4 KB (592 words) - 18:06, 7 December 2023
  • UC:TT:SlotOrdering (category Use case (TT)) (section Description / Beschreibung)
    departure Minimum stop time Stop type, stop description Commercial connections Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight
    2 KB (273 words) - 13:26, 13 March 2023
  • UC:TT:RunTimeCalculationInput (category Use case (TT)) (section Description / Beschreibung)
    frequency. Typically timetable data is exchanged on a macroscopic level, so that stop patterns of the trains can be described. It should however also be possible
    6 KB (858 words) - 12:09, 25 March 2024
  • TT:reserves TT:routeRef TT:routeRefs TT:rule TT:startPoint TT:stop:activities TT:stop:announcements TT:stop:passengerTextInfos TT:stoppingPlaceRef TT:tafTapTsiId
    3 KB (756 words) - 14:47, 27 June 2022
  • railway undertakings (//organizationalUnit/isRailWayUndertaking)) stop types (<stop>/<pass>) train status, information about the planning state of the
    4 KB (523 words) - 11:14, 18 July 2022
  • <infrastructure> is referenced from <ocpTT>.ocpRef to <ocp>.id (mandatory), from <sectionTT>.lineRef to <line>.id (optional), from <sectionTT>.<trackRef>.ref to <track>
    16 KB (1,903 words) - 13:27, 13 March 2023
  • Autoexport from the XML-Schema for element TT:transportServiceRef of railML® version 3.2 UML-visualization of TT Documentation Allows referencing a transport
    2 KB (5 words) - 12:43, 8 February 2024
  • UC:TT:IntegratedTMS (category Use case (TT)) (section Description / Beschreibung)
    shall stop. Timetable can optionally reference to a specific route. The Stop Description (Stop, No Stop, Stop on Demand, Stop only for Exit, Stop only for
    16 KB (1,744 words) - 18:21, 13 May 2024
  • vary per itinerary section), including coupling and branching of trains Stops, stations, tracks, track sections. They should refer to a validity, possibly
    3 KB (355 words) - 18:11, 27 June 2022