Search results

contain our codelists (as is usual in railML® 3) or if you need the most current codelists, you can retrieve them from https://development.railml.org/ra

Attributes: maxCurrent: maximum allowed current in Ampere (optional; xs:decimal), operationType: type of operation for maximum train current: standstill or

elements found in the infrastructure subschema UML visualization of the current railML® 3 IS subschema Examples (link to the railML® website) — collection

associated with <RTM:linearPositioningSystem> not max and min values of a current file with e.g. line section. Implementation for infrastructure surveys is

the main power engine has to be switched off noEddyCurrentBrakeForEmergencyBrake: The use of eddy current brakes (external link) is not allowed on this track

sophisticated topology model in the background. The current railML® 2 version is 2.5. The current railML® 3 version is 3.2. A detailed version list can

the signal manufacturing industry based on RailTopoModel (external link). Current UML visualization A list of use cases for railML's interlocking scheme can

XML elements found in the rollingstock subschema UML visualization of the current railML® 3 RS subschema A list of use cases for the railML® rollingstock

required (optional; xs:boolean), requiresPowerLimitation: flag, whether a current or power limitation on board is required (optional; xs:boolean) *Notice:

for the TVD section in case of a track circuit. Shall be zero for direct current. (optional; xs:decimal; minInclusive: 0; fractionDigits: 3), isBerthingTrack:

https://www.railML.org/en/user/subschemes.html (external link) for a list of the current coordinators of the respective schemas and their contact data. Further subschemas

have shorter cycles than railML® versions have you might want to get the current list from https://development.railml.org/railml/shared/-/raw/master/codelists/Registers

Exchange of Logical Train Positions   Current train positions should be exchanged between a TMS and other systems. Current position means: the position of trains

have shorter cycles than railML® versions have you might want to get the current list from https://development.railml.org/railml/shared/-/raw/master/cod

have shorter cycles than railML® versions have you might want to get the current list from https://development.railml.org/railml/shared/-/raw/master/cod

understood as alternatives to one another to traverse the distance between the current base itinerary point and the next. They cannot be combined or traversed

codelists have shorter cycles than railML® versions you might want to get the current list from https://development.railml.org/railml/shared/-/raw/master/cod

nt of railML® version 3.1 UML-visualization of CO Documentation If the current <trainDetectionElement> is an insulated rail joint or an axle counter and

xs:boolean), Mg: magnetic shoe brakes (optional; xs:boolean), Wb: eddy current brakes (optional; xs:boolean) *Notice: Elements may have different parent

(external link) or a commercial licence. Download the zip file with the current version of the railML® schema files. For obtaining the developers' version

associated with <RTM:linearPositioningSystem> not max and min values of a current file with e.g. line section   Proposed on April 08th 2024 Discuss this semantic

Automatic Schemaexport for Element maxTrainCurrent

Automatic Schemaexport for Element maxTrainCurrent

model the requirements of this use case have been implemented into the current railML® schema ☒ × finished the use case has been completely implemented

to other activities that are scheduled to take place directly before the current one. Subschema timetable Parents* previousActivities Children None Attributes:

Generic:limitsTrainDetectionElement of railML® version 3.2   Documentation If the current <trainDetectionElement> is an insulated rail joint or an axle counter and

timetable 6 months ahead of time STP: short term planning changes to the current timetable - e.g. updated timetable information is provided for days +2 to

Subschema infrastructure Parents* electrificationSection Children maxTrainCurrent (0..*) Attributes: allowsRegenerativeBraking: flag, whether the use of regenerative

the preliminary planning and cost estimation. disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly

the main power engine has to be switched off noEddyCurrentBrakeForEmergencyBrake: The use of eddy current brakes (external link) is not allowed on this track

the preliminary planning and cost estimation. disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly

to other activities that are scheduled to take place directly before the current one. Subschema timetable Parents* previousActivities Children None Attributes:

understood as alternatives to one another to traverse the distance between the current base itinerary point and the next. They cannot be combined or traversed

xs:boolean), Mg: magnetic shoe brakes (optional; xs:boolean), Wb: eddy current brakes (optional; xs:boolean) *Notice: Elements may have different parent

Systems (TMS) consider various sorts of input data for the calculation of the current traffic situation. One important input for TMS is the information about

the command and the use of special texts as defined in <textMessage>. Currently there are only two levels foreseen. normal - The normal level applies to

nt of railML® version 3.1 UML-visualization of CO Documentation If the current <trainDetectionElement> is an insulated rail joint or an axle counter and

