Search results

dependency is essential for the use case or considered optional. Please describe what data is exchanged for the use case. What is part and what is not part

edit an older use case, please stick to the following structure. To get an impression how to employ the templates of this list see Dev:Use case example/old

good use case. For an actual example see UC:IS:Schematic Track Plan. To get more information on use cases and how to describe them, see Dev:Use cases. Please

and Developer Pages   This page provides an overview over pages from the Dev-namespace that offer User Guides, information for developers and connected

Sharing Dev:Types of ocps Dev:UML Dev:Units Dev:Usage of the track between the stations Dev:Use case example/old Dev:Use cases Dev:UsingAny Dev:Wiki Documentation

with us. To learn where to find, how to use and how to contribute use cases see Dev:Use cases. While use cases follow a top-down approach, starting out

The railML® wiki offers a number of Use Cases. A Guideline to implementing Use Cases can be found under Dev:Use cases. In contrast to railML® 2, railML®

personResponsible must occur once. (line 17) In case the element contract is used the elements number and requirement have to be used, too. The element requirement may

references across files and data sources. In case of valid railML® files, no problems will occur. In case of consuming "good or bad styled" id values the

semantic constraint on the respective list below (Dev:Semantic_Constraints/table2 for railML® 2 and Dev:Semantic_Constraints/table3 for railML® 3). assign

(character sub-set) follows implicitly from the characters used in the name. So, the only case when to use the script sub-tag is to distinguish between two <additionalName>

all information that is collected about the ÖBB in the code list, in this case name, country code and company code: <infrastructureManager code="ÖBB"> <name>ÖBB

infrastructure elements are aggregated to an <ocp> depends on the context (use case) and the accuracy requirement of the timetable. Timetables that aim more

trainPart is in the best case redundant, if it is used as a shortcut to the commercial train number. The recommended practice is to use trainNumber only on

Infrastructure Rollingstock Timetable (Common) (Codelists) XML tree UML diagrams Use cases Versions & Changes

Article: Dev:Versions The development of the early alpha versions started in 2001. Version 1.0, the first version allotted for productive use, was published

single-track railway lines with regular traffic in both directions. In that case, please use value "none" in order to mark that there is no preferred driving direction

values of the connected <trackBegin> and <trackEnd> must be identical just in case both are provided and no mileageChange at this point is defined and both

values can be given per vehicle. In case of vehicles with interchangeable track gauge the value for the gauge mainly used shall be given. Additional information

most useful when shipping the railML® document as a zip archive. In this case the image resource can be provided along with the actual document. If the

the attributes @absPos and @absDir of the element <trackBegin> are used. Do not use a <mileageChange> at the beginning of a track, if you do not have any

but not more. Which mode is or shall be used is not further defined by railML® so far; it is a question of use case. You simple should be aware both possibilities

ema/railML.xsd"> ... </railml> Use the last released version number plus the current SVN number: version="2.1r416" Use the last released namespace as default

Certify your interface. While you can use railML® in island solutions e.g. for exercise, in most cases productive use aims at and depends on exchanging data

less $FILENAME$ <U+FEFF><?xml version="1.0" encoding="UTF-8"?> Always use camel case for all names. Don't mix with dashed naming schemas. Implementation

have made, do not hesitate to reach out railML for a review and feedback. In case your edits get reverted (external link), please understand that is our part

constraint below. beginDay: This is usually used only if the @mission of the <blockPart> is not timetable. In this case it describes on which day an activity

detaillierte Erklärung siehe Dev:identities. code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of

railML® website). The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity

xs:nonNegativeInteger remarks: xs:string The <states> element is optional. In case that no specific <state> is defined for the parent infrastructure element

practical use and maintenance by the registry is guaranteed. The further procedure is explained on the dev:Codelists#Missing_entries page. Use of a project-specific

<platformEdge> is not necessary for all use cases. However in the railML® schema it is declared mandatory. In case it is not needed it should be specified

train is provided in this use case. To determine whether an attribute must be specified or can be omitted, the respective use case must be taken into account

shall not rely on these default values as they might be misleading, i.e. in case the information is needed it shall be explicitely given. As there is no simple

detaillierte Erklärung siehe Dev:identities. code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of

headShape: This is the rough description of the head shape, which may be used in case no details about running resistance are available. angular This is an

must be used (first character of first word in lower case, first character of all other words in upper case; all other characters in lower case). (Exam­ple:

changes come closer than the length of the train (which may always be the case), the train has to maintain several speed restrictions. If the train passes

below figure demonstrates the case of the "left" course for the "outgoing" orientation. The below figure demonstrates the case of the "right" course for the

railML® website). The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity

scheduled arrival/departure track in case it was changed stop posts information areas for passenger information Using the element <sectionTT> it is possible

