ESRI has recently released ArcGIS 9.2 and many of our clients have begun the migration from legacy systems to ArcGIS. It is imperative that the data transition be seamless to both the public and other departments who access the GIS. For example, many of our clients post this information via the Internet or public kiosks. We have provided assistance during the entire process from maintenance activities to public access. EI Technologies has developed Cartographic Editing and Map Production System (CAMPS) to meet this seamless transition need. This custom built application provides an easy to understand and reliable product that migrates coverages and shapefiles to the geodatabase in an efficient and timely manner. It has been designed to integrate easily with the existing core editing and importing functions of ArcMap.

The CAMPS Object Loader module will allow the user to import multiple coverages, or shapefiles or CAD drawings directly into the geodatabase (thus ensuring database compliance and placement). Each layer will be carefully mapped to it’s GIS counter part based upon the snapping, domain constraints, custom queries, validation, subtype, and field mapping properties. Although the ESRI Object Loader offers the same functionality, CAMPS includes additional tools that provide the user with enhanced property definitions. The table below displays the differences between the ESRI Object Loader and the CAMPS Object Loader.

*Function*	*ESRI Object Loader*	*CAMPS Object Loader*
Snapping	a	a
Field Mapping	a	a
Populate by Domain Values		a
Query Builder	a	a
Single Couplet	a	a
Multiple Couplets		a
Change Properties On-The-Fly		a
Verification of Profile		a
Save Profile Properties		a
Loading Existing Profile		a
Load Based on Subtypes		a
Create Log File		a
Confirm Validation Properties	a	a

The user can monitor the migration process via a log file and save these parameters in a profile. The profile can then be run to transfer the data directly into the geodatabase on a regular basis. Many of our current clients create these profiles and then run them during the evening so that the new GIS data is ready first thing the following workday. Depending on the client’s situation, some profiles are only run once and some are run on a weekly basis. One profile can include several different “couplets”. For example, the user can identify parcels, zoning, and utility information in one profile. Each can have separate snapping and domain values specified and the order in which the user can also set which will be run first.