required (optional; xs:boolean), requiresPowerLimitation: flag, whether a current or power limitation on board is required (optional; xs:boolean) *Notice:

electrificationSection Children None Attributes: requiresPowerLimitation: flag, whether a current or power limitation on board is required (optional; xs:boolean), permit

Generic:limitsTrainDetectionElement of railML® version 3.2   Documentation If the current <trainDetectionElement> is an insulated rail joint or an axle counter and

be saved in your current project folder, typically as "catalog.xml". Select "Options > Preferences ... > XML > XML Catalog". Add current catalog file with

only reference one <trainPart>. Improvements for further versions: In the current implementation of railml® 2.x it is not clearly defined how two <trainPart>

{{XsdType|<type-name>}} example: {{XsdType|string}} results in xs:string The current wiki does not support version management itself. That's the reason for the

energy-efficient speed profile with which to meet the train’s current schedule. The DAS receives as input the current schedule (which may be updated at any time) together

there is no version 3 in use at time of writing. Infrastructure From the current experience, it is typical that railML® files of that use case contain a

Entwickler und Modellierer im railML-Umfeld. Under development since: Upcoming Current example version: Upcoming Subschemas: To be decided railML® Versions: To

responsible for RINF Reporting to the European Union. This use case describes the current structure of the yearly report of ÖBB Infrastructure in fulfillment of legal

frequency in Hertz in case of a track circuit. Shall be zero for direct current. (optional; xs:decimal; minInclusive: 0; fractionDigits: 3), id: unique

elements for vehicles with regeneration brake: propulsion (brakeCurrent[valueTable], brakeCurrentLimitation[valueTable], totalBrakeEfficiency/brakeVehicleEf

used to reference this element within railML. @indicatorType - There is currently only cautiousDriving defined for use. Other values might be defined to

railML®. See Dev:Downloading_and_using_railML® to learn how to obtain the current schema, or download it directly from https://www.railml.org/en/developers/download

for the TVD section in case of a track circuit. Shall be zero for direct current. (optional; xs:decimal; minInclusive: 0; fractionDigits: 3), isBerthingTrack:

elements and attributes. There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.  

elements and attributes. There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.  

validity. The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure state. It is important

elements and attributes. There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.  

to become a common base for the related abovementioned applications. The current data flows – concerning the trackside model infrastructure, rolling stocks

g. xmlns="https://www.railml.org/schemas/2009" Reason Depending on the current policy only Subversion commits for corrigendum, minor or major railML® releases

elements and attributes. There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.  

including all concepts and data required. In a first step, considering the current non-acceptance of the railML® standard by ERA, this railML3 file will be

of regular trains. This planning will always be done with regard to the current operational situation. This means that the actual state of the railway network

railML schema Timers interlocking tables/relay drawings relay drawings Current installation of relays relay drawings railML schema Gradient ATP plans railML

sanding for increasing coefficient of adhesion noEddyCurrentBrakeForEmergencyBrake noEddyCurrentBrakeForServiceBrake, id: the identifier of the object;

Subschema infrastructure Parents* electrificationSection Children maxTrainCurrent (0..*) Attributes: allowsRegenerativeBraking: flag, whether the use of regenerative

Subschema infrastructure Parents* electrificationSection Children maxTrainCurrent (0..*) Attributes: allowsRegenerativeBraking: flag, whether the use of regenerative

distinguishable at first glance. This documentation should describe the currently supported versions of railML®. Please, neither describe obsolete versions

and/or manufacturer Import of rollingstock data into the simulation system (currently manual) infrastructure timetable interlocking This section serves to specify

xs:string; patterns: other:\w{2,}) Possible values: disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly

the preliminary planning and cost estimation. disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly

is the start signal of the route. However, with railML3.1 there can be currently no relation described between any main signal and distant signal or repeater

xs:string; patterns: other:\w{2,}) Possible values: disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly

the preliminary planning and cost estimation. disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly

infrastructure manager. The capacity section at Jernbaneverket (JBV) is currently finishing a handbook that describes the process in Norwegian. An English

<linearCoordinateEnd> <designator> <electrificationSystemRef> <energyCatenary> <maxTrainCurrent> <energyPantograph> <energyRollingstock> <etcsElectrification> <external>

IS:linePerformance IS:lineString IS:lineTrafficCode IS:loadingGauge IS:maxTrainCurrent IS:netElement IS:netRelation IS:network IS:networkLocation IS:opEquipment

<linearCoordinateEnd> <designator> <electrificationSystemRef> <energyCatenary> <maxTrainCurrent> <energyPantograph> <energyRollingstock> <external> <gmlLocations> <lineString>