Search results

Multiplicity   The section Multiplicity in element documentation pages reports the occurence indicators of the respective element, by name the values of

elements, that are not referred to within the railML® file. The general railML® description states the following semantics for this attribute. id: XML-file-wide

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

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®

whole formation. <TT:stopDescription> TT:006 2018-09-03 2019-06-20 Constraints between the attributes <ocpTT>.ocpType, <stopDescription>.guaranteedPass, .commercial

{{UC title}}) What is the application behind the use case? Which data in general is required? Which kind of tool/application provides this data? Who usually

In order to get the current stable railML® package, go to the Download section (link to the railML® website) whilst logged on. Current stable releases

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

reference sources without weblinks (e.g. books), use Template:Source. A general outline how to include images in mediawiki can be found at Help:Images ()

UC:IS:RailInspectionData): Head/Title Description: A sketch of the task, the necessary steps and the requirements in general. What is the application behind

<alternative> code, description, id, name, rail:lang, xsi:type <additionalName> description, name, rail:lang, xsi:type <phase> code, description, endDate, id

In some cases, attributes in railML® are defined by physical units. All employed units are listed in Category:Unit. A historic overview regarding railML®

|constraints_en= |constraints_de= |notes_en= |notes_de= |name= |name_de= |description= |description_de= |childs= |inheritedAttributes= |attributes_en= |attributes_de=

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

Generally, examples are more illustrative, if they have a real background. As a general rule, minimal examples are more convenient to convey the principles of railML®

Sometimes there is a little confusion about the correct XML syntax in attribute definitions. Which version is valid, which not? <element attribute="value"/>

Declaration Schema Components" example: <xs:attribute name="description" type="rail:tElementDescription" /> example: <xs:attribute name="id" type="rail:tGenericID"

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

approach is focussed on providing a very detailed description. In a microscopic infrastructure description in railML®, tracks usually are limited by switches

This article explains basic concepts, how to handle reversing trains and formations within the timetable subschema. Dieser Artikel erklärt Grundlagen des

namespace (identical string) as defined by its corresponding XML Schema. For general information about namespaces see Defining namespaces and validating railML®

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:

Defaults Optional attributes may have defaults. Please, employ Template:Constraint, wherever defaults are employed. All pages where defaults are defined

has to be used by exactly one operational and one commercial train. In general, if we have the situation of train coupling and sharing, there is one ‘long’

name="Schienenersatzverkehr" lang="de"/> <category id="cat_3" code="EC" name="EuroCity" description="Schnellfahrende Reisezüge im internationalen Verkehr mit besonderem Komfort"

railML® schema changes between railML® 2.0 and railML® 2.1   This site collects sources helping you to compare railML® 2.0 and railML® 2.1. Changes are

If a train is not included in the railML® file with its entire itinerary and already has a midnight transition before "entering" the railML® file network

Guidelines for implementing new elements in railML® schemes This page gives instructions for implementing new elements for the railML® XML schema in the

agreed. They may occur in German railML® files but should not be used as general “pattern”. No infrastructural difference to a simple halt, just difference

<xs:annotation> <xs:documentation>additional names and its according descriptions to be provided in other languages, dialects, encodings...</xs:documentation>

<infrastructureManager> code, description, id, name, rail:lang <additionalName> description, name, rail:lang, xsi:type <vehicleManufacturer> code, description, id, name,

<infrastructureManager> code, description, id, name, rail:lang <additionalName> description, name, rail:lang, xsi:type <vehicleManufacturer> code, description, id, name,

railVIVID® railVIVID® is the railML® validation and viewer tool. It was financed by several European Railway Infrastructure Managers through and was initial

imes /trainParts/trainPart/ocpsTT/ocpTT/stopDescription /trainParts/trainPart/ocpsTT/ocpTT/stopDescription/stopTimes /trains/train/trainPartSequence /

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

availability of infrastructure elements and speed profiles Representation of general time restrictions using newly introduced attributes in railML® 2.4 IS New

gPeriodRef /ocpTT/stopDescription/trackInfo@track /ocpTT/stopDescription/trackInfo@platform New elements: /ocpTT/stopDescription/trackInfo

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

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

+ </xs:annotation> + </xs:element> <xs:element name="generalInfraAttributes" type="rail:eGeneralInfraAttributes" minOccurs="0"> <xs:annotation> <xs:documentation

