Search results
Jump to navigation
Jump to search
- IS:speedChange (section Position of speedChange in the XML-Tree / Position von speedChange im XML-Baum)Reference to the part of the train from where the speed change is valid. Normally, a speed change with a speed that is higher than the permitted speed in10 KB (1,890 words) - 15:25, 25 March 2024
- IS:mileageChange (section Position of mileageChange in the XML-Tree / Position von mileageChange im XML-Baum)in railML® definiert. For change of the mileage direction by <mileageChange> see Remarks and open issues on mileage changes.9 KB (1,586 words) - 15:01, 17 July 2023
- belegten Bahnhofsgleises powerSystemChange: Systemwechsel Stop caused by a change of power supply (e.g. to change pantograph) für Halte wegen Wechsels12 KB (1,375 words) - 12:14, 24 January 2022
- of frame contracts yearly for LTP planning the regular timetable regular changes for STP planning, e.g. for engineering infrastructure works, special event10 bytes (273 words) - 16:12, 3 February 2020
- the train(part) changes the direction - no matter whether the formation changes, reverses or neither of both. trainReverse with change of formation = e7 KB (948 words) - 18:45, 19 January 2024
- whereas local definitions are generally set in change-elements like <electrificationChange> and <speedChange> Not yet described. / Noch nicht beschrieben1 KB (479 words) - 18:52, 25 November 2018
- Dev:Types of ocps (section Überleitstelle zwischen zwei- und einsgleisigen Streckenabschnitten • Junction as change between double and single track (of the same line))bureaucracy, the beginning and ending of trains is regarded as “train order change”. <ocp id=… name=…> <propOperational operationalType='station' orderChangeable='true'16 KB (1,316 words) - 18:40, 22 January 2024
- After publication, take care, that changes are incorporated into the wiki asap. New or changed attribute: Add or change the attribute in "attributes" providing10 bytes (675 words) - 21:14, 23 January 2020
- IS:gaugeChange (section Position of gaugeChange in the XML-Tree / Position von gaugeChange im XML-Baum)code example defines gauge change of the track that connects Arnsdorf West and Nord junctions. <gaugeChanges> <gaugeChange id='gac_80.6228_0' pos='0' absPos='942'2 KB (728 words) - 15:34, 25 March 2024
- dayIndex). Whether a change of operating days during a train run actually happens can only be obtained by comparing the shifted bit masks. A change of <operatingPeriodRef>19 KB (2,347 words) - 18:40, 19 January 2024
- IS:geoCoord (redirect from IS:geoCoord speedChange)<gaugeChange>, <geoMapping>, <gradientChange>, <levelCrossing>, <lock>, <mileageChange>, <ocp>, <operationModeChange>, <ownerChange>, <platformEdge>, <p12 KB (1,472 words) - 19:28, 22 January 2024
- exist? How often is data exchanged? What is the granularity? How does it change over time, if it does at all? Diagrams/images would be helpful to visualize10 bytes (1,035 words) - 21:45, 23 January 2020
- IS:states (redirect from IS:states speedChange)IS:states Parent: (miscellaneous) – see Category:states Children: <state> [0..1] Container to define disabled/enabled pieces of infrastructure. None277 bytes (37 words) - 18:01, 25 November 2018
- station name to a typical usage or give it a “right to exist”. But it does not change the behaviour of a railML® parser when decoding the file. So, if the file10 KB (1,656 words) - 19:14, 22 January 2024
- physically signalised speed restriction or speed change, always both elements need to be modelled: the <speedChange> and the <speed> element of <signal>. In the4 KB (487 words) - 17:19, 19 January 2024
- exist? How often is data exchanged? What is the granularity? How does it change over time, if it does at all? Diagrams/images would be helpful to visualize10 bytes (263 words) - 21:42, 23 January 2020
- train part in subsequent sections applies for instance if the operating days change at an intermediate station. For more information, please read Train coupling2 KB (238 words) - 23:05, 25 November 2018
- IS:gradientChange (section Position of gradientChange in the XML-Tree / Position von gradientChange im XML-Baum)Thus, it is mandatory to place a <gradientChange> at the beginning of a model or at a mileage direction change once for each direction. The gradient itself3 KB (931 words) - 18:37, 25 March 2024
- additional information. While e. g. operating days or no. of vehicles may change during a train’s run, all such properties of a <trainPart> stay constant24 KB (3,449 words) - 18:37, 22 January 2024
- IS:speedChangeRef (section Position of IS:speedChangeRef in the XML-Tree / Position von IS:speedChangeRef im XML-Baum)IS:speedChangeRef Parent: <speed_signal> Children: None [0..∞] Reference to a speed change. ref: reference is required because it's the purpose of the349 bytes (44 words) - 23:28, 25 November 2018
- 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
- railML® 2.1 Changes between railML® 2.1 and railML® 2.2 Changes between railML® 2.2 and railML® 2.3 Changes between railML® 2.3 and railML® 2.4 Changes between10 bytes (403 words) - 16:31, 18 May 2020
- ausgibt. It should also be pointed out that with version 2.5 of railML® a change was introduced to the enumeration available for @trainUsage. With this version15 KB (1,905 words) - 11:46, 23 March 2023
- railML® schema changes between railML® 2.4 and railML® 2.5 This site is intended to collect the schema changes between railML® 2.4 and railML® 2.5. A29 KB (97 words) - 19:00, 22 January 2024
- Dev:changes/2.4 (section Change <vehicleBrakeOperation> to optional [0..*] to maintain backwards compatibility)railML® schema changes between railML® 2.3 and railML® 2.4 This site is intended to collect the schema changes between railML® 2.3 and railML® 2.4. A23 KB (104 words) - 11:10, 3 May 2022
- (optional) daily sometimes possibly several times on a day (short-term changes) The size of the data varies depending to the usage of the data. On the10 bytes (677 words) - 16:12, 3 February 2020
- Children: <axleWeightChanges>, <bridges>, <clearanceGaugeChanges>, <electrificationChanges>, <gaugeChanges>, <geoMappings>, <gradientChanges>, <levelCrossings>863 bytes (65 words) - 19:46, 25 November 2018
- where a train, which fulfills certain criteria, needs to stop in order to change passengers or because of other operational rules. id: XML-file-wide unique5 KB (1,258 words) - 17:26, 19 January 2024
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (section How often do the data change (update)?)Postcondition The train is changed within the validity of the change request, and unchanged outside. Change validity of a train Precondition: Import data10 bytes (209 words) - 16:12, 3 February 2020
- Interlocking module engineering data ; Stellwerksprojektierung The process of creating an interlocking is three-tiered. The manufacturer designs an interlocking10 bytes (828 words) - 16:12, 3 February 2020
- There should be one more error message. Change the count of error messages in the comment. Commit all changes (key, keyref, defectSample) together, if9 KB (1,033 words) - 17:59, 19 January 2024