2010 Gist

501 views

Published on

A Presentation given at the 2010 National GIS Transportation Conference on ODOT District 2\'s data sharing and compatibility solutions.

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

  • Be the first to like this

No Downloads
Views
Total views
501
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

2010 Gist

  1. 1. GIS-T 2010 Building a Successful Geospatial Data Sharing Framework: A Ohio DOT Success Story
  2. 2. Ohio Department of Transportation District Two John Puente District 1 GIS Coordinator Planning Administrator ODOT District 2 GIS
  3. 3. Ohio Department of Transportation District Two Interoperability
  4. 4. Ohio Department of Transportation District Two <ul><li>District 2’s data sharing challenges </li></ul><ul><ul><li>Safe Software – Feature Manipulation Engine (FME) </li></ul></ul><ul><ul><ul><li>Solve data interoperability issues </li></ul></ul></ul><ul><ul><ul><li>Conflate data to district sources </li></ul></ul></ul><ul><ul><ul><li>Produce new products to enhance business functions </li></ul></ul></ul>District 2’s GIS Customers
  5. 5. Ohio Department of Transportation District Two <ul><li>What is the Location Based Response System (LBRS)? </li></ul><ul><ul><li>The LBRS is a County/State partnership that gathers accurate locational information on all roads and addresses in a county. The information is used to save lives and save taxpayer dollars by reducing redundant data collection activities. The information is web-based, and is therefore current for all stakeholders as agencies or local governments gather new information. </li></ul></ul>Current Non-LBRS Counties Ohio's Location Based Response System (LBRS)
  6. 6. Ohio Department of Transportation District Two <ul><li>Data Conflation </li></ul><ul><ul><li>Combining LBRS Counties vs. Non-LBRS Counties </li></ul></ul><ul><ul><li>8 Counties </li></ul></ul><ul><ul><li>5 LBRS Centerlines </li></ul></ul><ul><ul><li>3 With Different Centerline Formats </li></ul></ul><ul><ul><li>2 Different File Types </li></ul></ul><ul><ul><li>11,000 Miles of Roadway </li></ul></ul><ul><ul><ul><li>43% Currently Non-LBRS </li></ul></ul></ul>LBRS – Data Optimization and Conflation
  7. 7. Ohio Department of Transportation District Two <ul><li>Optimization </li></ul><ul><ul><li>Removed duplicate nodes. </li></ul></ul><ul><ul><li>Removed unnecessary attributes. </li></ul></ul><ul><ul><li>Joined centerlines with same attributes. </li></ul></ul><ul><ul><li>Output to enterprise spatial data framework. </li></ul></ul><ul><li>Data used for district web mapping application. </li></ul><ul><li>Also used for cartographic rendering. </li></ul><ul><li>Used anywhere a lightweight centerline is required. </li></ul><ul><li>Used to tie Operational data such as maintenance quadrants and snow plow routing. </li></ul>LBRS – Data Optimization for Internal Operations   Start End Percent Reduction Percent of Orgional Megabytes 80.2 8.7 89% 11% Elements 60501 16392 73% 27%
  8. 8. Ohio Department of Transportation District Two <ul><li>Sign information collected as part of the LBRS project. </li></ul><ul><ul><li>District operations require different attributes and a different storage format. </li></ul></ul><ul><ul><li>Data needed to be conflated into the existing spatial data framework. </li></ul></ul><ul><li>Data will feed the proposed work order management system. </li></ul><ul><li>Data is available for MPO’s cities and villages. </li></ul>LBRS – Sign Data Conflation
  9. 9. Ohio Department of Transportation District Two <ul><li>What is OSIP? </li></ul><ul><ul><li>The Ohio Statewide Imagery Program (OSIP) is a partnership between State, Local and Federal government agencies to develop high-resolution imagery and elevation data for the State of Ohio to benefit Geographic Information System users at all levels of government. </li></ul></ul><ul><li>OSIP Products </li></ul><ul><ul><li>1FT Color Orthophotography in GeoTIFF and MrSID format </li></ul></ul><ul><ul><li>2.5FT DEM in ArcInfo GRID and ASCII grid format, </li></ul></ul><ul><ul><li>2M LiDAR postings in LAS format </li></ul></ul><ul><ul><li>Optional </li></ul></ul><ul><ul><ul><li>6IN Color Orthophotography </li></ul></ul></ul><ul><ul><ul><li>2FT and 5FT contours </li></ul></ul></ul><ul><ul><ul><li>1M Color Infrared photography. </li></ul></ul></ul>Ohio Statewide Imagery Program (OSIP)
  10. 10. Ohio Department of Transportation District Two Spike Removal Williams County Williams County <ul><li>District wide DEM for general drainage for the whole district. </li></ul><ul><ul><li>Eliminate anomalies </li></ul></ul><ul><ul><li>Re-Sample DEM for efficient operations. </li></ul></ul><ul><li>Data is distributed internally and to external agencies. </li></ul><ul><li>Used for cartographic operations. </li></ul><ul><li>And for general drainage planning. </li></ul>OSIP – DEM Editing and Re-sampling
  11. 11. Ohio Department of Transportation District Two OSIP DEM NOAA DEM Used for Clipping Clipped NOAA Data Data Normalized Complete DEM <ul><li>Data used to complete district elevation model </li></ul><ul><li>Example of Interoperability </li></ul>OSIP – NOAA Bathymetry and OSIP DEM
  12. 12. Ohio Department of Transportation District Two OSIP – NOAA Bathymetry and OSIP DEM
  13. 13. Ohio Department of Transportation District Two LIDAR Points TIN Surface Aerial Cropped Aerial Draped in 3d PDF <ul><li>Project was to test FME LIDAR to 3D PDF functionally and to test the 3d PDF itself. </li></ul><ul><li>Site was SR 350 at the fort ancient historical site. </li></ul><ul><li>Final data was delivered to an archeologist working on the site. </li></ul>OSIP – LIDAR to 3D PDF
  14. 14. Ohio Department of Transportation District Two OSIP – LIDAR to 3D PDF
  15. 15. Ohio Department of Transportation District Two <ul><li>ODOT Enterprise Formats </li></ul><ul><ul><li>GeoMedia </li></ul></ul><ul><ul><li>MicroStation </li></ul></ul><ul><li>External Customers Formats </li></ul><ul><ul><li>ESRI </li></ul></ul><ul><ul><li>AutoCAD </li></ul></ul><ul><li>No fluid way of data exchange </li></ul><ul><li>Time wasted on troubleshooting and data editing to convert data. </li></ul><ul><li>Uncertainty on changes of standards by ODOT central office. </li></ul>CAD Interoperability
  16. 16. Ohio Department of Transportation District Two <ul><li>District needed to store its data in a non-proprietary database. </li></ul><ul><ul><li>Accessed in other software products. </li></ul></ul><ul><ul><ul><li>Web Viewers </li></ul></ul></ul><ul><ul><ul><li>Custom Reports </li></ul></ul></ul><ul><ul><ul><li>GPS Units </li></ul></ul></ul><ul><ul><ul><li>Custom Applications </li></ul></ul></ul><ul><li>Choose Safe Software’s FME application. </li></ul><ul><ul><li>Move proprietary cad formats to open sources </li></ul></ul><ul><ul><li>Insure the district can change no matter how standards change. </li></ul></ul>CAD Interoperability
  17. 17. Ohio Department of Transportation District Two <ul><li>Example of CAD interoperability. </li></ul><ul><li>CAD to GIS Software for high quality presentations. </li></ul><ul><li>Data is also in a portable document format. </li></ul><ul><ul><li>Easily distributive. </li></ul></ul><ul><ul><li>Optional security. </li></ul></ul><ul><ul><li>Compressed file size. </li></ul></ul><ul><ul><li>High resolution printing. </li></ul></ul><ul><ul><li>Industry standard. </li></ul></ul>CAD Interoperability - Court Exhibits And Public Presentations
  18. 18. Ohio Department of Transportation District Two <ul><li>Need for interoperability. </li></ul><ul><ul><li>Major New 21.46 miles of 4 lane divided highway. </li></ul></ul><ul><ul><li>167.6 million </li></ul></ul><ul><ul><li>3 projects </li></ul></ul><ul><ul><li>2 counties </li></ul></ul><ul><ul><li>Effecting several cities and villages. </li></ul></ul><ul><ul><li>Directly and indirectly impacting thousands of residents. </li></ul></ul><ul><li>Data extracted from CAD files and archived in the district’s spatial data framework. </li></ul><ul><li>Data delivered to several governmental agencies, public and consultants </li></ul>CAD Interoperability – US 24
  19. 19. Ohio Department of Transportation District Two <ul><li>ODOT Business Plan </li></ul><ul><li>Strategy #4: Investing where it counts. </li></ul><ul><ul><li>Develop sustainable revenue sources for the entire transportation system and balance investments that preserve and maintain existing assets with those that enhance system capacity. </li></ul></ul><ul><li>ODOT District 2 is a leader in asset management for several areas. </li></ul>Asset Management
  20. 20. Ohio Department of Transportation District Two <ul><li>Bridge data is frequently requested by the other governmental agencies. </li></ul><ul><li>Previous workflows consisted of several steps. </li></ul><ul><ul><li>Querying out the info from the database. </li></ul></ul><ul><ul><li>Loading it into a GIS platform. </li></ul></ul><ul><ul><li>Geocoding coordinates. </li></ul></ul><ul><ul><li>Exporting data multiple times for different formats. </li></ul></ul><ul><li>With FME a workspace was created which reads directly from the production databases. </li></ul><ul><li>Now the only thing that needs done is a quick command line that runs the workspace. </li></ul><ul><ul><li>Automatically outputs both a shapefile and a excel document. </li></ul></ul>Bridge Asset Data
  21. 21. Ohio Department of Transportation District Two <ul><li>District 2 currently has 3 applications for asset management. </li></ul><ul><ul><li>Video Log Application </li></ul></ul><ul><ul><li>Web mapping Application </li></ul></ul><ul><ul><li>GPS Application </li></ul></ul><ul><li>Each reads from the same database. </li></ul><ul><li>When data is updated each application reflects the changes instantly. </li></ul>Geospatial Asset Data Management
  22. 22. Ohio Department of Transportation District Two Web Map Video Log GPS Asset Applications – Video Log
  23. 23. Ohio Department of Transportation District Two <ul><li>Current </li></ul><ul><ul><li>With advanced interoperability software ODOT district 2 is able to deal with the ever changing GIS technology. </li></ul></ul><ul><ul><li>Conflate different standards. </li></ul></ul><ul><ul><li>Retain the enterprise data formats. </li></ul></ul><ul><ul><li>Supply its customers with the format they require for their system. </li></ul></ul><ul><ul><li>Automate tasks that would have taken much more time to complete. </li></ul></ul><ul><li>Future </li></ul><ul><ul><li>Use FME Server to allow our end-users to upload or download any format they require from a web based form. </li></ul></ul><ul><ul><li>Implement ARCServer and publish services for frequent requests. </li></ul></ul>Conclusion
  24. 24. Ohio Department of Transportation District Two Contact Info Fred Judson, GISP ODOT GIS Coordinator [email_address] Thank You Questions

×