trackBegin   Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]

trackEnd   Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]

</xs:annotation> + </xs:attribute> <xs:attribute name="remarks" type="rail:tElementDescription"> <xs:annotation> <xs:documentation>This is to further explain the 'state'

<speedProfile id="sp1" name="Basis" influence="increasing" description="speed profile as general basis for other overlaying profiles"/> <speedProfile id="sp2"

in a feature branch to not contaminate the branches that are of a more general nature with intermediate solutions. Merge back your changes when you are

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

menschenlesbaren Datenfeldern. (introduced with version 2.1) description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

generalInfraAttribute   Parent: <generalInfraAttributes> Children: <attributes> [0..∞] The element generalInfraAttribute describes a single pre-defined

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

generalInfraAttributes   Parent: <infraAttributes> Children: <generalInfraAttribute> [0..1] The element <generalInfraAttributes> works as a "container

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

arrival="10:59:00" departure="11:04:00"/> <stopDescription> <platformEdgeRef ref="_pe" /> </stopDescription> </ocpTT> The above (incomplete) example describes

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

</xs:complexType> <xs:complexType name="eGeneralInfraAttributes"> <xs:sequence> - <xs:element name="generalInfraAttribute" type="rail:eGeneralInfraAttribute" minOccurs="0"

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

[0..1] The element stopDescription describes data concerning the stop (or pass) at the parent ocpTT. Das Element stopDescription beschreibt Daten, die den

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

please read Train coupling and Sharing - On trains and train parts in general. Not yet described. / Noch nicht beschrieben.

name="tStopDescription"> + <xs:complexContent> + <xs:extension base="rail:tBaseStopDescription"> + <xs:attributeGroup ref="rail:aStopDescription" /> + </xs:extension>

</xs:complexType> - - <!----> - <!-- generalInfraAttributes --> - <!-- +- generalInfraAttribute --> - <!----> - - <xs:complexType name="eGeneralInfraAttributes"> - <xs:sequence>

from such special use cases, railML® is a file format for general data exchange. In this general meaning - with no precise data source and destination -

startDate="2020-12-13" endDate="2021-12-11" description="2020/2021"/> <operatingPeriod id="opp_0" description="nur 10.-16.02." timetablePeriodRef="ttp_2020_21"

attributes   Parent: <generalInfraAttribute> Children: <attribute> [0..1] A <attributes> represents attributes of the infrastructure. The <attributes>

ts> as container groups ocp for journey time measurement points in the general sense (such as stations, stops, line changes, signals, etc.). Each infrastructure

couplers for main line railways by Georg Fischer AG, Schaffhausen GF_Coupler general halfautomatic couplers by Georg Fischer AG, Schaffhausen GFN half automatic

calculated/scheduled 'instance' of a formation but not for the formation in general. Due to the usage or not-usage of auxiliary brakes in regular or emergency

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

<propulsion> abgestimmt sein. Not yet described. / Noch nicht beschrieben. In general the auxiliaries of a train are supplied from the locomotive. Therefore the

Verbindungen für Steuerung oder Stromversorgung. designType: This is the description of design and function of the electrical coupling. Possible values are:

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

precise semantics of this attribute are not fixed in the standard. The general idea for this is to allow for specifying an attribute that distinguishes

<connection> element. orientation: Orientation of the switch element relative to general track direction (aligned with increasing mileage) incoming: A track is merging

used as a general input value for timetable planning (depending on the type of stop, vehicle type or train category among other things). In general, the time

<connection> element. orientation: Orientation of the switch element relative to general track direction (aligned with increasing mileage) incoming: A track is merging

additionalReserve="PT18S"/> </sectionTT> <stopDescription commercial="true"> <stopTimes minimalTime="PT42S" /> </stopDescription> </ocpTT> <ocpTT sequence="25" ocpRef="ocp_Y"

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