software how it deals with such attributes missing. It can opt for a default case, or ask the user, or force the usage of these attributes e. g. by providing

is executing a planned service on behalf of the <railwayUndertaking>, in case the service was delegated, by the RU. Definition einer Firma, die die betriebliche

tools in productive use shall use *.railml for files / exports. *.xml is always allowed since railML® files are xml files. It shall be used for non-certified

multiple uses page. Note that in some cases, the parents may belong to more than one schema, and in that case you have to cite the multiple uses page for

as <infrastructure>, <rollingstock>, <timetable>. This attribute is to be used for the version number of the railML® schema the XML file is based on. Major

topology, is that the courses given on the same switch are different. In the case of a symmetrical switch, it is maybe most intuitive that one is "left" and

(“forward”) without reversing: <ocpTT>.trainReverse: not used <formationTT>.orientationReversed: not used 2) A formation of several vehicles running in the other

Fahrdienstvorschrift. Not all of these types need to be used as <ocp>s in a railML® file. Rather, it depends on the use case which types are necessary. For instance,

occur in rare cases of an arrival before the first departure (“arrival from nowhere”, from outside the scope of the railML® file). In case a train did already

As these references are specific for one use case or IT system these numbers and identifiers shall not be used as the central code for a line. These additional

described. / Noch nicht beschrieben. In case of a non-motored vehicle with a driver's cab the element is only used for provision of the <monitoring> information

route is only used in case of the OCP is manned. ocpUnmanned: The route is only used in case of the OCP is unmanned. approachPointRef Used for a speed restriction

Creating instructions for new railML® elements Guideline on Use cases — what is a use case, where to find them and how to contribute to them. Certification

understood by systems that do not support reading of trainGroups in their use case. Das Element <trainGroup> verknüpft verschiedene Einzelzüge zu einer Gruppe

railML®. kind This attribute can be used e.g. for specifying a bridge, which crosses the railway track. In this case, it is suggested to define kind = "crossing"

allowed. Please, apply Dev:usingAny accordingly. fittedSection: This is the number of the section the pantograph is fitted to in case of an articulated vehicle

website) The railML® 2 ticket system For changes with other version upgrades see Dev:changes.

xs:nonNegativeInteger remarks: xs:string The <states> element is optional. In case that no specific <state> is defined for the parent infrastructure element

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

<macroscopicNode> does. This might severely mess up the infrastructure model in case of <macroscopicNode>s with many connected tracks. convert the <macroscopicNode>

details for each installed train control and protection system. In case the element is used for ETCS the specific details shall be defined in the separate

regularBrakeMass, regularBrakePercentage <auxiliaryBrakes> E, H, Mg, Wb, brakeUse, ep <vehicleBrakeOperation> brakeSupervision, decelerationDelay, meanDeceleration

detaillierte Erklärung siehe Dev:identities. code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of

emergencyBrakePercentage shall be used. brakePercentage is mainly for backward compatibility. It still can be used if both cases have identical brake percentages

the railML® website). Codelists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity

allows for defining consistency rules. railML.org recommends using border elements. In this case, a track is referred from the <propEquipment> section of a

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

attribute position or with detailed dimensions. In latter case the attribute position shall not be used. Not yet described. / Noch nicht beschrieben.

x-values may be not equidistant. In case the original series of curves have different x-values then interpolation must be used to get the missing y-values per

e are still viable, where existing. Please, read Dev:Using xsi:type for an introduction. In any case to extend your railML files you need to define a new

xs:nonNegativeInteger remarks: xs:string The <states> element is optional. In case that no specific <state> is defined for the parent rollingstock element this

constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly. <statisticAnalyses description="95% less than 4min delay"

and railML® 2.5. A complete diff comparison will soon be available under Dev:changes/2.5/diff. Changes are also marked on the element pages with (introduced

1…111" /> <speedProfile id="spf_0" operatingPeriodRef="opp_0" /> In this case, the <operatingPeriod> contains all days of validity. endDayOffset is 0 and

+ <xs:documentation>Used for unique identification of the objects handled in the messages such as train, path, path request or case refernce.</xs:documentation>

limit. In case there is no next valueLine the maximum is given by other values. In the example the maximum is taken from the speed attribute. Using this construct

limit. In case there is no next valueLine the maximum is given by other values. In the example the maximum is taken from the speed attribute. Using this construct

limit. In case there is no next valueLine the maximum is given by other values. In the example the maximum is taken from the speed attribute. Using this construct

limit. In case there is no next valueLine the maximum is given by other values. In the example the maximum is taken from the speed attribute. Using this construct

limit. In case there is no next valueLine the maximum is given by other values. In the example the maximum is taken from the speed attribute. Using this construct

limit. In case there is no next valueLine the maximum is given by other values. In the example the maximum is taken from the speed attribute. Using this construct