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-up7 KB (287 words) - 15:43, 8 April 2024
- that includes simple crossing as its part. Refer to the guide (link to the railML® website) for the extended tutorial. 1 <infrastructure id="is_01"> 2 <topology>19 KB (1,743 words) - 14:38, 11 April 2024
- The element documentation has been changed. The parents have changed. The attributes have been changed.949 bytes (15 words) - 16:52, 19 April 2024
- <netElement> and <netRelation> instances are drawn. Transferring this topology into railML we need first the four instances of <netElement>. <netElements> <netElement15 KB (1,510 words) - 19:13, 14 February 2022
- IS:line (section Documentation)section. The attribute <infrastructureManager>@code points to a value in the railML codelist InfrastructureManagers.xml where many national and regional infrastructure9 KB (873 words) - 14:24, 11 April 2024
- The element documentation has been changed. The attributes have been changed.780 bytes (11 words) - 16:56, 19 April 2024
- IS:mileageChange (section Documentation)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 questions2 KB (228 words) - 13:18, 17 April 2024
- CO:positioning (section Documentation)of RailTopoModel®, railML® 3.1 allows to define <netElement> elements with a certain length. This extension is based on the assumption that railML topology11 KB (1,110 words) - 09:59, 29 April 2024
- See intrinsic coordinate in RailTopoModel®'s wiki. The element documentation has been changed. The attributes have been changed.620 bytes (19 words) - 16:25, 19 April 2024
- by one of the railML® working groups (link to the railML® website) or suggested by anyone through a post in the forum (link to the railML® website). If4 KB (579 words) - 16:49, 13 March 2023
- XML-Schema for element RTM:associatedNetElement of railML® version 3.2 UML-visualization of RTM Documentation defines LinearLocation of the path of each track2 KB (5 words) - 12:39, 8 February 2024
- RTM:associatedNetElement/3.1 (category Missing Element Documentation/3.1)XML-Schema for element RTM:associatedNetElement of railML® version 3.1 UML-visualization of RTM Documentation This element is not documented in the schema!1 KB (5 words) - 14:21, 24 January 2020
- XML-Schema for element RTM:intrinsicCoordinate of railML® version 3.2 UML-visualization of RTM Documentation coordinate X after the start of the element in1 KB (5 words) - 12:39, 8 February 2024
- the XML-Schema for element RTM:spotLocation of railML® version 3.2 UML-visualization of RTM Documentation defines the concept of punctual location on a3 KB (5 words) - 12:39, 8 February 2024
- RTM:intrinsicCoordinate/3.1 (category Missing Element Documentation/3.1)XML-Schema for element RTM:intrinsicCoordinate of railML® version 3.1 UML-visualization of RTM Documentation This element is not documented in the schema!917 bytes (5 words) - 14:21, 24 January 2020
- RTM:spotLocation/3.1 (category Missing Element Documentation/3.1)the XML-Schema for element RTM:spotLocation of railML® version 3.1 UML-visualization of RTM Documentation This element is not documented in the schema!3 KB (5 words) - 14:21, 24 January 2020
- required for railML® 3.2 and higher. For all versions of railML® 2 plus for railML® 3.1, the proposed means are xs:any, xs:anyAttribute and rail:tOtherEnumerationValue18 KB (2,309 words) - 14:28, 1 August 2022