Search results

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-up

without long/lat coordinates: <geoCoord coord='0 0' extraHeight='250.03' heightEpsgCode='5783'/> (In railML® 2.0 and railML® 2.1, for syntactical reasons,

absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight, heightEpsgCode <to> absPos, absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight

followed by at minimum two characters, white space not allowed for extending railML® enumeration lists; pattern: other:\w{2,}, optional function: union of (restriction

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://www

<levelCrossing> or <tunnel>. None None Consider railML® 2.3 example of Middle Rhine Railway by GPSinfradat (link to the railML® website). This code example defines

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, signals

data (link to the railML® website) section. Consider railML® 2.3 example of Middle Rhine Railway by GPSinfradat (link to the railML® website). The purpose

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'>

absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight, heightEpsgCode <to> absPos, absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight

absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight, heightEpsgCode <to> absPos, absPosOffset, ocpRef, pos <geoCoord> coord, epsgCode, extraHeight

to the railML® website) — collection of examples provided by the railML® partners (railML.org https://railml.org railML.org (link to the railML® website)

parentPlatformEdgeRef: xs:IDREF Consider railML® 2.3 example of Middle Rhine Railway by GPSinfradat (link to the railML® website). This code example defines

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 Railway

(introduced with version 2.1), <any>, <geoCoord>, <states> [1..1] A <trackCircuitBorder> allows for defining insulated rail joints. id: XML-file-wide unique,

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 by

version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1] The trackBegin defines the start of a track in the railML® file. It could

version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1] The trackEnd defines the end of a track in the railML® file. It could

direkt erkennbar. Sie wird in railML® als relative Kilometrierung bezeichnet. Die relative Kilometrierung eines Gleises (railML®: Attribut @pos) ist immer

edit content. railML® is an open-source data exchange standard specifically tailored for railway applications. It includes railML® 2 and railML® 3 as well