1. Managing GIS Data
for Large EIS Projects
Chris Query, SWCA GIS - Phoenix

2. The EIS Process and NEPA
National Environmental Policy Act (NEPA)
Federal agencies prepare an Environmental Impact Statement (EIS) if a proposed major federal action is determined to significantly affect the quality of the human environment.
Therefore, an Environmental Impact Statement, or EIS, is a document that describes the impacts on the environment as a result of a proposed action. It also describes impacts of alternatives as well as plans to mitigate the impacts.
Common projects that an EIS may be required for:
Energy Production / Transmission
Transportation
Mining
is or may? (DD - I changed “is required” to “may be required”)

3. The EIS Process and NEPA, Cont.
Typical areas of analysis
Project Area “Affected Environment”
Threatened or Endangered Species
Air & Water Quality
Historic & Cultural Sites
Social and Economic
Maps and GIS calculations and recalculations are required for all of these!
Not a lecture on the EIS process but the complex amount of data from multiple sources and “quality” of datasets
Alternatives and Public Input steers this process
Alternatives / Public Input = versions
Think of these as Feature Datasets in the GeoDb

4. The EIS is building a court-defensible document
GIS data used to support the document, not just for the maps!!
Don’t forget about the administrative record!

5. Project Development / Kick-off
Project “Success” and the 7 Ps
Assume ESRI solution and ESRI spatial data formats Geodatabase(s)
Kick-off Meetings: GIS RnR, Who What Where
Analysis Area / Project Datasets, Base Data, Resource Data needs & wants?
Discussion of the integrity of the calculations based on the above datasets.
Proper Planning and Preparation Prevents Piss Poor Performance
RnR: Data tracking, QA/QC, Resource Map Production
“Where“ do you need SDE? Remote GIS staff needing access

6. Data Gathering, Creation, and Database Design
“Best Available” datasets, Where are they and Who has them?
Non-GIS formats, conversions? Data “cleanup”
Does the data “Fit” together? Integrity of the calculations
File Tracking / Naming Conversions, Versions & Metadata
Datasets “Grouping” for scripting, calculations, map production
Map templates / Feature symbology = Consistency
Geodatabase versions and scheduled backups
Basemap services
Editing the data makes it “Yours” and you now except that you will have to stand tall before the man and defend your editing decisions
Lyr and style files.
Maximize ESRI software for your daily tasks using scripting and map production tools

7. Conclusions
The EIS process can take many months and in many cases years to complete. Each EIS project has its unique challenges, and managing the GIS data through the EIS life cycle is often underestimated. While there is no one set of guidelines for EIS spatial data management, we hope with proper planning and workflows, this process will be easier to navigate.
You know it’s going to be this With the 7 Ps it can be this

8. “I Never Thought Of That”
Conclusions, Continued
INTOT
“I Never Thought Of That”
Not going to predict all of the project hurdles but hopefully you have a good plan in place and we discussed some things you may have not of thought about and it will prevent your data from looking like this.