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
- IS:geoCoord (category Infrastructure Elements) (section Position of geoCoord in the XML-Tree / Position von geoCoord im XML-Baum)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
- IS:signal (category Infrastructure Elements)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
- IS:brigde (category Infrastructure Elements)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://www5 KB (1,077 words) - 14:57, 14 March 2024
- IS:crossedElements (category Infrastructure Elements)<levelCrossing> or <tunnel>. None None Consider railML® 2.3 example of Middle Rhine Railway by GPSinfradat (link to the railML® website). This code example defines2 KB (168 words) - 22:01, 28 March 2023
- IS:track (category Infrastructure Elements)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
- IS:crossSection (category Infrastructure Elements)data (link to the railML® website) section. Consider railML® 2.3 example of Middle Rhine Railway by GPSinfradat (link to the railML® website). The purpose8 KB (1,542 words) - 10:55, 21 February 2024
- IS:ocp (category Infrastructure Elements)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
- 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
- Infrastructure (section Infrastructure (IS))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
- IS:platformEdge (category Infrastructure Elements)parentPlatformEdgeRef: xs:IDREF Consider railML® 2.3 example of Middle Rhine Railway by GPSinfradat (link to the railML® website). This code example defines3 KB (916 words) - 18:22, 22 March 2023
- IS:levelCrossing levelCrossings (category Infrastructure Elements)protection have been REMOVED with railML® version 2.4 since they were not useful for many applications. Consider railML® 2.3 example of Middle Rhine Railway4 KB (997 words) - 17:41, 1 August 2023
- IS:trackCircuitBorder (category Infrastructure Elements)(introduced with version 2.1), <any>, <geoCoord>, <states> [1..1] A <trackCircuitBorder> allows for defining insulated rail joints. id: XML-file-wide unique,1,017 bytes (705 words) - 18:51, 16 April 2023
- Dev:changes/2.2 (section Infrastructure 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
- IS:trackBegin (category Infrastructure Elements)version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1] The trackBegin defines the start of a track in the railML® file. It could3 KB (483 words) - 10:48, 15 April 2024
- IS:trackEnd (category Infrastructure Elements)version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1] The trackEnd defines the end of a track in the railML® file. It could4 KB (545 words) - 18:10, 22 March 2024
- IS:mileageChange (category Infrastructure Elements)direkt erkennbar. Sie wird in railML® als relative Kilometrierung bezeichnet. Die relative Kilometrierung eines Gleises (railML®: Attribut @pos) ist immer9 KB (1,586 words) - 15:01, 17 July 2023
- 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