usdot-jpo-ode / wzdx

The Work Zone Data Exchange (WZDx) Specification aims to make harmonized work zone data provided by infrastructure owners and operators (IOOs) available for third party use, making travel on public roads safer and more efficient through ubiquitous access to data on work zone activity.
Creative Commons Zero v1.0 Universal
89 stars 62 forks source link

Add additional values for MarkedLocationType enumeration #227

Closed dxpack closed 2 years ago

dxpack commented 2 years ago

Location markers in a work zone (or road event) may not be exclusive to the start or end positions, or may be indeterminate in terms of order within a series of location markers. Adding the following additional values for MarkedLocationType:

j-d-b commented 2 years ago

What is the utility of these values? Is it like a confirmed coordinate to help create the road event geometry?

dxpack commented 2 years ago

Yes, in the case of the -intermediate values. In the WZDxFeed, the geometry is set to either LineString or MultiPoint, with the former being preferred. A LineString is comprised of at least 2 points to describe "the entire road event path". MultiPoint is to be used "when only the start and end coordinates are known". As is (v4.0) the spec for WZDxFeed provides for (and prefers) the delineation of a work zone to include locations intermediate to the start and end points, but as the SwzDeviceFeed does not provide a means to ascribe a LocationMarker device as intermediate, those devices will be excluded from SwzDeviceFeed.

As for -undetermined values, there is also the need to include LocationMarker devices that are components of a work zone but are not part of the delineation of a work zone. For example, a GPS tracking device (LocationMarker) attached to moving equipment that is being used in the work zone, or a LocationMarker attached to a static message sign (or other unconnected/non-electronic device) placed far ahead of the work zone where the static message sign is used to notify upstream vehicles of the upcoming work zone. Although organizationally both are component devices of the work zone, as is (v4.0) these would be excluded from SwzDeviceFeed because there is no applicable MarkedLocationType.

j-d-b commented 2 years ago

Superseded by #311.