this use case. The use case covers the exchange of the following data in general: <train> elements with their routes and timings (in associated <trainPart>

Description: Infrastructure Managers (IM) wish to represent their railway system in terms of standardised data types. Eulynx collects the types and attributes

to structure an element documentation page within The railML® 2 wiki. A General outline for contibuting to this wiki can be found here. If you want to start

varies depending to the usage of the data. On the one hand there is the general data supply with the timetable e.g. for the next seven days in advance.

departure: xs:time; optional departureDay: xs:integer; default: 0; optional In general it is expected that all <times> instances of the same @scope are consistent

optional Train City Night Line 242: <train id="o242" type="operational" description="Berlin - Paris" trainNumber="242"> <trainPartSequence sequence="1"> <

Hardware and cable plan Subschema: Interlocking For general information on use cases see UC:Use cases

Infrastructure   Related subschemas: IL TT RS  Reported by: ProRail For general information on use cases see UC:Use cases

Railway Infrastructure Visualisation (RAIV) Subschema: Infrastructure For general information on use cases see UC:Use cases

Infrastructure Reported by: Czech Technical University in Prague (ČVUT) For general information on use cases see UC:Use cases

of track assets Subschema: Infrastructure   Related subschemas: IL  For general information on use cases see UC:Use cases

Subschema: Infrastructure   Related subschemas: IL  Reported by: IS For general information on use cases see UC:Use cases

Subschema: Infrastructure   Related subschemas: IL  Reported by: JBD For general information on use cases see UC:Use cases

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

select such a group and configure the toplogy would be useful. There is no description of this as of today. If RailML is introduced, the system will need to

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

Systems (SCWS) Subschema: Interlocking Reported by: Thales Austria For general information on use cases see UC:Use cases

Planning (MAPL) Subschema: Infrastructure   Related subschemas: RS  For general information on use cases see UC:Use cases

Infrastructure   Related subschemas: IL TT  Reported by: Bombardier For general information on use cases see UC:Use cases

Network Statement (NEST) Subschema: Infrastructure Reported by: SŽDC For general information on use cases see UC:Use cases

Infrastructure   Related subschemas: IL  Reported by: RailComplete For general information on use cases see UC:Use cases

simulation Subschema: Rollingstock   Related subschemas: IS IL TT  For general information on use cases see UC:Use cases

System (PISY) Subschema: Infrastructure   Related subschemas: TT RS  For general information on use cases see UC:Use cases

NRE Reporting Subschema: Infrastructure Reported by: ÖBB For general information on use cases see UC:Use cases

Operation and Control Subschema: Interlocking For general information on use cases see UC:Use cases

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

Speed directory Subschema: Infrastructure Reported by: ÖBB For general information on use cases see UC:Use cases

Positioning and Map-Matching (POSI) Subschema: Infrastructure For general information on use cases see UC:Use cases

Traffic Management Plan Description / Beschreibung / Description The UseCase TrafficManagementPlan (TMP) defines exchange of information between Timetable

Subschema: Infrastructure   Related subschemas: TT RS  Reported by: IS For general information on use cases see UC:Use cases

Infrastructure Recording Subschema: Infrastructure Reported by: Bahnkonzept For general information on use cases see UC:Use cases

Timetable and Rostering   Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases

supply simulation Subschema: Rollingstock   Related subschemas: IS TT  For general information on use cases see UC:Use cases

Interlocking For general information on use cases see UC:Use cases

Topology (schematic drawing) on micro, meso and macroscopic level, with description of data (values and position) Timetable graph, Platform occupation diagram

Timetable and Rostering   Related subschemas: IS IL RS  Reported by: SMA For general information on use cases see UC:Use cases

Timetable and Rostering   Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases

RailTopoModel® compliant railway network description enriched with the design layout and infrastructure description including also the essential information

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

line network Construction: assets along the track / line Track layout description ETCS level transition locations Points Signals BaliseGroups (if available

Timetable and Rostering   Related subschemas: IS RS  Reported by: iRFP For general information on use cases see UC:Use cases

vehicle. The activities mentioned can be carried out one after the other. Description of parallel work is not included in this use case. For the purposes of

systems. The typically necessary data for this UC can be separated into 3 general domains: Infrastructure (RTCI-a) Rollingstock and (RTCI-b) Timetable (RTCI-c)

competition (call for proposals) Ausschreibungsfahrplan; ??? Description / Beschreibung / Description The use case describes a timetable which is transferred

TMS Subschema: Infrastructure Reported by: DLR for In2Rail project For general information on use cases see UC:Use cases

Posession Management Subschema: Infrastructure For general information on use cases see UC:Use cases

Reason: In purely mesoscopic or macroscopic railway network descriptions a detailed description of operational routing (e.g. change of driving direction)

Infrastructure   Related subschemas: IL TT RS  Reported by: Siemens Mobility For general information on use cases see UC:Use cases