Search results
Jump to navigation
Jump to search
- UC:Use cases (section railML® Use Cases)page you learn what is a use case and find a list of railML® use cases. While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up10 bytes (287 words) - 16:31, 3 February 2020
- absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight, heightEpsgCode <to> absPos, absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight112 KB (4,754 words) - 18:02, 3 April 2022
- to the railML® website) — collection of examples provided by the railML® partners (railML.org https://railml.org railML.org (link to the railML® website)3 KB (350 words) - 19:56, 22 January 2024
- absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight, heightEpsgCode <to> absPos, absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight65 KB (2,931 words) - 12:19, 8 October 2021
- absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight, heightEpsgCode <to> absPos, absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight72 KB (3,235 words) - 11:59, 11 October 2021
- Dev:changes/2.2 (section Rollingstock subschema)railML® schema changes between railML® 2.1 and railML® 2.2 This site is intended to collect the schema changes between railML® 2.1 and railML® 2.2 by36 KB (103 words) - 13:54, 21 February 2022
- between railML® 2.1 and railML® 2.2 This page shows schema differences between railML® 2.1 and railML® 2.2. It is intended to support advanced railML® users331 KB (27,016 words) - 10:56, 8 October 2021
- WEITERLEITUNG Rollingstock31 bytes (2 words) - 14:49, 16 January 2023
- between railML® 2.4 and railML® 2.5 This page shows schema differences between railML® 2.4 and railML® 2.5. It is intended to support advanced railML® users398 KB (34,006 words) - 10:54, 8 October 2021
- between railML® 2.0 and railML® 2.1 This page shows schema differences between railML® 2.0 and railML® 2.1. It is intended to support advanced railML® users531 KB (37,474 words) - 10:55, 8 October 2021
- documentation page here in the railML® wiki. Elements with parent inheritance are used at several positions in the XML-Tree. In the railML® 2 wiki, the elements9 KB (1,033 words) - 17:59, 19 January 2024
- UC:TT:FGIInTrain (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)<rostering> is included, the element <rollingstock> is also required The elements <infrastructure> and <rollingstock> are master data for the use case "passenger10 bytes (677 words) - 16:12, 3 February 2020
- Infrastructure, Struktur noch unklar Guidline for Downloadiung and Using railML — neu Benutzer:Ferri Leberl/How to contribute — erstellen, Durchgangsseite793 bytes (73 words) - 14:49, 16 January 2023
- the railML wiki (wiki2; wiki3) ✔ RailML Coord Documentation (talk) 16:30, 3 April 2023 (CEST) Dev:Semantic Constraints (wiki2; wiki3) ✔ RailML Coord Documentation10 bytes (363 words) - 19:46, 15 December 2022
- electrification, ...) visualization data for displaying a net Please visit the railML-Website for more detailed information about the Infrastructure subschema2 KB (659 words) - 14:49, 16 January 2023
- description in other languages. version: This is the version number of the railML® release the current XML file conforms to. It is not any internal numbering9 bytes (574 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,930 words) - 14:49, 16 January 2023