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
- 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
- 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: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: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
- 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: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
- 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: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: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
- 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
- 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
- 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
- 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
- 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: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
- 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
- IS:electrificationChange (category Infrastructure Elements)Jernbanedirektoratet railML® 2.4 glossary (external link) Description of the FBS railML® interface (external link) [https://wiki3.railml.org railML® 3.1 Tutorial3 KB (1,150 words) - 15:33, 25 March 2024
- UC:IS:RailwayInfrastructureVisualisation (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)The resulting changes to the planned infrastructure shall be fed back into a visualization software. The infrastructure data to be modified contains railway10 bytes (180 words) - 16:12, 3 February 2020
- IS:speedChange (category Infrastructure Elements)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
- IS:radiusChange (category Infrastructure Elements) (section Modelling of transition curves in railML 2.3)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>9 KB (1,756 words) - 15:32, 25 March 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
- IS:balise (category Infrastructure Elements)org/wiki/Balise (external link) railML® forum post (link to the railML® website) Llorente González, Diego. "Application of railML® modelling to ERTMS-ETML."3 KB (936 words) - 19:16, 22 January 2024
- IS:gaugeChange (category Infrastructure Elements)millimeter); default: 1435; optional Consider railML® 2.2 example of East Saxony railway network by FBS (link to the railML® website). This code example defines2 KB (728 words) - 15:34, 25 March 2024
- IS:switch (category Infrastructure Elements)<any>, <geoCoord>, <states>, <connection>, [0..∞] A <switch> defines a standard railroad switch with three connections as an infrastructure element. A2 KB (1,151 words) - 16:06, 6 November 2022
- IS:position trackElementVis (category Infrastructure Elements)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 reintroduced956 bytes (142 words) - 13:02, 10 May 2023
- IS:ownerChange (category Infrastructure Elements)xs:positiveInteger, optional infrastructureManagerRef: xs:IDREF Please see also example (link to the railML® website) for border between infrastructure mangers. Positive2 KB (715 words) - 15:33, 25 March 2024
- IS:stopPost (category 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 posts5 KB (1,258 words) - 17:26, 19 January 2024
- IS:tunnel (category Infrastructure Elements)with version 2.1), <any>, <geoCoord>, <states>, <crossedElements> [0..∞] A <tunnel> defines a tunnel as an infrastructure element and its attributes.8 KB (1,348 words) - 17:47, 19 January 2024
- IS:border (category Infrastructure Elements)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)2 KB (847 words) - 17:36, 4 December 2023
- IS:powerTransmissionChange (category Infrastructure Elements)followed by at minimum two characters, white space not allowed for extending railML® enumeration lists); default: adhesion; optional style: xs:string; optional1 KB (772 words) - 15:32, 25 March 2024
- IS:gradientChange (category Infrastructure Elements)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>3 KB (931 words) - 18:37, 25 March 2024
- UC:IS:RailwayInfrastructureRecording (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)railway infrastructure data in an economical, fast and accurate way. Information about the track geometry, topology and related infrastructure elements10 bytes (335 words) - 16:12, 3 February 2020
- IS:to state (category Infrastructure Elements)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 its840 bytes (130 words) - 17:35, 19 January 2024
- IS:trainRadioChange (category Infrastructure Elements)<additionalName>, <any>, <geoCoord>, <states> [0..∞] Start of section with certain train radio system installed at the infrastructure. id: XML-file-wide unique1 KB (689 words) - 23:47, 14 September 2020
- 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® example16 KB (1,316 words) - 18:40, 22 January 2024
- IS:from state (category Infrastructure Elements)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 its842 bytes (130 words) - 19:27, 22 January 2024
- 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
- IS:lock (category Infrastructure Elements)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 a859 bytes (660 words) - 15:10, 23 May 2022
- IS:serviceSection (category Infrastructure Elements)bridge, other:[any], optional A car ramp shall be modelled using the existing railML® element <serviceSection> together with boolean attribute @ramp="true".4 KB (1,103 words) - 16:56, 13 March 2022
- IS:trainProtectionElement (category Infrastructure Elements)Monitoring of Railway Infrastructure—Encouraging Data Source or Errant Effort? (external link) Oleh Shchuryk. Finished Vehicle Logistics by Rail in Europe. the1 KB (1,452 words) - 14:01, 16 November 2022
- IS:trainDetector (category Infrastructure Elements)followed by at minimum two characters, white space not allowed for extending railML® enumeration lists; pattern: other:\w{2,}); optional posInTrack optional7 KB (1,535 words) - 18:44, 11 April 2024
- IS:operationModeChange (category Infrastructure Elements)s> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0..∞] A <operationModeChange> defines a point in which the operation937 bytes (948 words) - 23:50, 14 September 2020
- WEITERLEITUNG Benutzer:Infrastructure42 bytes (2 words) - 14:49, 16 January 2023
- IS:trackCondition (category Infrastructure Elements)followed by at minimum two characters, white space not allowed for extending railML® enumeration lists; optional Not yet described. / Noch nicht beschrieben4 KB (1,082 words) - 23:46, 14 September 2020
- 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
- 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
- UC:TT:FGIInTrain (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)train correctly to the other information <ocp> elements to refer to the infrastructure Different levels of complexity of the data import are possible. a minimal10 bytes (677 words) - 16:12, 3 February 2020
- Talk:Dev:How To Reference Infrastructure (section How to describe infrastructure / Beschreibung von Infrastruktur)a microscopic infrastructure description in railML®, tracks usually are limited by switches, crossings, bufferstops and such. In railML® that would mean17 KB (2,110 words) - 12:06, 14 December 2023
- Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen / Interaction avec autres schemas railML® Mandatory: infrastructure Optionally: rolling6 KB (416 words) - 19:32, 15 December 2022
- Benutzer:Ferri Leberl/Infrastructure Examples — verlinkt von Infrastructure, Struktur noch unklar Guidline for Downloadiung and Using railML — neu Benutzer:Ferri793 bytes (73 words) - 14:49, 16 January 2023
- User:RailML Coord Documentation/IS:Infrastructure (section Position of infrastructure in the XML-Tree / Position von infrastructure im XML-Baum)links to Infrastructure Documentation sites: Infrastructure Concepts Infrastructure Elements Infrastructure Examples infrastructure Parent: <railml> Children:2 KB (659 words) - 14:49, 16 January 2023
- the railML wiki (wiki2; wiki3) ✔ RailML Coord Documentation (talk) 16:30, 3 April 2023 (CEST) Dev:Semantic Constraints (wiki2; wiki3) ✔ RailML Coord Documentation10 bytes (363 words) - 19:46, 15 December 2022
- xs:positiveInteger, optional infrastructureManagerRef: xs:IDREF Please see also example (link to the railML® website) for border between infrastructure mangers. Positive9 bytes (715 words) - 14:49, 16 January 2023
- Monitoring of Railway Infrastructure—Encouraging Data Source or Errant Effort? (external link) Oleh Shchuryk. Finished Vehicle Logistics by Rail in Europe. the9 bytes (951 words) - 14:49, 16 January 2023
- description in other languages. version: This is the version number of the railML® release the current XML file conforms to. It is not any internal numbering9 bytes (574 words) - 14:49, 16 January 2023
- Monitoring of Railway Infrastructure—Encouraging Data Source or Errant Effort? (external link) Oleh Shchuryk. Finished Vehicle Logistics by Rail in Europe. the9 bytes (1,558 words) - 14:49, 16 January 2023
- 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://www9 bytes (1,077 words) - 14:49, 16 January 2023
- with version 2.1), <any>, <geoCoord>, <states>, <crossedElements> [0..∞] A <tunnel> defines a tunnel as an infrastructure element and its attributes.9 bytes (1,348 words) - 14:49, 16 January 2023
- within the railML® file defined by the use case (so in spite of they do not need to be unique by the railML® schema). Interference with other railML® schemas4 KB (578 words) - 19:37, 15 December 2022
- Dev:Codelists Dev:InfrastructureManagers Dev:Registers Dev:TrainClearanceGauges Dev:TrainProtectionSystems CO:infrastructureManagerCodes CO:infrastructureManager1 KB (45 words) - 19:46, 15 December 2022
- and consumer. With railML® 2.5 it is now possible to mark a train as a demand train. In order to mark demand trains as such in railML®2.5, the definition9 bytes (1,930 words) - 14:49, 16 January 2023