Search results

– The name of the asset in the related language. @description – The additional optional description for the asset. @language – The identification of the

<rail3:etcsAreas> <rail3:etcsArea id="etcsArea01" mVersion="33"> <rail3:name description="ETCS area Border: M_VERSION 1.1 -> 2.1" language="EN" name="etcsArea_Border_BON"/>

<gmlLocations> <lineString> <description> <descriptionReference> <identifier> <name> <pos> <posList> <point> <description> <descriptionReference> <identifier>

Rtm4railml Parents* network Children networkResource (0..*) Attributes: descriptionLevel: specifies the network aggregation, such as micro, macro or meso

IL:routeActivationSection of railML® version 3.2 UML-visualization of IL Documentation Description of the route activation, i.e. automatic setting or locking when the route

Xerces with some additional flags/parameter: <target name="xml-validate" description="Validate ${xml-file} against its schema files"> <schemavalidate file="${xml-file}

IL:reasonForConflict of railML® version 3.2 UML-visualization of IL Documentation Description of the reason for the conflict. Subschema interlocking Parents* conflictingRoute

Impacts of restrictions on train operations. Infrastructure location descriptions of varying granularity: <operationalPoint> <line> <signalIS> mileage

IL:overlapReleaseTimer of railML® version 3.2 UML-visualization of IL Documentation Description of overlap release timer (duration, start condition) Subschema interlocking

Exchange of Logical Train Positions   Current train positions should be exchanged between a TMS and other systems. Current position means: the position

Example entry <trainClearanceGauge code="GA"> <description>stucture gauge GA according European standard</description> <validFor>interoperable</validFor> </trainClearanceGauge>

Reason Commited changes have affects on XML-instance files and should be announced in advance in corresponding railML® newsgroups. Decision Tagging a major

Timetabling; Fahrplan Each RU has to provide a timetable for their train- and shunting movements in a coming time period. Besides the RU itself the involved

InfrastructureInstallations OperationalPlanning Rollingstock SecondaryCauses, reasonDescription: May be used to provide a textual reasoning for the cancellation intended

RS:brakes of railML® version 3.2 UML-visualization of RS Documentation The description and technical data of the installed brake system of the vehicle. Subschema

instance routesetting. An interlocking is required to set and lock routes. A description of routes in terms of railML is of interest to both engineering and simulation

Rail Inspection Data ; Schienenprüfdaten The application broaches the issue of railway track inspection and maintenance. With the help of railML data,

the objects associated with this route and set them accordingly. The description of a route starts with the following information: @locksAutomatically

scope='commercial' connections: <commercialConnection> element(s) stop description: only <stop> elements which contain a <isCommercial> elemente will be

connections: <connection> element(s) with connType='commercial' stop description: only <stopDescription> elements with commercial='true' will be relevant including