Search results

Jump to navigation Jump to search
  • cases. While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up approach, we also try to help users to capture the concepts
    10 bytes (287 words) - 16:31, 3 February 2020
  • IS:controller (category Infrastructure Elements)
    that controlles some track-side facilities. It may be something like an interlocking. id: XML-file-wide unique, machine-interpretable identity, required for
    2 KB (607 words) - 20:11, 13 December 2021
  • IS:locallyControlledArea (category Infrastructure Elements)
    signals which is usually operated by an (central) interlocking but which can be detached from this interlocking for local control. "Nahbedienbereich", "Nahstellbereich"
    2 KB (538 words) - 17:26, 15 February 2021
  • actual state of railML®. Please, describe only elements that already exist! Don't start articles about elements that are only in discussion or in development
    10 bytes (1,478 words) - 18:13, 5 March 2021
  • IS:trackGroups (category Infrastructure Elements)
    locallyControlledArea all tracks belonging to a station all tracks assigned to an interlocking ... None None Not yet described. / Noch nicht beschrieben. The tracks
    733 bytes (86 words) - 17:58, 25 November 2018
  • dependent upon if any, e.g. infrastructure, timetable, rolling stock, interlocking. Please also clarify if this dependency is essential for the use case
    10 bytes (263 words) - 21:42, 23 January 2020
  • information with signalling industry (link to IS:UC:InterlockingEngineering) The planning of the interlocking and signalling systems for individual yards is
    10 bytes (450 words) - 16:12, 3 February 2020
  • IS:electrification (category Infrastructure Elements)
    [https://wiki3.railml.org railML® 3.1 Tutorial Simple Example Step-by-Step Part 2: Interlocking] (external link) Not yet described. / Noch nicht beschrieben.
    546 bytes (269 words) - 16:16, 3 July 2023
  • IS:summary (category Infrastructure Elements)
    hasSwitches: if true, the ocp has switches signalBox: tInterlockingTypes (xs:string; classification of an interlocking system by kind of implementation (none, mechanical
    3 KB (274 words) - 07:25, 26 April 2024
  • producing SIL-4 interlocking. Main input for interlocking engineering are the track elements points, signals, sections. The interlocking needs to know the
    10 bytes (828 words) - 16:12, 3 February 2020
  • and interlocking tables for a specific station are made, also taken operational requirements into consideration. After the layout and interlocking tables
    10 bytes (558 words) - 16:12, 3 February 2020
  • the topology data from the interlocking system. These interlocking data (IxL-data) describe the track-topology track-elements block-information speed limits
    10 bytes (571 words) - 16:12, 3 February 2020
  • position of hardware elements (signals, switches etc.) Positioning for track-related elements based on topology Positioning for other elements based on coordinates
    10 bytes (367 words) - 16:12, 3 February 2020
  • <ocpTT> elements with commercially relevant stops have to be listed in a <trainPart>. The <infrastructure> has to provide the related <ocp> elements. There
    10 bytes (273 words) - 16:12, 3 February 2020
  • operations. An ocp is a grouping of infrastructure elements sharing traffic or operational (interlocking) functions. They typically but not necessarily fit
    18 KB (2,618 words) - 16:53, 19 March 2024
  • IS:derailer (category Infrastructure Elements)
    maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities
    2 KB (899 words) - 14:30, 28 November 2022
  • IS:electrificationChange (category Infrastructure Elements)
    maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities
    3 KB (1,150 words) - 15:33, 25 March 2024
  • Geometry Energy Safety system / interlocking Topology, Geometry (Location points, node-centre, node-ports), interlocking, 10 – 15 RINF parameter types for
    10 bytes (343 words) - 16:12, 3 February 2020
  • Cases. While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up approach, we also try to help users to capture the concepts
    10 bytes (1,035 words) - 21:45, 23 January 2020
  • points. Simulation of an interlocking by nature replicates the behaviour of the interlocking. In other words, the interlocking model would require the functions
    10 bytes (969 words) - 16:12, 3 February 2020
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)