Search results

Jump to navigation Jump to search
  • to describe and validate that a <train> must reference one or more <trainPart>s, that all <trackElements> must have a position on the <track>, that the
    10 bytes (579 words) - 15:58, 18 May 2020
  • blockPartSequence   Parent: <block> Children: <blockPartRef>, <xs:any> (introduced with version 2.3) [1..∞] The element <blockPartSequence> groups the
    2 KB (231 words) - 22:04, 25 November 2018
  • following characteristics of <blockPart> are allowed: <blockPart> as a reference to a <trainPart>: mission=timetable trainPartRef has to be used; the other
    12 KB (1,612 words) - 12:52, 14 May 2024
  • block   Parent: <blocks> Children: <additionalName> (introduced with version 2.1), <blockPartSequence>, <xs:any> [1..∞] The element <block> contains all
    2 KB (511 words) - 20:23, 22 January 2024
  • TT:rostering (category Timetable Elements)
    Angabe bei blockPartSequence erfolgt defaultPostProcessingTime: This is the default duration from the end of blockPart until the end of blocking of the ressource
    7 KB (1,167 words) - 20:40, 22 January 2024
  • name, rail:lang, xsi:type <blockPartSequence> basicBlockRef, dayOffset, postProcessingTime, preProcessingTime, sequence <blockPartRef> ref <circulations> <circulation>
    112 KB (4,754 words) - 18:02, 3 April 2022
  • blockPartRef   Parent: <blockPartSequence> Children: None [1..∞] The element <blockPartRef> refers to blockParts for building sequences of tasks. In dem
    626 bytes (85 words) - 22:05, 25 November 2018
  • + <xs:keyref name="vehicle-blockPartKeyref" refer="rail:vehicleKey"> + <xs:selector xpath=".//rail:blockParts/rail:blockPart" /> + <xs:field xpath="@vehicleRef"
    531 KB (37,474 words) - 10:55, 8 October 2021
  • </xs:keyref> + <xs:keyref name="ocp-blockPartStartKeyref" refer="rail:ocpKey"> + <xs:selector xpath=".//rail:blockParts/rail:blockPart" /> + <xs:field xpath="@startOcpRef"
    331 KB (27,016 words) - 10:56, 8 October 2021
  • TT:ocpTT ocpsTT patternTrainPart (category Timetable Elements)
    defined in the infrastructure part, providing some timetable related information for it. In the British railway timetabling system the ocpTT is called TIPLOC
    5 KB (633 words) - 11:47, 9 October 2023
  • for RTPIS-own journeys. Commonly connections/transfers are not part of the imported timetable. These information belong to the responsibility of another RTPIS
    10 bytes (677 words) - 16:12, 3 February 2020
  • diff --git a/schema/timetable.xsd b/schema/timetable.xsd index 2a6c84d..30d721b 100644 --- a/schema/timetable.xsd +++ b/schema/timetable.xsd @@ -1,12 +1,16
    108 KB (9,484 words) - 10:56, 8 October 2021
  • <xs:selector xpath=".//rail:blockParts/rail:blockPart" /> <xs:field xpath="@endOcpRef" /> </xs:keyref> + <xs:keyref name="ocp-trainPartOrigin" refer="rail:ocpKey">
    398 KB (34,006 words) - 10:54, 8 October 2021
  • description="Bern-Muensingen-Thun"> <trainPartSequence sequence="1"> <trainPartRef ref="trainPart1001"/> </trainPartSequence> <replacements> <replacementOf> <operatingPeriodRef
    23 KB (104 words) - 11:10, 3 May 2022
  • TT:ocpTT ocpsTT trainPart (category Timetable Elements) (section Train(part)s with one <ocpTT> only)
    defined in the infrastructure part, providing some timetable related information for it. In the British railway timetabling system the ocpTT is called TIPLOC
    12 KB (1,526 words) - 18:09, 7 March 2024
  • name, rail:lang, xsi:type <blockPartSequence> basicBlockRef, dayOffset, postProcessingTime, preProcessingTime, sequence <blockPartRef> ref <circulations> <circulation>
    65 KB (2,931 words) - 12:19, 8 October 2021
  • name, rail:lang, xsi:type <blockPartSequence> basicBlockRef, dayOffset, postProcessingTime, preProcessingTime, sequence <blockPartRef> ref <circulations> <circulation>
    72 KB (3,235 words) - 11:59, 11 October 2021
  • /trains/train/trainPartSequence/brakeUsage/auxiliaryBrakes /rosterings/rostering/blockParts /rosterings/rostering/blocks/block/blockPartSequence /rosterings/ros
    20 KB (238 words) - 18:57, 22 January 2024
  • categoryKey category-trainPartKeyref category-trainPartSequenceKeyref category-formationKeyref speedProfileKey speedProfile-trainPartSequenceKeyref stopPostKey
    36 KB (103 words) - 13:54, 21 February 2022
  • + </xs:sequence> + </xs:complexType> + <xs:complexType name="eTrainPartSequence"> <xs:complexContent> <xs:extension base="rail:tTrainPartSequence"> @@ -712
    104 KB (9,170 words) - 10:56, 8 October 2021
  • necessary data. The basis for planning would be a timetable, or possibly even a rough timetable concept. As part of this use case, data that has been determined
    10 bytes (926 words) - 14:45, 30 November 2023
  • railML consumer. Mandatory information imported from timetable system includes: <train> <trainPart> <category> <ocp> Optionally imported information includes:
    6 KB (416 words) - 19:32, 15 December 2022
  • rostering TT:blockParts TT:blockPart TT:additionalName blockPart TT:blocks TT:block TT:additionalName block TT:blockPartSequence TT:blockPartRef TT:circulations
    58 KB (3,897 words) - 17:57, 3 April 2022
  • comment. -->{{docBase |element=blockPartRef |subschema=timetable |parent={{parent|subschema=timetable|name=blockPartSequence}} |attributes={{attribut|name=ref}}
    48 bytes (330 words) - 12:27, 15 January 2024
  • Element '''blockPartRef'''&lt;/noinclude&gt; {{Schemaexport |element=blockPartRef |subschema=timetable |parent={{parent|subschema=timetable|name=blockPartSequence}}
    491 bytes (49 words) - 14:49, 16 January 2023
  • Automatic Schemaexport for Element blockPartRef
    244 bytes (5 words) - 17:34, 19 October 2017
  • Automatic Schemaexport for Element blockPartRef
    244 bytes (5 words) - 17:33, 19 October 2017
  • Automatic Schemaexport for Element blockPartRef
    244 bytes (5 words) - 08:13, 19 October 2017
  • here) <TT:blockPart> TT:004 2019-07-20 2019-07-18 vehicleRef and formationRef shall not be used within the same blockPart, since a blockPart is either
    18 KB (3 words) - 14:06, 14 May 2024