Search results
Jump to navigation
Jump to search
- Dev:Defining temporal availability of infrastructure elements and speed profiles (section Properties that change over time)(yards) X.Y, X.Z, X.J. Yard X.Y has a temporal part as soon as its properties change over time. <infrastructure> <operationControlPoints> <ocp id="X" name="X"14 KB (1,546 words) - 20:09, 12 April 2024
- <xs:enumeration value="powerSystemChange"> + <xs:annotation> + <xs:documentation>Stop caused by a change of power supply (e.g. to change pantograph)</xs:documentation>104 KB (9,170 words) - 10:56, 8 October 2021
- <IS:axleWeightChange> <clearanceGaugeChange> <electrificationChange> <gaugeChange> <ownerChange> <gradientChange> <powerTransmissionChange> <radiusChange> IS:01610 bytes (579 words) - 15:58, 18 May 2020
- overlap/safety zone/slip, timers, speeds), which is demanded by JBV. static (not changing) yearly big (station / yard) huge (region) whole data set (network) topology:10 bytes (198 words) - 16:12, 3 February 2020
- associated <category> element lastModified: allows to specify when the last change to this trainPart was done id: xs:ID, required a string, starting with a2 KB (516 words) - 11:31, 9 October 2023
- serves to specify the required data regarding certain aspects. static (not changing) on demand big (station/yard) Energy Construction Number of elements (signals10 bytes (119 words) - 16:12, 3 February 2020
- tables are finished, these are delivered to the supplier, and it is in this change of information we detect that lack in communication might occur. To standardize10 bytes (558 words) - 16:12, 3 February 2020
- pos, absPos) <mileageChanges> (id, pos, absPos, absPosIn) Track elements <gradientChanges> (id, pos, absPos, Slope) <speedChanges> (id, pos, absPos, dir10 bytes (180 words) - 16:12, 3 February 2020
- IS:state (redirect from IS:state speedChange)IS:state Parent: <states> Children: <designator> (introduced with version 2.5), <xs:any> [1..1] This is to define disabled/enabled infrastructure pieces5 KB (753 words) - 13:45, 14 May 2024
- This section should be used for a header or introduction. The headline is made with Template: UC title (type {{UC title}}) This article shows and explains10 bytes (220 words) - 16:47, 4 December 2023
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (section How often do the data change (update)?)interlocking systems. There are also changes possible or necessary due to operational findings, which force the change of specific parameters for track-sections10 bytes (571 words) - 16:12, 3 February 2020
- UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (section How often do the data change (update)?)graphical attributes of edges or nodes, i.e. no colours or line-styles. Changes occur on a irregular and unpredictable basis, usually associated with track10 bytes (383 words) - 16:12, 3 February 2020
- Timetabling; Fahrplan Each RU has to provide a timetable for their train- and shunting movements in a coming time period. Besides the RU itself the involved10 bytes (343 words) - 16:12, 3 February 2020
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (section How often do the data change (update)?)Exchange of planning parameters for interlocking with suppliers; Austausch von Planungsparametern für Stellwerke mit Anbietern All the planning parameters10 bytes (367 words) - 16:12, 3 February 2020
- Geometry. The track geometry can be described in terms of <radiusChanges> and <gradientChanges>. Railway infrastructure elements enclose a variety of railway3 KB (350 words) - 19:56, 22 January 2024
- splitting from Through connections (connecting to) Through connections (change of service number) Details of transport services Stops with traffic restrictions10 bytes (592 words) - 16:12, 3 February 2020
- the operating status and the decommissioned assets). Regular / occasional changes: updating the model (dashed arrows in the schema) Realtime (seconds): providing10 bytes (427 words) - 16:12, 3 February 2020
- aren't very clear. It seems to be redundant to the definitions with mileageChanges in "overlapping regions". absDir (introduced with version 2.2): Defines3 KB (483 words) - 10:48, 15 April 2024
- aren't very clear. It seems to be redundant to the definitions with mileageChanges in "overlapping regions". absPosIn: the mileage of the (incoming) line in4 KB (545 words) - 18:10, 22 March 2024
- cancellations, extra trains Relevant changes to existing trains need to be represented in the export file. A complete list of changes needs to be defined. This will10 bytes (751 words) - 16:12, 3 February 2020