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,

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

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

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

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

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

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

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

NORWAY RailML Coord Common/Codelist pages RailML Coord Common/Dev pages RailML Coord Common/Sandbox RailML Coord Common/Switches RailML Coord Common/Tools

Dev:Codelists Dev:InfrastructureManagers Dev:Registers Dev:TrainClearanceGauges Dev:TrainProtectionSystems CO:infrastructureManagerCodes CO:infrastruc

No links are displayed in the text and only one interwiki link (the first) will be displayed in the "In other languages" section in the left panel. <baseItinerary

WEITERLEITUNG Common

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

In compliance with Dev:Syntactic_Guidelines (min|max)Occurs="1" use="optional" //*[text() and not(normalize-space()) and not(*)] //xs:element[not(xs:a

the railML wiki (wiki2; wiki3) ✔ RailML Coord Documentation (talk) 16:30, 3 April 2023 (CEST) Dev:Semantic Constraints (wiki2; wiki3) ✔ RailML Coord Documentation

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>

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