UC:IS:NetworkStatement: Difference between revisions
[checked revision] | [checked revision] |
(adding some text for NSTM use case) |
(re-working text for NSTM use case) |
||
Line 38: | Line 38: | ||
<u>Which views are represented by the data (focus)?</u> | <u>Which views are represented by the data (focus)?</u> | ||
* Geometry | * Geometry | ||
* Construction | * Construction | ||
Line 46: | Line 45: | ||
<li> Topology | <li> Topology | ||
<ul> <li> < | <ul> <li> micro level topology (tracks + track nodes)</li></ul> | ||
<ul> <li> | <ul> <li> macro level topology (lines + operational points)</li></ul> | ||
<ul> <li> | <ul> <li> support of different levels of detail</li></ul> | ||
<ul> <li> | <ul> <li> location referencing</li></ul> | ||
<ul> <li> | <ul> <li> orientation</li></ul> | ||
<ul> <li> grouping of elements</li></ul> | |||
<li> Geometry | <li> Geometry | ||
Line 68: | Line 68: | ||
<ul> <li> <designator> (register, entry)</li></ul> | <ul> <li> <designator> (register, entry)</li></ul> | ||
</li></ul> | </li></ul> | ||
( * no railML-attribute available for this information yet) | ( * no railML-attribute available for this information yet) |
Revision as of 06:55, 19 April 2016
|
Use case / Anwendungsfall / :
Network Statement; Network Statement;
Description / Beschreibung /
The Network Statement provides information about the technical and operational features of the railway network to the railway undertakings that want to operate their rollingstock on the network.
Data Flows and Interfaces / Datenflüsse und Schnittstellen /
The infrastructure managers are responsible for exporting all the required data.
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)?
- Geometry
- Construction
- Railway Operation
Which specific infrastructure data do you expect to receive/send (elements)?
- micro level topology (tracks + track nodes)
- macro level topology (lines + operational points)
- support of different levels of detail
- location referencing
- orientation
- grouping of elements
- <horizontalCurve> (radius)
- <gradientCurve> (slope)
- <superelevationCurve> (superelevation)
- Signalling (train radio; communication system)
- Electrification (voltage, frequency, contactLineType)
- Rails (track gauge; clearance gauge; switch; crossing)
- <operationControlPoints> (id, name)
- <propOperational> (operationalType)
- <propService> (passenger)
- <designator> (register, entry)
( * no railML-attribute available for this information yet)