Closed mark-mockett closed 1 year ago
Once @j-d-b, @sknick-iastate, and @jlarsonOmahaNE review and approve, this can be merged to release v4.1.
@mark-mockett, @sknick-iastate, @jlarsonOmahaNE released! I'll tag the commit and add the release notes to "Releases".
The PR marks the release of version 4.1 of the WZDx specification.
Noteworthy documentation changes are that the two feeds that WZDx defines are renamed:
Changes to the specification are listed below:
New Functionality
is_moving
boolean property to the FieldDeviceCoreDetails to allow indicating if any field device is moving as part of a mobile operation.road_direction
property to the FieldDeviceCoreDetails to allow providing the direction of the roadway that a field device is associated with.id
property of the RoadEventFeature, FieldDeviceFeature, and FeedDataSource, noting that a UUID may be required in the next major release.name
property to RoadEvenCoreDetails to allow providing a human-friendly name for a road event.personal-device
ramp-closure
road-closure
delineator
undefined
unknown
no-passing
to the RestrictionType enumerated type.sign_text
property to the FlashingBeacon object.two-way-center-turn-lane
to the LaneType enumerated type to replace the existingcenter-left-turn-lane
with a more generic value.Refactoring
is_moving
property on the ArrowBoard; use the newis_moving
on the FieldDeviceCoreDetails instead.road_event_id
property on the TrafficSensorLaneData from "Required" to "Optional" to allow providing lane-level data without a defined road event.road_event_feed_info
property on the [WorkZoneFeed] object; use the newfeed_info
property instead.is_start_position_verified
andis_end_position_verified
boolean properties to the WorkZoneRoadEvent to allow indiciating if the start and end positions are verified and clarify what verified means; these properties replacebeginning_accuracy
andending_accuracy
.beginning_accuracy
andending_accuracy
properties on the WorkZoneRoadEvent object; use the newis_start_position_verified
andis_end_position_verified
properties instead.is_start_date_verified
andis_end_date_verified
boolean properties to the WorkZoneRoadEvent to allow indiciating if the start and end date and times are verified and clarify what verified means; these properties replacestart_date_accuracy
andend_date_accuracy
.start_date_accuracy
andend_date_accuracy
properties on the WorkZoneRoadEvent object; use the newis_start_date_verified
andis_end_date_verified
properties instead.event_status
property on the WorkZoneRoadEvent object.road_names
property on the FieldDeviceCoreDetails from "Required" to "Optional".traffic-signal
value in the [MarkedLocationType] enumerated type; use the new [TrafficSignal] object instead.center-left-turn-lane
value in the LaneType enumerated type; use the newtwo-way-center-turn-lane
instead.related_road_events
property (and new supporting object RelatedRoadEvent and enumerated type RelatedRoadEventType) to the RoadEventCoreDetails to allow explicitly defining relationships/connections between road events; this replaces the Relationship object/concept.relationship
property on the RoadEventCoreDetails; use the newrelated_road_events
property instead.Cleanup
average_speed_kph
,volume_vph
, andoccupancy_percent
properties on the TrafficSensor and TrafficSensorLaneData object from "Integer" to "Number"average_speed_kph
on TrafficSensorLaneData from1
to0
.feed_info
property to the WorkZoneFeed object to replace theroad_event_feed_info
.update_date
property on the RoadEventCoreDetails and FieldDeviceCoreDetails to clarify what the value represents.edited by @j-d-b