20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Contractors: Getting the CleanestGeospatial Data Possible
Urgent News from FoxNewsNetwork
E.O. 12907, signed by President Bush onMarch 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….”
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Contractors: Getting the CleanestGeospatial 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
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• Background Example
• The Issues
• The Solutions
• The Tools
• The Results
Summary
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• No Involvement by Park with Contract
• Multi-Year Project, Same Contractor
• Many Field Data Collectors
• Miscommunication of Requirements
Background Project Example
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Too Many Shape Files with Attribute Errors
Too Many Metadata Records by Contractor
Approx. 2 weeks Park spent editing data
Example Results:
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• Background Example
• The Issues
• The Solutions
• The Tools
• The Results
Summary
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Different Data Dictionaries
Inconsistent Field Values/Attributes
Misspelled Attributes
Unnecessary Data
Multi-Year Project Problems
The Issues
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
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
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• Background Example
• The Issues
• The Solutions
• The Tools
• The Results
Summary
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
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
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Provide Supporting Park Data & Metadata to Contractor
Set the Example
Assist w/ GPS Data Dictionaries
Provide Data Schemae.g., List of Required Fields
The Solution: Assistance
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Provide Example DeliverablesGeodatabase, Metadata Record
Review Data periodically before end of project (write into contract)
The Solution: Assistance
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Define Your Preferred Data Format:
File GeodatabasePersonal Geodatabase
Shape FileCoverages
Projection/Datum
Solution: Preferred Data Format
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
ALL CAPS/Initial Caps/Does It Matter?
Solution: Define Field Value Rules
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Ex: “Surveyor” Format:
Solution: Define Field Value Rules
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Ex: Date Format: YYYYMMDD
Date or String or Numeric?
Solution: Define Field Value Rules
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Solution: Define Field Value Rules
Ex: Date in MetadataDate Format: YYYMMDD
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Did you know that “Process Step”
is not an FGDC Requirement?
Therefore, do you know how
the data was created then?
Solution
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
The Solution: Process Step
Require “Process Step” (Metadata) in the Contract:Data Quality Process Description/Software_Version/Date/Contact
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• 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
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• Background Example
• The Issues
• The Solutions
• The Tools
• The Results
Summary
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Review with Contractors:
• Contract Standards
• Define/Provide Data Dictionary
• Data Schema:Values/Attributes Format
Domains/Ranges
Provide The Tools
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Review with Contractors:
• ArcToolBox Frequency Tool: unique ID spelling inconsistenciesmissing valuesleading spaces, etc. other ways?
(Access, Excel, SQL, Oracle, scripts?)
Provide The Tools
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
NPS Metadata Tools & Editor
Provide Tools Linkhttp://science.nature.nps.gov/nrdata/tools/index.cfm
Review with Contractor: Spell Check MetadataParse MetaFind and Replace, etc.
Provide the Tools
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
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
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• Have a Party!
• Present to Park Management/Employees
• Thank them officially for a job well done
End of Project
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
• Background Example
• The Issues
• The Solutions
• The Tools
• The Results
Summary
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Contractors: Getting the CleanestGeospatial 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
20080401 ZION: Elena Robisch @ nps.govNCPN: Aneth Wight @nps.gov
Discussion/Questions?
Elena RobischGIS Program ManagerZion National Park435-772-0213
Aneth WightGIS SpecialistNCPN435-719-2348