Home  » Tools & Links

Geospatial Data Coordination Policy

  1. Purpose
  2. Applicability and Scope
  3. Responsibility
  4. Provisions for Waivers
  5. Policy
  6. Administration Procedures

Aug 23 2005

MEMORANDUM FOR:

Regional Flood Insurance and Mitigation Division Directors
Risk Identification Branch Staff

FROM:

David I. Maurstad
Acting Director
Mitigation Division

SUBJECT:

Geospatial Data Coordination Policy

1. PURPOSE

This policy establishes the principles for coordinating, communicating, documenting, and reporting existing and proposed geospatial data collected, produced or manipulated under the Federal Emergency Management Agency’s (FEMA) Map Modernization Program.  The purpose is to enable data sharing and secondary data use.

The primary goals of this policy are to ensure that the Map Modernization Program will:

  1. protect its investments in geospatial data by requiring data to be documented, standards compliant and easily accesible to the general public when appropriate and release of the data does not pose a security risk,
  2. maximize the use of partnerships, including Federal, State and local partners, for the acquisition and production of geospatial data,
  3. minimize duplicative requests from Federal agencies to State and local data stewards,
  4. recognize the value of existing coordination efforts at the State and local levels, and
  5. comply with all Federal requirements for coordination and reporting of geospatial activities.

Through Circular A-16 the Office of Management and Budget (OMB) directed Federal agencies that produce, maintain, or use spatial data to participate in the development of the National Spatial Data Infrastructure (NSDI).  The goals of the NSDI are to reduce duplication of effort among agencies; improve quality and reduce costs related to geographic information; make geographic data more accessible to the public; increase the benefits of using available data; and establish key partnerships with states, counties, cities, tribal nations, academia and the private sector to increase data availability.

FEMA supports the requirements, guidance and standards provided by the Federal Geographic Data Committee (FGDC) and the related e-Government initiative goals of the Geospatial One-Stop (GOS) that implement the NSDI.

Back to top

2. APPLICABILITY AND SCOPE

This policy applies to all FEMA organizations, contractors and grantees of FEMA, who design, develop, compile, collet, convert or maintain FEMA geospatial data collections developed for the Map Modernization Program.

This policy does to preclude or rescind more stringent regional or program-specific policy and guidance.

Back to top

3. RESPONSIBILITY

  1. The Risk Identification Branch (RIB) shall be responsible for implementing and supporting this policy and for providing guidance and technical assistance where feasible and appropriate in implementing and improving the requirements of this policy.
  2. Regional Flood Insurance and Mitigation Division Directors shall establish procedures within their respective organizations to ensure that information collection and reporting requirements under their direction are in compliance with this policy.

Back to top

4. PROVISIONS FOR WAIVERS

Requests for waivers from specified provisions of the policy may be submitted for review to the Risk Identification Branch Chief at FEMA Headquarters.  Waiver requests must be based clearly on data quality objectives and cost impacts and must be signed by the relevant Regional Flood Insurance and Mitigation Division Director prior to submission to the Risk Identification Branch Chief.

Back to top

5. POLICY

It is FEMA’s policy that geospatial data for use in the development of Digital Flood Insurance Rate Maps be coordinated, collected, documented and reported with standardized, complete and current information in compliance with Federal geospatial data reporting standards.

It is FEMA’s policy to avoid all unnecessary duplication of Federal, State or local mapping efforts by consistent coordination and application of this policy to mapping projects.

