Closed j-d-b closed 1 year ago
Deferred as there needs to be more discussion regarding other verification/accuracy properties that would be beneficial to make it worthwhile to create a separate object.
Closing until more descriptive location accuracy is desired.
This issue is related to #201, #213, and #232.
Background
Currently, the properties for describing positional accuracy of a road event—that is, the "accuracy" of coordinates of a RoadEventFeature's
geometry
—occur directly on the WorkZoneRoadEvent (the only type of road event where they are currently used). There are two properties related to positional accuracy,beginning_accuracy
andending_accuracy
, but could be more in the future to allow representing the accuracy of intermediate points (see #232) or the measured accuracy of the coordinates as a distance (see #201).Since these properties are defined only on the WorkZoneRoadEvent, if there was desire to add them to another type of road event, such as the DetourRoadEvent, they would have to be duplicated there—any changes in the future would have to be made in two places, which is error prone and inelegant.
Proposal
All properties related to positional (or "spatial") accuracy could occur on a new
PositionalAccuracy
object. ThePositionalAccuracy
object would be used by theWorkZoneRoadEvent
and in the future any other objects that need to describe positional accuracy. In addition, expansions to what positional accuracy defines can be represented would be added to this object.PositionalAccuracy Object
The
PositionalAccuracy
object describes the accuracy of geographical coordinates.Properties
beginning_accuracy
ending_accuracy
Used By
positional_accuracy
Note that the above implementation just moves the
beginning_accuracy
andending_accuracy
properties to thePositionalAccuracy
object. However, i think it would be cleaner to also implement the approach in #213