Your SlideShare is downloading. ×
  • Like
GIS-T Notes Public
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

GIS-T Notes Public



Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. GIS-T Conference CONFERENCE : LOCATION: DATE: GIS-T Charleston, WV April 12-15, 2010 PARTICIPANTS: Steve Lewis, Patricia Solano, Richard Grady, Michael Terner, Todd Barr CONFERENCE NOTES GIS-T 2010 was hosted in Charleston WV April 12th -April 15th , 2010. The TFTN-Strategic Planning Group hosted a panel discussion of 8 speakers, to discuss what is TFTN and what does it mean to me. The panel discussion took place on April 13th . Speakers- Federal Perspective • Steve Lewis - DOT • Randy Fusaro - Census • Ronald Vaughn – DOT • Dan Wider – VDOT, but representing NSGIC Speakers – State Perspective • Tamela Lang - Colorado DOT • Skip Turner – NavTeq • David Blackston – Ohio DOT • Melanie Rippon Seigler – Virginia DOT April 12, 2010 The panel met during the afternoon break to discuss their thoughts and give a general overview of their presentations. The following are notes harvested from that discussion. • US DOT culmination of FGDC one transportation data model • FHWA how can HPMS support the TFTN • Tammy – more work for DOT outside of our business line, recommend to use HPMS. Common voice, open street did not know HPMS. Common geometry used for different purposes. Using private products use private partnerships. • Randy – Federal requirements. • Parker – NavTeq- they can provide a routable dataset quick. Then the government can take over an add to it. • Randy – • Dan Widner identify basic needs build it once use it many times April 13, 2010 The Panel Discussion began at 8:00am. Patricia Solano and Richard Grady have a brief overview, that was followed by the presenters. PRINTED: 1/29/2015 PAGE 1 OF 5 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE
  • 2. GIS-T Conference The following are notes harvested from the first panel discussion, which focused on the federal perspective. Steve Lewis Points • Feds shouldn’t tell YOU what to do. We want to hear from you on how to do it right. • All modes of transit eventually • Routing, LRS, addressable à Common geometry – Private sector adds routing? – Census adds addressing? Ronald Vaughn’s Points • Nation trans data source with surface system attributes • Feds: coordinate/reporting reqs; States: data authority for collection; Locals: acquires and aggregates; Private: support & technical services • States should take an enterprise approach: GIS = ARRA; Traffic; Accidents • HPMS can influence states via reporting requirements; would like to assist states, if possible Randy Fusaro’s Points • Core features – NOT everything to everybody • Aggregation from the bottom-up • Planning begins with ensuring Federal agency road reqs are met; then moves on to cover broader “national” requirements • State & Local: populate and maintain the roads • Private sector: YES, but the “features” should be in the public domain – value add “linked” to public domain • Other stakeholder: NGOs & academia Dan Widner • NSGIC wants to see people get together in a coordinated fashion. “Coordinated approach” • Leverage the VGI/crowdsourcing activities • Attributes: begin with the bare minimum attributes – addresses • We need to identify everyone’s “business needs”. Not about ownership, identify what people need. The following are questions asked/comments made by the audience and the panelists responses after the first panel finished • Volunteered Geographic Information (VGI), are there any “active plans” from panelists? Steve: reaching out to OSM. Randy: USGS had an external VGI conference, Census participated. Open questions “how do we control and incorporate”. • Gene Parcher, USGS: How do envision the states owning the standards? 50 potential standards? Ron: Feds would help the states arrive at a common standard. Reporting requirements can drive that. Steve: it doesn’t work for the Feds to dictate, need input on what states should provide. • Is basic routability part of the TFTN vision? Steve: we would like to see a complete, routable data set in the public domain. Randy: it would be difficult for the Feds to do it well. Especially the maintainability part. Bruce/CSI’s followup question: Distinction between “basic topology” (connectivity) vs. “fully routable” (turn restrictions)? Ron: Yes, we’re looking at basic topology. Steve/Randy: YES, basic topology. PRINTED: 1/29/2015 PAGE 2 OF 5 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE
  • 3. GIS-T Conference • CO-DOT: Concerns about VGI. Concerned about losing authoritative source and trust. The crowd isn’t already right. Dan: what is the definition of “authoritative source”. Different needs – finding a restaurant, get close; sending an ambulance, no margin for error. Nebraska: agrees with Lou/Co. What’s true and trustable? Randy: trust, but verify. How do you verify is the big question. Dan: we can’t be asleep – these technologies are catching on and we can’t be left behind. • Answer to VGI. There are editors from the public contributions. How soon is the data checked? A formal process for checking. • Kentucky Transportation: The public is willing to live with an imperfect world. We need to adapt to a faster turnover. Capture metadata on who collected the data. You can see trends on who provides quality. • VA-DOT: What does routable mean? What does roadway mean? What does network mean? What about a higher level standard like an ISO process? More standardized definitions? Steve: no such effort underway. But the standards could be part of this process. Randy: first need to identify the core features and attributes, then we move to the standard. Dan: we are behind, other are leading the way. We need to set the lead. Panel Discussion 2, the State Perspective Tamela Lang • What does it mean to me? Potentially more work without resources? Why can’t we use something that’s already been done? Why can’t we partner the private sector and work deals with them? • There’s less duplication in state govt. than people thought • Private sector: “data enhancers” • Public: error reporters • CO has statewide roads, we meet our HPMS requirements. HPMS is the starting point; build our LRS on top of that. Add bridges and accidents and addresses ON TOP of that. • Clarify – Transportation DATA for the Nation Skip Turner • TFTN is a consistent base map with common structure used across applications. All parts of the country – rurals have less quality in commercial products. • Cross jurisdictional – city-to-city; state-to-state; US-Canada • Public-private partnership models are workable. We will need to continue to charge for the special sauce. We have field geographers and do validation. • Willing to work with you to put the “geometry into the public domain”. Melanie Rippon Seigler • Melanie/VDOT: Federal, state, local “collaborative” • CL’s are the basis for LRS and routable • We need to think of multi-modal going forward • Feds should coordinate the standards development by states • States should educate and support local govts. • Other stakeholders, Mass Transit organizations • In VA state provides good orthos to support local govts • Keep the attributes simple • Census population can help prioritize data colllection. David Blackstone • Create it once, use it a bunch. Uses of centerlines have expanded over the years. Accidents, emergency response. It’s not just mileposts PRINTED: 1/29/2015 PAGE 3 OF 5 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE
  • 4. GIS-T Conference • Federal requirements = once/year; doesn’t work for local govt. need a more transactional model • Avoid a “top down” implementation • E911 can be a key ally • Other stakeholders US Postal Service The following are questions asked/comments made by the audience and the panelists responses after the second panel finished • Steve Lewis: States, would you submit a “complete road network”? Should we change the requirement? Melanie: we have it, we would provide it, but it needs to be a requirement that create a business need. Blackstone: NO, the attributes are extensive and need to be defined first. “Roughness tests” are expensive. Relax some attributes. Subsets, we could do it. • GA-DOT: Mandates get resources assigned to them. Can’t do something “for the good of the public”. How does TFTN work if there’s not strong internal state coordination? Blackstone: Be creative in finding the money. Tie-in to safety. Census spent $24M on improvements in OH. Spending $’s to locals is popular and politically workable. • VA: E911 and safety funds are key participants; homeland security funding. • LA-DOT: Emerging issue is to tie-in DHS and emergency managers. • LA-DOT: Google is now using NON commercial data. But the data seems degraded. What is the definition of acceptably accurate? Emergency managers have accuracy needs. Blackstone: The commercial providers and Google are asking for our data. Skip: New products LiDAR + panoramic cameras are being driven now. 3 cities will be available this summer. New York, Chicago and Los Angeles • Steve Lewis: Skip and Virginia, you have a partnership for HPMS? Is this a prototype for TFTN. Skip: Not identical products, but two parallel products that share geometry. VDOT doing daily updates. In MA, we did lots of QA that improved the geocode success >90%. These presentations can be found it under TFTN documents GIS-T 2010. TFTN Breakout Session Tidbits: • Bruce Spear of Cambridge Systems: Don’t necessarily need all HPMS attributes down to local level • Mark from FHWA asked about examples of TFTN-like approaches in other countries • Jean Archer of USGS: Is US unique? What is HPMS geometry • Ron: HPMS geometry is the state’s base network of road geometry that attributes can be attached to • Steve: What is the relationship of State GIS Coordinators with State DOT GIS Managers? • Randy: Leverage federal resources to create common core data set; start with roads; look at funding availability; TIGER is a good place to start; you can hook-on data to TIGER; Fairfax County example mentioned • Bruce: If a state DOT had better data, would Census use it? Emerging Issues Panel • Jim Mitchell/ Louisiana DOT: The National Map and a National Transportation Layer – is it part of the solution, or part of the problem? Where does the money come from? What are transportation networks used for (e.g. emergency management), and what do they need? - Put it in a map - Geocoding - Analysis • Costi/DHS IICD: HSIP data used by DHS and federal HIFLD community; states have access through HSIN, using iCAV • Data should be “Accurate, Authoritative, Accessible, Actionable, and Affordable” (the Five A’s) • Bruce Spear: Fundamentally, we need geometry and network topology, with addresses. PRINTED: 1/29/2015 PAGE 4 OF 5 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE
  • 5. GIS-T Conference • Randy: TIGER was tested against survey quality points, and has feature-level metadata • Mark from TeleAtlas: Update frequency may be important; TA offers quarterly updates, but some customers have trouble absorbing a new dataset every 3 months. • Randy: TIGER updating depends on funding to be determined by Congress via budget process PRINTED: 1/29/2015 PAGE 5 OF 5 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE
  • 6. GIS-T Conference • Randy: TIGER was tested against survey quality points, and has feature-level metadata • Mark from TeleAtlas: Update frequency may be important; TA offers quarterly updates, but some customers have trouble absorbing a new dataset every 3 months. • Randy: TIGER updating depends on funding to be determined by Congress via budget process PRINTED: 1/29/2015 PAGE 5 OF 5 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE