Search results

This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:designator>

This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:name> that might

generic subschema. It is available only in railML® 3.2. There exists an element <CO:name> that might have preceded it. Do not hesitate to contact railML.org for

generic subschema. It is available only in railML® 3.2. There exists an element <CO:designator> that might have preceded it. Do not hesitate to contact railML

This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:external> that

generic subschema. It is available only in railML® 3.2. There exists an element <CO:external> that might have preceded it. Do not hesitate to contact railML.org

Profiles for a railway track section 'Extract of a corresponding railML modelling according to ETCS Baseline 3 (part 1 of 2) <common id="co_01"> <speedProfiles>

reference systems. Thus, positioning systems are not specific for infrastructure and consequently shall be modelled in the <common> domain: <common id="co_01">

use case can be defined as a single task, performed by the end user of a system, that has some useful outcome*. It is described as a list of steps (actions

ue"> <linearCoordinateBegin positioningSystemRef="lps01" measure="0.0"/> <linearCoordinateEnd positioningSystemRef="lps01" measure="700.0"/> </associatedNetElement>

"> <linearCoordinateBegin positioningSystemRef="lps01" measure="11200.0"/> <linearCoordinateEnd positioningSystemRef="lps01" measure="11600.0"/> </associatedNetElement>

must reference one or more <trainPart>s, that all <trackElements> must have a position on the <track>, that the length of a <tunnel> is a decimal number

or 3-dimensional coordinate system, e.g. the WGS84 that is widely used by today's navigation software. Geometry: The track geometry can be described in

CO:alternative CO:approvedBy CO:checkedBy CO:etcsSpeedProfile CO:holiday CO:holidays CO:isConcessionaire CO:isContractor CO:isCustomer CO:isInfrastructureManager

screenPositioningSystem, serviceSection, signalIS, speedProfile, speedSection, spotElementProjection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement

switchIL, switchIS, switchInPosition, switchPositionInDepartureTrack, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio

serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio

UIC IRS/leaflet 920-1:2006 (also called RICS or Railway Interchange Coding System (external link)). For instance, the entry for ÖBB Infra looks like this: