UC:IS:RailwayInfrastructureRecording: Difference between revisions
| [unchecked revision] | [checked revision] |
(Die Seite wurde neu angelegt: „'''Use case / {{Deu|Anwendungsfall}} / {{Fra|Scénario d’utilisation}}:''' Railway Infrastructure Recording; {{Deu|Erfassung der Schieneninfrastruktur}}; {{…“) |
(insert of content) |
||
| Line 6: | Line 6: | ||
'''Description / {{Deu|Beschreibung}} / {{Fra|Description}}''' | '''Description / {{Deu|Beschreibung}} / {{Fra|Description}}''' | ||
There are several systems and projects that follow the aim to record and visualize railway infrastructure data in an economical, fast and accurate way. Information about the track geometry, topology and related infrastructure elements are dynamically recorded with a multi-sensor measurement unit and combined with image capturing. As a result the railway track will be visualized within a high resolution video based simulation. Further, measured data can be exported for utilization in other railway applications. | There are several systems and projects that follow the aim to record and visualize railway infrastructure data in an economical, fast and accurate way. Information about the track geometry, topology and related infrastructure elements are dynamically recorded with a multi-sensor measurement unit and combined with image capturing. As a result the railway track will be visualized within a high resolution video based simulation. Further, measured data can be exported for utilization in other railway applications. | ||
'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}''' | '''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}''' | ||
| Line 44: | Line 45: | ||
<u>Which specific timetable data do you expect to receive/send (elements)?</u> | <u>Which specific timetable 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> <connections> <switch> (id, pos, absPos, model, length, type, trackContinueCourse)</li></ul> | ||
<ul> <li> <crossSections> (id, pos, absPos, dir, ocpRef)</li></ul> | <ul> <li> <crossSections> (id, pos, absPos, dir, ocpRef)</li></ul> | ||
| Line 50: | Line 51: | ||
<ul> <li> <trackEnd> (id, pos, absPos)</li></ul> | <ul> <li> <trackEnd> (id, pos, absPos)</li></ul> | ||
<ul> <li> <mileageChanges> (id, pos, absPos, absPosIn)</li></ul> | <ul> <li> <mileageChanges> (id, pos, absPos, absPosIn)</li></ul> | ||
<li> Track elements | <li> Track elements | ||
<li> <gradientChanges> (id, pos, absPos, Slope)</li> | <ul> <li> <gradientChanges> (id, pos, absPos, Slope)</li></ul> | ||
<li> <speedChanges> (id, pos, absPos, dir, signalised, vMax)</li> | <ul> <li> <speedChanges> (id, pos, absPos, dir, signalised, vMax)</li></ul> | ||
<li> <electrificationChanges> (id, pos, absPos, type, voltage, frequency)</li> | <ul> <li> <electrificationChanges> (id, pos, absPos, type, voltage, frequency)</li></ul> | ||
<li> <platformEdges> (id, pos, absPos, length, dir, height, side, ocpRef, parentPlatformEdgeRef)</li> | <ul> <li> <platformEdges> (id, pos, absPos, length, dir, height, side, ocpRef, parentPlatformEdgeRef)</li></ul> | ||
<li> <radiusChanges> (id, pos, absPos, dir, radius, superelevation, *Übergangsbogentyp, *Übergangsbogenparameter)</li> | <ul> <li> <radiusChanges> (id, pos, absPos, dir, radius, superelevation, *Übergangsbogentyp, *Übergangsbogenparameter)</li></ul> | ||
<li> <geoMappings> (id, pos, absPos) | <ul> <li> <geoMappings> (id, pos, absPos) | ||
<li> <geoCoord> (coord, extraHeight, epsgCode)</li> | <ul> <li> <geoCoord> (coord, extraHeight, epsgCode)</li></ul> | ||
</li> | </li></ul> | ||
<li> <bridges> (id, name, pos, absPos, length, dir, kind, *Name der überquerten Straße) | <ul> <li> <bridges> (id, name, pos, absPos, length, dir, kind, *Name der überquerten Straße)</li></ul> | ||
<li> <tunnels> (id, name, pos, absPos, length, dir, crossSection, kind, name, *Name der unterquerten Straße bzw. Flusses)</li> | <ul> <li> <tunnels> (id, name, pos, absPos, length, dir, crossSection, kind, name, *Name der unterquerten Straße bzw. Flusses)</li></ul> | ||
<li> <levelCrossings> (id, name, pos, absPos, angle, protection, ocpStationRef, *Bezeichnung der kreuzenden Straße)</li> | <ul> <li> <levelCrossings> (id, name, pos, absPos, angle, protection, ocpStationRef, *Bezeichnung der kreuzenden Straße)</li></ul> | ||
</ | |||
<li> Operational infrastructure elements | <li> Operational infrastructure elements | ||
<li> <operationControlPoints> (id, name) | <ul> <li> <operationControlPoints> (id, name) | ||
<li> <propOperational> (operationalType)</li> | <ul> <li> <propOperational> (operationalType)</li></ul> | ||
<li> <propService> (passenger)</li> | <ul> <li> <propService> (passenger)</li></ul> | ||
<li> <designator> (register, entry)</li> | <ul> <li> <designator> (register, entry)</li></ul> | ||
</li> | </li></ul> | ||
</ | |||
<li> Operation and control system elements | <li> Operation and control system elements | ||
<li> <signals> (id, name, pos, absPos, dir, type, function, ocpStationRef)</li> | <ul><li> <signals> (id, name, pos, absPos, dir, type, function, ocpStationRef)</li></ul> | ||
</ | |||
( * no railML-attribute available for this information yet) | ( * no railML-attribute available for this information yet) | ||
Revision as of 11:05, 5 October 2015
Use case / Anwendungsfall / :
Railway Infrastructure Recording; Erfassung der Schieneninfrastruktur;
Description / Beschreibung /
There are several systems and projects that follow the aim to record and visualize railway infrastructure data in an economical, fast and accurate way. Information about the track geometry, topology and related infrastructure elements are dynamically recorded with a multi-sensor measurement unit and combined with image capturing. As a result the railway track will be visualized within a high resolution video based simulation. Further, measured data can be exported for utilization in other railway applications.
Data Flows and Interfaces / Datenflüsse und Schnittstellen /
Infrastructure data provided by the recording system include information about railway topology, track elements and operational elements of the railway network. All objects in the database are exported with a coordinate reference to further applications (e.g. simulators, onboard passenger information systems, timetable tools, construction planning).
Generic topology information (e.g. electrification, track classification, ocp attributes) can be imported from external sources, e.g. from a database provided by the infrastructure manager.
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 timetable data do you expect to receive/send (elements)?
- <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)
- <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)
- <operationControlPoints> (id, name)
- <propOperational> (operationalType)
- <propService> (passenger)
- <designator> (register, entry)
- <signals> (id, name, pos, absPos, dir, type, function, ocpStationRef)
( * no railML-attribute available for this information yet)