Search results
Jump to navigation
Jump to search
- CO:positioning (category Pages using Tabber parser tag)gSystem>. It is used to locate infrastructure elements within the topology network. For the mesoscopic topology, it is recommended to use the classic railway11 KB (1,110 words) - 09:59, 29 April 2024
- layout and formatting. This is useful for making more complex changes or for contributors who prefer working with markup directly. Use the “Preview” feature11 KB (1,424 words) - 18:13, 15 April 2024
- IL:interface (category Pages using Tabber parser tag)@messString – This is the representation of the single messages status. The use is the same as for the @comString. A level crossing is a typical field element13 KB (1,119 words) - 17:46, 30 January 2020
- <designator> <name> <usesSymbol> <designator> <isLocatedAt> <name> <designator> <ellipticalProjection> <center> <designator> <name> <usesSymbol> <designator>188 KB (2,767 words) - 13:38, 4 December 2023
- IS:line (category Pages using Tabber parser tag)</linearLocation> ... </line> </lines> Suppose you want to make use of the intrinsic coordinates instead. In that case, you may leave out the linear positioning coordinates9 KB (873 words) - 11:03, 13 May 2024
- address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity errors. The concept is explained here. The list17 KB (299 words) - 15:10, 7 December 2023
- IL:routeExit (category Pages using Tabber parser tag)destination signal. <refersTo> – This is the reference to the physical end of the route path. This is in most cases a signal but can also be a buffer stop2 KB (187 words) - 20:37, 29 January 2020
- partialRouteReleaseDelay: Delay time after which the section may be released for use in a new route (obligatory; xs:duration), technology: the technical type of2 KB (5 words) - 14:21, 24 January 2020
- IS:border (category Pages using Tabber parser tag)element IS:border of railML® version 3.2 UML-visualization of IS Documentation A border point is used to separate the railway network due to different reasons706 bytes (9 words) - 18:23, 15 April 2024
- IL:hasTVDresetStrategy (category Pages using Tabber parser tag)and clearance sequence from a passing train is notified from the axle counter. In this case the section is reset immediately without any further operator4 KB (406 words) - 17:47, 22 January 2020
- values: axleCounter: The TVD section is formed by axel counter detection points. trackCircuit: The TVD section is using track circuit equipment with insulated3 KB (5 words) - 12:41, 8 February 2024
- <any> <coordinate> <name> <usesSymbol> <any> <isLocatedAt> <name> <linearElementProjection> <any> <coordinate> <name> <usesSymbol> <any> <isLocatedAt>125 KB (1,906 words) - 03:09, 26 October 2023
- 1) Attributes: preferredPosition: This is the state of level crossing under normal conditions, i.e. when not in use. For most level crossings this would3 KB (5 words) - 14:21, 24 January 2020
- xs:duration), minimumOpenTime: This is the time the level crossing has to be open before it is allowed to close again. This is to ensure a certain capacity for4 KB (5 words) - 12:41, 8 February 2024
- IL:activationCondition (category Pages using Tabber parser tag)level crossing is activated, i.e. requested to close for road traffic, upon train approach. There is a range of conditions to conclude a train is approaching4 KB (465 words) - 12:14, 30 May 2020
- IL:relatedMovableElement (category Pages using Tabber parser tag)UML-visualization of IL Documentation reference to other movable element in case of single/double slip switch or coupled switch Subschema interlocking Parents*524 bytes (5 words) - 18:47, 19 December 2019
- IL:assetsForIL (category Pages using Tabber parser tag)infrastructure subschema. In such cases just the suffix “IL” was added to the name, e.g. signalIS vs. signalIL. The element of <assetsForIL> is not only a collection2 KB (272 words) - 12:02, 21 May 2022
- IS:levelCrossingIS (category Missing Element Documentation/IS)Semantic Constraint "IS:003": <levelCrossingIS> should not have a <crossesElement> child of type railway. This case should be represented either1,015 bytes (15 words) - 11:37, 13 May 2024
- IL:tunnelGateIL (category Pages using Tabber parser tag)might be cases when the tunnel gate is normally blockingClosed and opened for railway traffic only on route setting. The normal closed status is used for tunnel5 KB (599 words) - 14:26, 27 May 2022
- IL:assetsForInterlocking (category Pages using Tabber parser tag)of containers for elements to decribe their functional characteristics in use of the interlocking domain. These are track related, route related objects3 KB (359 words) - 13:19, 29 May 2022
- 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 (10 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
- 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
- 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
- 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: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
- 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) - 14:34, 13 March 2024
- 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
- TT:destination (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 further514 bytes (38 words) - 21:56, 25 April 2022
- Generic:places (category Pages using Tabber parser tag)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:places> that might514 bytes (58 words) - 12:42, 8 February 2024
- IL:branchTip (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 further512 bytes (38 words) - 21:51, 25 April 2022
- IL:refersToInfrastructureElement (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 further532 bytes (38 words) - 21:53, 25 April 2022
- CO:powerMode (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further512 bytes (38 words) - 21:53, 25 April 2022
- IL:hasConfiguration (category Pages using Tabber parser tag)field elements is done by electric power. The interlocking logic is realised by relay circuits. electronic - The operation of field elements is done by electric3 KB (385 words) - 14:00, 21 August 2021
- TT:commercialTrainReference (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 further527 bytes (38 words) - 21:56, 25 April 2022
- IL:etcsGeneralData (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 further518 bytes (38 words) - 21:53, 25 April 2022
- signal is a main signal within a station neither used for entry nor exit routes. intermediateStop: This is a special intermediate signal that is used for7 KB (5 words) - 12:41, 8 February 2024
- In this case, an ordinary switch is described, so the @navigability attribute is set to “both”. In other cases where only unidirectional travel is allowed18 KB (2,052 words) - 18:20, 15 April 2024
- and clearance sequence from a passing train is notified from the axle counter. In this case the section is reset immediately without any further operator2 KB (5 words) - 12:42, 8 February 2024
- automatique in French. Note that this functionality is often part of the control system in which case this attribute should be omitted. (optional; xs:boolean)4 KB (5 words) - 12:42, 8 February 2024
- designators as per manufacturer, owner, operator and keeper. This element is only useful in case of an individual vehicle. Subschema rollingstock Parents* vehicle680 bytes (5 words) - 21:53, 25 April 2022
- itinerary point. Usually the section with the highest priority is used, however in case of operational requirement TMS may select among the others usually818 bytes (5 words) - 17:41, 15 January 2024
- This is the reference to the underlying track section in infrastructure of the tip branch. Especially in case of switch crossing this element is not used844 bytes (5 words) - 21:51, 25 April 2022
- destination of the train in case it can not or should not be extracted from the path of the train. The provided information is related to the stopindicated1 KB (5 words) - 21:56, 25 April 2022
- the origin of the train in case it can not or should not be extracted from the path of the train. The provided information is related to the stopindicated1 KB (5 words) - 21:56, 25 April 2022
- 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 absence846 bytes (5 words) - 16:17, 5 March 2021
- 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 absence846 bytes (5 words) - 18:48, 19 December 2019
- Documentation Description of the route destination point. In most cases the route destination is a signal or a buffer stop. Subschema interlocking Parents* route1,018 bytes (5 words) - 14:22, 24 January 2020
- 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 of920 bytes (5 words) - 16:18, 5 March 2021
- 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 of919 bytes (5 words) - 18:19, 23 December 2019
- UML-visualization of IL Documentation reference to other movable element in case of single/double slip switch or coupled switch Subschema interlocking Parents*890 bytes (5 words) - 16:16, 5 March 2021
- describing the group/area. In that case the member list may be omitted, e.g. referring to electrificationSection in IS with groupType="catenary". Subschema935 bytes (5 words) - 21:53, 25 April 2022
- UML-visualization of IL Documentation reference to other movable element in case of single/double slip switch or coupled switch Subschema interlocking Parents*889 bytes (5 words) - 14:21, 24 January 2020
- Possible values: first second third, compartmentSize: In case of seats arranged in a compartment this is the number of seats per compartment. (optional; xs:positiveInteger)2 KB (5 words) - 15:55, 8 February 2024
- [0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}), number: Used to specify the train number itself. (obligatory; xs:string), type: Allows2 KB (5 words) - 12:43, 8 February 2024
- Gives the priority of the path in case there are several possible paths between entry and exit. The highest priority is 0. (optional; xs:nonNegativeInteger)2 KB (5 words) - 12:42, 8 February 2024
- Gives the priority of the path in case there are several possible paths between entry and exit. The highest priority is 0. (optional; xs:nonNegativeInteger)2 KB (5 words) - 12:42, 8 February 2024
- Documentation Description of the route destination point. In most cases the route destination is a signal or a buffer stop. Subschema interlocking Parents* route1 KB (5 words) - 12:42, 8 February 2024
- IS:functionalType/3.2 (category Missing Element Documentation/IS)for this function. signal: This balise group is linked physically (in case of ETCS L1) or logical (in case of ETCS Level 2) with a main signal. In relation3 KB (5 words) - 12:39, 8 February 2024
- element IS:border of railML® version 3.1 UML-visualization of IS Documentation A border point is used to separate the railway network due to different reasons3 KB (5 words) - 14:21, 24 January 2020
- element IS:border of railML® version 3.2 UML-visualization of IS Documentation A border point is used to separate the railway network due to different reasons3 KB (5 words) - 12:39, 8 February 2024
- the position of the indicator in the route in case not clear by reference from routeEntry or routeExit. It is related to the functions the indicator will1 KB (5 words) - 12:41, 8 February 2024
- including the voltage and frequency of a related electrification system. In case of independent power source like diesel the electrification values shall2 KB (5 words) - 12:43, 8 February 2024
- numberOfWagons: The number of non-powered wagons in the formation. This value is only useful in case of a loco hauled train. (optional; xs:positiveInteger), speed: The2 KB (5 words) - 12:43, 8 February 2024
- automatique in French. Note that this functionality is often part of the control system in which case this attribute should be omitted. (optional; xs:boolean)3 KB (5 words) - 14:22, 24 January 2020
- field, the leftmost digit is the digit to be dialled first. In case the NID_MN is shorter than 6 digits, the remaining space is to be filled with special2 KB (5 words) - 12:42, 8 February 2024
- IL:etcs (category Pages using Tabber parser tag)field, the leftmost digit is the digit to be dialled first. In case the NID_MN is shorter than 6 digits, the remaining space is to be filled with special2 KB (329 words) - 08:04, 8 May 2021
- vehicle in metric tons usable for traction. (optional; xs:decimal), belongsToParent: In case of describing an individual vehicle this is the reference to the3 KB (5 words) - 12:42, 8 February 2024
- fullControlled: The level crossing is activated and deactivated only from interlocking independently of the direction. This is the case for level crossings within2 KB (5 words) - 12:42, 8 February 2024
- connection is also represented by a CommercialTrainReference, the same operation needs to be performed for the other part in case a trainValidityRef is specified2 KB (5 words) - 12:43, 8 February 2024
- cannot be cleared normally. In most cases such aspect is used with a special call-on route. caution: This is used for an announcing aspect/slave aspect3 KB (5 words) - 12:42, 8 February 2024
- IL:radioBlockCenter (category Pages using Tabber parser tag)field; the leftmost digit is the digit to be dialled first. In case the NID_MN is shorter than six digits, the remaining space is to be filled with the special5 KB (671 words) - 05:46, 18 April 2022
- 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 the1 KB (5 words) - 17:41, 15 January 2024
- 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 the1 KB (5 words) - 18:41, 19 December 2019
- "Theirs" is not a solution. If necessary contact the other comitters to find a solution. Write commit messages in English. The first line of commit is a summary8 KB (1,082 words) - 13:18, 26 July 2023
- order of the vehicles in a formation is defined by increasing <trainOrder>.orderNumber. That is, the lowest order number is at the front of the train, while7 KB (771 words) - 13:39, 13 March 2023