Your SlideShare is downloading. ×
0
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Federal roads mtg  trans survey-results 9
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Federal roads mtg trans survey-results 9

208

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
208
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Geospatial Transportation Data Needs for Federal Agencies Results of the Questionnaire Tim Trainor, U.S. Census Bureau October 19, 2009
  • 2. Responses by Organization <ul><li>Departments of : </li></ul><ul><li>Agriculture </li></ul><ul><li>Commerce </li></ul><ul><li>Defense </li></ul><ul><li>Energy </li></ul><ul><li>Departments of : </li></ul><ul><li>Housing and Urban Development </li></ul><ul><li>Interior </li></ul><ul><li>Transportation </li></ul><ul><ul><ul><li>Office of the Secretary of Defense </li></ul></ul></ul><ul><ul><ul><li>Library of Congress </li></ul></ul></ul><ul><ul><ul><li>Environmental Protection Agency </li></ul></ul></ul>
  • 3. Agencies Responding by Department <ul><li>Farm Service Agency </li></ul><ul><li>Forest Service </li></ul><ul><li>Natural Resources Conservation Service </li></ul><ul><li>Census Bureau </li></ul><ul><li>National Geospatial- Intelligence Agency </li></ul><ul><li>Oak Ridge National Laboratory </li></ul><ul><li>Housing and Urban Development </li></ul><ul><li>Bureau of Land Management </li></ul><ul><li>Bureau of Reclamation </li></ul><ul><li>Fish and Wildlife Service </li></ul><ul><li>US Geological Survey </li></ul><ul><li>Federal Highway Administration </li></ul><ul><li>Environmental Protection Agency </li></ul><ul><li>Library of Congress </li></ul><ul><li>Office of the Secretary of Defense </li></ul>
  • 4. Question 1 - Briefly describe your agency’s greatest issue with geospatial transportation data <ul><li>Public domain restrictions </li></ul><ul><li>Lack of current data </li></ul><ul><li>Lack of feature level metadata </li></ul><ul><li>Duplication of effort </li></ul><ul><li>Lack of data in rural areas </li></ul><ul><li>Maintenance </li></ul><ul><li>Priority of corrections </li></ul><ul><li>Incomplete features and attributes </li></ul><ul><li>Establishing the authoritative source </li></ul>
  • 5. Question 1 continued <ul><li>Adhering to security requirements in a collaborative environment </li></ul><ul><li>Data volume </li></ul><ul><li>Inaccurate address ranges </li></ul><ul><li>Lack of agency specific attributes </li></ul><ul><li>Internal data not centralized </li></ul><ul><li>Need rail, air, and cargo </li></ul>
  • 6. Question 4 - Summarize other needs such as accuracy requirements, update frequency, and consistency of data quality <ul><li>Update frequency: </li></ul><ul><ul><li>3 months </li></ul></ul><ul><ul><li>6 months </li></ul></ul><ul><ul><li>1 year </li></ul></ul><ul><ul><li>2 years </li></ul></ul><ul><ul><li>5 years </li></ul></ul><ul><li>Accuracy requirements: </li></ul><ul><ul><li>engineering quality </li></ul></ul><ul><ul><li>1 ft </li></ul></ul><ul><ul><li>7.6 meters CE 95 </li></ul></ul><ul><ul><li>10 meters </li></ul></ul><ul><ul><li>1:24,000 meeting National Map Accuracy Standards </li></ul></ul>
  • 7. Question 4 continued <ul><li>Accuracy in rural areas </li></ul><ul><li>Alignment with NAIP imagery </li></ul><ul><li>Planned roads </li></ul><ul><li>Consistent and seamless features and attributes </li></ul><ul><li>Direction and turn restrictions </li></ul><ul><li>Accurate address ranges </li></ul><ul><li>Governmental unit and ZIP Code information </li></ul><ul><li>Up-to-date Metadata </li></ul><ul><li>Ongoing updates </li></ul><ul><li>Vertical offsets for over/under passes </li></ul><ul><li>Linear reference system </li></ul>
  • 8. Question 5 - What is the source of your geospatial transportation data today <ul><li>NAVTEQ </li></ul><ul><li>Census Bureau TIGER/Line </li></ul><ul><li>Local data </li></ul><ul><li>NAIP imagery </li></ul><ul><li>Federal and State DOT </li></ul><ul><li>Tele Atlas </li></ul><ul><li>In-house </li></ul><ul><li>USGS topographic maps </li></ul><ul><li>Field updates </li></ul><ul><li>GPS sources </li></ul><ul><li>Federal Rail Administration </li></ul><ul><li>Federal land management agencies </li></ul>
  • 9. Question 6 - Provide a brief description or a bulleted list of your Agency’s applications that require transportation data <ul><ul><li>Web-based viewer </li></ul></ul><ul><ul><li>Web map service </li></ul></ul><ul><ul><li>Engineering design </li></ul></ul><ul><ul><li>Planning </li></ul></ul><ul><ul><li>Assessment </li></ul></ul><ul><ul><li>Inventory </li></ul></ul><ul><ul><li>Maintenance </li></ul></ul><ul><ul><li>Base maps </li></ul></ul><ul><ul><li>Presentation maps </li></ul></ul><ul><ul><li>Census, surveys </li></ul></ul><ul><ul><li>Evaluating access </li></ul></ul><ul><ul><li>Geocoding </li></ul></ul><ul><ul><li>Emergency response </li></ul></ul><ul><ul><li>Navigation/routing </li></ul></ul><ul><ul><li>Compliance monitoring </li></ul></ul><ul><ul><li>Administrative support </li></ul></ul>
  • 10. Question 7 – Additional Comments <ul><li>Utilize existing interagency trails data standard </li></ul><ul><li>Consider existing proposals </li></ul><ul><li>Align transportation planning efforts with land-use and ecological reference data </li></ul><ul><li>Integrate geospatial data into a &amp;quot;knowledge network framework” </li></ul><ul><li>Consider update access by trusted data stewards at the state or local level </li></ul><ul><li>Analyze the requirement and level of support for data access in the public domain </li></ul>
  • 11. Answer Commonalities for Questions 1, 4, 5, 6, 7 <ul><li>Data sources include public and private </li></ul><ul><li>Public data sources include federal, tribal, state, county, and local </li></ul><ul><li>Most agencies utilize more than one source of data </li></ul><ul><li>Desire to have public domain data meet agency needs </li></ul>
  • 12. Answer Differences for Questions 1, 4, 5, 6, 7 <ul><li>Level of accuracy </li></ul><ul><li>Measure of accuracy </li></ul><ul><li>Frequency of updates </li></ul>
  • 13. Survey Results for Features <ul><li>Features </li></ul><ul><ul><li>Required </li></ul></ul><ul><ul><li>Desirable </li></ul></ul><ul><ul><li>Not Required </li></ul></ul><ul><ul><li>Public Domain Requirement, Yes </li></ul></ul><ul><ul><li>Public Domain Requirement, No </li></ul></ul><ul><ul><li>Note: 17 respondents to Requirement column </li></ul></ul><ul><ul><li> 16 respondents to Public Domain column </li></ul></ul><ul><ul><li>Note: Public Domain Y or N for “Not required” feature considered not applicable </li></ul></ul>
  • 14. Features Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Local streets and roads 13, 4, 0 15, 1, 0 Secondary highways 17, 0, 0 15, 1, 0 Major highways (non interstates) 16, 1, 0 15, 1, 0 Interstates 17, 0, 0 15, 1, 0 Entry / Exit ramps 10, 6, 1 13, 2, 1
  • 15. Features Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Road Bridges/Culverts 11, 5, 1 14, 1, 1 Road Tunnels 9, 6, 2 13, 1, 2 Unpaved Roads 9, 5, 3 12, 1, 3 Under/Overpasses 8, 7, 2 13, 1, 2 Private streets and alleys 4, 10, 3 9, 4, 3
  • 16. Features Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Other Federal Lands Roads (specify: National Forest Roads, National Park Roads, etc.) 13, 2, 2 12, 2, 2 Other private land roads 5, 9, 3 9, 4, 3 Cul-de-sacs 3, 12, 2 13, 1, 2 Trails and bicycle paths 7, 8, 2 12, 2, 2
  • 17. Features Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Rail 12, 4, 1 14, 1, 1 Waterways 11, 4, 2 13, 1, 2 Runways/Airports 8, 6, 3 12, 1, 3 Exits 8, 7, 2 13, 1, 2 Rest Areas 5, 6, 6 9, 1, 6
  • 18. Features Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Toll plazas 5, 5, 7 8, 1, 7 Truck stops 3, 7, 7 8, 1, 7 Weigh Stations 5, 5, 7 8, 1, 7 Mile Posts 9, 6, 2 13, 1, 2 Mass Transit station/stop 5, 6, 6 9, 1, 6
  • 19. Features Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Park and Ride 2, 8, 7 8, 1, 7 Recreation site 6, 6, 5 10, 1, 5 Fill in Additional Features if necessary: Road Medians 0, 1, 0 1, 0, 0 Aerial Photography 0, 1 ,0 1, 0, 0
  • 20. Feature Survey Response Commonalities <ul><li>Mostly all indicate requirement for public domain data </li></ul><ul><li>Mostly all require (10 or more indicated R): </li></ul><ul><ul><li>Local streets and roads </li></ul></ul><ul><ul><li>Secondary highways </li></ul></ul><ul><ul><li>Major highways (non-interstates) </li></ul></ul><ul><ul><li>Interstates </li></ul></ul><ul><ul><li>Entry/Exit ramps </li></ul></ul><ul><ul><li>Road Bridges/Culverts </li></ul></ul><ul><ul><li>Other Federal Lands Roads </li></ul></ul><ul><ul><li>Rail </li></ul></ul><ul><ul><li>Waterways </li></ul></ul>
  • 21. Feature Survey Response Commonalities continued <ul><li>More than one indicate no public domain requirement for: </li></ul><ul><ul><li>Private streets and alleys </li></ul></ul><ul><ul><li>Other private land roads </li></ul></ul><ul><ul><li>Federal lands roads (for military bases) </li></ul></ul>
  • 22. Feature Survey Response Differences <ul><li>Most varied ratings on: </li></ul><ul><ul><li>Rest areas </li></ul></ul><ul><ul><li>Toll plazas </li></ul></ul><ul><ul><li>Truck stops </li></ul></ul><ul><ul><li>Weigh Stations </li></ul></ul><ul><ul><li>Park and Ride </li></ul></ul><ul><ul><li>Recreation site </li></ul></ul>
  • 23. Survey Results for Attributes <ul><li>Attributes </li></ul><ul><ul><li>Required </li></ul></ul><ul><ul><li>Desirable </li></ul></ul><ul><ul><li>Not Required </li></ul></ul><ul><ul><li>Public Domain Requirement - Yes </li></ul></ul><ul><ul><li>Public Domain Requirement – No </li></ul></ul><ul><ul><li>Note: 17 respondents to Requirement column </li></ul></ul><ul><ul><li>16 respondents to Public Domain column </li></ul></ul><ul><ul><li>Note: Public Domain Y or N for “Not required” attribute considered not applicable </li></ul></ul>
  • 24. Attributes Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Names 14, 2, 1 13, 2, 1 Address Ranges 11, 4, 2 13, 1, 2 Address Points 10, 5, 2 12, 2, 2 Directional Routing Information 11, 3, 3 12, 1, 3 Linear Referencing 10, 5, 2 13, 1, 2
  • 25. Attributes Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Functional Classification (HPMS schema) 11, 5, 1 14, 1, 1 Administrative Classification 9, 6, 2 11, 3, 2 Pavement Types 8, 7, 2 12, 2, 2 Speed Limits 5, 6, 6 9, 1, 6
  • 26. Attributes Requirement for agency needs (R, D, N) Requirement to be in the Public Domain (Y, N, n/a) Fill in Additional Features if necessary: All signed routes 1, 0, 0 1, 0, 0 Road condition 0, 1, 0 0, 1, 0 Safety index 0, 1, 0 0, 1, 0 Bridge condition 0, 1, 0 0, 1, 0
  • 27. Attribute Survey Response Commonalities <ul><li>Mostly all indicate requirement for public domain data </li></ul><ul><li>Mostly all require (10 or more indicated R): </li></ul><ul><ul><li>Names </li></ul></ul><ul><ul><li>Address ranges </li></ul></ul><ul><ul><li>Address points </li></ul></ul><ul><ul><li>Directional routing information </li></ul></ul><ul><ul><li>Linear referencing </li></ul></ul><ul><ul><li>Functional Classification (HPMS schema) </li></ul></ul>
  • 28. Attribute Survey Response Commonalities continued <ul><li>More than one indicate no public domain requirement for: </li></ul><ul><ul><li>Names </li></ul></ul><ul><ul><li>Address points </li></ul></ul><ul><ul><li>Administrative classifications </li></ul></ul><ul><ul><li>Pavement types </li></ul></ul>
  • 29. Attribute Survey Response Differences <ul><li>Most varied response on </li></ul><ul><ul><li>Speed limits </li></ul></ul>
  • 30. Questions?

×