UC:IS:RailwayInfrastructureVisualisation: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
m (1 revision imported)
No edit summary
Line 1: Line 1:
{{mirror}}
{{useCase|IS|2.3|title=Railway Infrastructure Visualisation|abbr=RAIV}}
 
{{UC title}}
Railway Infrastructure Visualisation; {{Deu|Visualisierung von Schieneninfrastruktur}}; {{Fra|nom descriptif en Francais}}
 
{{UC description}}
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.
 
{{UC flows}}
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.
 
{{UC interference}}
* none
 
{{UC data}}
This section serves to specify the required data regarding certain aspects.
 
{{UC update}}
* irregularly, depending on the planning iterations
 
{{UC complexity}}
* typically, single lines
 
{{UC focus}}
* Geometry
* Construction
 
{{UC elements|IS}}
<li> Topology
<ul> <li> <connections> <switch> (id, pos, absPos, model, length, type, trackContinueCourse)</li></ul>
<ul> <li> <crossSections> (id, pos, absPos, dir, ocpRef)</li></ul>
<ul> <li> <trackBegin> (id, pos, absPos)</li></ul>
<ul> <li> <trackEnd> (id, pos, absPos)</li></ul>
<ul> <li> <mileageChanges> (id, pos, absPos, absPosIn)</li></ul>
 
<li> Track elements
<ul> <li> <gradientChanges> (id, pos, absPos, Slope)</li></ul>
<ul> <li> <speedChanges> (id, pos, absPos, dir, signalised, vMax)</li></ul>
<ul> <li> <electrificationChanges>  (id, pos, absPos, type, voltage, frequency)</li></ul>
<ul> <li> <platformEdges> (id, pos, absPos, length, dir, height, side)</li></ul>
<ul> <li> <radiusChanges> (id, pos, absPos, dir, radius, superelevation)</li></ul>
<ul> <li> <geoMappings> (id, pos)</li></ul>
<ul> <li> <geoCoord> (coord, extraHeight, epsgCode)</li></ul>
<ul> <li> <bridges> (id, name, pos, length, dir)</li></ul>
<ul> <li> <tunnels> (id, name, pos, length, dir, crossSection)</li></ul>
</li>
 
<li> Operational infrastructure elements
<ul> <li> <operationControlPoints> (id, name)</li></ul>
  <ul> <li> <propOperational> (operationalType)</li></ul>
  <ul> <li> <propService> (passenger)</li></ul>
  <ul> <li> <ocp> (id, name)</li></ul>
</li>

Revision as of 17:58, 3 February 2020

Railway Infrastructure Visualisation
(RAIV)
Subschema: Infrastructure
Stift.png DRAFT railML® 2.3
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®-Schemas

  • 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)
    • Retrieved from "https://wiki3.railml.org/index.php?title=UC:IS:RailwayInfrastructureVisualisation&oldid=3504"