Closed thomassedlmayer closed 1 year ago
CCB 2022-11-07: First to be further discussed in Harmonisation group, and possibly await results from dynamic signs harmonization effort.
The enum VARIABILITY_VARIABLE is not clearly defined, if it is movable and mutable, it can be, or can't. An additional field "VARIABILITY_MOVABLE_AND_MUTABLE" will be more specific.
Movable assumes, you can have a temporary sign e.g., for road works, but also traffic signs on vehicles. @SensorWG: Do we need to distinguish between these tempory signs or signs on vehicles?
CCB 2022-12-12: Merge as-is.
Description
As already mentioned by @jdsika in #623, the differentiation between mutable content (e.g. traffic sign type) and changes in position of traffic signs is not given yet. To maintain backwards compatibility the existing type VARIABILITY_VARIABLE is essentially kept as it is. It still describes traffic signs that CAN BE semantically and positionally variable. This means that it has to be expected that the traffic sign's type and position could change over time (exactly as it is with the current OSI version). If further differentiation in terms of semantics and position is desired, the new types VARIABILITY_VARIABLE_MOVABLE and VARIABILITY_VARIABLE_MUTABLE can be used.
Examples
VARIABILITY_VARIABLE:
VARIABILITY_VARIABLE_MUTABLE:
VARIABILITY_VARIABLE_MOVABLE:
Checklist
#### References resolves #623
671