Project

General

Profile

Feature #5652

Roadmarks with irregular length and spaces

Added by Thorsten Rennekamp 7 months ago. Updated 29 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
specification 1.5
Start date:
09.02.2017
Due date:
% Done:

0%


Description

We would like to define broken roadmarks with irregular spaces and length which are nor periodic and change with each roadmark. The roadmarks are measured from real world roads.

Now it is only possible to define irregular roadmarks by defining new roadmarks which overwrite the one before and switching between solid and node:

      ...
      <roadMark width="0.14" weight="standard" type="solid" sOffset="0" color="standard" laneChange="none"/>
      <roadMark width="0" weight="standard" type="none" sOffset="5.641212091809487" color="standard" laneChange="none"/>
      <roadMark width="0.14" weight="standard" type="solid" sOffset="15.59618091854981" color="standard" laneChange="none"/>
      <roadMark width="0" weight="standard" type="none" sOffset="20.83390254467857" color="standard" laneChange="none"/>
      <roadMark width="0.14" weight="standard" type="solid" sOffset="31.81983379583627" color="standard" laneChange="none"/>
      ...

And if we have to model double lines with non-periodic length and spaces it gets even more complicated:

      ...
       <roadMark width="0" weight="standard" type="solid" sOffset="0" color="standard" laneChange="none">
       <type width="0" name="RoadMark">
        <line space="0" width="0.12" length="11.87457133947167" sOffset="0" rule="none" tOffset="0.2014206014707397"/>
        <line space="8.748427371137444" width="0.12" length="3.126143968334221" sOffset="0" rule="none" tOffset="0.01894396090607186"/>
       </type>
      </roadMark>
      <roadMark width="0" weight="standard" type="solid" sOffset="11.87457133947167" color="standard" laneChange="none">
       <type width="0" name="RoadMark">
        <line space="0" width="0.12" length="13.06821128030493" sOffset="0" rule="none" tOffset="0.2014206014707397"/>
        <line space="9.946790173853477" width="0.12" length="3.121421106451452" sOffset="0" rule="none" tOffset="-0.01199556023114942"/>
       </type>
      </roadMark>
      <roadMark width="0" weight="standard" type="solid" sOffset="24.94278261977659" color="standard" laneChange="none">
       <type width="0" name="RoadMark">
        <line space="0" width="0.12" length="4.289984429816286" sOffset="0" rule="none" tOffset="0.2014206014707397"/>
        <line space="1.033422224445282" width="0.12" length="3.256562205371004" sOffset="0" rule="none" tOffset="-0.02609114701200324"/>
       </type>
      </roadMark>
      <roadMark width="0" weight="standard" type="solid" sOffset="29.23276704959288" color="standard" laneChange="none">
       <type width="0" name="RoadMark">
        <line space="7.12448067211988" width="0.12" length="2.776494313023775" sOffset="0" rule="none" tOffset="0.2014206014707397"/>
        <line space="9.116622483087603" width="0.12" length="0.784352502056052" sOffset="0" rule="none" tOffset="-0.01387127919126065"/>
        <line space="0" width="0.12" length="7.614860703687665" sOffset="2.286114281455991" rule="none" tOffset="-0.199350982995597"/>
       </type>
      ...

We would like to define a list of single lines which are not periodically repeated and with individual sOffset, length, width and tOffset.

History

#1 Updated by Andreas Richter about 2 months ago

That's definitely an interesting issue! It could be an idea to use a list of all stripes and gaps following one trajectory to model this real world scenario.
It would be good to have the possibility to define the tOffset with a poly3 function to have more flexibility in modelling markings independent from the course of the road.

Additional an End-sOffset would be nice, thus no placeholder with type=none is needed if the road section is longer than the marking should be.

#2 Updated by Marius Dupuis 29 days ago

  • Description updated (diff)

#3 Updated by Marius Dupuis 29 days ago

Proposal:

- The style guide should make a distinction between "regular/preferred" and "custom" definitions
- using a list, as proposed in comment no. 1 should be considered for the realization (s/t for begin and end of each stripe)
- end s-offset should be in Odr 1.5
- variable t-offset later...

Also available in: Atom PDF