Let’s Get Work Zones on the Map
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 70 | |
| Author | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/58509 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
State of the Map US 201931 / 70
5
7
14
20
26
28
30
31
33
36
38
40
43
44
51
53
55
56
60
61
67
68
69
00:00
Computer animation
Transcript: English(auto-generated)
00:01
Hello everybody, I'm Darryl Dudley, and I'm going to talk about work zone data today, trying to get work zones on the map. So I'm a geographer at the US Department of Transportation. I work in the research branch of the Office of the Secretary of Transportation, and most of my work is focused on developing geospatial data for transportation data sets and standards.
00:23
Today I'm going to talk about I'm going to give you an update on the department's oops Get my notes here of the department's Davey
00:40
Initiative which is data for automated vehicles and integration and also talk about like I said the work zone data exchange project Also going to talk about the priorities for data exchange and the important role they play in digital mapping I'll highlight both the federal and non-federal role for accelerating voluntary data exchange between infrastructure operators and owners
01:04
Or we call them IOOs and original equipment manufacturers And then I'll identify new critical use cases and priorities for data exchange And we'll address specific needs that will help further inform and provide innovation for transportation decision-making
01:23
So let's start by looking at The AV program back in October of 2018 the department published preparing for the future of transportation Automated vehicles 3.0 and that study focused on
01:41
Advancing multimodal safety advancing multimodal safety reducing policy uncertainty There's people want to know what the department's going to do about automated vehicles and outline policies for how to work with the department During that those activities
02:02
Data is a cross-cutting issue that appears throughout AV 3.0 And in this document the department explicitly calls for stakeholders to identify opportunities for voluntary data exchanges and for groups It also highlights efforts that are aimed at enabling voluntary data exchanges
02:27
So AV 3.0 was developed around the input from a diverse set of stakeholder engagements throughout the nation Through these engagements engagements We frequently heard about the need for data to remove various barriers barriers to autonomous vehicles and their integration
02:44
This includes data produced by AV vehicles and cells but also the data that's consumed by Companies that map map for AV automated vehicles autonomous vehicles
03:02
The US Department of Transportation launched AV as a multimodal initiative to identify Prioritize monitor and where necessary address data exchange needs For automated vehicles Access to data is a critical enabler for the safe efficient and accessible integration of a automated vehicles into the transportation system
03:22
And a lack of access to data could impede That integration or delay their safe interjection into the transportation system A better work zone activity data has been focused for a while at the department It's becoming a crucial and important part and a driver
03:44
for improved agency capabilities Particularly as our transportation environment evolves and it to accommodate auto autonomous vehicles In the case of work zone data. We are determined We determined that there was likely a need for federal government to play an active role and in this case we're
04:05
facilitating The meeting of industry players IOs OEMs And they're kind of getting together to do this stuff to figure out the specification
04:25
In the category of infrastructure data and the need to exchange data We see a common pattern and we'd like to call this the local data challenge Up to date information about dynamic conditions occurring on the road such as construction events Can help AVs safely navigate
04:43
Those areas and make them more efficient For example many infrastructure owners and operators IOs maintain data on work zone activity, but a lack of common data standards And the convening mechanism for those organizations to talk to each other
05:03
Make it difficult for that data to be consumed and used by AVs, so The whole work zone data exchange is inspired by the GTFS story general transit fee specification
05:21
Which was originally developed via the Portland TriMet Transit Authority and Google GTFS enables the exchange of transit information between service providers publishers and writers and The specification is very flexible and easy to adopt which makes it
05:43
More efficient at meeting the mission of what it needs to do of meetings purpose So inspired by the GTFS the department launched the work zone data exchange to jumpstart a voluntary adoption of The basic work zone data specification through a collider through a collaboration of data publishers data publishers and users
06:05
The specification enables infrastructure infrastructure owners and operators to make harmonized work zone data available for third-party use the intent of This exchange is to make travel on public roads safer and more efficient through a ubiquitous access to that work zone data
06:24
Specifically the project aims to get data on work zones into vehicles to help automated driving systems and To help you've been drivers navigate more safely the long-term goal is to enable a collaborative maintenance and expansion of the specification to meet emerging needs of AVs
06:43
But more broadly through this project the department aims to identify a repeatable approach to accelerate The harmonization of local data sources that can improve safety
07:06
So here we have an example Maricopa County, Arizona It's a pretty busy corridor in an industrial area and you can see they've broken into two phases If you want to see the feed itself, it's a jeep. It's a JSON feed. You can go there and check it out
07:21
It's just a string But through that they can show it on the map and then it can also be read by Navigation systems as well. We also have another example in Iowa
07:41
The Iowa DUT is currently publishing a work zone data feed Via the specification it's an XML feed not a JSON so we don't tell you how to do it We just tell you what what the contents is They start by formatting the existing 511 data to match the WZD specification
08:00
And then the asset management information data Is added to that and then the data is cleaned and then published as an XML file. So a few lessons learned
08:23
From all this work Number one immediate benefits or may not be connected to automated driving systems human drivers can also benefit though Planners benefit construction companies and workers can benefit and we need to adopt adapt
08:41
Value proposition based on the stakeholder Lesson two we gained more clarity about who the primary data uses are Which turns out to be the folks that are making the HD maps high-definition maps Which are either done by in-house service or by a third party and not necessarily OEMs or the car companies
09:10
Lesson three we also learned that standing up these data feeds is harder for IOs Independent owners and operators to do even when they already collect that information
09:20
Proprietary infrastructure data systems make producing this data a challenge For example confirmation of the local data challenge Public agencies often lack resources and capabilities to make the data available Data layer services like Google Cloud or esri are critical for IOs to get this data out
09:44
IOs will not necessarily be the ones to build the feeds but rather they would host them in their provider layers Lesson four there are multiple potential starting points for generating harmonized feeds
10:01
The current approach is based on harmonizing the basic work zone data that states could already make available today and identifying What would be the highest priority data for them to make available tomorrow and then lesson five?
10:21
There are many potential organizations and mechanisms to drive this vision forward Stakeholders were supportive of the GTFS style approach to advance the new data exchanges Several were especially enthusiastic about the US DOT's modern and Modern and collaborative approach to standards development a little bit about that. We've kind of tried to do standards in the past
10:44
By defining what the standard is and putting it out there and say here's a standard please adhere to it. It didn't really work We tried to do everything in one big standard but the the GTFS model kind of follows the market and lets the Community drive its its
11:01
Development and specification. So we're trying to stick with that model. See if that's successful and go forward from there So the work zone working group is accountable to the federal geographic data
11:21
Data committees transportation subcommittee. I happen to be the chair of that committee. Hi If you want to get involved, please talk to me after So the whole purpose of that committee is to drive the development of geospatial Transportation data and standards We want to highlight our heightened federal awareness
11:42
Not just for awareness about transportation data across the country and use that data to make transportation safer Safer need it done soon here. Okay
12:12
So the work zone data working group Has a few objectives and goals here we wanted to not only define the specification
12:22
But also stand up a working group that would Be that organization that manages that specification as well. So we didn't want it We didn't want the department to have it. We wanted to put it out into a community. So members include a Lot lyft is there
12:43
General Motors is there Google Uber is is there a Lot of states so it's a community that it's kind of diverse and they're all talking about it and really kind of doing a good job of managing that specification Through that group they have meet these objectives they review current content of
13:06
version 1.1 of the work zone data specification and I also review the comments received from that community and then prioritize those as well They recommend the changes that will happen to the specification
13:21
And then they also groom the backlog of potential and future changes to the specification as well We have a gift page you guys can check it out. So we know that one of the biggest
13:48
Priorities we've heard through this development is need for to get current information about whether works And workers are actually present in the work zone We're seeing improvements we see improvements to worker safety as being one of the strongest reasons for investing in works on dating
14:05
publication We're looking to create a campaign around putting workers on the map and address the technical and institutional barriers to get that accomplished
14:20
Safety is a top priority at the US Department of Transportation And it's our organizational mission to enhance safety and mobility on our nation's highways Some statistics here in 2017 there were 799 fatalities that took place in work zones and That was a 2% increase over the previous year
14:40
132 of those deaths were work zone workers Over 80% of fatalities in work zones are drivers are by drivers or Passengers just trying to navigate through the work zone. So we've created a grants program for work zone data
15:12
The purpose of the research program is to increase the safety of traveling the traveling public through the production of consistent public work zone data feeds across jurisdictions
15:23
So if you're a DOT and you want to get in on board apply for a grants And we hopefully give you some money to kind of get these speeds up and running buyers for yourself
15:42
Goonan This is not my presentation. I'm still a little awkward with it. I'm sorry about that If you have any questions about work zone data though happy to answer them Sir Yes it was I
16:01
Want to kind of wanted to make a bigger working group, but not just work zone I wanted to kind of be a roads event working group so that we couldn't incorporate closures But they had kind of they had a momentum with the work zone data thing So changing the name would have kind of slowed it down But I do I do see this evolving into a much larger road events kind of thing
16:34
Not right now, but if you want to join the working group you can actually suggest that
16:41
So if you just work zone data on github and it'll come right up you'll find us and there's a place there to submit Change requests and things like that We're not but I'm certainly you know, it's open to whomever wants to join
17:06
Certainly Certainly to build an international standard that we great. Yeah, so is it okay. Thank you for your time Sorry about reading to you