ESRM 250/CFR 520 Autumn 2009 Phil Hurvitz

1. Project Management in GIS ESRM 250/CFR 520 Autumn 2009 Phil Hurvitz 1 of 26

2. Overview • Managing non-ArcInfo data sets • Managing ArcInfo data sets • Managing Geodatabases • Copying & moving ArcMap documents • Geodatabases 2 of 26

3. Overview • Managing non-ArcInfo data sets • Managing ArcInfo data sets • Managing Geodatabases • Copying & moving ArcMap documents • Geodatabases 3 of 26

4. Managing non-ArcInfo data sets • General system file management • Setting the working directory • Renaming • Copying • Archiving 4 of 26

5. General system file management • GIS is more file-intensive than most other computer applications • Knowledge of OS file system operation is critical • Disk, directory, and file management skills • Disk space • Directory structure & nomenclature • File nomenclature, file sizes, multiple-file data sets • Where (file system-wise) is every file in the current project? 5 of 26

6. Setting the working directory • Default location for new files • Set the working directory early • Avoids major headache later • Have no doubt about where new files will be placed • TIPs: • Create a new directory for each project • Set working directory to the new directory • New data sets can be easily archived 6 of 26

7. Setting the working directory • Geoprocessing environment: default output directory, etc. 7 of 26

8. Renaming & copying • Be careful about renaming & copying files • Every file of a multiple-file data source must be renamed/copied • Files that are renamed/copied will not be “found” in map documents • Files to be copied/renamed cannot be in use in current project • Data sources are frequently composed of multiple individual files • Shapefiles are composed of at least 3 separate files • Image data sources are composed of at least 1 file, at most 4 8 of 26

9. Renaming & copying • Use OS find files functionality to identify all files in multiple-file data sources 9 of 26

10. Renaming - Use ArcCatalog ArcCatalog renames all files withone operation 10 of 26

11. Copying - Use ArcCatalog! ArcCatalog copiesall files withone operation 11 of 26

12. Renaming & copying • ArcCatalog functionality applies to any supported data sets • Other files can be copied/moved/renamed using OS file management • images • text files • dBase files (that are not theme tables) • CAD files 12 of 26

13. Managing non-ArcInfo data sets: Archiving • Create new “backup” directories, copy files • Write to stable media (tape, CD, DVD, etc.) • Use archiving tool, e.g. PKZip, WinZip, tar • create archive files • copy to “safe” directories • write to stable media 13 of 26

14. Overview • Managing non-ArcInfo data sets • Managing ArcInfo data sets • Managing Geodatabases • Copying & moving ArcMap documents • Geodatabases 14 of 26

15. Managing ArcInfo data sets • Supported data types • Archiving • Dealing with ArcInfo coverages 15 of 26

16. Managing ArcInfo data sets: Copying & Renaming • ArcCatalog will rename, copy, and move • Coverages • grid data sources • TIN data sources • Possible to convert any vector data format to and manage as shapefile or geodatabase • Possible loss of informational content 16 of 26

17. Managing ArcInfo data sets: Archiving • Coverage, grid, & TIN themes • Use standard ArcCatalog rename & copy • Archive files as you would any other files • create archive files • copy to “safe” directories • write to stable media • NEVER attempt to manage ArcInfo (coverage, grid, or TIN) source files with the OS; you will corrupt your data 17 of 26

18. Dealing with ArcInfo coverages • ArcInfo File Structure • some of the files in the info directory • are associated with files in the geodataset directory 18 of 26

19. Dealing with ArcInfo coverages • ArcInfo data sets are somewhat problematic in ArcGIS • Cannot be edited without ArcInfo run level • Convert & manage as shapefile • Loss of informational content if polymorphic data set • Import to whole new directory/folder • copy & archive entire directory • Do not alter Info directories/folders • you will corrupt data 19 of 26

20. Overview • Managing non-ArcInfo data sets • Managing ArcInfo data sets • Managing Geodatabases • Copying & moving ArcMap documents • Geodatabases 20 of 26

21. Copying & Moving Map (.mxd) Documents • ArcGIS map document files do not “contain” copies of data sets • ArcGIS map documents contain instructions that include pointers to data location • File locations are “hard coded” into project files 21 of 26

22. Copying & Moving Map (.mxd) Documents • Copying & moving map documents does NOT copy or move data sets • Data sets must be either: • Moved • Identical file structure • Copied • Identical file structure • Specified • Restructure your .mxd map document 23 of 26

23. Copying & Moving Map (.mxd) Documents • Map documents may specify absoluteor relative path names to data sources 24 of 26

24. Copying & Moving Map (.mxd) Documents • Map documents may specify absoluteor relative path names to data sources • With relative path names, if data sets are in the same folder as the map document, the entire folder can be moved, copied, or renamed. • With absolute path names, file structures must be recreated identically if map documents and data sets are to be copied to a different computer. 25 of 26

25. Overview • Managing non-ArcInfo data sets • Managing ArcInfo data sets • Managing Geodatabases • Copying & moving ArcMap documents • Geodatabases 22 of 26

26. Geodatabases • Geodatabases are the new preferred data storage standard for ArcGIS • A “container” for data sets • feature classes (vector data) • raster data • tables • Two formats: • MS Access mdb format (“personal geodatabase”) • 2 GB size limit • Special files in a folder (“file geodatabase”) • 1 TB size limit • Manage with ArcCatalog 26 of 26