Search results

Jump to navigation Jump to search
  • name="metadata" type="dc:elementContainer" minOccurs="0" /> <xs:element ref="rail:infrastructure" minOccurs="0" /> example: <xs:attributeGroup name="aPlaces"> <xs:attribute
    5 KB (331 words) - 10:51, 14 November 2023
  • converted from the other specific data formats from tooling of infrastructure managers. Infrastructure managers have already invested in developing own data formats
    10 bytes (450 words) - 16:12, 3 February 2020
  • of platform Information Category: Yearly Infrastructure Report Sending (producing) System: ÖBB Infrastructure AG Receiving System: SCHIG none This section
    10 bytes (225 words) - 16:12, 3 February 2020
  • structured in two parts First part being the generic description of infrastructure topology, geometry, installations and attributes (no specificity relative
    10 bytes (297 words) - 16:12, 3 February 2020
  • zulässiger Geschwindigkeiten The VzG Process is the central interface between infrastructure business processes (building maintenance) on the one hand and the operational
    10 bytes (117 words) - 16:12, 3 February 2020
  • parameters relating to the vehicle itself. Data inputs Track attributes (Infrastructure): Track Centre Line (as a polyline) Track altitude (polyline) Geometry:
    10 bytes (306 words) - 16:12, 3 February 2020
  • This shall be harmonised in one element with sub-elements. --Dirk Bräuer (Diskussion) 17:14, 14. Aug. 2015 (CEST) The mileage of the following track first
    9 KB (1,326 words) - 11:31, 12 June 2017
  • <stopPost>-element of the infrastructure If a railML file already includes the definition of <stopPost>-elements as part of the infrastructure, these stopPosts
    15 KB (1,099 words) - 07:10, 13 June 2020