Search results
Jump to navigation
Jump to search
- IS:route (category Infrastructure Elements)switches and their position included in the path. In addition, there may be elements outside the (running) path of the route.(introduced with version 2.5) id:4 KB (1,036 words) - 11:47, 3 November 2023
- UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (section Which specific IS data do you expect to receive/send (elements)?)viewport doesn´t capture lines between elements because the infrastructure model already captures the links between elements. Visualisation artefacts are kinks10 bytes (383 words) - 16:12, 3 February 2020
- incorporated into the operation and control systems. They uses the interlocking to operate elements get element status schedule and manage train operation These10 bytes (209 words) - 16:12, 3 February 2020
- UC:IS:CADForRailwaySignaling (section Which specific IS data do you expect to receive/send (elements)?)Geometry Construction Tracks, operation control elements (signal, balise, derailer, signs, etc.), interlocking, other infrastructure data.10 bytes (127 words) - 16:12, 3 February 2020
- UC:IS:Railway Simulation Laboratory (section Which specific data do you expect to receive/send (elements)?)railway lines and stations, including signaling based on various real interlocking systems used in our country. Many functions are ensured by computer simulations10 bytes (427 words) - 16:12, 3 February 2020
- UC:IL:HardwareAndCablePlan (section Which specific IL data do you expect to receive/send (elements)?)(not changing) on demand big (station/yard) Energy Construction Number of elements (signals, distant signals, repeater, supplementary signals, point machines10 bytes (119 words) - 16:12, 3 February 2020
- IS:trainDetector (category Infrastructure Elements)maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities7 KB (1,535 words) - 18:44, 11 April 2024
- <railML> (railML® 3), <infrastructure>, <rollingstock> <timetable> or <interlocking> (railML® 3) <railml ...> ... </railml> The root element should contain10 bytes (1,996 words) - 21:49, 23 January 2020
- timetable tool (Treno) and the simulation tool (Opentrack). The rest (mostly interlocking) is added manually from technical drawings. Jernbaneverket is planning10 bytes (687 words) - 16:12, 3 February 2020
- between, the line layout is schematically interpolated Schematic drawings All elements have screen coordinates resulting from their complete schematic layout10 bytes (198 words) - 16:12, 3 February 2020
- UC:RS:OperationalSimulation (section Which specific RS data do you expect to receive/send (elements)?)into the simulation system (currently manual) infrastructure timetable interlocking This section serves to specify the required data regarding certain aspects10 bytes (146 words) - 16:12, 3 February 2020
- UC:TT:TimetableInformation (section Which specific TT data do you expect to receive/send (elements)?)<operationalPoint>, <platform>, <platformEdge> rolling stock: <formation> (?) interlocking: - This section serves to specify the required data regarding certain10 bytes (751 words) - 16:12, 3 February 2020
- infrastructure model, some basic infrastructure elements (as switches, sidings, signals) are aggregated into “higher elements”. A very common aggregation is to form16 KB (1,299 words) - 15:29, 20 May 2024
- name="crossedElements" type="rail:eCrossedElements" minOccurs="0" maxOccurs="1"> + <xs:element name="crossedElements" type="rail:eCrossedElements" minOccurs="0">104 KB (9,170 words) - 10:56, 8 October 2021
- data set as basis for all project members, independent of ETCS Level) Interlocking Regular changes The frequency for updates should be low. The updates10 bytes (441 words) - 16:12, 3 February 2020
- <xs:element name="trackElements" type="rail:eTrackElements" minOccurs="0" /> - <xs:element name="ocsElements" type="rail:eOcsElements" minOccurs="0" /> +331 KB (27,016 words) - 10:56, 8 October 2021
- UC:IS:Asset status representation (section Which specific data do you expect to receive/send (elements)?)(network) Construction: railway infrastructure elements along tracks Operation: status of railway infrastructure elements Switch Crossing Track (Rail) Catenary10 bytes (129 words) - 16:12, 3 February 2020
- org/dc/elements/1.1/" schemaLocation="http://dublincore.org/schemas/xmls/qdc/2008/02/11/dc.xsd"> + <xs:import namespace="http://purl.org/dc/elements/1.1/"398 KB (34,006 words) - 10:54, 8 October 2021
- UC:IS:MaintenancePlanning (section Which specific IS data do you expect to receive/send (elements)?)outside the defined interface, done only once) Delta transfer of updated elements rolling stock This section serves to specify the required data regarding10 bytes (133 words) - 16:12, 3 February 2020
- refers to elements of all - sub schemas from "xs:include" paths - </xs:documentation> + <xs:import namespace="https://purl.org/dc/elements/1.1/" sche531 KB (37,474 words) - 10:55, 8 October 2021