osi3::MovingObject::VehicleClassification::LightState::IndicatorState describes the state of the indicator. It is however not totally clear if this is the steady state of the indicator (continuously set as long as the indicator is pulsing) or a pulsing state. This should be clarified (Until now I assumed the state was steady, but after reading the description I am no longer sure).
Moreover, we noticed that we need both variants of that state:
- A steady state is useful e.g. for agent models, who are not interested in when the light turns on and off, but just want to know "is this vehicle currently using the left indicator"
- A pulsing state is useful to connect prototype displays in a driving simulator (where it is essential that all displays or sound outputs use the same frequency)
Therefore I would request that both the steady and the pulsing be represented.
I am willing to write a PR for this, if there is consensus that this is useful.
osi3::MovingObject::VehicleClassification::LightState::IndicatorStatedescribes the state of the indicator. It is however not totally clear if this is the steady state of the indicator (continuously set as long as the indicator is pulsing) or a pulsing state. This should be clarified (Until now I assumed the state was steady, but after reading the description I am no longer sure).Moreover, we noticed that we need both variants of that state:
Therefore I would request that both the steady and the pulsing be represented.
I am willing to write a PR for this, if there is consensus that this is useful.