Search results

page you learn what is a use case and find a list of railML® use cases. While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up

as its part. Refer to the guide (link to the railML® website) for the extended tutorial. 1 <infrastructure id="is_01"> 2 <topology> 3 <netElements> 4 <netElement

</functionalInfrastructure> </infrastructure> The railway line is owned by the infrastructure manager referenced via the attribute @infrastructureManagerRef

asset <crossing> from the infrastructure part. <branchUpLeft> – This the reference to the underlying track element in infrastructure forming its upper left

element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions

The resulting changes to the planned infrastructure shall be fed back into a visualization software. The infrastructure data to be modified contains railway

of RailTopoModel®, railML® 3.1 allows to define <netElement> elements with a certain length. This extension is based on the assumption that railML topology

railway infrastructure data in an economical, fast and accurate way. Information about the track geometry, topology and related infrastructure elements

by one of the railML® working groups (link to the railML® website) or suggested by anyone through a post in the forum (link to the railML® website). If

also possible to locate the crossing at tracks 30 and 27 in railML® 3. According to in the railML® 2 wiki, the navigability of straight branches is described

@passable=“true” is not defined. In railML® 3 navigability is defined explicitly by a corresponding attribute. In railML® 2 <crossing> is used to describe

@applicationDirection railML® 3. The orientation of a switch in railML® 2 was always dependent on the direction of the track. In railML® 3 the directions specified

train correctly to the other information <ocp> elements to refer to the infrastructure Different levels of complexity of the data import are possible. a minimal

required for railML® 3.2 and higher. For all versions of railML® 2 plus for railML® 3.1, the proposed means are xs:any, xs:anyAttribute and rail:tOtherEnumerationValue