UC:IS:RailwayInfrastructureVisualisation

Railway Infrastructure Visualisation (RAIV) Subschema: Infrastructure

DRAFT railML® version TBD

For general information on use cases see UC:Use cases

Use case / Anwendungsfall

Railway Infrastructure Visualisation; Visualisierung von Schieneninfrastruktur

Description / Beschreibung

The typical railway planning process involves several iterations with different planning tools. The resulting changes to the planned infrastructure shall be fed back into a visualization software.

Data Flows and Interfaces / Datenflüsse und Schnittstellen

The infrastructure data to be modified contains railway topology, track and operational elements. These elements are exported with geo-referenced coordinates and can thus be visualized.

Interference with other railML^® schemas / Interferenz mit anderen railML^®-Schemen

• none

Characterizing Data / Charakterisierung der Daten

This section serves to specify the required data regarding certain aspects.

How often do the data change (update)?

• irregularly, depending on the planning iterations

How big are the data fragments to be exchanged (complexity)?

• typically, single lines

Which views are represented by the data (focus)?

• Geometry
• Construction

Which specific IS data do you expect to receive/send (elements)?

Topology

• <connections> <switch> (id, pos, absPos, model, length, type, trackContinueCourse)

• <crossSections> (id, pos, absPos, dir, ocpRef)

• <trackBegin> (id, pos, absPos)

• <trackEnd> (id, pos, absPos)

• <mileageChanges> (id, pos, absPos, absPosIn)

Track elements

• <gradientChanges> (id, pos, absPos, Slope)

• <speedChanges> (id, pos, absPos, dir, signalised, vMax)

• <electrificationChanges> (id, pos, absPos, type, voltage, frequency)

• <platformEdges> (id, pos, absPos, length, dir, height, side)

• <radiusChanges> (id, pos, absPos, dir, radius, superelevation)

• <geoMappings> (id, pos)

• <geoCoord> (coord, extraHeight, epsgCode)

• <bridges> (id, name, pos, length, dir)

• <tunnels> (id, name, pos, length, dir, crossSection)

Operational infrastructure elements

• <operationControlPoints> (id, name)

• <propOperational> (operationalType)

• <propService> (passenger)

• <ocp> (id, name)