1. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Contractors: Getting the Cleanest Geospatial Data Possible Urgent News from FoxNewsNetwork E.O. 12907, signed by President Bush on March 31, 2008, states: “Beginning April 15, 2008, all federal geodatabases are required to have FGDC metadata for: each feature class, each feature data set, and the geodatabase….”

2. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Contractors: Getting the Cleanest Geospatial Data Possible The Goal: Deliverables that I don’t have to edit That upload into Park’s Geospatial Library That upload to NPS Data Store

3. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Background Example The Issues The Solutions The Tools The Results Summary

4. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 No Involvement by Park with Contract Multi-Year Project, Same Contractor Many Field Data Collectors Miscommunication of Requirements Background Project Example

5. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Too Many Shape Files with Attribute Errors Too Many Metadata Records by Contractor Approx. 2 weeks Park spent editing data Example Results:

6. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Background Example The Issues The Solutions The Tools The Results Summary

7. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Different Data Dictionaries Inconsistent Field Values/Attributes Misspelled Attributes Unnecessary Data Multi-Year Project Problems The Issues

8. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Leading Space(s) Capital “O” for Zero One too many digits in date field How was data created? Spelling Errors Missing Values Issues: Common Results

9. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Background Example The Issues The Solutions The Tools The Results Summary

10. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 NPS National Standards & Park-Specific Standards Trimble Export Routine (if applicable) Ask for Documentation of Protocols before contract signed ******************************************* “No Good Data, No Good Pay” The Solution: Written Contract

11. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Provide Supporting Park Data & Metadata to Contractor Set the Example Assist w/ GPS Data Dictionaries Provide Data Schema e.g., List of Required Fields The Solution: Assistance

12. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Provide Example Deliverables Geodatabase, Metadata Record Review Data periodically before end of project (write into contract) The Solution: Assistance

13. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Define Your Preferred Data Format: File Geodatabase Personal Geodatabase Shape File Coverages Projection/Datum Solution: Preferred Data Format

14. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 ALL CAPS/Initial Caps/Does It Matter? Solution: Define Field Value Rules

15. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Ex: “Surveyor” Format: Solution: Define Field Value Rules

16. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Ex: Date Format: YYYYMMDD Date or String or Numeric? Solution: Define Field Value Rules

17. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Solution: Define Field Value Rules Ex: Date in Metadata Date Format: YYYMMDD

18. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Did you know that “Process Step” is not an FGDC Requirement? Therefore, do you know how the data was created then? Solution

19. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 The Solution: Process Step Require “Process Step” (Metadata) in the Contract: Data Quality Process Description/Software_Version/Date/Contact

20. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Separate or Combined Data? Who will do that Same Data Dictionary? What IF it changes How will it append/merge Contract needs written instructions addressing multi-year project Solution: Multi-Year Project

21. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Background Example The Issues The Solutions The Tools The Results Summary

22. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Review with Contractors: Contract Standards Define/Provide Data Dictionary Data Schema: Values/Attributes Format Domains/Ranges Provide The Tools

23. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Review with Contractors: ArcToolBox Frequency Tool: unique ID spelling inconsistencies missing values leading spaces, etc. other ways? (Access, Excel, SQL, Oracle, scripts?) Provide The Tools

24. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 NPS Metadata Tools & Editor Provide Tools Link http://science.nature.nps.gov/nrdata/tools/index.cfm Review with Contractor: Spell Check Metadata Parse Meta Find and Replace, etc. Provide the Tools

25. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Solution & Tools Summary Get it In the Contract Write the GPS Data Dictionary Define the Schema Provide the Tools Work w/ During Project Review the Data Before You Pay

26. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Have a Party! Present to Park Management/ Employees Thank them officially for a job well done End of Project

27. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Background Example The Issues The Solutions The Tools The Results Summary

28. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Contractors: Getting the Cleanest Geospatial Data Possible The Results: Deliverables that I don’t have to edit That upload into Park’s Geospatial Library That upload to NPS Data Store

29. ZION: Elena Robisch @ nps.gov NCPN: Aneth Wight @nps.gov 20080401 Discussion/Questions? Elena Robisch GIS Program Manager Zion National Park 435-772-0213 Aneth Wight GIS Specialist NCPN 435-719-2348