add moving direction to moving object classification

[0815-code]

Signed-off-by: Schloemicher, Thomas AVL,AT [email protected]

#### Reference to a related issue in the repository Add a reference to a related issue in the repository.

Add a description

Adding moving direction to moving object classification to have a high level sematic information of the overall moving direction of a moving object whether it is oncoming, moving in the same direction or crossing.

Some questions to ask: What is this change? What does it fix? Is this a bug fix or a feature? Does it break any existing functionality or force me to update to a new version? How has it been tested?

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

• [x] My suggestion follows the style and contributors guidelines.
• [x] I have taken care about the documentation.
• [x] I have done the DCO signoff.
• [x] My changes generate no errors when passing CI tests.
• [ ] I have successfully implemented and tested my fix/feature locally.
• [x] 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!

[kmeids]

@ThomasSchloemicherAVL any update from your side on this topic? And do you need to discuss this in the SensorModelilng group?

[clemenshabedank]

OSI CCB 09.05.2022:

• It might makes sense to just introduce this information in SensorData (Detected object).
• Could be a good topic for v3.6.