Difference between revisions of "Infrastructure"

From wiki.railML.org
Jump to: navigation, search
[checked revision][checked revision]
(Use Cases)
(Use Cases: IS:UseCases linked twice)
Line 17: Line 17:
== Use Cases ==
== Use Cases ==
A list of the [[:IS:UseCases | infrastructure use cases]] can be found [[:IS:UseCases | on the use case subpage]].
A list of the infrastructure use cases can be found [[IS:UseCases|on the use case subpage]].
==== Documentation ====
==== Documentation ====

Revision as of 20:07, 16 March 2016

Infrastructure (IS)

General Information

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.

The main element of this subschema is IS:infrastructure.

Please visit the railML-Website for more detailed information about the Infrastructure subschema or send an email to the coordinator of the subschema.

Use Cases

A list of the infrastructure use cases can be found on the use case subpage.


The following lists provide links to Infrastructure Documentation sites: