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-up8 KB (307 words) - 11:40, 20 August 2024
- IS:line (category Infrastructure Elements)</functionalInfrastructure> </infrastructure> The railway line is owned by the infrastructure manager referenced via the attribute @infrastructureManagerRef9 KB (873 words) - 11:03, 13 May 2024
- IS:crossing (category Infrastructure Elements)ref="swi313"/> 462 </track> 463 </tracks> 464 </functionalInfrastructure> 465</infrastructure>18 KB (1,737 words) - 17:48, 23 May 2024
- asset <crossing> from the infrastructure part. <branchUpLeft> – This the reference to the underlying track element in infrastructure forming its upper left15 KB (1,510 words) - 19:13, 14 February 2022
- IS:mileageChange (category Infrastructure 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 questions2 KB (222 words) - 18:16, 23 May 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
- 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
- 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 railway2 KB (180 words) - 13:43, 13 March 2023
- 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 elements3 KB (335 words) - 13:48, 13 March 2023
- also possible to locate the crossing at tracks 30 and 27 in railML® 3. According to in the railML® 2 wiki, the navigability of straight branches is described29 KB (2,875 words) - 15:03, 10 September 2024
- Dev:Simple crossing (section Comparison with railML® 2)@passable=“true” is not defined. In railML® 3 navigability is defined explicitly by a corresponding attribute. In railML® 2 <crossing> is used to describe24 KB (2,447 words) - 17:49, 30 May 2024
- Dev:Railway switch (section Comparison with railML® 2)@applicationDirection railML® 3. The orientation of a switch in railML® 2 was always dependent on the direction of the track. In railML® 3 the directions specified18 KB (2,069 words) - 17:38, 8 August 2024
- Dev:Splitting and merging railML files (section Splitting functional infrastructure entities with <linearLocation> or <areaLocation>)</lines> </functionalInfrastructure> </infrastructure> </railML> <?xml version="1.0" encoding="UTF-8"?> <railML xmlns="https://www.railml.org/schemas/3.1"546 KB (49,685 words) - 17:13, 11 September 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 minimal9 KB (677 words) - 14:07, 4 June 2024
- 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,277 words) - 18:25, 22 July 2024
- Return to UC:Use_cases in the railML® 3 wiki/in the railML® 2 wiki29 bytes (16 words) - 19:18, 4 January 2023
- <xsl:when test="ancestor::*:infrastructure"> <xsl:text>IS</xsl:text> </xsl:when> <xsl:when test="ancestor::*:infrastructureVisualizations"> <xsl:text>IS</xsl:text>3 KB (237 words) - 19:18, 4 January 2023
- schema. It will continue the “railML® 3.1 Tutorial Part1: Infrastructure” without repeating the basics of XML. In the text, railML <elements> are put into XML8 KB (1,122 words) - 19:18, 4 January 2023
- ion additionalName IS infrastructure description;name;lang;xsi:type metadata IS infrastructure infraAttrGroups IS infrastructure infraAttributes infraAttributes46 KB (4,606 words) - 19:18, 4 January 2023
- railML® 3 Wiki – RailTopoModel® Wiki18 bytes (0 words) - 19:18, 4 January 2023