The document summarizes a meeting of the Strategic Planning for Transportation for the Nation Executive Steering Committee. The meeting agenda included an overview of the Transportation for the Nation concept, strategic planning, stakeholder outreach activities, data requirements from federal agencies, and potential road data sources. Discussion touched on including tribal nations, defining authoritative data sources, federal data needs, and challenges integrating data from various levels of government. The U.S. Census Bureau discussed their road network data from the TIGER program and efforts to improve accuracy through partnerships.

2. TFTN Concept

3. TFTN Strategic Planning

4. Steering Committee Roles and Responsibilities

5. Stakeholder Outreach and Finding

6. Stakeholder Outreach Activities

7. Trends & Findings to Date

8. Geospatial Transportation Data Requirements from Federal Agencies Meeting

9. Pro’s and Con’s of Potential Road Data Sources

10. The Road Ahead

11. Examples of Desired Inputs from Executive Steering Committee

12. Questions / AnswersDan Widner – Tim Trainor - Rich Grady – Randy Johnson - Steve Lewis – Don Cooke – Tom Roff – Ron Vaughn <br />Tribal Nations need to be included – BIA – Bull Benette – NGAC Member<br />ID Key Stakeholders within the BIA<br />Randy – Semetics- How can the states be the authoritative source? State DOT is the authoritative source, and the states believe that the local areas are the authoritative source (Producer of the data). <br />Tom Roff – When I think of authoritative data, I get it from the state, and the state is the authoritative data. <br />Randy – Obviously the state isn’t developing the dataset, but they also compile for push in and pull out to federal highway. <br />Come up with a new concept besides authoritative data sources. Leave it open at this point. Come up with new concept for the “authoritative” data source.<br />Tim – Federal agencies in the same room together for BASIS of road data, and this would be the basic part of the federal road network. Roads for the nation for federal requirements. Then TFTN could consume it. Strawman with different needs for roads. Refine and keep raising questions, and from this meeting there is a final step of high level requirements. Basic information, the LOD that of managing safety issues, and need for open access, and putting stuff in the public domain. <br />There is a surprising, need for an LRS. General talks of that effort.<br />Randy – How are those things left off the document is taken into account. Non Federal are going to have different requirements - federal requirements are substanancive enough to make a baseline that we need to have a conversation about this.<br />Roff – Rumors from safety that it might be in the appropriations bill, it’s been put into the draft. There are grumblings that they are asking for a large amount dedicated to building for the state DOTs<br />Throwing the question out to the data providers, does this meet within their swim lane, can they even do it? Do they want to take on this responsibility? Lack of resources for collecting detailed data from non-Federal Agencies<br />***Tiger, not updated every ten years, nationwide, Tiger produces once a year, and reflects the updates every year. FY11 Budget, to improve the address list, and the maintenance of the road network. Partnerships with local government. ts, all levels 7.6 meter accuracy standard, and matched only those roads that you can find. USGS did try to use it as their national map standards…result of the tiger line data. Working with USGS to fix the problem. Improvement to overall line data. Census is using imagery to build the road data, feature level metadata that goes thru. One time expense to clean up the data, Census => USGS workflows, and get it out on the next version of Tiger. More web-based development, with lots of irons in the fire. Tim thinks Census is both a data producer as well as a data integrator.<br />Don Cooke, Feature Metadata=>which line segs meet the 7.6 meters, that’s a goal, when we have that information we are putting together feature level metadata. If someone wanted to raise the whole of the national map standard. 5 meters or better for its accuracy. Don Cooke is no longer at TeleAtlas he’s at ESRI on the Payroll….TeleAtlas did a similar thing in the late 90s , improving accuracy, and improving accuracy and Tiger is a reasonable starting place for TFTN…<br />Not yearly updates, and look at variety of options and manage the processes and state governments. Provide transaction data instead of full datasets. Hammer and chisel…Working with USGS and others and VGI/OSM to assist with the accuracy of tiger, and continue to support them and add to it. If the attributes are no good, there is a way to go through a validation process, with a crowd-sourced model. We haven’t had that kind of capability. Those are the things we’ll be looking at the first year. <br />Next time for TIGER line, 2010 census, Geographic base. 2010 line data end of this year, and done by end of January. Will be putting out a roads layer, help people in the use of the data. Shapes, and have all the attribution and metadata with it<br />Navigation? Routing? Not really, its TIGER. We don’t have the routing data associated with the TIGER data. We would be able to hook in Navteq data as something we can take from a private vendor as part of a service..what’s out there, and what makes sense to put into tiger, and have other elements put in, but there a number of things we can look at.<br />How far are we along to getting to what a final product would look like?<br />Roff, Going through the ongoing process, and putting information as to what is information as to what we are approaching….and the current time…<br />