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

Allow specifying the sign text for a Flashing Beacon #308

Closed j-d-b closed 2 years ago

j-d-b commented 2 years ago

This PR resolves #295 by adding an optional sign_text property to the FlashingBeacon object which allows a producer to provide the text on the sign the beacon is mounted on, if applicable.

RHolt-RIDOT commented 2 years ago

This added option seems safe for now thank you. But I have just moments ago added some input to Issue #295 that may pertain to this, and so below I repeat that input in case/hopes it helps with moving forward on this Issue.


Many others have already well noted/described (e.g., via Issue #238) that there are many, many, many possible use cases for Flashing Beacons (FBs) in work zones, and while at first glance I was thinking @tfoster-vm and others have been 100% spot-on above in noting that that spec/feed ideally should accommodate/indicate the reason/purpose for (function of) the FB (i.e., what are they telling the road users?), as I think on it further, it may be helpful to remember the following: per current MUTCD an FB is almost always SUPPLEMENTING an appropriate warning or regulatory sign, marker, or other TCD (only exception I can think of is for an Intersection Control Beacon (ICB) where a Yellow FB need not be supplemented by anything else, and in vast vast vast majority of Work Zones there will NOT be any ICBs). So I suggest considering whether it makes sense to not focus on the FBs but instead focus on the "greater TCD" or system that each FB is associated with. Not that anyone wants to see another list, but a 'high-end' generic list of such system functionality that I assume may be most commonly used in Work Zones in near future could be:

I may certainly be missing a few from the above.

If more specific static text to specifically indicate what the TCD is telling road users is needed, then I can understand and am fully open to as proposed above by @tfoster-vm. I just hope (from my DOT perspective) that, given there are so many, many possible messages on TTCDs that FBs can be used to supplement in a Work Zone, there won't be any undue burden on data providers/contractors (all the more support for making things "optional" at least for now).