-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alignment with USDOT Connected Work Zones #74
Comments
Going through the WZDx specs, A great start would be looking into the WorkZoneRoadEvent Object and RoadEventFeature Object. I think that |
In order to tie together I think another Activity called |
From @bhamlinSDOT in #53: I recently had some discussions with SDOT staff that are involved with the WZDx and there seems to be a number of areas where CDS could align with the WZDx.
|
See this discussion for possibly aligning lane types in #37. |
Idea for cross referencing WZDx and CDS by unique identifiers, eg CDS curb_zone_id or curb_area_id and WZDx id. Added to the public CDS Curbs feed in the curb and area objects could be the following fields in an array:
which would simply reference any active or upcoming WZDx feeds and ids that impact the defined CDS locations. E.g. And added to public WZDxFeed feed in one of the RoadEvent properties under their CoreDetails could be the following fields in an array:
that reference any CDS curbs or areas from the public Curbs API feed that are impacted by this workzone. Maybe these can be wrapped and grouped under a This would allow producers of WZDx to check then include a reference to any overlapping CDS feeds for their consumers, and the producers of any CDS feeds to check then include a reference to any overlapping WZDx feeds for their consumers. |
I know that for most providers at the state level, introducing a required field for CDS may be hard as they do not necessarily work with loading/unloading. I think it may also break compatibility with their current spec but would love to see what Nate or Mark from Volpe have to say. In the WZDx feed, I think some new LaneType values could be added. These could be For another direct connection, I think that RestrictionType could include the addition: |
@schnuerle After previous discussions with WZDx members, I think it would be best for the WZDx feed to have an optional CDS reference point so that agencies would be able to track how many workzones are affecting different types of curb zones at a given time. This could be done internally without a new field in WZDx by looking at intersecting data. A new field would allow for a management system to actively tie the workzone to a curb zone without having to run a spatial analysis but still could be ran for verification. |
There is now a PR in WZDx to add references to CDS here usdot-jpo-ode/wzdx#326 |
The PR #326 has been approved by the WZDWG and will allow for curb zones to be referenced in v4.2 which will be released this month! |
Links:
Discussed in #53
Originally posted by schnuerle December 20, 2021
How could CDS align with the USDOT's Work Zone Data Exchange (WZDx)?
This came up in a discussion of lane types around a curb, vehicles that could be double parking or blocking curbs, and where and how to specify or align with WZDx IDs.
#37 (reply in thread)
The text was updated successfully, but these errors were encountered: