Search results

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

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

<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"/>

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

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

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

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

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

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

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

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

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

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

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

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

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

Automatic Schemaexport for Element description

Automatic Schemaexport for Element descriptionReference

RS:brakeEffort of railML® version 3.2 UML-visualization of RS Documentation The description of the resulting brake effort for regular brake application as x-y-curve

RS:tractiveEffort of railML® version 3.2 UML-visualization of RS Documentation The description of the tractive effort of this engine as x-y-curve vs. speed. Subschema

Automatic Schemaexport for Element description

Automatic Schemaexport for Element descriptionReference

after finalizing the use case in the working groups alongside with this description. Rollingstock data usually includes the capabilities of the available

CAD for railway signalling; CAD für Zugsignalisierung Engineers of the railway signaling discipline use a Computer-Aided Design (CAD) tool to model a railway

Operational simulation; Betriebssimulation For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire

Earliest departure Latest departure Minimum stop time Stop type, stop description Commercial connections Infrastructure <ocpTT> Ordered stops Rolling stock

Railway Infrastructure Visualisation; Visualisierung von Schieneninfrastruktur The typical railway planning process involves several iterations with different

ÖBB-SCHIG-Reporting (NRE Reporting Austria); NRE Meldung Österreich ÖBB Infrastructure reports several properties of the line and track network periodically

</netRelation> </netRelations> <networks> <network id="nw01"> <level id="lv0" descriptionLevel="Micro"> <networkResource ref="ne_a01"/> <networkResource ref="ne_a02"/>

the use case here. The headline is made with Template: UC description (type {{UC description}}) In this section the data flows should be drafted. The headline

document for the equipment of the interlocking logic. An interlocking description consists mainly of: Track and trackside signalling components, Route control

Speed directory; VzG – Verzeichnis zulässiger Geschwindigkeiten The VzG Process is the central interface between infrastructure business processes (building

Traction power supply simulation; Simulierung der Bahnstromversorgung For various purposes it is necessary to simulate the (electrical) traction power

Adopt vehicle working scheduling to timetable changes; Umlauf an Jahresfahrplan anpassen The importing system holds timetable and vehicle working data

information of the related network in the interlocking. Therefore the description of is mainly a list of references to the related items needed for the

Only commit to the master branch directly if the changes your are commiting are complete in themselves and don't change the syntax of railML®. Changes

Extending railML®   There exists a wide range of means to extend XML Schemas. As railML® is intended for collaboration with other parties, there is a frame

Railway Laboratory (Simulations and Research Support) The aim of our project is to simulate railway traffic in laboratory conditions in order to improve

Capture schematic visualisation information of track assets; Erstellung schematischer Visualisierungsinformationen von Schienenanlagen railML data will

elementNumber="0" id="" indicatorType="cautiousDriving"> <rail3:designator description="" entry="" register=""/> <rail3:hasCommand entityCode="" ref=""/> <rail3:hasIndication

tor elementNumber="0" id="" positionInRoute="end"> <rail3:designator description="" entry="" register=""/> <rail3:hasCommand entityCode="" ref=""/> <rail3:hasIndication

Long Term Strategic Timetabling; Langfristfahrplanerstellung The timetable data prepared in this use case is not formally linked to the production process

Schematic Track Plan Infrastructure managers use maps for the visualization of their railway infrastructure. These maps comprise: Geographic maps Geoschematic

(optional; xs:string) Possible values: backward forward, fromDescription: Textual description of the origin. (optional; xs:string), ref: The actual reference

RINF-XML, and therefore support and maintain natively the railML3 RINF file description according to the evolutions of the project. The railML3 file for RINF

Using xsi:type   Before implementing any extensions to the railML® schema, please consider Dev:Extending_railML#when. The means described in this page

Parents* hasHmiIndication, hasOperatorCommand Children None Attributes: description: should be interpreted in its elements' context, substantiates the name