Search results

the <track> has no topologic dimension. Considering the <track> as a pure NetEntity derived object that is placed on top of a topology, the track does

might be a physicalEnd or the endOfSupervision. The first one is related to a <bufferStop> which marks the physical end of a track. The latter one is related

stationIndicator, stoppingPlace, switchIL, switchIS, switchInPosition, track, trackBed, trackGauge, trackIL, trainDetectionElement, trainNumberField, trainProtectionElement

register="_Example" 299 entry="TRACK track9"/> 300 <length value="240.000" 301 type="physical"/> 302 <trackEnd ref="swi53"/> 303 </track> 304 <track id="trk25" 305 mainDirection="both"

by a speedSection element. The speedSection element defines the start and end location of the speed section and the maximum speed limit valid for this section

switchIS, switchInPosition, switchPositionInDepartureTrack, track, trackBed, trackGauge, trackIL, trailingSwitchInPosition, trainDetectionElement, trainEngine

<hasIndication> <hasIndicator> <hasOverlap> <objectName> <refersTo> <endOfTracks> <endOfTrack> <assetName> <belongsToOperationalPoint> <designator> <hasCommand>

</linearLocation> <trackBegin ref="brd01" /> <trackEnd ref="crx01" /> <length type="operational" value="100" /> </track> <track type="mainTrack" id="trk02">

" intrinsicCoordEnd="0" keepsOrientation="true"/> <associatedElement netElementRef="ne_x11" intrinsicCoordBegin="0" intrinsicCoordEnd="1" keepsOrientation="true"/>

@isBerthingTrack is set to true. Within the simple example there are different kind of TVD sections. Here is a platform track with physical track end at one

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

via its attribute @type (e.g. "axleCounter" or "insulatedRailJoint" or "trackCircuit"). If the train detection element/system is not included in the list

requirements of uniqueness concerning ID. The physical features of tracks and trackside components (“track assets”) are described in the infrastructure subschema,

Autoexport from the XML-Schema for element IL:endOfTracks of railML® version 3.2 UML-visualization of IL Documentation Container for all limits in the

It is available only in railML® 3.1. There exists an element <generic:trackEnd> that might have replaced it. Do not hesitate to contact railML.org for

</controlsSystemAsset> <controlsTrackAsset extentOfControl="fullControl"> <connectedTrackAsset ref="A01T"/> </controlsTrackAsset> … <controlsTrackAsset extentOfControl="fullControl">

the danger point is situated at the end of a TVD section. <situatedAtTrackAsset> – This is the reference to the track asset the danger point is located.

conflictingRoute, controller, dangerPoint, derailerIL, destinationPoint, endOfTrack, genericDetector, implementsElementGroup, interface, keyLockIL, levelCrossingIL

combinedRoute, conflictingRoute, dangerPoint, derailerIL, destinationPoint, endOfTrack, genericDetector, implementsElementGroup, interface, keyLockIL, levelCrossingIL

combinedRoute, conflictingRoute, dangerPoint, derailerIL, destinationPoint, endOfTrack, genericDetector, implementsElementGroup, interface, keyLockIL, levelCrossingIL