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
- without long/lat coordinates: <geoCoord coord='0 0' extraHeight='250.03' heightEpsgCode='5783'/> (In railML® 2.0 and railML® 2.1, for syntactical reasons,12 KB (1,472 words) - 19:28, 22 January 2024
- 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
- followed by at minimum two characters, white space not allowed for extending railML® enumeration lists; pattern: other:\w{2,}, optional function: union of (restriction15 KB (2,400 words) - 19:48, 22 January 2024
- separate source page. All tracks in railML® and the connections make up a graph. But different to many other data models, railML® does NOT require points, signals9 KB (1,420 words) - 10:23, 1 February 2024
- demo file East Saxony railway network by FBS (link to the railML® website, railML®; by railML® partner iRFP) <ocp id='ocp01' name='Pulsnitz' type='operationalName'>18 KB (2,618 words) - 16:53, 19 March 2024
- 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 Common 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
- Dev:How to edit and contribute to the Wiki (redirect from Dev:How to join, edit and create the railML wiki) (section Start a new railML® Wiki page for a new railML® element)edit content. railML® is an open-source data exchange standard specifically tailored for railway applications. It includes railML® 2 and railML® 3 as well15 KB (1,952 words) - 18:11, 15 April 2024
- etcsTrainCategory: (introduced with version 2.2)(deprecated with version 2.5) in railML® 2.2 to railML® 2.4: the international train category number as specified on page10 KB (1,890 words) - 15:25, 25 March 2024
- Dev:Guides (link to the railML® website), e.g. Passenger station (link to the railML® website), Intermodal terminal (link to the railML® website) The <ocp>16 KB (1,316 words) - 18:40, 22 January 2024
- 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
- Germany (external link). absBrakeDist wheel slide control systems. The most common of these operates rather like ABS (automatic braking systems) on road vehicles937 bytes (948 words) - 23:50, 14 September 2020
- 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
- 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
- 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