Search results
Jump to navigation
Jump to search
- 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 determined10 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:circulations58 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'''</noinclude> {{Schemaexport |element=blockPartRef |subschema=timetable |parent={{parent|subschema=timetable|name=blockPartSequence}}491 bytes (49 words) - 14:49, 16 January 2023
- Automatic Schemaexport for Element blockPartRef244 bytes (5 words) - 17:34, 19 October 2017
- Automatic Schemaexport for Element blockPartRef244 bytes (5 words) - 17:33, 19 October 2017
- Automatic Schemaexport for Element blockPartRef244 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 either18 KB (3 words) - 14:06, 14 May 2024