PENNDOT Generic Mapping Interface (GMI) Project

1. PENNDOT Generic MappingInterface (GMI) Project Enhancing the Enterprise Through GIS Web Services Joe McGinnes, PENNDOT Manager, Geographic Information Division Jim Knudson, GeoDecisions Sr. Development Manager, PENNDOT Project Manager

2. Presentation • Project Background • GMI Components • Project Details • Demonstration • Wrap-Up

3. Project Background

4. What is GMI? A Restructured Architecture To Integrate Applications • Modified web applications to easily step between each other • Redesigned Intranet web pages to highlight an application suite • Extend architecture concepts to new applications • Expand enterprise developers’ visualization toolbox • Support PENNDOT’s “Legacy System Integration Strategy” (LSIS) • Initiated implementation in 2002

5. GIS At PENNDOT • Twelve years of progressive development • Two strategic plans • On-site agency / contractor partnership • Intergraph / Bentley / Oracle platform • Only legacy system integrator at PENNDOT • Dedicated IT shop/IT Service provider • Current Enterprise focus: • Spatial Database/LRS Enhancements • Web deployment of applications • Visualization Tools

6. Application Development • Desktop • Custom applications (e.g., TMS, SIMOS) • Enterprise utilities (e.g., GIS 2000) • Web Services • Custom applications (e.g., CRS, MPMS) • Enterprise utilities (e.g., intranet suite) • TMS Presentation is Tuesday, 3:30 PM, Session 5.4.3

7. GMI Components

8. Redesigned Intranet Web Pages

9. GIS Interactive Query Bridge Analysis and Permitting using Digital Terrain Modeling Presentation is Wednesday, 10 AM, Session 7.2.1

10. Segment Location Information Query

11. MPMSMaps

12. Interactive Straight Line Environment

13. As-Builts AsBuilt Presentation is Tuesday, 1:30 PM, Session 4.3.1

14. VideoLog v.2

15. Data Dictionary

16. GMI Project Details

17. GMI Conception • Integrate all GID web applications developed to date • Establish an enterprise black-box architecture for GIS and other visualization/application services provided by BPR/GID • Enable other developers to use GID tools without understanding GIS or location referencing systems or web programming

18. STEP ONE – Define GMI Requirements • Create an attractive and functional User Interface for each Web visualization application to enhance application navigation and usability • Add ability to call other applications and view the same location as selected in current application • LRS key gateway – location is standard reference for highways and bridges to bypass ‘Front-End’ (e.g. County, SR, Segment Number) • Standardize all GMI applications query string parameters on LRS key values

19. STEP TWO – Interface and Application Changes • Each application must maintain knowledge of the user’s selected LRS location for GMI to work • Modify each application to add buttons for calling other visualization web services • When a roadway segment is selected, build proper query string and display/enable buttons • When application button is pressed, open a new browser window and step into the new application • Redesign GID Intranet home page to showcase new integrated suite of applications

20. STEP THREE – Documentation • Documentation is the key to application integration and utilization across the enterprise • Documentation initially created as a Word document • Documentation Components • Application description • Interface definition – server, URL • Query string parameters – format, content • Source code examples (VB, ASP) • Eventually will have a GMI page on BPR intranet web site

21. VideoLog Source Code Documentation Example Videolog – Calling application provides County, Route and Segment. Videolog application opens and jumps to RMS segment. Shows videolog images at beginning of segment The syntax for accessing the url is as follows: http://164.156.155.62/vidlog/default.asp?cn=CC&rt=RRRR&sg=SSSS where CC = 2 character PENNDOT county code where RRRR = 4 character PENNDOT Route where SSSS = 4 character PENNDOT Segment identifier For example to view Segment 0490 on Route 0022 in County 22... http://164.156.155.62/vidlog/default.asp?cn=22&rt=0022&sg=0490

22. GMI Architecture Proof • Desktop: Traffic Monitoring System (TMS) - Visual Basic – first desktop application to use GMI • Web: VideoLog Application - Active Server Pages (ASP) – when version 2 was developed in 2002, integrated ISLE, GIS Interactive Query • Mainframe: Bridge Management System (BMS) - PC3270 screen scrape macro developed to demonstrate GMI VideoLog capabilities for LSIS • All application development environments can potentially use GMI application services

23. DEMONSTRATION

24. Wrap-Up

25. GMI Benefits • Facilitates expansion of web services • Enables future integration ease • Enhances the user experience • Provides expanded capabilities for analysis and visualization • Expands functionality of existing applications • Provides GIS-illiterate developers with access to existing, high-level visualization web services • Supports PENNDOT’s Legacy System Integration Strategy by providing videolog and LRS services across the enterprise

26. What’s Next • Integration with EDMS (FileNet) • Address non-highway (alternate LRS) applications • Consider geocoding / reverse geocoding applications • Enable alternative map output formats • Expand interactive GIS on the Internet • Enhance documentation • Develop marketing and education strategies

27. PRESENTERS Joe McGinnes, PENNDOT Manager, Geographic Information Division Jmcginnes@state.pa.us (717) 787-3200 Jim Knudson, GeoDecisions Sr. Development Manager, PENNDOT Project Manager Jknudson@geodecisions.com (717) 772-0567

28. Q & A