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
92
stars
62
forks
source link
Add town/municipality/jurisdiction field to road event information #83
This issue replaces/continues the discussion from #35. Please see the discussion there for background.
From the original discussion:
I'm part of a team working with MassDOT, and we believe town (as the general term; also encompasses city) would be beneficial information about a work zone to include in our data feed.
The road event entity includes location information such as the road name, road number, begin/end cross streets & mileposts, and actual coordinates. An optional human-readable "town" (name tbd) field would provide the same human-readable benefits as these location fields.
In #35, jurisdiction seemed to be the most general term for town/city but this should be discussed here. This optional field would be added to the road_event entity and would allow for providing this information if a producer desires.
This issue replaces/continues the discussion from #35. Please see the discussion there for background.
From the original discussion:
The road event entity includes location information such as the road name, road number, begin/end cross streets & mileposts, and actual coordinates. An optional human-readable "town" (name tbd) field would provide the same human-readable benefits as these location fields.
In #35,
jurisdiction
seemed to be the most general term for town/city but this should be discussed here. This optional field would be added to theroad_event
entity and would allow for providing this information if a producer desires.