Search results

Jump to navigation Jump to search
  • of the lateral offset in unit specified by the referenced positioning system (optional; xs:double), measure: This attribute is not documented in the schema
    1 KB (5 words) - 18:16, 23 December 2019
  • latitude (obligatory; xs:double), z: altitude (optional; xs:double), positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (obligatory;
    1 KB (5 words) - 15:45, 17 May 2024
  • latitude (obligatory; xs:double), z: altitude (optional; xs:double), positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (obligatory;
    1,020 bytes (5 words) - 15:45, 17 May 2024
  • requiresLevelCrossingInState (0..*), requiresSwitchInPosition (0..*) Attributes: releaseSpeed: Release speed in km/h associated with the overlap (optional; xs:decimal)
    2 KB (5 words) - 14:22, 24 January 2020
  • advance of a stop signal, or a stopping point in a continuous signalling system, which must be kept clear to avoid the risk of collision should a train
    2 KB (5 words) - 15:48, 17 May 2024
  • is not documented in the schema! Subschema Rtm4railml Parents* associatedPositioningSystem Children geometricCoordinate (0..*), linearCoordinate (0..*) Attributes:
    917 bytes (5 words) - 14:21, 24 January 2020
  • attribute is not documented in the schema! (optional; xs:double), positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (obligatory;
    861 bytes (5 words) - 18:16, 23 December 2019
  • attribute is not documented in the schema! (optional; xs:double), positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (obligatory;
    857 bytes (5 words) - 18:16, 23 December 2019
  • easier for the bidders to reproduce the timetable in their own software systems. This allows a quicker calculation e. g. of the number of vehicles necessary
    16 KB (1,903 words) - 13:27, 13 March 2023
  • "> <associatedNetElement netElementRef="ne_102" keepsOrientation="true" posBegin="200.0" posEnd="600.0"> <linearCoordinateBegin positioningSystemRef="lps01"
    17 KB (2,081 words) - 19:18, 4 January 2023
  • CO:isVehicleOwner CO:name CO:positioning CO:geometricPositioningSystems RTM:geometricPositioningSystem RTM:isValid CO:name CO:linearPositioningSystems RTM:linearPositioningSystem
    77 KB (2,609 words) - 19:18, 4 January 2023
  • "> <associatedNetElement netElementRef="ne_102" keepsOrientation="true" posBegin="200.0" posEnd="600.0"> <linearCoordinateBegin positioningSystemRef="lps01"
    3 KB (303 words) - 19:18, 4 January 2023
  • NEST WG each line with own mileage should always be associated with its own <linearPositioningSystem>, i.e. Advanced example of railML has three lines with
    9 KB (3 words) - 14:14, 31 May 2024
View ( | next 20) (20 | 50 | 100 | 250 | 500)