Search results

Children ownsInfrastructureElement (0..*), ownsPlatform (0..*), ownsServiceSection (0..*), ownsSignal (0..*), ownsStoppingPlace (0..*), ownsTrack (0..*)

depends on the signalled speed of the approaching train hence on signal aspect. <refersToSignal> – This is the reference to the related signal in the interlocking

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

interlocking Parents* signalBox Children designator (0..*), firstRemoteTvdSection (1..1), hasInterface (0..1), incomingRoute (0..*), lastOwnTvdSection (1..1)

</lines> ... </functionalInfrastructure> </infrastructure> The railway line is owned by the infrastructure manager referenced via the attribute @infrastructureManagerRef

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

<networkLocation> <opEquipment> <ownsInfrastructureElement> <ownsPlatform> <ownsServiceSection> <ownsSignal> <ownsStoppingPlace> <ownsTrack> <opOperations> <opOperation>

cy> SignalAndAspect – This combines a signalIL with reference to an aspect as defined in hasAspect. <distantAspect> <masterAspect> <relatedSignalAndAspect>

set of assets in <ownsSetsOfAssets>. <specificIM id="BaneNor"> <designator register=„_SimpleRegister“ entry="BaneNor (JBV)"/> <ownsSetsOfAssets ref="ass_simpex_v0

</spotLocation> <designator register="RL100" entry="OCS"/> <opEquipment> <ownsPlatform ref="plf02"/> <ownsPlatform ref="plf03"/> </opEquipment> <opOperations> <opOperation

aspect expected at the next signal is included in this signal aspect. However, such an aspect can be combined on a signal with a speed indicator restricting

crossing type as used in Norway. The first picture show the signal flow in an overview. The signal flow is amended by the detailed list of inputs and outputs

with own mileage should always be associated with its own <linearPositioningSystem>, i.e. Advanced example of railML has three lines with their own mileages

Generic:operatingDay Generic:ownsInfrastructureElement Generic:ownsPlatform Generic:ownsPlatformEdge Generic:ownsServiceSection Generic:ownsSignal Generic:ownsStoppingPlace

Automatic Schemaexport for Element ownsSignal

Automatic Schemaexport for Element ownsSignal

Children ownsInfrastructureElement (0..*), ownsPlatform (0..*), ownsServiceSection (0..*), ownsSignal (0..*), ownsStoppingPlace (0..*), ownsTrack (0..*)

operationalPoint Children ownsPlatform (0..*), ownsServiceSection (0..*), ownsSignal (0..*), ownsStoppingPlace (0..*), ownsTrack (0..*) Attributes: nu

<name> <networkLocation> <opEquipment> <ownsPlatform> <ownsServiceSection> <ownsSignal> <ownsStoppingPlace> <ownsTrack> <opOperations> <opOperation> <spotLocation>

Release time Switching time (of switches) (optional) Signal aspect at the start signal (which signal aspect is provided when the block section is reserved)