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
- 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
- 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
- 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
- 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
- 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
- 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
- Children: <axleWeightChanges>, <bridges>, <clearanceGaugeChanges>, <electrificationChanges>, <gaugeChanges>, <geoMappings>, <gradientChanges>, <levelCrossings>863 bytes (65 words) - 19:46, 25 November 2018
- (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
- 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
- Maintenance Planning; Wartungsplanung The application focuses the transfer of infrastructure data from an asset management source system (e.g. DfA in Switzerland)10 bytes (133 words) - 16:12, 3 February 2020
- CAD for railway signalling; CAD für Zugsignalisierung Engineers of the railway signaling discipline use a Computer-Aided Design (CAD) tool to model a railway10 bytes (127 words) - 16:12, 3 February 2020
- specify the required data regarding certain aspects. only on configuration changes big (station/yard) huge (region) Signaling Permission/operating zones: ID10 bytes (209 words) - 16:12, 3 February 2020
- serves to specify the required data regarding certain aspects. static (not changing) yearly big (station/yard) huge (region) whole data set (network) Geometry10 bytes (169 words) - 16:12, 3 February 2020
- to specify the required data regarding certain aspects. on demand or on changes of RS depending on the number of various vehicle types and train formations10 bytes (146 words) - 16:12, 3 February 2020
- required data regarding certain aspects. Bulk transfer: regular changes 5-6 times a year Daily changes for incremental transfers Granularity of data: macro-level10 bytes (157 words) - 16:12, 3 February 2020
- of existing equipment evaluation for weak points feasibility of network changes (time table, rolling stock, electrical equipment) investment strategy for10 bytes (236 words) - 16:12, 3 February 2020
- ÖBB-SCHIG-Reporting (NRE Reporting Austria); NRE Meldung Österreich ÖBB Infrastructure reports several properties of the line and track network periodically10 bytes (225 words) - 16:12, 3 February 2020
- IS:electrificationChange (section Position of electrificationChange in the XML-Tree / Position von electrificationChange im XML-Baum)<electrificationChange> of the track adjacent to Bft Bingen (Rhein) Vorbahnhof station. <electrificationChanges> <electrificationChange id="ec263011" dir="up"3 KB (1,150 words) - 15:33, 25 March 2024
- characteristics, etc.), i.e. a change of the formation data does not affect the running times nor the path of the trains. Furthermore, a change of the formation data10 bytes (688 words) - 16:12, 3 February 2020
- specifying when the <trainPart> last was changed in the exporting system. May be used by importing systems to detect changed <trainPart>s. id: xs:ID, required12 KB (1,930 words) - 15:44, 13 May 2024
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (section How often do the data change (update)?)infrastructure restrictions allow computation of itineraries, including changes of direction Vehicle information should include validity reference length10 bytes (355 words) - 16:12, 3 February 2020
- (weekly/daily) Schedule attributes: daily, with realtime changes Vehicle attributes: occasional changes (event-driven) huge (region) Train regulation Energy10 bytes (306 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 (335 words) - 16:12, 3 February 2020
- Speed directory; VzG – Verzeichnis zulässiger Geschwindigkeiten The VzG Process is the central interface between infrastructure business processes (building10 bytes (117 words) - 16:12, 3 February 2020
- railML® for RINF Reporting; railML® für RINF Meldung This use case aims at providing a railML3 file, fulfilling the functional requirements published by10 bytes (297 words) - 16:12, 3 February 2020
- <speedChanges> <speedChange id="sc26301" dir="up" pos="15613" vMax="110" absPos="106663" signalised="true" trainRelation="headOfTrain"/> <speedChange id="sc26302"15 KB (2,400 words) - 19:48, 22 January 2024
- Positioning and Map-Matching; Positionierung und Kartenabgleich With a train-borne positioning system, which is a multi-sensor on-board positioning device10 bytes (367 words) - 16:12, 3 February 2020
- Long Term Strategic Timetabling; Langfristfahrplanerstellung The timetable data prepared in this use case is not formally linked to the production process10 bytes (523 words) - 16:12, 3 February 2020
- specify the required data regarding certain aspects. infrastructure: regular changes (Existing infrastructure is updated on a daily basis. But due to todays10 bytes (687 words) - 16:12, 3 February 2020
- IS:clearanceGaugeChange (section Position of clearanceGaugeChange in the XML-Tree / Position von clearanceGaugeChange im XML-Baum)<clearanceGaugeChanges> <clearanceGaugeChange id="cs263011" pos="182"> <clearanceGauge code="GA"/> </clearanceGaugeChange> </clearanceGaugeChanges> </trackElements>3 KB (806 words) - 15:34, 25 March 2024
- serves to specify the required data regarding certain aspects. static (not changing) in cases of error-corrections: weekly .. daily in rare cases during a10 bytes (1,903 words) - 16:12, 3 February 2020
- along the track) superelevation of outer rail relative height and height changes especially at switches list of reference points with their geo-coordinates10 bytes (737 words) - 16:12, 3 February 2020
- for all project members, independent of ETCS Level) Interlocking Regular changes The frequency for updates should be low. The updates depends on reconstructions10 bytes (441 words) - 16:12, 3 February 2020
- IS:ownerChange (section Position of ownerChange in the XML-Tree / Position von ownerChange im XML-Baum)ownerChange Parent: <ownerChanges> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0..∞] A <ownerChange> defines2 KB (715 words) - 15:33, 25 March 2024
- IS:powerTransmissionChange (section Position of powerTransmissionChange in the XML-Tree / Position von powerTransmissionChange im XML-Baum)powerTransmissionChange Parent: <powerTransmissionChanges> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0.1 KB (772 words) - 15:32, 25 March 2024
- The changed type of extension attribute SAP-Number in the element timetable has no influence into the XML Instance document. (line 3) The changed type10 bytes (2,659 words) - 17:25, 30 May 2022
- Simulation; Simulation Infrastructure Managers simulate traffic on increasingly realistic models of their networks to design and test timetables. Alternative10 bytes (969 words) - 16:12, 3 February 2020
- railML® schema changes between railML® 2.1 and railML® 2.2 This site is intended to collect the schema changes between railML® 2.1 and railML® 2.2 by36 KB (103 words) - 13:54, 21 February 2022
- rail:lang, xsi:type <macroscopicNode> flowDirection, ocpRef <mileageChanges> <mileageChange> absDir, absPos, absPosIn, absPosInOffset, code, description, dir112 KB (4,754 words) - 18:02, 3 April 2022
- IS:radiusChange (section Position of IS:radiusChange in the XML-Tree / Position von IS:radiusChange im XML-Baum)IS:radiusChange Parent: <radiusChanges> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0..∞] A radiusChange defines9 KB (1,756 words) - 15:32, 25 March 2024
- IS:axleWeightChange (section Position of axleWeightChange in the XML-Tree / Position von axleWeightChange im XML-Baum)axleWeightChange Parent: <axleWeightChanges> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0..∞] A <axleWeightChange>1 KB (838 words) - 15:34, 25 March 2024
- coordinate the work on this page. Recognize that the content of this page may change quickly. Vivian Augele (Diskussion) 08:14, 30. Jun. 2016 (CEST)10 bytes (450 words) - 16:12, 3 February 2020
- master branch directly if the changes your are commiting are complete in themselves and don't change the syntax of railML®. Changes to the syntax of railML®10 bytes (1,082 words) - 19:21, 3 July 2023
- reference to a <trainPart> within a roster, as well as services without change of location (without reference to a <trainPart>). These 3 basic types are12 KB (1,612 words) - 12:52, 14 May 2024
- dc:format and/or dc:identifier. As above mentioned the XML namespace does also change with the railML® version. The following table shows this relationship for10 bytes (1,043 words) - 11:29, 15 February 2023
- IS:trainProtectionChange (section Position of trainProtectionChange in the XML-Tree / Position von trainProtectionChange im XML-Baum)<trainProtectionChange> can be set at the position of a track in which the train protection method changes. The direction to which the change is valid, protection1 KB (1,558 words) - 20:14, 13 December 2021
- Asset Status Representation for TMS Traffic Management Systems (TMS) consider various sorts of input data for the calculation of the current traffic situation10 bytes (129 words) - 16:12, 3 February 2020
- Especially, employ template:external for external links. If you want to change or extend some content on a specific railML element page, do the following:15 KB (1,952 words) - 18:11, 15 April 2024
- Timetable (Common) (Codelists) XML tree UML diagrams Use cases Versions & Changes2 KB (260 words) - 21:06, 22 January 2024
- @trackContinueCourse is bound to the continuation of the track, and you cannot change which leg it refers to without also swapping the connections. So you should5 KB (1,094 words) - 19:21, 22 January 2024
- the Czech Republic and DB InfraGO ( 🇩🇪) in Germany, meaning there is a change in infrastructure managers. Mileage of the border was obtained from Variabler6 KB (516 words) - 11:57, 26 April 2024
- supplements etc. become incorrect by this practice. Also, it can only be used to change between a certain stop and run through but not to switch between two different7 KB (917 words) - 18:11, 24 September 2023
- Timetable (Common) (Codelists) XML tree UML diagrams Use cases Versions & Changes3 KB (452 words) - 20:21, 22 January 2024
- IS:operationModeChange (section Position of operationModeChange in the XML-Tree / Position von operationModeChange im XML-Baum)operationModeChange Parent: <operationModeChanges> Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states> [0..∞] A <operationModeChange>937 bytes (948 words) - 23:50, 14 September 2020
- referenced from the following <speedChange> elements: <speedChange id="sc1" pos="12.34" profileRef="sp1" vMax="90"/> <speedChange id="sc2" pos="12.34" profileRef="sp4"4 KB (819 words) - 10:31, 28 March 2023
- clearanceGauge Parent: <clearanceGaugeChange> Children: None [1..1] The element <clearanceGauge> (introduced with version 2.3) contains all data with2 KB (306 words) - 09:05, 15 November 2022
- IS:gradientChanges (section Position of gradientChanges in the XML-Tree / Position von gradientChanges im XML-Baum)gradientChanges Parent: <trackElements> Children: <gradientChange> [0..1] A gradientChanges is a container for all elements of gradientChange. They are397 bytes (52 words) - 19:49, 25 November 2018
- IS:radiusChanges (section Position of radiusChanges in the XML-Tree / Position von radiusChanges im XML-Baum)radiusChanges Parent: <trackElements> Children: <radiusChange> [0..1] radiusChanges is a container for all elements of radiusChange. An unlimited number347 bytes (44 words) - 19:49, 25 November 2018
- IS:clearanceGaugeChanges (section Position of clearanceGaugeChanges in the XML-Tree / Position von clearanceGaugeChanges im XML-Baum)clearanceGaugeChanges Parent: <trackElements> Children: <clearanceGaugeChange> [0..1] A clearanceGaugeChanges is a container for all elements of clearanceGaugeChange540 bytes (58 words) - 17:25, 10 October 2023