Search results
Jump to navigation
Jump to search
- from IS state geoCoord absPos;absPosOffset;ocpRef;pos geoCoord IS from coord;epsgCode;extraHeight;heightEpsgCode to IS state geoCoord absPos;absPosOffset;ocpRef;pos46 KB (4,606 words) - 19:18, 4 January 2023
- xsi:schemaLocation="http://www.railml.org/schemas/2016 railML.xsd "> <rail:metadata> <rail:organizationalUnits> <rail:infrastructureManager code="" description=""63 KB (5,185 words) - 19:18, 4 January 2023
- RAILML:railML CO:common CO:electrificationSystems CO:electrificationSystem CO:organizationalUnits CO:concessionaire CO:isConcessionaire CO:isContractor77 KB (2,609 words) - 19:18, 4 January 2023
- User:RailML Coord Documentation/IS:baliseGroup (section Semantic Rules applicable for railML® element “baliseGroup”)https://forum.railml.org (link to the railML® website) – reporting the missing information to be modelled in railML®. railML®.org will provide a suggestion for22 KB (2,620 words) - 19:18, 4 January 2023
- User:RailML Coord Documentation/CO:speedProfile (section Extract of a corresponding railML® modelling according to ETCS Baseline 3 (part 1 of 2):)Profile (SPP) is uniquely described by the railML® attribute @isBasicSpeedProfile. The modelling in railML® is <common id="co_01"> <speedProfiles> <speedProfile17 KB (2,081 words) - 19:18, 4 January 2023
- Test4 bytes (1 word) - 10:52, 8 February 2024
- 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) - 15:45, 17 May 2024
- Codelist-tags ✔ RailML Coord Documentation (talk) 15:09, 3 April 2023 (CEST) Dev:TrainProtectionSystems Problem: Codelist-tags ✔ RailML Coord Documentation (talk)5 KB (363 words) - 14:51, 24 April 2023
- 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
- 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,307 words) - 18:01, 13 June 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) - 15:45, 17 May 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
- Ich bin der Bot von User:RailML Coord Documentation. Was ich tue kann man teilweise auf User:RailML_Bot_Documentation/Log sehen.137 bytes (20 words) - 13:12, 2 November 2023
- comment. -->{{docBase |element=geoCoord |comment= |subschema=[[IS]] |parent=[[from]] |children=None |attributes=coord<br>epsgCode<br>extraH339 KB (42,145 words) - 19:18, 4 January 2023
- Return to UC:Use_cases in the railML® 3 wiki/in the railML® 2 wiki20 KB (16 words) - 09:41, 25 June 2024
- {{edited|IS:infrastructure}} delivers: December 19th 2019 by User:RailML Coord Documentation {{edited|MZAJvL28BfjTjRGhXbWBjWLSRV6bKD}} delivers: FIXME Page506 bytes (30 words) - 14:22, 30 November 2023