The document reports the results of a questionnaire given to various federal agencies regarding their geospatial transportation data needs. Most agencies cited a lack of current, complete, and accurate public domain data as a key issue. Common data sources included Census Bureau, state and local governments. Many applications require features like roads, bridges, and railroads. Attributes like names and routing were also important. However, needs varied between agencies, especially regarding update frequency, accuracy standards, and whether certain attributes should be public.
Integrating Regional Spatial Information with FMESafe Software
The North Central All-Hazards Emergency Management Region (NCR) for the State of Colorado contracted Critigen to develop a web-based GIS data portal where the ten NCR member counties could upload their spatial data to populate one common GIS database. Using a customized FME Server interface, users can upload spatial data and have it automatically translated into a common data model. Counties and other jurisdictions also reap the benefits when they download user-defined subsets of data for their own use into their own data schema. Additionally, the composite database supports an emergency preparedness planning tool, providing first response planners access to a continuous, region-wide dataset. In this session, you will learn how Critigen overcame the challenges faced in completing this project and will be given a view into the proposed next steps and potential applications beyond this effort.
Using Utah's Linear Referencing GIS Layer: SGID93.Transportation.UDOTRoutes_LRSBert Granberg
Slides from UGIC 2011 conference in Logan (April 2011).
First half of slides (Bert Granberg AGRC) discuss what, why and how of the LRS dataset created by AGRC and UDOT to represent state and federal routes in Utah in a polylineM format.
Second half (Thomas McMurtry, Interplan) shows use cases where tabular data on traffic volume, accidents, projects, etc was linked to the GIS representation of the LRS for map display and query
Leptonmaps supplies RF Maps, RF Network Planning, RF Planning, RF Network planning Maps for different cities and countries which makes rf map planning easy.
Geospatial Native Title Information: Reality, not a DreamSteven James
Why should it be hard to share geospatial native title information? The focus of this presentation will be to highlight geospatial information sharing initiatives which been flourished in the native title landscape and the reasons for their success
Integrating Regional Spatial Information with FMESafe Software
The North Central All-Hazards Emergency Management Region (NCR) for the State of Colorado contracted Critigen to develop a web-based GIS data portal where the ten NCR member counties could upload their spatial data to populate one common GIS database. Using a customized FME Server interface, users can upload spatial data and have it automatically translated into a common data model. Counties and other jurisdictions also reap the benefits when they download user-defined subsets of data for their own use into their own data schema. Additionally, the composite database supports an emergency preparedness planning tool, providing first response planners access to a continuous, region-wide dataset. In this session, you will learn how Critigen overcame the challenges faced in completing this project and will be given a view into the proposed next steps and potential applications beyond this effort.
Using Utah's Linear Referencing GIS Layer: SGID93.Transportation.UDOTRoutes_LRSBert Granberg
Slides from UGIC 2011 conference in Logan (April 2011).
First half of slides (Bert Granberg AGRC) discuss what, why and how of the LRS dataset created by AGRC and UDOT to represent state and federal routes in Utah in a polylineM format.
Second half (Thomas McMurtry, Interplan) shows use cases where tabular data on traffic volume, accidents, projects, etc was linked to the GIS representation of the LRS for map display and query
Leptonmaps supplies RF Maps, RF Network Planning, RF Planning, RF Network planning Maps for different cities and countries which makes rf map planning easy.
Geospatial Native Title Information: Reality, not a DreamSteven James
Why should it be hard to share geospatial native title information? The focus of this presentation will be to highlight geospatial information sharing initiatives which been flourished in the native title landscape and the reasons for their success
Posting travel times on dms webinar 042711raymurphy9533
The following Transportation agencies, Idaho Transportation Department (ITD), North Carolina Department of Transportation (NCDOT), Illinois Department of Transportation (IDOT) and Maryland State Highway Administration (M-SHA) will share lessons learned and best practices regarding Travel Time (TT) posting on Dynamic Message Signs (DMS) and the use of third party data services.
The webinar covered DMS Operations and:
• POLICIES…
• POSTINGS…
• UPDATES…
• WORK ZONES…
• VARIABLE SPEED LIMITS…
• PARTNERSHIPS: with Law Enforcement, TIM, etc…
• DATA RELIABILITY: data testing/history/accuracy…
• PUBLIC OUTREACH/MEDIA: customer feedback…
• MAINTAINING ASSETS: investment, financial aspects…
• EQUIPMENT: portable & fixed, characters, placement, detection…
.
1. Geospatial Transportation Data Needs for Federal Agencies Results of the Questionnaire Tim Trainor, U.S. Census Bureau October 19, 2009
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
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.
21.
22.
23.
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