• Skip to main content
itrc_logo

EDM

Home
Interactive Directory
Introduction and Overview
Introduction
Overview of Guidance Document
Data Management Planning
Data Management Planning Home
Data Management Planning Overview
Data Governance
Data Lifecycle
Data Access, Sharing, and Security
Data Storage, Documentation, and Discovery
Data Disaster Recovery
Data Quality
Data Quality Home
Data Quality Overview 
Analytical Data Quality Review: Verification, Validation, and Usability
Using Data Quality Dimensions to Assess and Manage Data Quality
Considerations for Choosing an Analytical Laboratory 
Active Quality Control During Screening-level Assessments
Field Data Collection
Field Data Collection Home
Introduction to and Overview of Field Data Collection Best Practices
Defining Field Data Categories and Collection Methods
Field Data Collection Process Development Considerations
Field Data Collection Quality Assurance and Quality Control (QA/QC)
Field Data Collection Training Best Practices
Field Data Collection Training Best Practices Training Development Checklist
Other Considerations for Field Data Collection
Data Exchange
Data Exchange Home
Data Exchange Overview
Valid Values
Electronic Data Deliverables and Data Exchange
Data Migration Best Practices
Traditional Ecological Knowledge
Traditional Ecological Knowledge Home
What is Traditional Ecological Knowledge?
Acquiring Traditional Ecological Knowledge Data
Using and Consuming Traditional Ecological Knowledge Data
Managing Traditional Ecological Knowledge Data
Geospatial Data
Geospatial Data Home
Overview of Best Practices for Management of Environmental Geospatial Data
Organizational Standards for Management of Geospatial Data
Geospatial Data Standards
Geospatial Data: GIS Hardware
Geospatial Metadata
Geospatial Data Software
Geospatial Data Collection Consistency
Geospatial Data Field Hardware
Geospatial Data Dissemination: Web Format
Geospatial Visualization of Environmental Data
Public Communications
Public Communications Home
Public Communication and Stakeholder Engagement
Environmental Data Management Systems
Environmental Data Management Systems Home
Environmental Data Management Systems
Case Studies
Case Studies Home
Historical Data Migration Case Study: Filling Minnesota’s Superfund Groundwater Data Accessibility Gap
Case Study: USGS Challenges with secondary use of multi-source water quality monitoring data
LEK Case Study: Collection and Application of Local Ecological Knowledge to Local Environmental Management in Duluth, Minnesota
TEK Case Study: Improving Coastal Resilience in Point Hope, Alaska
Case Study: Integration of Traditional Ecological Knowledge to the Remediation of Abandoned Uranium Sites
Case Study: Local Ecological Knowledge of Historic Anthrax in a Natural Gas Field
Rest in Peace? A Cautionary Tale of Failure to Consult with an Indigenous Community
Case Study: Use of Traditional Ecological Knowledge to Support Revegetation at a Former Uranium Mill Site
Additional Information
Supplemental Resources
References
Acronyms
Glossary
Acknowledgments
Team Contacts
Navigating this Website
Document Feedback

 

Environmental Data Management (EDM) Best Practices
HOME

Organization Standards for Geospatial Environmental Data Management

Environmental Data Management Best Practices

Geospatial Data Management
Organization Standards

This document provides an outline of standards that may be considered by an organization to provide credibility of the organization’s geospatial data and improve transparency and trust by the public in that data. Organization standards for geographic data are the standards for quality that an organization has in place to ensure all geospatial data are managed properly, from project planning, geospatial data collection, storage, presentation of geospatial information to other organizations or the public, and archival or disposal standards. These standards may be in either an organization-wide geospatial data strategy or included with a project-specific quality management plan. Organization standards ensure quality data for scientifically valid decisions. GIS professionals, information technology (IT) professionals, project managers, and program managers will find the information in this fact sheet useful. The Geographic Data Management subgroup created these best management practices and guidelines for management, collection, communication, visualization, and dissemination of environmental geospatial data.

Overview

Formally, a “standard” is documentation established by consensus of subject matter experts and approved by a standard authority that provides rules, guidelines, or characteristics for activities or their results (ISO 2021). State or federal agencies may have organizational or institutional standards they must follow due to state or federal law, administrative rules, or organizational information technology policy. Agencies may also have internal “standard operating procedures” or other quality management planning documents that include geospatial data storage, collection, management, and dissemination guidelines or requirements. These topics are expanded in other fact sheets in this series (Geospatial Data Collection Consistency, Geospatial Visualization of Environmental Data, and Geospatial Data Dissemination: Web Format subtopic sheets).  

Agency standards for geographic data are the standards for quality that an organization has in place to ensure all geospatial data are managed properly for the life of a program or project. The life of a project includes project planning, geospatial data collection, geospatial data storage, presentation of geospatial information to other organizations or the public, and finally geospatial archival or disposal standards. These standards may be either organization-wide (example: USEPA National Geospatial Data Policy) or contained with a project-specific quality management plan.  

Management, standards, and dissemination of geospatial environmental data can be unique to an agency. Validation of coordinate information can be a component of a sample’s accuracy and determine the sample result’s appropriateness for use in further analysis. Because the locations of environmental information are contained within geographic data, it is wise to be aware of and respect any laws, policies, or potential legal or privacy concerns inferred by analysis, dissemination, and management of geospatial data. Due to the importance of accurate and legally defensible geospatial data, it is best practice to have organizational policy and standards for collecting, storing, managing, analyzing, and disseminating geospatial data collected and used by the organization that follow all applicable state, federal, and local laws and rules.  

Importance of Organization Standards 

