UC:IS:NetworkStatement: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Page created)
 
m (template information for NSTM use case)
Line 1: Line 1:
{{Missing information|topic=the use case|user=[[Benutzer:Vasco Paul Kolmorgen|Vasco Paul Kolmorgen]] ([[Benutzer Diskussion:Vasco Paul Kolmorgen|Diskussion]]) 14:23, 15. Mär. 2016 (CET)}}
{{Missing information|topic=the use case|user=[[Benutzer:Vasco Paul Kolmorgen|Vasco Paul Kolmorgen]] ([[Benutzer Diskussion:Vasco Paul Kolmorgen|Diskussion]]) 14:23, 15. Mär. 2016 (CET)}}
'''Use case / {{Deu|Anwendungsfall}} / {{Fra|Scénario d’utilisation}}:'''
Network Statement; {{Deu|Network Statement}}; {{Fra|nom Network Statement}}
'''Description / {{Deu|Beschreibung}} / {{Fra|Description}}'''
...
'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}'''
...
'''Interference with other railML<sup>®</sup> schemas / {{Deu|Interferenz mit anderen railML<sup>®</sup>-Schemen}} / {{Fra|Interaction avec autres schemas railML<sup>®</sup>}}'''
* none
'''Characterizing Data / {{Deu|Charakterisierung der Daten}} / {{Fra|Caractérisation des données}}'''
This section serves to specify the required data regarding certain aspects.
<u>How often do the data change (update)?</u>
* static (not changing)
* yearly
<u>How big are the data fragments to be exchanged (complexity)?</u>
* big (station/yard)
* huge (region)
* whole data set (network)
<u>Which views are represented by the data (focus)?</u>
* Signaling
* Geometry
* Construction
* Railway Operation
<u>Which specific infrastructure data do you expect to receive/send (elements)?</u>
<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, ocpRef, parentPlatformEdgeRef)</li></ul>
<ul> <li> <radiusChanges> (id, pos, absPos, dir, radius, superelevation, *Übergangsbogentyp, *Übergangsbogenparameter)</li></ul>
<ul> <li> <geoMappings> (id, pos, absPos)
  <ul> <li> <geoCoord> (coord, extraHeight, epsgCode)</li></ul>
</li></ul>
<ul> <li> <bridges> (id, name, pos, absPos, length, dir, kind, *Name der überquerten Straße)</li></ul>
<ul> <li> <tunnels> (id, name, pos, absPos, length, dir, crossSection, kind, name, *Name der unterquerten Straße bzw. Flusses)</li></ul>
<ul> <li> <levelCrossings> (id, name, pos, absPos, angle, protection, ocpStationRef, *Bezeichnung der kreuzenden Straße)</li></ul>
<li> Operational infrastructure elements
<ul> <li> <operationControlPoints> (id, name)
  <ul> <li> <propOperational> (operationalType)</li></ul>
  <ul> <li> <propService> (passenger)</li></ul>
  <ul> <li> <designator> (register, entry)</li></ul>
</li></ul>
<li> Operation and control system elements
<ul><li> <signals> (id, name, pos, absPos, dir, type, function, ocpStationRef)</li></ul>
( * no railML-attribute available for this information yet)

Revision as of 23:20, 18 April 2016

Missinginformation.png In this article there is information missing with respect to the use case. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Vasco Paul Kolmorgen (Diskussion) 14:23, 15. Mär. 2016 (CET)

Use case / Anwendungsfall / :

Network Statement; Network Statement;


Description / Beschreibung /

...


Data Flows and Interfaces / Datenflüsse und Schnittstellen /

...


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)?

  • static (not changing)
  • yearly

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

  • big (station/yard)
  • huge (region)
  • whole data set (network)

Which views are represented by the data (focus)?

  • Signaling
  • Geometry
  • Construction
  • Railway Operation

Which specific infrastructure 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, ocpRef, parentPlatformEdgeRef)
    • <radiusChanges> (id, pos, absPos, dir, radius, superelevation, *Übergangsbogentyp, *Übergangsbogenparameter)
    • <geoMappings> (id, pos, absPos)
      • <geoCoord> (coord, extraHeight, epsgCode)
    • <bridges> (id, name, pos, absPos, length, dir, kind, *Name der überquerten Straße)
    • <tunnels> (id, name, pos, absPos, length, dir, crossSection, kind, name, *Name der unterquerten Straße bzw. Flusses)
    • <levelCrossings> (id, name, pos, absPos, angle, protection, ocpStationRef, *Bezeichnung der kreuzenden Straße)
  • Operational infrastructure elements
    • <operationControlPoints> (id, name)
      • <propOperational> (operationalType)
      • <propService> (passenger)
      • <designator> (register, entry)
  • Operation and control system elements
    • <signals> (id, name, pos, absPos, dir, type, function, ocpStationRef)


    ( * no railML-attribute available for this information yet)

    • Retrieved from "https://wiki2.railml.org/index.php?title=UC:IS:NetworkStatement&oldid=5015"