Importing Stop Lines from ASAM OpenDrive Model into SUMO

[dzakharekin]

Hello!

Following up on our discussion here: https://github.com/eclipse-sumo/sumo/issues/16283

We would like to ask whether it is possible to control the creation of stop lines from an .xodr file during model import into SUMO. At the moment, we are unable to import stop lines directly, and those generated automatically by SUMO based on traffic lights do not always match the original model. For example, the automatically generated stop lines can be placed either closer to or further from the intersection than intended.

Is there currently a way to import stop lines from OpenDrive, or to influence their placement during conversion?

Please see the attached .xodr file (with .txt extension), which includes manually added stop lines for reference.

data.txt

Thanks a lot

Example:

    <signals>
      <signal id="382b0b84-6ba8-49f1-a79f-82935db581a5" s="37.210409224970164" t="-2.6452082782438695" zOffset="0" orientation="+" dynamic="no" country="RU" countryRevision="2018" type="roadMarking" subtype="1.12" length="0.4" width="5.290416556487739">
        <validity fromLane="-1" toLane="-1" />
        <semantics>
          <priority type="stopLine" />
        </semantics>
      </signal>
    </signals>

References:

• https://publications.pages.asam.net/standards/ASAM_OpenDRIVE/ASAM_OpenDRIVE_Specification/latest/specification/14_signals/14_08_signal_semantics.html
• https://publications.pages.asam.net/standards/ASAM_OpenDRIVE/ASAM_OpenDRIVE_Specification/latest/specification/16_annexes/enumerations/map_uml_enumerations.html#top-EAID_6C1E90A5_2BD7_4a01_B744_A04A326D29C6

[namdre]

note, that the file cannot be loaded with https://odrviewer.io/ due to problems with the name attributes

[dzakharekin]

@namdre yes, it's my mistake. I updated file and now it works in https://odrviewer.io/