280 likes | 297 Views
Learn about the implementation of the Automated Mapping Engine (AME) in IndyGIS, a division within ISA that serves the City of Indianapolis/Marion County. Discover the contributing factors, key points, and future plans for this map generation system.
E N D
Automated Map Generation in Indianapolis Chuck Carufel, IndyGIS Joe LaCombe, Woolpert, Inc.
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.
AME Automated Mapping Engine
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.
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
Initial Plan Two separate applications…. Subscription service Maps published by GIS Staff Map Wizard Replacement for ArcView3.x wizard very popular with users.
Convened focus groups of users from various areas. And Then……. Adjusted our Plans!
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
Key AME Points Database Driven Map Templates Layer Availability Layers Symbology Report Definitions Attributes Query Definition User Registration Subscription Definition Web-based Interface, (No Client Licensing)
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.
Continuing On…. Overview of Interface System Architecture – What’s happening behind the scenes? Future plans
Technology ASP.NET 1.1 ArcGIS Server Database driven
Challenges/Lessons Learned Learning curve – this was the first project of this magnitude and complexity using ArcGIS Server Performance of Map Export Complexity: Database Portal Map output Decreased front-end complexity is a product of increased back-end complexity
What’s Coming/Enhancements Basic migration to ArcGIS Server 9.2 environment Eventual Enhancements: Migration of code to ArcGIS Server 9.2 Web ADF Migration to ASP.NET 2.0 Integration with new printing web service (Requirements being defined now).
This Room, 1:45 Cheryl Spencer Joe Lacombe