Your SlideShare is downloading. ×
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

280

Published on

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

  • Be the first to like this

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

×