Search results

for example added by a new optional sub-element “railML/infrastructure/functionalInfrastructure/balises/balise/isEbicabBalise“ which includes the new requested

Codelist InfrastructureManagers The list InfrastructureManagers.xml contains infrastructure managing companies. The items are named <infrastructureManager>

  Main Menu   Subschemas Infrastructure Interlocking Rollingstock Timetable (Common) (Codelists) XML tree UML

This concept is explained on the RailTopoModel® wiki at TOPO:Topological structure (network) The children have changed. The attributes have been changed

The movable elements are already defined in infrastructure. Thus a reference to the related infrastructure element is a common part of all moveable elements

elements: Infrastructure subschema <impairmentSection> <ocp> <state> Common subschema <concessionaire> <contractor> <customer> <infrastructureManager>

system for the spatial identification of objects. Almost all railway infrastructure components have such a spatial identification, either in a global context

The concept is explained here. The list contains infrastructure managing companies. The container element for the list is named <infrastructureManagerCodes>

element <railml> as well as in the root elements of the sub-schemas as <infrastructure>, <rollingstock>, <timetable>. This attribute is to be used for the

pages: <infrastructure> — documentation of the main element Infrastructure Elements — overview off all XML elements found in the infrastructure subschema

Interlocking   The interlocking subschema will focus on information that infrastructure managers and signal manufacturing industry typically maintain in signal

the codes listed in InfrastructureManagers.xml can be used as values for the code attribute of the following elements: Infrastructure subschema <clearanceGauge>

element should be one of <railml> (railML® 2), <railML> (railML® 3), <infrastructure>, <rollingstock> <timetable> or <interlocking> (railML® 3) <railml

and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The list contains train protection systems

elements in a bottom-up approach, we also try to help users to capture the concepts of railML® via examples and use cases in a top down approach. A use case

category as a new functional infrastructure element that can be located on the topology the same way all other functional infrastructure elements are. Regarding

RS root element — RS use cases — Concepts & examples The rollingstock subschema is part of the complete railML (link to the railML® website) schema providing

The process starts with a service concept that describes the railroad service being provided. This service concept is shared with the traffic modeling

describe what domains of railML the use case is dependent upon if any, e.g. infrastructure, timetable, rolling stock, interlocking. Please also clarify if this

data rely heavily on infrastructure data. In fact, the interlocking data mostly are pointers to objects defined in the infrastructure Namespace. This implies