Display oriented speed limit differently than the non-oriented ones

[Castavo]

Pitch

When looking at the map for a train, we see this on its path. It appears as though the train is limited to 200 km/h or above (blue), but actually it is limited to 160 km/h.

It turns out that the speed limit we see on the map does not apply because it's oriented in the direction opposite of the train so it falls back to a lower speed limit.

It would have been great to directly see that the speed limit we see on the map does not apply to the train.

Acceptance Criteria

• [ ] The oriented speed sections are displayed differently than the non-oriented ones.
• [ ] The orientation of the speed section is visible.
• [ ] Other oriented data benefit of the same changes ?

[bougue-pe]

Summary:

• we all forgot that speedLimits are directed
• no bug detected on speedLimitTags handling (and fallbacks)
• path is questionable (circulating on the right track), so probably an issue with routes (or PF bug?)
• it's hard but possible to debug this from OSRD's interface (the tag used to limit will be added to speed-space graph later in this PI: https://github.com/OpenRailAssociation/osrd/issues/7732)

Details:

• The 160-limited parts of the path are when circulating on the right track

• On those tracks, E32C and V160 speed limits are available on both directions, E30C is only available on the "usual" direction (circulating left).

  • explore this with the "rectangle select" and zoom enough from infra editor, selecting only the interesting speed limit tags (here E30C on south track).
  • then select and edit the speedLimit shows (clic "see 0 additional track sections" 😅... opening a bug on that)
  • then determine the actual direction of the track-section (used a switch this check if BEGIN/END is connected): start is at the North on this

• from the speedLimitTags config, E30C ends up fallbacking on V160 on those, while E32C uses its original speedLimit.

[Castavo]

I feel like the front should show directed track ranges in a different way than the undirected ones then This bug could be turned in a feature request maybe, what do you think ?

[bougue-pe]

I agree (close or new issue is fine): The whole "show directed object" may be improved/designed: track sections, speedLimits (there are probably more) is especially valuable on infra editor.

Another issue is that a lot of info are only readable in "edition" mode.

[Castavo]

I transformed this bug into a feature request, and changed the description