Attachment4_TNF_ManagingGISProjectRecord.docx

DOCX document 602 KB Posted

Attached to
Harris South Project Environmental Impact Statement
Solicitation number
1168154
Issued by

About this file

This document is a procedural guide for managing, documenting, and producing Geographic Information System (GIS) data for Forest Service project records, specifically within the context of National Environmental Policy Act (NEPA) processes. The guide, last updated June 14, 2026, provides comprehensive standards for GIS specialists and interdisciplinary teams managing spatial data throughout project development, from initiation through post-NEPA project management.

The document establishes mandatory requirements for GIS data management including folder structure protocols, permissions frameworks, and data compilation standards to ensure all project records can be independently referenced and reproduced. Key requirements include: clipping and re-projecting all external data sources into project folders; archiving datasets at critical planning stages (scoping, comment, objection, and final decision); including baseline/existing condition data alongside proposed action and alternative analyses; maintaining detailed metadata and ReadMe documents for all layers and feature classes; ensuring Section 508 compliance for all project products; and properly handling sensitive and restricted data in designated folders. The guide mandates that all GIS data, analysis results, maps, and associated documentation used directly or indirectly in project decisions must be retained as part of the administrative record, as this data may be subject to Freedom of Information Act (FOIA) requests or required for litigation proceedings. The document includes three sample attachments demonstrating Project Record ReadMe documentation, Analysis ReadMe documentation, Project Development ReadMe documentation, and a GIS NEPA Project Data Lifecycle diagram. Additionally, the guide addresses special considerations for Image Services data preservation through PDF exports, ArcGIS Online data migration protocols, project photo management with geotagging and metadata requirements, and base data updates coordination with corporate GIS systems.

View the file

Other files

Show all 15

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Region 1 | Data, Information and Geospatial | Ecosystem Planning

Managing, Documenting, and Producing GIS Data for Project Records

Modified by Tom Heutte, Tongass NF GIS Leader from document by… Jeff Erwin, R1 NEPA Strike Team Geospatial Analyst, Kim Smolt, R1 NEPA Objections and Litigation Specialist, EAP Staff Rosa Nygaard, R1 Technology Information Resource Coordinator, Data Governance Revised by Zo Anderson, Rita Bennett, Rachel Corley and Rebecca Lilja

Last Updated: 6/14/2026

Table of Contents

Overview3
Project Collaboration between GIS Specialists and ID Teams3
Project GIS Data and FOIA3
Production of Project GIS Data for Administrative Records3
Folder Structure and Permissions4
Data to Include in the Record5
Clipping Data5
Image Services Data5
Archiving Data5
ArcGIS Online Data Management5
Section 508 Compliance6
ReadMe Documents (Metadata)6
Project Record ReadMe Document (Attachment 1)6
Analysis ReadMe Documents (Attachment 2)6
Project Development ReadMe document (Attachment 3)7
Project Photo Management7
Coordination Between the T: Drive and Pinyon (Box)7
Handling of Sensitive and Restricted Data8
Post-NEPA Project Management8
Base Data Updates8
Other Websites and Referenced Sources8
Attachments9
Attachment 1: Project Record Documentation example9
Attachment 2: Analysis ReadMe example10
Attachment 3: Project Development ReadMe Example10
Attachment 4: GIS NEPA Project Data Lifecycle10

This document is intended to be a supplement to the Northern Region Project and Administrative Record Guidance.

Overview Geographic Information System (GIS) is the melding of digital cartography, statistical analysis, and database technology. It is a system that integrates, stores, edits, analyzes, shares, and displays geographic information and, as such, it is an integral part of the decision-making process for the Forest Service. Not only is the retention of spatial data mandated by law and regulation, but it is also critical that the data, analysis, and maps be preserved as part of the project record so that it can be reproduced in the future. Forest Service GIS data is available to the public through Freedom of Information Act (FOIA) requests and will be produced in an administrative record (AR) if the project decision is litigated. Therefore, it is imperative that the GIS Project Record be properly managed, documented, and produced.

Project Collaboration between GIS Specialists and ID Teams GIS plays an important role during the NEPA process. It is important that project specialists and GIS specialists coordinate throughout the project. As GIS specialists are frequently assigned to interdisciplinary teams (ID team), it is important that GIS specialists be able to participate fully, that they have the ability to communicate GIS information to team members in easy-to-understand formats, have GIS knowledge relative to the analysis process, and be able to objectively conceptualize and solve problems.

The ID Team Leader needs to work with the GIS specialists in providing and retaining the data for the project record. The Team needs to share the big picture of the project, stay in communication, involve the GIS specialist from the beginning of the project, take an active role in documenting the outputs, guarantee that each Team member provides appropriate documentation to support their analysis, and provides clear objectives for the outputs.

During project initiation, it is important to set up the record structure, which includes GIS data. As the project develops, the team acquires data, performs analysis, and creates maps, spreadsheets, models, charts, and data sets. The team members should use the workspace folders to create products (e.g. layers, feature classes, maps) and work with the GIS specialist to copy the final products, metadata, and supporting process documentation to the “Data” folder in the project file geodatabase. Some resource specialists do their own GIS analysis, whereas some will ask the GIS specialist to run their GIS analysis.

Project GIS Data and FOIA It is important to note that some GIS data may be exempt under FOIA. If data is requested pursuant to a FOIA request, contact your FOIA coordinator for a determination.

Production of Project GIS Data for Administrative Records All information relied on indirectly or directly for a decision are part of the project record[footnoteRef:1], including GIS data and associated metadata and process documentation. If there is litigation on a decision, an administrative record (AR) will be produced from the project record. The AR is filed with the court and is the basis for review of an agency’s decision. Even though some GIS data cannot be opened and read without special software, it must be included in the AR. There are free software programs on the Web such as ArcGIS Online, which the public can use to read some of the GIS data produced by the Forest Service. [1: “Project record” and “project file” are synonymous. We will use the term “project record” in this document for simplicity.]

