Proposal for discussion: Add more detailed lane information to MovingObject

[tbleher]

Rationale: currently there is some lane information in OSI, but simple
requests like "what is the next vehicle on my lane" still require a lot
of calculations. This makes writing agent models unnecessarily hard.

Simulation environment usually already have all the required information
(since they already need to calculate assigned_lane_id and
assigned_lane_percentage). By providing this information directly, a lot
of code and calculation time can be removed e.g. from agent models.

The information is lightweight: three doubles per moving object. No
additional fields are needed for lanes. All lanes for which this
information is needed must have a center line, but OSI can be configured
to transmit all this static information at initialization time.

This is currently a breaking change, designed for 4.0.
It could be made compatible for 3.5 if desired.

This is a proposal for discussion.

Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:

• My suggestion follows the style and contributors guidelines.
• I have taken care about the documentation.
• I have done the DCO signoff.
• My changes generate no errors when passing CI tests.
• I have successfully implemented and tested my fix/feature locally.
• Appropriate reviewer(s) are assigned.

If you can’t check all of them, please explain why.
If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!

[clemenshabedank]

@ThomasSchloemicherAVL you might have an opinion on this.

[0815-code]

@clemenshabedank @tbleher
In fact i do. Fixing #368 and #490 where steps in this directions. #507 is missing. With all three i think we can have the functionality as desired above.

[tbleher]

This is obsoleted by the much more comprehensive approach in PR #599.