User:Ferri Leberl/Hauptseite

From railML 2 Wiki
Jump to: navigation, search
Filename extension  .railml, .railmlx
Developed by
Initial release 22 December 2005
Latest release 2.2 (11 June 2013)
Type of format  Railway exchange format
Extended from XML
Standard Industry standard
Open format? Yes, CC BY-NC-ND

Welcome to the railML® wiki / Willkommen im railML®-Wiki / Bienvenue au Wiki® du railML

railML® (railway Markup Language) is an open, XML based data exchange format for data interoperability of railway applications. For further information please visit the official project website or Wikipedia.

This wiki should support you in the development of railML® interfaces and inform you about the basic elements and modelling concepts of the railML® schema.

This wiki is being kept in English. At certain points information is provided additionally also in German and/or French. You are invited to contribute to this wiki. Please, see our guideline "How to join the railML wiki" to get to know the standards of railML's wiki and the procedure for getting a writer's account.

railML® (railway Markup Language) ist ein offenes, XML-basiertes Datenaustauschformat zur gegenseitigen Benützbarkeit der Daten von Anwendungen im Eisenbahnbereich. Für weitere Informationen besuchen Sie bitte die offizielle Projektwebsite oder Wikipedia.

Ziel dieses Wikis ist, Sie bei der Entwicklung von railML®-Schnittstellen zu unterstützen und Sie über die grundlegenden Elemente und Modellierungskonzepte des railML®-Schemas zu informieren.

Dieses Wiki wird auf Englisch geführt. Einzelne Informationen stellen wir außerdem auf Deutsch und Französisch zur Verfügung. Sie sind herzlich eingeladen, sich an der Entwicklung dieses Wikis zu beteiligen. Lesen Sie dazu bitte unseren Leitfaden How to join the railML wiki, um sich mit den Standards des railML®-Wikis vertraut zu machen und die Vorgangsweise zur Erteilung eines Autorenaccounts kennenzulernen.

railML® (railway Markup Language) est un format public, fondé sur XML et destiné à l’échange de données ferroviaires, en vue de l’interopérabilité des applications informatiques. Pour plus d’informations, veuillez consulter la page de projet officielle dans Wikipedia.

Le présent wiki vous aidera à développer des interfaces railML®, notamment en vous présentant les éléments de base et les concepts fondamentaux du schéma railML®.

Ce wiki est tenu en anglais. Des informations particulières sont parfois fournies en français ou en allemand. Vous êtes invité(e) à y contribuer : veuillez consulter notre guide "How to join the railML wiki", qui vous indiquera les règles applicables au wiki, ainsi que la marche à suivre pour y contribuer en tant qu’auteur.

Current railML schema

Currently there exist four subschemata: Infrastructure (IS), Timetable and Rostering (TT), Rollingstock (RS) and Interlocking (IL). Elements that do not fit into this structure are subsumed in the class Common (CO).

Open for a list of the current coordinators of the respective schemas.

Timetable and Rostering (TT)

The timetable subschema is part of the complete railML schema providing a data structure in XML language for the exchange of railway specific data. It is the subschema that is employed most.

The timetable schema provides container for all data about any kind of timetables for operational or conceptional purposes. A flexible description of operating periods, which are important elements while dealing with timetables, is also included in the schema.

The subschema contains the following information:

  • Operating Periods: The operating days for train services or rostering.
  • Train Parts: The basic parts of a train as a sequence of operation or control points with the same characteristics such as formation and operating period. The train part includes the actual information regarding the path of the train as well as the corresponding schedule information.
  • Trains: One or more train parts make up a train and represent either the operational or the commercial view of the train run.
  • Rostering: Train parts can be linked to form the circulations necessary for rostering (rolling stock schedules).

Infrastructure (IS)

The railML® Infrastructure subschema is focused on the description of the railway network infrastructure including all its various facets that are needed by the data exchange applications. In particular, the railML infrastructure schema contains the following information:

  • Topology. The track network is described as a topological node edge model.
  • Coordinates. All railway infrastructure elements can be located in an arbitrary 2- or 3-dimensional coordinate system, e.g. the WRG84 that is widely used by today's navigation software.
  • Geometry. The track geometry can be described in terms of radius and gradient.
  • Railway infrastructure elements enclose a variety of railway relevant assets that can be found on, under, over or next to the railway track, e.g. balises, platform edges and level crossings.
  • Further located elements encompass elements that are closely linked with the railway infrastructure, but that "cannot be touched", e.g. speed profiles and track conditions.

Rollingstock (RS)

The rollingstock subschema is part of the complete railML schema providing a data structure in XML language for the exchange of railway specific data.

The rollingstock schema provides container for all data about any kind of rail vehicles including locomotives, multiple units, passenger and freight wagons. The second part of the schema enables the combination of single vehicles to formations as a fixed composition within a train or an entire train. It is intended to use this data schema for vehicle management as well as for detailed run-time calculations.

The Rollingstock schema comprises the following features:

  • separate parts for vehicles and for train parts or complete trains
  • possible specification of vehicle families and individual vehicles using the common features of the family
  • different level of detail for data
  1. vehicle as black box (with respect to dynamic characteristics) with only mean values
  2. vehicle as black box (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
  3. vehicle as white box with details about the internal propulsion system
  • vehicles with motive power, for passenger or freight use
  • combination of vehicles to formations, i.e. train parts or complete trains

Interlocking (IL)

The interlocking subschema is under active development from 2015.

Common (CO)

The Common class shall cover all topics, which affect all other railML-schemas alike.

The actual planned tasks and enhancements can be found at Trac-Tickets of the railML development space.

There is also a "historic" collection of proposed Data Types for the Common subschema. It was developed in the preparation works of railML version 1.1. Some of the suggestions are already implemented in the stable railML 2.0 release. Other extensions wait for users with strong needs for them.

Prospect on Future Schemata

Shift planning

Additional to (vehicle) rosterings, there are ideas for implementing (personnel) shift planning.

Station asset management and properties

A schema for station databases, asset management and properties was developed in the early 2000's but place on hold due to the very limited use cases at this time. With a focus to the upcoming [PRM] a reopening of the development might be started depending from sectors needs in 2016 ff.

Users and Developers Guides


Feel free to direct any comments, questions or remarks to the coordinators of railML.

For our contact information see Contact

Enjoy the Wiki!