Project record data should be named and dated appropriately.

Folder Structure and Permissions The following GIS record structure and user permissions should be used.

Figure 1 below displays the initial folder structure.

Figure 1: NEPA GIS project folder structure Data to Include in the Record Teams must compile GIS records that can be independently and reliably referenced or used. Therefore, the project’s GIS record must contain data from all. All data used, including spatial and tabular sources, results from any analysis performed, data used to create maps and other displays, data referenced in maps, and associated metadata, should be directly accessed from the project folder only, with few exceptions (see the Image Services Data section below).

The final raw data used to develop and structure any analytical tools is part of the record as well as all final model outputs. Data created for analysis should be included in the project FGDB in its final format.

Interim, draft data does not belong in the final database for the project record. Specialists may keep this data in their workspace folders, if they’d like – the workspace is like a sandbox. Final datasets of the proposed action and alternatives, if applicable, and specialists’ analysis data for final versions of draft reports released for each stage of the NEPA process should be included in the project record and clearly labeled (e.g. 20260120_DraftEA_FisheriesSpecialistReportData, 20260120_DraftEA_Proposed Action). The final project record also needs to include baseline/existing condition data, such as existing roads or habitat.

Clipping Data Data from the library, national applications, and other sources should be clipped, re-projected, and copied into the project folder because data outside of the project folder could be modified, deleted, or become inaccessible. This may seem redundant or time consuming, but it is crucial that data used in an analysis be reproducible;

Image Services Data Data accessed through an Image Services connection (IIPP, NAIP, eTOPO, softcopy) is often not feasible to save to the project folder due to its size and limitation in extraction routines. This “background” information can be preserved by exporting map products and metadata to a .pdf format and saved in the Maps Folder.

Archiving Data Datasets should be archived at key points in the planning process, such as for scoping, comment, objection, and final decision. Key datasets used by resource specialists to reach findings for their effects analysis must be included in the Data folder in the project record.

ArcGIS Online Data Management Data created in ArcGIS Online (AGOL) data is also pertinent for the project record and AR. The AGOL Content Creation Guide (p. 41) provides guidance on content lifecycle management and moving AGOL data to Pinyon (Box).

AGOL content management includes removing unused data and applications when field data collection is complete. AGOL data should be migrated into the project record if it was used to inform the decision.

Section 508 Compliance Every effort shall be made to ensure project products are Section 508 compliant.

ReadMe Documents (Metadata) Metadata should be attached to all layers and feature classes. Metadata should document reasons for changes to feature classes (i.e., units or roads) at each stage in the NEPA process.

Completed ReadMe documents must also be included in the record and are usually stored in the documents folder. You may create one comprehensive readme or a readme for each purpose described below.

Project Record ReadMe Document (Attachment 1) This document outlines the folder structure and data content for the project and should address the following:

· List of and description of final datasets and metadata used. See the GDB Metadata Summary tool for how to automate a list of datasets and metadata.

· Data limitations and anomalies (e.g. NFS acres outside of the proclaimed boundary), if any.

· List and description of final map products: Map sizes, dates, resolution, and imaging software used.

· Other applicable information that would be helpful in recreating the products in the future.

Analysis ReadMe Documents (Attachment 2) The Analysis ReadMe document serves as a comprehensive guide to the analysis process, detailing the geodatabase used, input and output data classes, and the overall purpose of the analysis. The Readme should include:

· Sources of data: Date acquired, format, and source (corporate library, contractor, website, and web services). Names: People requesting analyses, dates of requests and people performing the analyses.

· Names of geodatabase and starting and ending (final) data classes

· Description and purpose of the analysis

· Special queries including definition queries used in the process

· Naming conventions of created data should be easy to read and include a date

· Include pathnames

· Analysis Steps: Description of what was combined and how they were combined (intersect, clip, etc.)

· Description of geoprocessing tools used for analysis.

Project Development ReadMe document (Attachment 3) It is important to create a project development ReadMe document when the project begins and update it as the project proceeds. A project development ReadMe document is basically a series of notes made by the GIS specialist or Resource Specialist that could be used to recreate the finished product or document project progression. If a product is created by a resource specialist, they will provide a ReadMe document to the GIS specialist and update the metadata within the dataset. It may be easier to document the process as it is created. If the project has multiple components such as wildlife and timber, separate ReadMe documents can be created.

Project Photo Management Photographs play a vital role in project decision making and should be included in the project record. Managing project photographs can be a daunting task and all efforts should be made to ensure both spatial and tabular references can be maintained. A good process setup at project conception can really make things easier down the road. Photos without location data and a description of why the photo was taken are not helpful for the record.

It is recommended to enable geotagging when capturing photos and to use a basic schema for tracking and metadata inclusion. The simplest approach is to create a Word document that includes all photos with captions describing the content, relevance, photographer, location, and date.

Handling of Sensitive and Restricted Data It is the responsibility of the Data Steward or specialist to inform the GIS specialist on a project of any sensitive or restricted data. All sensitive or restricted data should be maintained in the Restricted Folder with view/edit permissions for the data steward and Project GIS specialist. We also recommend including “CUI” in the document path name.

Base Data Updates During the planning stages of a project, base data may be identified as needing updates. Base data updates should be discussed with the team and incorporated into the corporate data system, as appropriate, by an agency GIS Specialist. Metadata should explain how and when the updates were identified and made, and what the updates included.

image1.jpeg image2.png image3.png image4.png

File details come from the government source that posted it. Updated .