Having geospatial environmental data standards for the organization provides credibility for the organization’s data, improving transparency and trust by the public in that data. Such standards ensure the correct use of the geospatial data at the correct scale and resolution. Additionally, these standards promote geospatial data transfer and interoperability, enabling the smooth transfer of geospatial data from one organization or entity to another.  

Organization standards are different from an organization’s geospatial data policy. The organization’s geospatial policy, if it exists, is an aspirational document, with a vision and mission of how geospatial data fit into the organization’s overall business needs (see Lewin [2021] for more thorough discussion of components of a geospatial strategy). An organization’s geospatial standards are for specific aspects of a geospatial project and may include standards for planning, location data collection, presentation, or dissemination of geospatial data, as well as storage and eventual disposal or archiving of geospatial environmental data.  

Suggested Components of Geospatial Standards 

Standards can be written for each phase or component of geospatial data management, including but not limited to:  

  • project planning 
  • geospatial data collection (the collection of coordinate data using a GPS device, for example) 
  • visualization or dissemination of geospatial data 
  • storage or archiving of geospatial data 

For every phase or component of geospatial environmental data management, an organization should consider the following topics when developing standards. For illustrative purposes, each topic includes an example of a geospatial standard.  

  • Scope of the standards or policy
    • Does the standard apply only to data held within the organization, or must entities submitting data to the organization follow the standards?  
    • Do contractors need to adhere to or be aware of your agency’s geospatial data standards, quality assurance plans, or project plans?
      • Example: If an organization hires a private company to complete their required environmental sample collection, does the private company need to adhere to the collection standards of the contracting organization? Does that private company need to have a GPS collection standard? It is up to the organization to determine whether they will have that standard in place, or if it is the responsibility of the private company to have the geospatial location collection standard.
  • Audience
    • Who is the audience of the geospatial standard? Typically, the audience would include direct GIS data stewards, data owners, users, developers, and any person involved with using or distributing geospatial data. The audience can also include information officers, field technicians, program or project management personnel, and other management or leadership personnel. Typically, the general public is not the direct audience of a standards document. An exception would be if the standard is designed specifically for citizen science projects, then the general public would be the audience. However, citizen science is outside the scope of this fact sheet.
      • Example: If a GPS standard is written by the organization, the audience may be the field personnel of the private company that is collecting the GPS data. It may also be future GIS professionals who are reviewing the data to see if a particular procedure is followed or indicated in the standard.
  • Background and authority
    • Geospatial standards for an organization can list reasons why they are developing the standard, and list legal authority to both write and enforce the standards. Authority can include state or federal statutory requirements or both. Organizations will often create or adopt their own geospatial data standards to meet the requirements of the National Geospatial Data Infrastructure Strategic Plan (FGDC 2020).
      • Example: If the organization is a state agency, it may reference applicable state or federal laws as the basis for its authority to write standards to meet quality measures identified in a project plan.   
  • Procedures 
    • Organization geospatial standards outline proper procedures for geospatial project-related tasks, such as field data collection, geospatial data storage, or geospatial data archival procedures. The standard may describe a step-by-step process or procedure that the GIS professional, IT professional, or manager must do to ensure quality geospatial data. Often the individual procedures may be separate standards. Procedures can include guidance for data documentation, new data collection and acquisition, geospatial data processing and final documentation, data storage and access, maintenance of data, and procedures for incorporating historical geospatial data, and geospatial data retirement, disposal, or archiving. Examples of a geospatial procedure standard or policy can be found on USEPA’s Geospatial Policies and Standards web page (see Resources below).
      • Example: An organization’s GPS data collection standard may include a step-by-step description of the tasks that field personnel are to use if they are to collect accurate coordinate information that meets a project’s intended data quality measures. 
  • Roles and responsibilities
    • Agency standards can also outline the roles and responsibilities for geospatial data management among GIS staff. They can include the geospatial information officer or coordinator, data steward(s), data owners, and system administrators. The defined roles can be used for establishing data governance and stewardship protocols.
      • Example: The organization’s GPS data collection standard may define the role and responsibility of a field technician. Their role may be collection of the data, and responsibility is to ensure that the procedure is followed as outlined in the standard. 

Resources 

  • ITRC GRO-1, Geospatial Analysis for Optimization at Environmental Sites: https://gro-1.itrcweb.org/  
  • USEPA FRS data dictionary: https://www.epa.gov/sites/default/files/2015-09/documents/frs_data_dictionary.pdf  
  • Federal Geographic Data Committee data standards: https://www.fgdc.gov/standards  
  • Open Data standards: https://standards.theodi.org/  
  • NJDEP GPS Data Collection Standards for GIS Data Development–April 2017 https://www.nj.gov/dep/gis/standards.html  
  • USEPA Geospatial Policies and Standards web page: https://www.epa.gov/geospatial/geospatial-policies-and-standards  
image_pdfPrint this page/section


EDM

Home
glossaryGlossary
referencesReferences
acronymsAcronyms
ITRC
Contact Us
About ITRC
Visit ITRC
social media iconsClick here to visit ITRC on FacebookClick here to visit ITRC on TwitterClick here to visit ITRC on LinkedInITRC on Social Media
about_itrc
Permission is granted to refer to or quote from this publication with the customary acknowledgment of the source (see suggested citation and disclaimer). This web site is owned by ITRC • 1250 H Street, NW • Suite 850 • Washington, DC 20005 • (202) 266-4933 • Email: [email protected] • Terms of Service, Privacy Policy, and Usage Policy ITRC is sponsored by the Environmental Council of the States.