Specifically, anyone collecting, acquiring, producing, contracting for or managing geospatial data for Map Modernization projects shall:

  1. Post Planned Projects to Appropriate Systems for Coordination
    1. Post planned production to Geospatial One-Stop (GOS).
      1. A record will be posted to GOS describing each major data theme required for the project such as orthoimagery, vector data, and elevation data.  The record should include the specific project area and general information about the project sufficient to assist potential partners in determining if there is a possible overlap with their requirements.
      2. The initial posting for each project shall be accomplished prior to January 31st of the fiscal year prior to the year when the project will be initiated based on OMB/GOS requirements.
      3. The information posted to GOS shall be updated after scoping, when data collections are completed, and whenever more details are available that would assist potential partners in determining if project data would support their requirements as well.
    2. Planned orthoimagery should be posted in the National Digital Orthophoto Program (NDOP) project tracking system and coordinated with NDOP.
    3. Planned digital land or bathymetric elevation data should be posted in the National Digital Elevation Program (NDEP) project tracking system and coordinated with NDEP.
  2. Identify Existing Data
    Prior to initiating any new data production, source at the Federal, State, and local levels should be coordinated with in order to identify existing holdings:
    1. Federal — Investigate the Federal data holdings in appropriate systems, including GOS, NDOP, and NDEP.  Search existing FEMA holdings.  Contact state-level Federal Agency contacts.
    2. State — Coordinate with the designated state geospatial data contact and investigate state data inventories.
    3. Local — Contact the affected jurisdictions and the County to determine available sources of information.
  3. Acquire Existing Data
    1. Follow data acquisition procedures based on current state specific Geospatial Coordination Procedures maintained by the Regional Office.
    2. When acquiring existing data for use in the development of the DFIRM, ensure that each distinct data set is accompanied by metadata that is FGDC compliant.
    3. Ensure that FEMA has distribution rights for acquired data as appropriate.  (See section 5.e.iii)
    4. Non-Federal orthoimagery used for a project should be posted in the NDOP project tracking system.
    5. Non-Federal digital land or bathymetric elevation data used for a project should be posted in the NDEP project tracking system.
    6. Ensure that the data are archived on the MIP or in an approved partner archive and made available as appropriate.
  4. Build Partnerships for the Creation of New Data
    1. Search for similar planned projects in the area in order to identify potential partnerships.
    2. Check with Federal, State and local partners for potentially compatible projects and work to build partnerships arrangements for the acquisition or creation of the new data.  Be flexible and seek partnerships that are beneficial to all parties.
    3. Planned orthoimagery production should be coordinated with NDOP and posted in the NDOP project tracking system.
    4. Planned digital land or bathymetric elevation data production should be coordinated with NDEP and posted in the NDEP project tracking system.
    5. Post the planned acquisition to GOS.
    6. Ensure that any partnership agreement provides FEMA unlimited public distribution rights to the data (See sections 5.e.iii).
  5. Document and Standardize Data
    1. Regional offices shall maintain state specific Geospatial Coordination Procedures for each state in the Region.  These will identify points of contact, desired level of State involvement, State geospatial resources and other information to facilitate coordination with the State.
    2. When new data is produced or acquired for a flood study project, ensure that FGDC compliant metadata is part of the deliverable.
    3. Insure that data partnership agreements provide FEMA appropriate data distribution rights.
      1. All flood data and all base maps must allow unlimited free distribution by FEMA and partners.
      2. Elevation data created using FEMA funding must allow unlimited free distribution by FEMA and partners.
      3. Community (or other partner) supplied elevation data should allow unlimited free distribution unless there are substantial cost savings or other compelling reasons to use data that are not freely distributable.
      4. Licensed, commercial datasets other than flood data and base maps may be used if it is advantageous for the project.
      5. Data that represents a security risk if disclosed do not need to allow unlimited free distribution.
    4. When production is complete, remove GOS records for planned datasets and post GOS records for the finished datasets.
    5. Publish metadata for completed dataset on an NSDI clearinghouse node.
    6. Update information provided to the NDOP and NDEP to reflect completed status of the project.
    7. Document:
      1. Amount spent for each data category by FEMA (ground elevation, cross section survey, base map, etc.).
      2. Acquisition cost/in-kind contribution for each partner.

Back to top

6. ADMINISTRATION PROCEDURES

The detailed procedures and guidelines for implementing the policy are issued under separate cover (Geospatial Data Coordination Implementation Guide).  This implementation guidance will provide more detail on the Geospatial Data Coordination Policy as well as procedures for its implementation.

Back to top