s p a t i a l  i n f o r m a t i o n  s y s t e m s © GeoAnalytics, Inc – All Rights Reserved Technical Aspects: Wisconsin Historical Society GIS Project March 2002 WLIA 2002 Annual Conference Presented by: Anita Temple Team Members: Puneet Kishor and Jim Cory

Presentation Outline  Project Background and Scope  Situation at Project Start  Changes to New System  Application Details  Technical and Non-technical Lessons

Acknowledgements  Wisconsin Department of Transportation  Staff members of WHS – especially  Bob Birmingham, John Broihahn, and LTE’s  Jim Draeger, Joe DeRose, Brad Schwarzhoff  Rick Dexter, Dan Duchow, and Compliance Reviewers  Maggie Buck, GIS Coordinator  WDOA, Office of Land Information Services

Project Background and Scope  WHS founded in  Mandate –collect, maintain, manage and disseminate archaeological and historical data in Wisconsin.  This project – One division, three sections.  Archaeology  Survey and Registration  Compliance  Project started Fall Completed December 2001.

Project Background and Scope  Goals of Project – modernize!  Migrate data to a new system  Create spatial data  Create web-based applications for all (data viewers and editors)  Easy access to all data via a web browser  Visual display and maps of data via the web applications  Online decision support for Compliance reviews  More options for data distribution

In the Beginning  Paradox on PCs  DOS or Windows 3.1 versions  Four separate databases, few links  AHI (Architectural Historical Inventory)  ASI (Archeological Site Inventory)  BAR (Bibliography of Archeological Reports)  Compliance (a tracking database)  Four applications by different developers, dates, functions, and levels of robustness  No Spatial data  Arch sites and survey data drawn on USGS hardcopy quads  No digital spatial representation of architectural sites

In the Beginning  Hardcopy data galore!  In the basement  Upstairs in several file places  Staff – “techno-peasants”  What is GIS?  How to digitize?  What is a web-based application?

But…Change Had to Happen Because  Heavy workload on a few staff due to compliance review mandates  Inefficient or difficult access to data – time!  Paradox database crashes  No spatial data for visualization, maps, analysis, etc.  Pending budget cuts against all resources (and now…even worse!)

The Changes  Acquisition of software and hardware.  Oracle  ESRI product suite: Arc 8, ArcView 3.2, ArcIMS, ArcSDE  MacroMedia Cold Fusion  New servers, PCs, monitors, etc.  Spatial data creation.  Archaeological, Survey, and Burial sites captured as heads-up digitizing in ArcView  Geocoding Architectural sites with QMS to point locations

The Changes  Databases migrate to:  Oracle 8.2  Four schemas, one for each application + an additional schema for common data  Share lookup tables, location (PLSS) tables  Significant data scrubbing  Changes in field values and definitions

Application Development  Four applications for business needs including a map component.  Web browser  Cold Fusion programming  Oracle connect  ArcIMS via CF connector  Administrator module for user access permissions.

Admin Module

Entry into System

Search Functions  Each application has simple and advanced search options that are customized to the business needs.  ASI have PLSS, County, Muni, Site#, etc. (BAR is similar).  AHI has Address (e.g. 707 Main) as well as County, municipality, etc.  Compliance has project lead, project number, project name, Street address, County, PLSS.

Search Functions

Search Results

Viewing Records

Data Updates

Mapping Functions

Specialized Features  Complex queries / searches.  Organized information into ‘tab’ screens.  Within each tab, information is organized logically for updates / edits.  Map application allows browsing to another nearby site and when new site is selected, record is refreshed to that information.

Specialized Features - Compliance  Compliance – not like the others – is a tracking application.  Contact list  Reviewer list  Correspondence list  Search related records in ASI and AHI  Search proposed project area visually via map tab  Status tracking of review process  Generates form letters

Specialized Features – Related Records

Related Records Map

Tracking Options

Technical Lessons  Versions of software are important for functions and compatibility issues.  CF 4.5 versus 5.0  ArcIMS 3.0 and 3.1  IE and Netscape  Prescribe minimum technology and user experience requirements for the applications.

Technical Lessons  One application cannot serve all user needs or levels of experience.  Browsers of data versus editors of data  Data analysts  Reuse Code! The use of custom tags and functions.

Technical Lessons  Application development should be iterative, not sequential.  Changes / discoveries in the 4 th application can cycle back to the 1 st application.  Testing of applications should be done by all, even those outside of the business area.

Non-technical Lessons  Process changes can be difficult.  From a personal data entry method to another  Work flow of data  Understanding the new system  User needs change as more becomes possible with technology.  User needs change as staff become educated on the new system  Expectations change over time.

Outcomes  for WHS –  State-of-the-art database and work applications.  Integrated system.  Access to all data to all staff resulting in increased efficiencies (especially to compliance).  Capability for remote staff access to data.  Map-making capabilities.  for WDOT & other agencies– web access to generalized data for a first “cut” with compliance reviews.

s p a t i a l  i n f o r m a t i o n  s y s t e m s © GeoAnalytics, Inc – All Rights Reserved March 2002 Madison, WisconsinWest Palm Beach, FloridaChicago, Illinois Anita Temple or Puneet Kishor GeoAnalytics, Inc Fordem Avenue Madison, WI Phone: Fax: or Web: