Search results
Jump to navigation
Jump to search
- IL:hasIndication (category Elements)element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions516 bytes (38 words) - 16:16, 5 March 2021
- Examples (link to the railML® website) — collection of examples provided by the railML partners (railML.org login needed) All elements in the Wiki are documented3 KB (288 words) - 18:19, 23 May 2024
- IL:belongsToOperationalPoint (category Elements)element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions528 bytes (38 words) - 16:15, 5 March 2021
- IL:hasCommand (category Elements)element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions716 bytes (61 words) - 15:10, 14 May 2022
- IS:typeDesignator (category Elements)element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions517 bytes (38 words) - 21:50, 25 April 2022
- element Rollingstock Elements — overview off all XML elements found in the rollingstock subschema UML visualization of the current railML® 3 RS subschema A3 KB (458 words) - 17:20, 29 November 2023
- IS:gmlLocations (category Elements)lineString (0..*), point (0..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts515 bytes (4 words) - 18:41, 19 December 2019
- can retrieve them from https://development.railml.org/railml/shared/-/tree/master/codelists (link to the railML® website) The code lists are intended to6 KB (797 words) - 12:50, 29 November 2023
- IL:assetsForInterlocking (category Elements)to some infrastructure elements. Within the entire railML schema there are no different namespaces used. Subsequently some elements (types) in interlocking3 KB (359 words) - 13:19, 29 May 2022
- IS:functionalInfrastructure (category Elements)(0..1), weightLimits (0..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts527 bytes (4 words) - 18:42, 19 December 2019
- IS:networkLocation (category Elements)a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts518 bytes (9 words) - 18:41, 19 December 2019
- IL:assetsForIL (category Elements)to some infrastructure elements. Within the entire railML schema there are no different namespaces used. Subsequently some elements (types) in interlocking2 KB (272 words) - 12:02, 21 May 2022
- CO:external (category Elements)This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:external> that511 bytes (58 words) - 18:42, 19 December 2019
- IS:speedSection (category Elements)Speed limits are modelled in railML® using speedSection elements in combination with <speedProfile> elements. The element documentation has been changed2 KB (250 words) - 18:16, 15 January 2024
- IS:baliseGroup (category Elements)the ATP elements (like for ETCS). According to the use case “ETCS Track Net”, the railML® element <baliseGroup> provides the attributes and elements to transfer19 KB (2,555 words) - 16:55, 18 January 2024
- Generic:assetName (category Elements)This element does not appear in railML® 3.1 within the generic subschema. It is available only in railML® 3.2. There exists an element <CO:assetName> that517 bytes (58 words) - 12:41, 8 February 2024
- TT:timetable (category Elements)transportServices (0..1), validities (0..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts512 bytes (4 words) - 18:52, 19 December 2019
- IS:underCrossing (category Elements)named levelCrossing in railML 3 a railway track crossing another railway track via a bridge can be modelled using the elements <overcrossing> and <underCrossing>3 KB (242 words) - 11:48, 13 May 2024
- IS:signalIS (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts623 bytes (15 words) - 10:23, 13 May 2024
- IS:overCrossing (category Elements)named levelCrossing in railML 3 a railway track crossing another railway track via a bridge can be modelled using the elements <overcrossing> and <underCrossing>3 KB (216 words) - 13:04, 13 May 2024