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

The resulting changes to the planned infrastructure shall be fed back into a visualization software. The infrastructure data to be modified contains railway

Jernbanedirektoratet railML® 2.4 glossary (external link) Description of the FBS railML® interface (external link) [https://wiki3.railml.org railML® 3.1 Tutorial

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® users

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 page

millimeter); default: 1435; optional Consider railML® 2.2 example of East Saxony railway network by FBS (link to the railML® website). This code example defines

org/wiki/Balise (external link) railML® forum post (link to the railML® website) Llorente González, Diego. "Application of railML® modelling to ERTMS-ETML."

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>

<any>, <geoCoord>, <states>, <connection>, [0..∞] A <switch> defines a standard railroad switch with three connections as an infrastructure element. A

railway infrastructure data in an economical, fast and accurate way. Information about the track geometry, topology and related infrastructure elements

solution is sufficient and the concept of referencing will be revised with railML® version 3.1. verbalConstraints attribute can be used for: - stop posts

xs:positiveInteger, optional infrastructureManagerRef: xs:IDREF Please see also example (link to the railML® website) for border between infrastructure mangers. Positive

with version 2.1), <any>, <geoCoord>, <states>, <crossedElements> [0..∞] A <tunnel> defines a tunnel as an infrastructure element and its attributes.  

specified using the <geoCoord> element. (deprecated with version 2.1)(introduced with version 2.4) This Element has been deprecated with railML® 2.1 but reintroduced

followed by at minimum two characters, white space not allowed for extending railML® enumeration lists); default: adhesion; optional style: xs:string; optional

to the infrastructure based on a specific project or an area that is relevant for a specific project. Compare forum discussion (link to the railML® website)

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® users

xs:decimal, 6 fraction digits, radius value measured in meter, optional In railML® 2.4nor/in the use in the Norwegian railway sector the <gradientChange>

<additionalName>, <any>, <geoCoord>, <states> [0..∞] Start of section with certain train radio system installed at the infrastructure. id: XML-file-wide unique

reference to a well-known 'operation or control point' defined in the same railML® file pos: This is the position on a track defined as distance from its

bridge, other:[any], optional A car ramp shall be modelled using the existing railML® element <serviceSection> together with boolean attribute @ramp="true".

reference to a well-known 'operation or control point' defined in the same railML® file pos: This is the position on a track defined as distance from its

is not known. xs:anyAttribute: This provides an extension point for non-railML® attributes in a foreign namespace. How to use it? id: xs:ID, required a

Monitoring of Railway Infrastructure—Encouraging Data Source or Errant Effort? (external link) Oleh Shchuryk. Finished Vehicle Logistics by Rail in Europe. the

s> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0..∞] A <operationModeChange> defines a point in which the operation

followed by at minimum two characters, white space not allowed for extending railML® enumeration lists; pattern: other:\w{2,}); optional posInTrack optional

iRFP’s railML® example files Ostsachsen (link to the railML® website, PDF, visited on 2018-06-18; Model of eastern Syxony by iRFP; official railML® example

followed by at minimum two characters, white space not allowed for extending railML® enumeration lists; optional Not yet described. / Noch nicht beschrieben

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 elements

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® users

train correctly to the other information <ocp> elements to refer to the infrastructure Different levels of complexity of the data import are possible. a minimal