|
|
| Line 1: |
Line 1: |
| {{UseCase|IS|2.3|title=Railway Infrastructure Recording|reporter=Bahnkonzept}} | | {{mirror}} |
| | |
| {{UC title}}
| |
| Railway Infrastructure Recording; {{Deu|Erfassung der Schieneninfrastruktur}}; {{Fra|nom descriptif en Francais}}
| |
| {{UC 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.
| |
| | |
| {{UC flows}}
| |
| 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.
| |
| {{UC interference}}
| |
| * none
| |
| | |
| {{UC data}}
| |
| This section serves to specify the required data regarding certain aspects.
| |
| | |
| {{UC update}}
| |
| * static (not changing)
| |
| * yearly
| |
| | |
| {{UC complexity}}
| |
| * big (station/yard)
| |
| * huge (region)
| |
| * whole data set (network)
| |
| | |
| {{UC focus}}
| |
| * Signaling
| |
| * Geometry
| |
| * Construction
| |
| * Railway Operation
| |
| | |
| {{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, 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>
| |
| | |
| | |
| ( * railML-attribute available from v2.3 only)
| |