Describe the feature
For mixed traffic, it can significantly help to know how a vehicle is controlled (e.g. for analysing traffic data from different sources). This information (if available) can help for traffic analysis.
Describe the solution you would like
I want to add a MotionControlType variable to VehicleAttributes (as it is not relevant for moving objects in general).
Suggested code within vehicle attributes:
enum MotionControlType
{
// Type of motion control is unknown.
//
TYPE_UNKNOWN = 0;
// Other (unspecified but known) type of controller for moving object.
//
TYPE_OTHER = 1;
// Real world regular person controls vheicle.
//
TYPE_REGULAR_DRIVER = 2;
// Real world professional driver (e.g. safety driver) controls vehicle.
//
TYPE_PROFESSIONAL_DRIVER = 3;
// Object is controlled by ADAS function but driver is in responsible.
//
TYPE_ADAS = 4;
// Object is controlled by AD function (no responsibility but possibility for passenger (if there are any) to takeover).
//
TYPE_AD = 5;
// Object is controlled remotely.
//
TYPE_REMOTE = 6;
}
// The type of the controller moving the object.
//
optional MotionControlType motion_control_type = 3;
Describe alternatives you have considered
Haven't seen any (but if already available, I would be glad to know).
Describe the backwards compatibility
How does the feature impact the backwards compatibility of the current major version of OSI? --> no issue since it could be optional
If the suggested feature would be implemented would there be an issue with the previous versions of OSI? What part of OSI would break or improve by this feature? --> more information available (obviously just for new osi traces)
Additional context
Relevant for data recording campaings and so maybe useful for projects as SYNERGIES. It is intended to use that information in omega-prime as well.
Describe the feature
For mixed traffic, it can significantly help to know how a vehicle is controlled (e.g. for analysing traffic data from different sources). This information (if available) can help for traffic analysis.
Describe the solution you would like
I want to add a MotionControlType variable to VehicleAttributes (as it is not relevant for moving objects in general).
Suggested code within vehicle attributes:
Describe alternatives you have considered
Haven't seen any (but if already available, I would be glad to know).
Describe the backwards compatibility
How does the feature impact the backwards compatibility of the current major version of OSI? --> no issue since it could be optional
If the suggested feature would be implemented would there be an issue with the previous versions of OSI? What part of OSI would break or improve by this feature? --> more information available (obviously just for new osi traces)
Additional context
Relevant for data recording campaings and so maybe useful for projects as SYNERGIES. It is intended to use that information in omega-prime as well.