1. Automated Map Generation in Indianapolis Chuck Carufel, IndyGIS Joe LaCombe, Woolpert, Inc.

2. Background IndyGIS is comprised of 9 staff members supplemented by our GIS Services vendor, Woolpert. IndyGIS is a division within ISA which is the IT organization for The City of Indianapolis/Marion County serving approximately 6000 computing devices.

3. AME Automated Mapping Engine

4. Contributing Factors Staff time spent creating basic maps. Not a good use of talents. Last minute requests. Reduced staffing. User intimidation. Cartographic skills are rare. Map requests are often repeated.

5. Contributing Factors Cont… Create a more consistent look. Expand the use of GIS without the associated software & training costs. Three-year Strategic Plan “Geo-reporting Wizard” – Query based IndyProjects Bulletin Board – For Citizens

6. Initial Plan Two separate applications…. 1. Subscription service Maps published by GIS Staff 2. Map Wizard Replacement for ArcView3.x wizard very popular with users.

7. Convened focus groups of users from various areas. And Then……. Adjusted our Plans!

8. Revised Plan The users felt that the Map Wizard was much more important than published maps. Phase 1 Map Wizard Maintenance Application Automated Cleanup Service Phase 2 Tabular Reports Save Map Definitions Email Subscription Service

9. Key AME Points Database Driven Database Driven Map TemplatesMap Templates Layer AvailabilityLayer Availability Layers SymbologyLayers Symbology Report DefinitionsReport Definitions Attributes Query DefinitionAttributes Query Definition User RegistrationUser Registration Subscription DefinitionSubscription Definition Web-based Interface, (No Client Licensing) Web-based Interface, (No Client Licensing)

10. Key AME Points Cont…. ArcGIS Server Based Full ArcGIS Cartography Wizard Interface Saved Queries, Live Data Intranet Only Realization that the real benefit will result when we can present non-GIS based information spatially via transparent integrations.

11. Continuing On…. Overview of Interface Overview of Interface System Architecture – What’s happening behind the scenes? System Architecture – What’s happening behind the scenes? Future plans Future plans

12. Map Wizard Walkthrough

13. User Portal Login

14. Saved Map Definitions

15. Subscriptions

16. Add New Subscription

18. Add Subscription Recipients

19. How It Works……

20. Technology ASP.NET 1.1 ASP.NET 1.1 ArcGIS Server ArcGIS Server Database driven Database driven

21. System Architecture

22. Map Generation Process Flow

23. System Architecture – Phase 2

24. Challenges/Lessons Learned Learning curve – this was the first project of this magnitude and complexity using ArcGIS Server Learning curve – this was the first project of this magnitude and complexity using ArcGIS Server Performance of Map Export Performance of Map Export Complexity: Complexity: Database  Portal  Map outputDatabase  Portal  Map output Decreased front-end complexity is a product of increased back-end complexityDecreased front-end complexity is a product of increased back-end complexity

25. What’s Coming/Enhancements Basic migration to ArcGIS Server 9.2 environment Basic migration to ArcGIS Server 9.2 environment Eventual Enhancements: Eventual Enhancements: Migration of code to ArcGIS Server 9.2 Web ADFMigration of code to ArcGIS Server 9.2 Web ADF Migration to ASP.NET 2.0Migration to ASP.NET 2.0 Integration with new printing web service (Requirements being defined now).Integration with new printing web service (Requirements being defined now).

26. This Room, 1:45 Cheryl Spencer Joe Lacombe

27. Questions?

28. Thank You for Coming Today!