UC:IS:NetworkStatement

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)