Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 2railML 2
  • Issues
  • #413
Something went wrong while setting issue due date.
Closed
Open
Issue created 4 years ago by Coordination@coordination.GOVOwner
  • New related issue

  • New related issue

Adding turning resistances to the <ocp> (de: Hinzufügen von Abbiegewiderständen zum <ocp>)

Open

Adding turning resistances to the <ocp> (de: Hinzufügen von Abbiegewiderständen zum <ocp>)

Description

For the exchange of route networks in macroscopic modelling, the individual turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.

(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)

Background

[…]

Links

  • Forum discussion:
  • Michael Gruschwitz, 18.06.2021: [https://www.railml.org/forum/index.php?t=msg&th=819&goto=2767&#msg_2767]
  • Trac tickets:
  • #413
  • Wiki documentation:
  • IS:ocp: [https://wiki2.railml.org/wiki/IS:ocp]

Proposed solution in railML 2.5

It is suggested to integrate topological relationships into the element to define OCP-internal connections.

In particular, a new, repeatable element shall be added in <ocp / propOperational>:

  • has mandatory child elements and to reference the lines and OCPs that are connected by the (directed) connection
  • with required attribute @line (tGenericRef)
  • with required attribute @ocp (tGenericRef)
  • has required enumeration attribute @type to specify the type of the connection with possible values:
  • "direct"
  • "changeDrivingDirection"
  • "crossesContraflowTraffic"
  • "requiresShunting"
  • ...
  • has optional attribute @priority (integer 1..255) to specify the priority of a relation (relevant when several relations exist in parallel), whereas 1 is the highest priority.
  • has optional child element with required attribute @value (xs:duration) to specify the average delay time due to waiting, shunting or other delay reasons
Edited 3 years ago

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Activity


    • O
      Organisation @organisation.GOV · 4 years ago
      Owner
      • Description changed
      + == Description ==
      + 
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
      + 
      + Which of the existing elements can be used?
      + 
      + * [...]
      + 
      + === Background ===
      + 
      + […]
      + 
      + === Links ===
      + 
      + * Forum discussion:
      +  * […]
      + * Trac tickets:
      +  * […]
      + * Wiki documentation:
      +  * none
      + 
      + == Proposed solution in railML 2.5 ==
      + 
      + tbd
    • O
      Organisation @organisation.GOV · 4 years ago
      Owner
      • Description changed
        == Description ==
        
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
        
        Which of the existing elements can be used?
        
        * [...]
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
         * […]
        * Trac tickets:
         * […]
        * Wiki documentation:
      -  * none
      +  * [...]
        
        == Proposed solution in railML 2.5 ==
        
        tbd
    • IS Coordination
      IS Coordination @coordination.IS · 4 years ago
      Maintainer
      • Description changed
        == Description ==
        
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
      - 
      - Which of the existing elements can be used?
      - 
      - * [...]
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
      -  * […]
      +  * [...]
        * Trac tickets:
      -  * […]
      +  * #413
        * Wiki documentation:
         * [...]
        
        == Proposed solution in railML 2.5 ==
        
      - tbd
      + It is suggested to integrate topological relationships into the <ocp> element to define OCP-internal connections.
      + 
      + In particular, a new, repeatable element **<connection>** shall be added in <ocp / propOperational>:
      + * <connection> has attributes **@fromLine** and **@toLine** to reference the lines that are connected by the (directed) connection
      + * <connection> has enumeration attribute **@type** to specify the type of the connection with possible values:
      +  * "direct"
      +  * "changeDirection"
      +  * ...
    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer
      • Description changed
        == Description ==
        
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
      -  * [...]
      +  * Michael Gruschwitz, 18.06.2021: [https://www.railml.org/forum/index.php?t=msg&th=819&goto=2767&#msg_2767]
        * Trac tickets:
         * #413
        * Wiki documentation:
      -  * [...]
      +  * IS:ocp: [https://wiki2.railml.org/wiki/IS:ocp]
        
        == Proposed solution in railML 2.5 ==
        
        It is suggested to integrate topological relationships into the <ocp> element to define OCP-internal connections.
        
        In particular, a new, repeatable element **<connection>** shall be added in <ocp / propOperational>:
        * <connection> has attributes **@fromLine** and **@toLine** to reference the lines that are connected by the (directed) connection
        * <connection> has enumeration attribute **@type** to specify the type of the connection with possible values:
         * "direct"
         * "changeDirection"
         * ...

      adding link to forum post and wiki page

    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer
      • Description changed
        == Description ==
        
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
         * Michael Gruschwitz, 18.06.2021: [https://www.railml.org/forum/index.php?t=msg&th=819&goto=2767&#msg_2767]
        * Trac tickets:
         * #413
        * Wiki documentation:
         * IS:ocp: [https://wiki2.railml.org/wiki/IS:ocp]
        
        == Proposed solution in railML 2.5 ==
        
        It is suggested to integrate topological relationships into the <ocp> element to define OCP-internal connections.
        
      - In particular, a new, repeatable element **<connection>** shall be added in <ocp / propOperational>:
      ?                                              ^^^^ ^
      
      + In particular, a new, repeatable element **<relation>** shall be added in <ocp / propOperational>:
      ?                                              ^ ^^
      
      - * <connection> has attributes **@fromLine** and **@toLine** to reference the lines that are connected by the (directed) connection
      + * <relation> has child elements **<from>** and **<to>** to reference the lines and OCPs that are connected by the (directed) connection
      +  * with attribute **@line**
      +  * with attribute **@ocp**
      - * <connection> has enumeration attribute **@type** to specify the type of the connection with possible values:
      ?    ^^^^ ^
      
      + * <relation> has enumeration attribute **@type** to specify the type of the connection with possible values:
      ?    ^ ^^
      
         * "direct"
      -  * "changeDirection"
      +  * "changeDrivingDirection"
      ?           +++++++
      
         * ...
      + * <relation> has optional attribute **@priority** (integer 0..255) to specify the priority of a relation (relevant when several relations exist in parallel)
      + * <relation> has child element **<averageDelayTime>** with attributes **@value** (xs:duration) to specify the average delay time due to waiting, shunting or other delay reasons

      adding some more details for the railML 2.5 solution proposal

    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer

      In [changeset:"1221/railML"]:

      implementing first version of OCP turning resistances, see #413
    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer
      • Description changed
        == Description ==
        
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
         * Michael Gruschwitz, 18.06.2021: [https://www.railml.org/forum/index.php?t=msg&th=819&goto=2767&#msg_2767]
        * Trac tickets:
         * #413
        * Wiki documentation:
         * IS:ocp: [https://wiki2.railml.org/wiki/IS:ocp]
        
        == Proposed solution in railML 2.5 ==
        
        It is suggested to integrate topological relationships into the <ocp> element to define OCP-internal connections.
        
        In particular, a new, repeatable element **<relation>** shall be added in <ocp / propOperational>:
      - * <relation> has child elements **<from>** and **<to>** to reference the lines and OCPs that are connected by the (directed) connection
      + * <relation> has mandatory child elements **<from>** and **<to>** to reference the lines and OCPs that are connected by the (directed) connection
      ?                 ++++++++++
      
      -  * with attribute **@line**
      +  * with required attribute **@line**
      ?        +++++++++
      
      -  * with attribute **@ocp**
      +  * with required attribute **@ocp**
      ?        +++++++++
      
      - * <relation> has enumeration attribute **@type** to specify the type of the connection with possible values:
      + * <relation> has required enumeration attribute **@type** to specify the type of the connection with possible values:
      ?                 +++++++++
      
         * "direct"
         * "changeDrivingDirection"
         * ...
        * <relation> has optional attribute **@priority** (integer 0..255) to specify the priority of a relation (relevant when several relations exist in parallel)
      - * <relation> has child element **<averageDelayTime>** with attributes **@value** (xs:duration) to specify the average delay time due to waiting, shunting or other delay reasons
      ?                                                                       -
      
      + * <relation> has optional child element **<averageDelayTime>** with required attribute **@value** (xs:duration) to specify the average delay time due to waiting, shunting or other delay reasons
      ?                 +++++++++                                            +++++++++
      

      clarification of attribute and element usage (required/optional)

    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer
      • Description changed
        == Description ==
        
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
         * Michael Gruschwitz, 18.06.2021: [https://www.railml.org/forum/index.php?t=msg&th=819&goto=2767&#msg_2767]
        * Trac tickets:
         * #413
        * Wiki documentation:
         * IS:ocp: [https://wiki2.railml.org/wiki/IS:ocp]
        
        == Proposed solution in railML 2.5 ==
        
        It is suggested to integrate topological relationships into the <ocp> element to define OCP-internal connections.
        
        In particular, a new, repeatable element **<relation>** shall be added in <ocp / propOperational>:
        * <relation> has mandatory child elements **<from>** and **<to>** to reference the lines and OCPs that are connected by the (directed) connection
      -  * with required attribute **@line**
      +  * with required attribute **@line** (tGenericRef)
      ?                                       ++++++++++++++
      
      -  * with required attribute **@ocp**
      +  * with required attribute **@ocp** (tGenericRef)
      ?                                      ++++++++++++++
      
        * <relation> has required enumeration attribute **@type** to specify the type of the connection with possible values:
         * "direct"
         * "changeDrivingDirection"
         * ...
      - * <relation> has optional attribute **@priority** (integer 0..255) to specify the priority of a relation (relevant when several relations exist in parallel)
      ?                                                              ^
      
      + * <relation> has optional attribute **@priority** (integer 1..255) to specify the priority of a relation (relevant when several relations exist in parallel), whereas 1 is the highest priority.
      ?                                                              ^                                                                                                ++++++++++++++++++++++++++++++++++++
      
        * <relation> has optional child element **<averageDelayTime>** with required attribute **@value** (xs:duration) to specify the average delay time due to waiting, shunting or other delay reasons
      • Status changed from new to accepted

      updating railML 2.5 solution proposal (references instead of strings, range of priority integer)

    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer

      In [changeset:"1234/railML"]:

      adapting implementation of OCP internal relations, see #413
    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer

      In [changeset:"1235/railML"]:

      adding further enumeration values for OCP relation type as requested in the forum post, see #413
    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Maintainer
      • Cc added @coordination.IS
      • Description changed
        == Description ==
        
        For the exchange of route networks in macroscopic modelling, the individual <ocp> turning resistances at the transition from one line of a node to another line of a node are to be assigned. Exemplary applications are path finding algorithms for the compilation before (!) ordering train paths of a train.
        
        _(de: Für den Austausch von Streckennetzen bei makroskopischer Modellierung sollen den einzelnen <ocp> Abbiegewiderstände beim Übergang von einer Strecke eines Knotens auf eine andere Strecke eines Knotens zugewiesen werden. Beispielhafte Anwendung sind Wegesuch-Algorithmen für die Zusammenstellung vor (!) der Bestellung von Trassen eines Zuges.)_
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
         * Michael Gruschwitz, 18.06.2021: [https://www.railml.org/forum/index.php?t=msg&th=819&goto=2767&#msg_2767]
        * Trac tickets:
         * #413
        * Wiki documentation:
         * IS:ocp: [https://wiki2.railml.org/wiki/IS:ocp]
        
        == Proposed solution in railML 2.5 ==
        
        It is suggested to integrate topological relationships into the <ocp> element to define OCP-internal connections.
        
        In particular, a new, repeatable element **<relation>** shall be added in <ocp / propOperational>:
        * <relation> has mandatory child elements **<from>** and **<to>** to reference the lines and OCPs that are connected by the (directed) connection
         * with required attribute **@line** (tGenericRef)
         * with required attribute **@ocp** (tGenericRef)
        * <relation> has required enumeration attribute **@type** to specify the type of the connection with possible values:
         * "direct"
         * "changeDrivingDirection"
      +  * "crossesContraflowTraffic"
      +  * "requiresShunting"
         * ...
        * <relation> has optional attribute **@priority** (integer 1..255) to specify the priority of a relation (relevant when several relations exist in parallel), whereas 1 is the highest priority.
        * <relation> has optional child element **<averageDelayTime>** with required attribute **@value** (xs:duration) to specify the average delay time due to waiting, shunting or other delay reasons
      • Owner set to @documentation.GOV
      • Status changed from accepted to assigned

      added further enumeration values for OCP relation type;

      implementation in XSD has been done, documentation in Wiki is pending; handing over the ticket to Mr. Leberl as he is responsible for the wiki documentation

    • Documentation
      Documentation @documentation.GOV · 3 years ago
      Maintainer
      • https://wiki2.railml.org/wiki/IS:propOperational#:~:text=relation and childs have been added
      • https://wiki2.railml.org/wiki/Dev:changes/2.5#Turning_restistances_added_to_.3Cocp.3E has been added

      @coordination.IS Please, check.

    • Documentation changed the description 3 years ago

      changed the description

    • Documentation assigned to @coordination.IS and unassigned @root 3 years ago

      assigned to @coordination.IS and unassigned @root

    • Documentation removed Wiki label 3 years ago

      removed Wiki label

    • IS Coordination mentioned in issue version3#452 (closed) 3 years ago

      mentioned in issue version3#452 (closed)

    • TT Coordination changed milestone to %2.5 2 years ago

      changed milestone to %2.5

    • TT Coordination removed 2.5 label 2 years ago

      removed 2.5 label

    Please register or sign in to reply
    Assignee
    Documentation's avatar
    Documentation
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets

    railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany