Search results

railML® version 3.2 UML-visualization of generic Documentation name and description of the asset dependent on the language Subschema generic Parents* derailerIL

format and language for the data to be exchanged. The aim of the use case description is to formulate requirements on the technical implementation of the data

Concepts & examples The railML® Infrastructure subschema is focused on the description of the railway network infrastructure including all its various facets

vehicleManufacturer, vehicleOperator, weightLimit Children None Attributes: description: should be interpreted in its elements' context, substantiates the name

railML® version 3.2 UML-visualization of generic Documentation name and description of the object dependent on the language Subschema generic Parents* combinedRoute

Downloading and using railML® This Guideline is intended to help you through the first steps in downloading and using railML®. If you are not yet registered

elements' context (e.g. signal/name, vehicle/name) (obligatory; xs:string), description: should be interpreted in its elements' context, substantiates the name

number of the information. (optional; xs:nonNegativeInteger), description: The verbal description of the information. (optional; xs:string), normalState: The

number of the information. (optional; xs:nonNegativeInteger), description: The verbal description of the information. (optional; xs:string), normalState: The

trainRadio, tunnelGateIS, underCrossing, weightLimit Children None Attributes: description: This attribute is not documented in the schema! (optional; xs:string)

typicalTimeToOpen="P1D"> <rail3:designator description="" entry="" register=""/> <rail3:assetName description="" language="EN" name=""/> <rail3:belongsToOperationalPoint

IL:routeEntry of railML® version 3.2 UML-visualization of IL Documentation Description of the start point of the route. This is normally a signal. Subschema

❗ Please note, that this page is made for saving ideas, concepts and descriptions for the upcoming railML® 3.2 Timetable scheme. This page shall be replaced

IL:routeExit of railML® version 3.2 UML-visualization of IL Documentation Description of the route destination point. In most cases the route destination is

isSignalized="false" refersToTrain="endOfTrain"> <name name="JNA-201" description="Speed section" language="EN"/> <linearLocation id="spsec100_lloc" ap

version 3.2 UML-visualization of IL Documentation Reference to physical description of level crossing interface with list of commands to the field and notifications

schema! Subschema infrastructure Parents* polygon Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (0..1)

{{Attr|processStatus}}, {{Attr|id}}, {{Attr|code}}, {{Attr|name}}, {{Attr|description}}, {{Attr|xml:lang}} Describe your changes with "Summary" or Zusammenfassung

the schema! Subschema infrastructure Parents* circle Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (1..1)

Please, notice the basic Principles for joining this wiki, as explained here The working language of this wiki is English. The complete content should

downleft-rightup: Description of a logical position of a simple crossing within a route path from the lower left to upper right upleft-rightdown: Description of a logical

IL:deactivatedBy of railML® version 3.2 UML-visualization of IL Documentation The description of deactivation conditions for this level crossing. Subschema interlocking

version 3.2 UML-visualization of generic Documentation particular name and description of the system asset dependent on language Subschema generic Parents* controller

IL:activationCondition of railML® version 3.2 UML-visualization of IL Documentation Description of the possible activation conditions of this level crossing. Subschema

name="InterCity" description="Fast large city connection" trainUsage="passenger" my:colour="red"/> <category id="c2" code="RE" name="RegionalExpress" description="Fast

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

to reference this element within railML. @description – The string element takes a more detailed description of the logic. This is for information of the

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

test the limmitations of applications. Good examples contain a brief description (abstract) information of the content (number, formats and functions of

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

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

Rtm4railml Parents* network Children networkResource (0..*) Attributes: descriptionLevel: This attribute is not documented in the schema! (optional; xs:string)

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

Guideline for participating in the development process This guideline is supposed to explain the development of the railML® schema and how you can contribute

The following templates may be used at every wiki page for referring to a certain railML® element documentation page. The link is shown in angle brackets:

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

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

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

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

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

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

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

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

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

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

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

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

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