Search results

changes between the railML® 2 minor versions are available in the following descriptions: Changes between railML® 2.0 and railML® 2.1 Changes between railML®

<name>, with attributes name and description. name: A short, human readable Identifier. Uniqueness is not required. description: Human readable text that gives

vehicle, vehiclePart, weightLimit, workZone Children None Attributes: description: description of the designator, which can be used to provide basic information

complete bitmask it defines the bit position in the byte. @description – This is just the description/meaning of the command send. @normalState – This gives

Consequently, for balise based ATP systems, there are two levels of description: the higher level “balise group”, which is presented by the railML® element

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

tunnelGateIS, underCrossing, weightLimit Children None Attributes: description: description of the external identifier or reference, providing basic information

isBasicSpeedProfile="true" mVersion="32"> <name name="ETCS Basic SSP" description="Basic ETCS static speed profile used by trains for which no Specific

Autoexport from the XML-Schema for element GML4RAILML:description of railML® version 3.2   Documentation deprecated This element is part of GML, version

Autoexport from the XML-Schema for element GML4RAILML:descriptionReference of railML® version 3.2   Documentation gml:ReferenceType is intended to be used

. UNISIG-baseline 3 is in use (mVersion="32"). Corresponding railML® description: <baliseGroups> <baliseGroup id="bg1" mileageDirection="nominal" coverage="none"

be tolerated due to running self-test. (optional; xs:duration), description: Description of the logic. (optional; xs:string), elementNumber: element number

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

release is indicated to the operator. (optional; xs:duration), description: Description of the logic. (optional; xs:string), elementNumber: element number

detail is usually included. On what does this level of detail depend. This description is usually the starting point for the next level of determining a more

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

ref: a reference to an external element (optional; xs:string), description: description of the external identifier or reference, providing basic information

Element ID Proposal date Date of acception Date of deprecation Description <TT:operationalTrainSectionPart> TT:001 2022-09-15 2022-10-13 There is

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

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

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

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

❗ 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

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

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

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

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