Search results
Jump to navigation
Jump to search
- GML4RAILML:pos (category Pages using Tabber parser tag)this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the514 bytes (15 words) - 18:41, 19 December 2019
- IL:routeSequence (category Pages using Tabber parser tag)This 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 further516 bytes (38 words) - 21:53, 25 April 2022
- RS:administrativeData (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further521 bytes (38 words) - 21:53, 25 April 2022
- IL:situatedAtTrackAsset (category Pages using Tabber parser tag)of IL Documentation This is the reference to the track asset the danger point is located. It is used when the danger point is situated in the middle of523 bytes (5 words) - 18:51, 19 December 2019
- location at the net element of a switch beginning. In this case, sw317a is located at ne3, and sw317b is located at ne30. Crossing then should be located with29 KB (2,876 words) - 17:49, 30 May 2024
- IL:initStatus (category Pages using Tabber parser tag)Documentation The initial status of commands and messages on the interface in case of "cold start", i.e. a kind of predefined status to be assumed in absence513 bytes (0 words) - 18:48, 19 December 2019
- RS:formation (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further512 bytes (38 words) - 16:19, 5 March 2021
- IL:hasLevelCrossingType (category Pages using Tabber parser tag)interlocking independently of the direction. This is the case for level crossings within stations. The level crossing is activated by route setting and deactivated3 KB (405 words) - 15:31, 29 October 2023
- IL:routeEntry (category Pages using Tabber parser tag)changed. The start of a route is described in <routeEntry>. The element contains the following information: <refersTo> – This is the reference to the start1 KB (151 words) - 20:08, 29 January 2020
- RS:vehicle (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further510 bytes (38 words) - 16:19, 5 March 2021
- IL:dangerPoint (category Pages using Tabber parser tag)the danger point is located. It is used when the danger point is situated in the middle of a TVD section or beyond any TVD section in case of not supervised2 KB (232 words) - 20:39, 29 January 2020
- IS:functionalType (category Missing Element Documentation/IS)This 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 further517 bytes (38 words) - 16:13, 5 March 2021
- IL:combinedRoute (category Pages using Tabber parser tag)entry and exit of the route combination. The highest priority is 0. It is omitted if there is no alternative path. <designator> - A coded name as per a specified3 KB (348 words) - 12:05, 28 May 2022
- IL:routeStatusIndicator (category Pages using Tabber parser tag)@id - The unique identifier used to reference this element within railML. @positionInRoute - This marks whether the indicator is at the start or the end.2 KB (200 words) - 13:21, 28 May 2022
- IL:hasAspect (category Pages using Tabber parser tag)cannot be cleared normally. In most cases such aspect is used with a special call-on route. caution – This is used for a distant signal aspect/slave aspect8 KB (1,085 words) - 10:48, 10 November 2023
- TT:followupSections (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further519 bytes (38 words) - 21:54, 25 April 2022
- Certify your interface. While you can use railML® in island solutions e.g. for exercise, in most cases productive use aims at and depends on exchanging data3 KB (371 words) - 17:02, 3 April 2023
- TT:identifier (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further513 bytes (38 words) - 21:55, 25 April 2022
- In this way, you inherit all information that is collected about the ÖBB in the code list, in this case name, country code and company code: <infrastructureManager6 KB (797 words) - 12:50, 29 November 2023
- TT:origin (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further509 bytes (38 words) - 21:56, 25 April 2022