Search results
Jump to navigation
Jump to search
- comprises the feedpoint at the next signal, one running rail, first locomotive axle, another running rail and back to the signal feedpoint. The resulting electromagnetic9 bytes (951 words) - 14:49, 16 January 2023
- axleWeightChange Parent: <axleWeightChanges> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0..∞] A <axleWeightChange>9 bytes (841 words) - 14:49, 16 January 2023
- clearanceGaugeChange Parent: <clearanceGaugeChanges> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states>, <clearanceGauge>9 bytes (809 words) - 14:49, 16 January 2023
- formation Parent: <formations> Children: <additionalName> (introduced with version 2.1), <trainOrder>, <categoryRef>, <trainEngine>, <trainBrakes>,17 bytes (1,075 words) - 14:49, 16 January 2023
- GPSinfradat (link to the railML® website). View/edit list on the separate source page. Template:Table/RailML Coord Documentation/IS:levelCrossing levelCrossings9 bytes (1,006 words) - 14:49, 16 January 2023
- derived from tMeterLoad, optional Consider railML® 2.3 example of Middle Rhine Railway by GPSinfradat (link to the railML® website). The map source is https://www9 bytes (1,080 words) - 14:49, 16 January 2023
- bridge, other:[any], optional A car ramp shall be modelled using the existing railML® element <serviceSection> together with boolean attribute @ramp="true".9 bytes (1,106 words) - 14:49, 16 January 2023
- Codelist-tags ✔ RailML Coord Documentation (talk) 15:09, 3 April 2023 (CEST) Dev:TrainProtectionSystems Problem: Codelist-tags ✔ RailML Coord Documentation (talk)10 bytes (363 words) - 19:46, 15 December 2022
- beschrieben. Jernbanedirektoratet railML® 2.4 glossary (external link) Description of the FBS railML® interface (external link) railML® 3.1 Tutorial Simple Example9 bytes (1,147 words) - 14:49, 16 January 2023
- since the release of railML 2.2, all tools in productive use shall use *.railml for files / exports. *.xml is always allowed since railML® files are xml files11 KB (1,751 words) - 14:49, 16 January 2023
- concrete-made tunnel with two tracks. Bis einschließlich Version 2.3 hat railML® den Ansatz verfolgt, alle physikalischen Parameter, welche den Tunnelwiderstandsfaktor9 bytes (1,351 words) - 14:49, 16 January 2023
- comprises the feedpoint at the next signal, one running rail, first locomotive axle, another running rail and back to the signal feedpoint. The resulting electromagnetic9 bytes (1,561 words) - 14:49, 16 January 2023
- User:RailML Coord Documentation/IS:radiusChange (section Modelling of transition curves in railML 2.3)is not an explicit number, railML® uses the value 0 here, which is a virtual value and does not exist in reality. With railML® 2.3 the element <radiusChange>9 bytes (1,759 words) - 14:49, 16 January 2023
- vehicle Parent: <vehicles> Children: <additionalName> (introduced with version 2.1), <classification>, <curvingLimitation>, <engine>, <loadLimitMatrix>28 bytes (1,800 words) - 14:49, 16 January 2023
- and consumer. With railML® 2.5 it is now possible to mark a train as a demand train. In order to mark demand trains as such in railML®2.5, the definition9 bytes (1,933 words) - 14:49, 16 January 2023
- Dev:Downloading and using railML Dev:Examples Dev:Examples for a non-zero operating day offset at the first ocpTT of a train run Dev:Extending railML Dev:Git Guidelines202 bytes (229 words) - 18:26, 23 November 2020
- Ich bin der Bot von User:RailML Coord Documentation. Was ich tue kann man teilweise auf User:RailML_Bot_Documentation/Log sehen.137 bytes (20 words) - 17:53, 1 December 2023
- Testimport am Mi 13. Mär 15:21:24 CET 2024 durch RailML Bot Documentation74 bytes (14 words) - 16:21, 13 March 2024
- Testimport am Mi 13. Mär 19:04:18 CET 2024 durch RailML Bot Documentation74 bytes (14 words) - 20:04, 13 March 2024
- Testimport am Mo 15. Apr 16:53:31 CEST 2024 durch RailML Bot Documentation74 bytes (14 words) - 16:53, 15 April 2024