Search results

Jump to navigation Jump to search

  • IL:key (category Pages using Tabber parser tag)
    The Boolean value gives indication whether the key is of physical type for use in a mechanical lock.
    964 bytes (88 words) - 19:16, 29 January 2020
  • IL:signalIL (category Pages using Tabber parser tag)
    which is neither used as block, entry, exit nor intermediate signal. This is the more general function in case no specific one can be used. repeater – The
    9 KB (1,314 words) - 10:15, 19 May 2023
  • UC:IS:ETCS track net (category Use case (IS)) (section Use case / Anwendungsfall)
    than in use case ETCS-a because data such as balises or routes will be added. The amount of the data to be exchanged is the same as in use case ETCS-a.
    5 KB (441 words) - 09:30, 12 June 2023
  • IL:signalIndicator (category Pages using Tabber parser tag)
    unique identifier used to reference this element within railML. @indicatorType - There is currently only cautiousDriving defined for use. Other values might
    2 KB (240 words) - 13:40, 28 May 2022
  • IL:permissionZone (category Pages using Tabber parser tag)
    the set of assets for which the permission is transferred. In the simple case the permission can only be changed for the entire station or interlocking
    1 KB (151 words) - 19:42, 29 January 2020
  • UC:IS:CADForRailwaySignaling (category Use case (IS)) (section Use case / Anwendungsfall)
    signalling; CAD für Zugsignalisierung Engineers of the railway signaling discipline use a Computer-Aided Design (CAD) tool to model a railway construction project
    1 KB (127 words) - 14:12, 7 December 2023
  • UC:RS:OperationalSimulation (category Use case (RS)) (section Use case / Anwendungsfall)
    Subschema: Rollingstock   Related subschemas: IS IL TT  For general information on use cases see UC:Use cases
    1 KB (146 words) - 13:29, 13 March 2023
  • IL:genericDetector (category Pages using Tabber parser tag)
    interlocking needs to trigger the self-test of the detector. It has to be used in combination with @triggeredSelfTest. <detectorType> – This is the reference
    2 KB (218 words) - 19:17, 29 January 2020
  • UC:IS:Schematic Track Plan (category Use case (IS)) (section Use case / Anwendungsfall)
    Schematic Track Plan Infrastructure managers use maps for the visualization of their railway infrastructure. These maps comprise: Geographic maps Geoschematic
    4 KB (198 words) - 16:57, 13 February 2023
  • UC:TT:LongTermStrategicTimetabling (category Use case (TT)) (section Use case / Anwendungsfall)
    the infrastructure and state their validity. The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure
    4 KB (523 words) - 11:14, 18 July 2022
  • IL:trainNumberField (category Pages using Tabber parser tag)
    This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    3 KB (348 words) - 13:08, 28 May 2022
  • UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (category Use case (IS)) (section Use case / Anwendungsfall)
    von Schienenanlagen railML data will be used for engineering signalling and interlocking systems. Engineers are used to working with paper plans that schematically
    3 KB (383 words) - 13:44, 13 March 2023
  • IL:movableBridge (category Pages using Tabber parser tag)
    This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    3 KB (405 words) - 15:00, 27 May 2022
  • IL:implementsSignalplan (category Pages using Tabber parser tag)
    signal is showing. This element shall be used for “old-style” signalling systems with separate distant signals or in case of repeaters within the route. <signalsSpeedProfile>
    17 KB (1,655 words) - 17:19, 30 January 2020
  • UC:TT:FGIInTrain (category Use case (TT)) (section Use case / Anwendungsfall)
    master data for the use case "passenger information inside the train". The information from the <timetable> are data which will be used individually for every
    9 KB (677 words) - 18:10, 27 June 2022
  • UC:IS:IntegratedTMS (category Use case (IS)) (section Use case / Anwendungsfall)
    control. This use case aims to cover all data exchange necessary for the functions listed above. A major difference to previous railML use cases is that this
    2 KB (179 words) - 17:27, 13 February 2023
  • IL:conflictingRoute (category Pages using Tabber parser tag)
    value is used in case of any TVD section of the route is also used by the conflicting one. ConflictingHeadProtection – This value is used in case any signal
    5 KB (573 words) - 12:09, 28 May 2022
  • IL:interface (category Pages using Tabber parser tag)
    element. @bitNr – This is the order number of the command in the list. In case of transmission as complete bitmask it defines the bit position in the byte
    13 KB (1,119 words) - 17:46, 30 January 2020
  • UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category Use case (IS)) (section Use case / Anwendungsfall)
    Export of planning tool: planning data, handing-over to the supplier (by using a database). interlocking (see also: Interlocking Engineering) This section
    3 KB (367 words) - 13:47, 13 March 2023
  • UC:IS:CapacityPlanning (category Use case (IS)) (section Use case / Anwendungsfall)
    Infrastructure   Related subschemas: IL TT RS  Reported by: Jernbaneverket For general information on use cases see UC:Use cases
    5 KB (687 words) - 13:46, 13 March 2023
View ( | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki3.railml.org/wiki/Special:Search"