Search results
Jump to navigation
Jump to search
- electrificationSection Children None Attributes: requiresPowerLimitation: flag, whether a current or power limitation on board is required (optional; xs:boolean), permit1 KB (5 words) - 18:42, 19 December 2019
- Generic:limitsTrainDetectionElement of railML® version 3.2 Documentation If the current <trainDetectionElement> is an insulated rail joint or an axle counter and947 bytes (5 words) - 15:47, 17 May 2024
- responsible for RINF Reporting to the European Union. This use case describes the current structure of the yearly report of ÖBB Infrastructure in fulfillment of legal2 KB (225 words) - 13:45, 13 March 2023
- the command and the use of special texts as defined in <textMessage>. Currently there are only two levels foreseen. normal - The normal level applies to2 KB (255 words) - 15:33, 29 October 2023
- be saved in your current project folder, typically as "catalog.xml". Select "Options > Preferences ... > XML > XML Catalog". Add current catalog file with15 KB (1,996 words) - 12:36, 20 August 2021
- {{XsdType|<type-name>}} example: {{XsdType|string}} results in xs:string The current wiki does not support version management itself. That's the reason for the5 KB (572 words) - 15:29, 15 April 2024
- elements for vehicles with regeneration brake: propulsion (brakeCurrent[valueTable], brakeCurrentLimitation[valueTable], totalBrakeEfficiency/brakeVehicleEf2 KB (236 words) - 13:43, 13 March 2023
- Entwickler und Modellierer im railML-Umfeld. Under development since: Upcoming Current example version: Upcoming Subschemas: To be decided railML® Versions: To5 KB (674 words) - 15:49, 15 April 2024
- validity. The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure state. It is important4 KB (523 words) - 11:14, 18 July 2022
- frequency in Hertz in case of a track circuit. Shall be zero for direct current. (optional; xs:decimal; minInclusive: 0; fractionDigits: 3), id: unique2 KB (5 words) - 14:21, 24 January 2020
- to become a common base for the related abovementioned applications. The current data flows – concerning the trackside model infrastructure, rolling stocks3 KB (427 words) - 17:57, 27 June 2022
- railML®. See Dev:Downloading_and_using_railML® to learn how to obtain the current schema, or download it directly from https://www.railml.org/en/developers/download5 KB (671 words) - 17:12, 3 April 2023
- for the TVD section in case of a track circuit. Shall be zero for direct current. (optional; xs:decimal; minInclusive: 0; fractionDigits: 3), isBerthingTrack:3 KB (5 words) - 15:47, 17 May 2024
- used to reference this element within railML. @indicatorType - There is currently only cautiousDriving defined for use. Other values might be defined to2 KB (240 words) - 13:40, 28 May 2022
- including all concepts and data required. In a first step, considering the current non-acceptance of the railML® standard by ERA, this railML3 file will be3 KB (297 words) - 13:49, 13 March 2023
- of regular trains. This planning will always be done with regard to the current operational situation. This means that the actual state of the railway network16 KB (1,744 words) - 18:21, 13 May 2024
- elements and attributes. There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.964 bytes (88 words) - 19:16, 29 January 2020
- elements and attributes. There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.2 KB (218 words) - 19:17, 29 January 2020
- elements and attributes. There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.3 KB (405 words) - 15:00, 27 May 2022
- g. xmlns="https://www.railml.org/schemas/2009" Reason Depending on the current policy only Subversion commits for corrigendum, minor or major railML® releases9 KB (1,043 words) - 15:24, 10 June 2024