Presentation on theme: "Migrating a County Government to Geodatabase Editing"— Presentation transcript:
1 Migrating a County Government to Geodatabase Editing Shannon PorterJohnson County AIMS
2 AbstractJohnson County AIMS (Automated Information Mapping System) is the GIS department in the third fastest growing county in the nation and the largest county in Kansas. The department, originally started in 1986, has a significant code investment in AML, Avenue, and MapObjects for the purpose of data maintenance and quality control.
3 Abstract (Cont.)In order to utilize many of the new advances in ArcSDE and ArcGIS, AIMS realized it needed to expedite its transition from coverage to geodatabase editing and replace current editing applications. This paper identifies not only the issues and problems AIMS faced, but the solutions, workarounds, and best practices that AIMS has discovered in the process of this transition.
4 Preparations Inventory geographic data and required formats Inventory editing routinesInventory applications that consume geographic dataIdentify frequency of dataset updateReview naming for standardization
6 Milestones Load data into SDE environment Determine Order of Coverages to MigrateDevelop Editing ProceduresDetermine Publishing MechanismDevelop Publishing Procedures
7 1. Load data into SDE environment Load proceduresArcCatalog - manualSDE Administration CommandsDoes not register with the geodatabaseArcObjectsReloadingDynamic dataSlow
8 2. Order of Coverages to Migrate Actively Edited Point FilesGolfHole_PTSchool_PTCntyFuel_PTCntyOffice_PTFireStation_PTGovtOffice_PTHospital _PTHotel_PTLibrary_PTMedActStation_PTNursingHome_PTPoliceStation_PTPostOffice_PTShelter_PTSiren_PTATM_PTConvenienceStore_PTRestaurant_PTTowers_PT
9 2. Order of Coverages to Migrate Other Actively Edited Files Without AnnotationCerizip_PLFireDist_PLSherDist_PLSubParcZoning_PLZip_PLWatershed_PLGolfFairway_PLElectricServiceArea_PLGasServiceArea_PLNpmsPipe_LNWaterDist_PLWilliamsPipe_LNCentCorpBnd_PLCemetery_PLApartment_PL
10 2. Order of Coverages to Migrate Actively Edited Files With AnnotationLake_PLWater_LNStream_LNGolf_PLSchoolDist_PLSchoolPrivate_PTShopCenter_PLMuseum_PT
11 2. Order of Coverages to Migrate Semi-Static FilesSunflower_PLCntyBnd_PLPLSS_PLPLSSQuarter_PLFloodZone_PLRiver_PLFemaQ3_PLSoil_PLPlat_PLPark_PLSchoolAttendBnd_PLAirCenter_PLAirExec_PLRail_LNFlightCorridor_PL
12 3. Develop Editing Procedures Utilize built in tools as much as possibleCreate custom Add data and zoom to tools
13 3. Develop Editing Procedures Use of Custom Editor ListenersNew Fields in the DataAIMSFIDWill go into every editing feature class except annotationDATEADDEDDATEMODLASTUSER 20 Characters, Login UsernameXCOORD (If point file) DoubleYCOORD (If point file) DoubleSECTID (in Plani)Multiple Magnifier windows
14 4. Develop Publishing Mechanism Data ConverterTableIni fileGUICommand line
15 5. Develop Publishing Procedures AIMSDataMaint SQL table:Accessible via websiteed reminder to checkKeeps track of:Last updateNext updateUpdateePrimary FormatPublishing Website
16 Other Issues Archiving Annotation Coverage requires subclassFeature linked?Database maintenance and database accessConversion back to tiled coverageDev/Pub serverHad to add subclass to coveragesWhenever you are doing geodatabase maintenance (i.e. compressing, loading, etc) everyone else must be out of the database. Not exactly best situation for multi-user environment, especially if you know you are not overlapping in data or extent.When exporting to coverage it ran a clean and use the countwide extents to determine tolerances. It would then wipe most of the data out on the clean.
17 Summary Take small steps Utilize arcobjects to create scripts for loading data into SDEChoose easy migrations and learn from themUtilize the power of ArcGISArcobjects loading of data will register the data with the geodatabase and you will not have problems with spatial indexes, geocoding, etc.
18 Contact InformationShannon PorterJohnson County AIMS111 S Cherry St, Ste 3500Olathe, KS 66061(913)