Search results
Jump to navigation
Jump to search
- TT:stopTimes stopDescription ocpTT ocpsTT patternTrainPart (section Scheme description / Schemenbeschreibung)used as a general input value for timetable planning (depending on the type of stop, vehicle type or train category among other things). In general, the time4 KB (507 words) - 13:04, 15 May 2024
- <connection> element. orientation: Orientation of the switch element relative to general track direction (aligned with increasing mileage) incoming: A track is merging5 KB (1,094 words) - 19:21, 22 January 2024
- siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional2 KB (379 words) - 12:35, 3 February 2022
- this use case. The use case covers the exchange of the following data in general: <train> elements with their routes and timings (in associated <trainPart>10 bytes (1,903 words) - 16:12, 3 February 2020
- Description: Infrastructure Managers (IM) wish to represent their railway system in terms of standardised data types. Eulynx collects the types and attributes10 bytes (450 words) - 16:12, 3 February 2020
- to structure an element documentation page within The railML® 2 wiki. A General outline for contibuting to this wiki can be found here. If you want to start7 KB (871 words) - 16:02, 3 April 2023
- UC:TT:FGIInTrain (section Description / Beschreibung)varies depending to the usage of the data. On the one hand there is the general data supply with the timetable e.g. for the next seven days in advance.10 bytes (677 words) - 16:12, 3 February 2020
- departure: xs:time; optional departureDay: xs:integer; default: 0; optional In general it is expected that all <times> instances of the same @scope are consistent23 KB (2,742 words) - 17:27, 24 September 2023
- optional Train City Night Line 242: <train id="o242" type="operational" description="Berlin - Paris" trainNumber="242"> <trainPartSequence sequence="1"> <7 KB (964 words) - 21:04, 22 January 2024
- Hardware and cable plan Subschema: Interlocking For general information on use cases see UC:Use cases10 bytes (119 words) - 16:12, 3 February 2020
- UC:IS:Timetabling (section Description / Beschreibung)Infrastructure Related subschemas: IL TT RS Reported by: ProRail For general information on use cases see UC:Use cases10 bytes (343 words) - 16:12, 3 February 2020
- Railway Infrastructure Visualisation (RAIV) Subschema: Infrastructure For general information on use cases see UC:Use cases10 bytes (180 words) - 16:12, 3 February 2020
- Infrastructure Reported by: Czech Technical University in Prague (ČVUT) For general information on use cases see UC:Use cases10 bytes (427 words) - 16:12, 3 February 2020
- of track assets Subschema: Infrastructure Related subschemas: IL For general information on use cases see UC:Use cases10 bytes (383 words) - 16:12, 3 February 2020
- Subschema: Infrastructure Related subschemas: IL Reported by: IS For general information on use cases see UC:Use cases10 bytes (367 words) - 16:12, 3 February 2020
- Subschema: Infrastructure Related subschemas: IL Reported by: JBD For general information on use cases see UC:Use cases10 bytes (198 words) - 16:12, 3 February 2020
- UC:TT:TAF/TAP TSI (section Description / Beschreibung)connections: <connection> element(s) with connType='commercial' stop description: only <stopDescription> elements with commercial='true' will be relevant including10 bytes (592 words) - 16:12, 3 February 2020
- select such a group and configure the toplogy would be useful. There is no description of this as of today. If RailML is introduced, the system will need to10 bytes (558 words) - 16:12, 3 February 2020
- scope='commercial' connections: <commercialConnection> element(s) stop description: only <stop> elements which contain a <isCommercial> elemente will be10 bytes (751 words) - 16:12, 3 February 2020
- Systems (SCWS) Subschema: Interlocking Reported by: Thales Austria For general information on use cases see UC:Use cases10 bytes (571 words) - 16:12, 3 February 2020
- Planning (MAPL) Subschema: Infrastructure Related subschemas: RS For general information on use cases see UC:Use cases10 bytes (133 words) - 16:12, 3 February 2020
- Network Statement (NEST) Subschema: Infrastructure Reported by: SŽDC For general information on use cases see UC:Use cases10 bytes (169 words) - 16:12, 3 February 2020
- Infrastructure Related subschemas: IL Reported by: RailComplete For general information on use cases see UC:Use cases10 bytes (127 words) - 16:12, 3 February 2020
- simulation Subschema: Rollingstock Related subschemas: IS IL TT For general information on use cases see UC:Use cases10 bytes (146 words) - 16:12, 3 February 2020
- System (PISY) Subschema: Infrastructure Related subschemas: TT RS For general information on use cases see UC:Use cases10 bytes (157 words) - 16:12, 3 February 2020
- UC:IS:NREReporting (section Description / Beschreibung)NRE Reporting Subschema: Infrastructure Reported by: ÖBB For general information on use cases see UC:Use cases10 bytes (225 words) - 16:12, 3 February 2020
- Operation and Control Subschema: Interlocking For general information on use cases see UC:Use cases10 bytes (209 words) - 16:12, 3 February 2020
- RINF-XML, and therefore support and maintain natively the railML3 RINF file description according to the evolutions of the project. The railML3 file for RINF10 bytes (297 words) - 16:12, 3 February 2020
- Speed directory Subschema: Infrastructure Reported by: ÖBB For general information on use cases see UC:Use cases10 bytes (117 words) - 16:12, 3 February 2020
- Positioning and Map-Matching (POSI) Subschema: Infrastructure For general information on use cases see UC:Use cases10 bytes (367 words) - 16:12, 3 February 2020
- Subschema: Infrastructure Related subschemas: TT RS Reported by: IS For general information on use cases see UC:Use cases10 bytes (306 words) - 16:12, 3 February 2020
- Infrastructure Recording Subschema: Infrastructure Reported by: Bahnkonzept For general information on use cases see UC:Use cases10 bytes (335 words) - 16:12, 3 February 2020
- supply simulation Subschema: Rollingstock Related subschemas: IS TT For general information on use cases see UC:Use cases10 bytes (236 words) - 16:12, 3 February 2020
- Timetable and Rostering Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases10 bytes (209 words) - 16:12, 3 February 2020
- Interlocking For general information on use cases see UC:Use cases10 bytes (828 words) - 16:12, 3 February 2020
- Topology (schematic drawing) on micro, meso and macroscopic level, with description of data (values and position) Timetable graph, Platform occupation diagram10 bytes (687 words) - 16:12, 3 February 2020
- Timetable and Rostering Related subschemas: IS IL RS Reported by: SMA For general information on use cases see UC:Use cases10 bytes (523 words) - 16:12, 3 February 2020
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (section Description / Beschreibung)Timetable and Rostering Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases10 bytes (355 words) - 16:12, 3 February 2020
- RailTopoModel® compliant railway network description enriched with the design layout and infrastructure description including also the essential information10 bytes (737 words) - 16:12, 3 February 2020
- UC:IL:Simulation (section Description / Beschreibung)instance routesetting. An interlocking is required to set and lock routes. A description of routes in terms of railML is of interest to both engineering and simulation10 bytes (969 words) - 16:12, 3 February 2020
- line network Construction: assets along the track / line Track layout description ETCS level transition locations Points Signals BaliseGroups (if available10 bytes (441 words) - 16:12, 3 February 2020
- Timetable and Rostering Related subschemas: IS RS Reported by: iRFP For general information on use cases see UC:Use cases10 bytes (688 words) - 16:12, 3 February 2020
- vehicle. The activities mentioned can be carried out one after the other. Description of parallel work is not included in this use case. For the purposes of10 bytes (926 words) - 14:45, 30 November 2023
- systems. The typically necessary data for this UC can be separated into 3 general domains: Infrastructure (RTCI-a) Rollingstock and (RTCI-b) Timetable (RTCI-c)10 bytes (860 words) - 16:39, 8 June 2023
- competition (call for proposals) Ausschreibungsfahrplan; ??? Description / Beschreibung / Description The use case describes a timetable which is transferred16 KB (2,372 words) - 16:07, 12 November 2021
- TMS Subschema: Infrastructure Reported by: DLR for In2Rail project For general information on use cases see UC:Use cases10 bytes (129 words) - 16:12, 3 February 2020
- Posession Management Subschema: Infrastructure For general information on use cases see UC:Use cases10 bytes (400 words) - 12:03, 18 July 2022
- Reason: In purely mesoscopic or macroscopic railway network descriptions a detailed description of operational routing (e.g. change of driving direction)29 KB (97 words) - 19:00, 22 January 2024
- Infrastructure Related subschemas: IL TT RS Reported by: Siemens Mobility For general information on use cases see UC:Use cases10 bytes (1,443 words) - 11:51, 18 July 2022