5.3 Geospatial Metadata Standards: FGDC CSDGM and the ISO 19115 Family

5.3 Geospatial Metadata Standards: FGDC CSDGM and the ISO 19115 Family

Core Principle: Metadata is frequently described as "data about data," but in professional GIS practice, it is the legal, scientific, and operational contract governing geospatial assets. Without metadata, a shapefile, feature class, or raster grid is an unverified collection of coordinates. Metadata preserves institutional knowledge, protects agencies from legal liability, enables automated catalog harvesting, and ensures that decision-makers understand the spatial accuracy, provenance, and fitness for use of geographic data.

---

1. The Operational Necessity of Geospatial Metadata

Geospatial data collection represents a substantial financial investment. Surveys, airborne LiDAR missions, satellite acquisitions, and manual parcel digitizing cost billions of dollars across public and private sectors. Metadata safeguards this investment by addressing several operational imperatives:

1. Data Discovery: Enabling search engines, clearinghouses, and catalog services to index datasets based on spatial bounding footprints, temporal epochs, and standardized thematic keywords.
2. Fitness-for-Use Evaluation: Providing potential users with quantifiable metrics regarding positional accuracy, completeness, and collection methodology before they incorporate the data into high-stakes engineering or emergency response workflows.
3. Historical Lineage & Reproducibility: Documenting the exact transformation algorithms, source datums, scale thresholds, and manual editing procedures applied over time, ensuring scientific reproducibility.
4. Legal Liability and Risk Mitigation: Establishing clear liability disclaimers, usage constraints, public records access limitations, and intellectual property licensing terms.
5. Preventing Duplication of Effort: Providing public clearinghouse records so adjacent jurisdictions or federal agencies avoid expending taxpayer funds re-acquiring existing imagery or elevation coverage.

---

2. FGDC Content Standard for Digital Geospatial Metadata (CSDGM)

In 1994, Presidential Executive Order 12906 established the National Spatial Data Infrastructure (NSDI) and tasked the Federal Geographic Data Committee (FGDC) with standardizing spatial documentation. The resulting standard, the Content Standard for Digital Geospatial Metadata (CSDGM, FGDC-STD-001-1998), became the mandatory metadata architecture for all U.S. federal agencies and recipients of federal geospatial grants.

                  FGDC CSDGM 7-SECTION ARCHITECTURAL SCHEMA
                  
   +-------------------------------------------------------------------------+
   |  Section 1: IDENTIFICATION INFORMATION                                  |
   |  (Citation, Title, Abstract, Purpose, Bounding Box, Keywords, Rights)   |
   +-------------------------------------------------------------------------+
   |  Section 2: DATA QUALITY INFORMATION                                    |
   |  (Positional Accuracy, Completeness, Consistency, Lineage Process Steps)|
   +-------------------------------------------------------------------------+
   |  Section 3: SPATIAL DATA ORGANIZATION INFORMATION                       |
   |  (Direct/Indirect Reference: Vector, Raster, Point, Grid Architecture)  |
   +-------------------------------------------------------------------------+
   |  Section 4: SPATIAL REFERENCE INFORMATION                               |
   |  (GCS Datum, Ellipsoid, Projection Parameters, Vertical Datum & Units)  |
   +-------------------------------------------------------------------------+
   |  Section 5: ENTITY AND ATTRIBUTE INFORMATION                            |
   |  (Feature Classes, Field Names, Data Types, Enumerated/Range Domains)   |
   +-------------------------------------------------------------------------+
   |  Section 6: DISTRIBUTION INFORMATION                                    |
   |  (Distributor Contact, Formats, Fees, Digital Transfer URLs, Waivers)   |
   +-------------------------------------------------------------------------+
   |  Section 7: METADATA REFERENCE INFORMATION                              |
   |  (Metadata Creation Date, Review Date, Contact Person, Standard Version)|
   +-------------------------------------------------------------------------+

The Seven Primary Sections of CSDGM

Understanding the exact contents and architectural placement of information across the seven CSDGM sections is a recurring focus of GISP exam questions:

Section 1: Identification Information

Establishes the fundamental identity and spatial/temporal footprint of the dataset:

• Citation: Title, originators, publication date, edition, and online link.
• Description: Comprises the Abstract (objective summary of what the data contains), the Purpose (why the data was created and intended uses), and Supplemental Information.
• Time Period of Content: The calendar date and time for which the data is valid, including whether it represents a single date, multiple dates, or a continuous temporal interval.
• Spatial Domain: Bounding coordinates defining the minimum bounding rectangle in geographic coordinates (West Bounding Coordinate, East Bounding Coordinate, North Bounding Coordinate, South Bounding Coordinate).
• Keywords: Categorized search terms across five controlled domains: Theme (often using ISO 19115 topic categories), Place, Stratum (elevation/atmospheric layers), and Temporal.
• Access and Use Constraints: Legal restrictions governing who can acquire the data and how it can be utilized.

Section 2: Data Quality Information

Documents the quantitative and qualitative fitness of the dataset across the core quality dimensions:

• Attribute Accuracy Report: Measures the correctness of non-spatial attribute values.
• Logical Consistency Report: States fidelity to data structures, schema rules, and topological constraints.
• Completeness Report: Details errors of omission, commission, and selection criteria.
• Positional Accuracy: Explicit horizontal and vertical accuracy reports, detailing testing methods, check points, and statistical confidence levels (e.g., NSSDA statements).
• Lineage: An exhaustive chronological log of the data's life cycle. Subdivided into Source Information (original input datasets, scales, and media) and Process Steps (dated descriptions of operations, coordinate transformations, and processing contacts).

Section 3: Spatial Data Organization Information

Defines the computational geometric mechanism used to encode spatial positions:

• Indirect Spatial Reference: Spatial indexing via administrative codes, FIPS codes, street addresses, or geographic names without explicit coordinates.
• Direct Spatial Reference Method: Declares whether spatial entities are represented as Vector (point, string, ring, polygon), Raster (grid cell, pixel dimensions, row/column counts), or Point / TIN.

Section 4: Spatial Reference Information

Provides mathematical parameters required to project and locate coordinates on the Earth:

• Horizontal Coordinate System:
  • Geographic: Latitude and longitude resolution, angular units.
  • Planar: Map projection name (e.g., Transverse Mercator, Lambert Conformal Conic), standard parallels, central meridian, false easting, false northing, or grid system identifier (e.g., SPCS zone code, UTM zone).
  • Geodetic Model: Horizontal datum name (e.g., NAD83), reference ellipsoid name (e.g., GRS80), semi-major axis length, and flattening factor.
• Vertical Coordinate System: Altitude datum name (e.g., NAVD88), depth datum (e.g., Mean Lower Low Water), distance resolution, and linear measurement units.

Section 5: Entity and Attribute Information

Acts as the data dictionary, defining tabular schema, field names, and value domains:

• Detailed Description: Entity type definitions (e.g., Feature Class: Tax_Parcel), followed by exhaustive attribute definitions (e.g., Field: ZONING_CODE).
• Attribute Domain Values: Standardizes allowable data entries using four formal domain structures:
  1. Enumerated Domain: A defined lookup list of pre-approved values and their explicit definitions (e.g., R-1 = Single Family Residential, C-2 = General Commercial).
  2. Range Domain: A minimum and maximum numerical boundary for continuous values (e.g., Building Height between $0$ and $500$ feet).
  3. Codeset Domain: Reference to an external published authority (e.g., FIPS county codes, USGS hydrologic unit codes).
  4. Unrepresentable Domain: Freeform text, names, or values with no pre-definable domain (e.g., property owner names, unique parcel deed descriptions).

Section 6: Distribution Information

Documents how external users acquire the data:

• Distributor Contact: Agency name, address, telephone, email.
• Distribution Liability: Legal disclaimer waiving liability for improper secondary use.
• Standard Order Process: Digital order instructions, supported transfer formats (Shapefile, GeoPackage, File Geodatabase), transfer sizes, and online download URLs.

Section 7: Metadata Reference Information

Documents the currency and authorship of the metadata document itself:

• Metadata Date: The date the metadata record was created or updated.
• Metadata Contact: The individual or organization responsible for authoring the metadata.
• Metadata Standard Name and Version: e.g., FGDC Content Standard for Digital Geospatial Metadata, version FGDC-STD-001-1998.
• Metadata Access Constraints: Security clearance or restrictions governing metadata distribution.

3. Element Conditionality: Mandatory, Mandatory-if-Applicable, and Optional

Every element within the CSDGM hierarchy possesses a strict conditionality rule:

1. Mandatory ($M$): The element must be populated for the metadata record to be structurally valid. Omitting a mandatory element causes automated parser validation to fail. Examples: Dataset Title, Abstract, Purpose, Bounding Coordinates, Metadata Date, Metadata Contact.
2. Mandatory-if-Applicable ($MIA$): The element must be populated if the specific condition or geographic characteristic exists in the underlying dataset. If the condition does not apply, the element is omitted. Examples:
   • If the dataset includes attributes, the Entity and Attribute Information section is mandatory.
   • If coordinate geometry is present, the Spatial Reference Information section is mandatory.
   • If processing steps or source alterations were performed, the Lineage Process Steps elements are mandatory.
   • If access restrictions exist, the Access Constraints explanation is mandatory.
3. Optional ($O$): The element provides valuable context but is not required for standard compliance. Examples: Supplemental Information, Maintenance and Update Frequency, Hours of Service for contact personnel.

---

4. International Standards: the ISO 19115 Family

While CSDGM served the North American community for decades, modern global interoperability demanded an international standard. The International Organization for Standardization Technical Committee 211 (ISO/TC 211) developed the ISO 19115 geographic metadata standard, which has now superseded CSDGM as the preferred architecture across federal and international geospatial agencies.

The ISO 19115 Standard Family

• ISO 19115-1:2014 (Fundamentals): Defines the conceptual model, Unified Modeling Language (UML) class schemas, and data dictionary for general geographic information.
• ISO 19115-2:2019 (Extensions for Imagery and Gridded Data): Extends the core standard to support complex sensor architectures, satellite platforms, instrument characteristics, radiometric calibration, raw telemetry, and digital aerial cameras.
• ISO 19115-3:2023 (XML Schema Implementation): Provides the current modular XML schemas for implementing metadata concepts, using namespaces such as mdb, cit, mri, and mrl.
• ISO 19139:2007 (Legacy XML Implementation): Implemented the older ISO 19115 model and remains common in existing catalogs, but ISO lists it as withdrawn. Treat it as a legacy interchange format rather than the current implementation standard.

Key Architectural Differences: CSDGM vs. ISO 19115 / ISO 19115-3

---

5. Metadata Catalogs, Clearinghouses, and OGC CSW Harvesting

Creating metadata is futile if datasets cannot be found. Spatial Data Infrastructures (SDIs) rely on automated catalog architectures to register and expose metadata records.

The OGC Catalogue Service for the Web (CSW)

The Open Geospatial Consortium (OGC) developed the Catalogue Service for the Web (CSW) standard (OGC 07-006r1 / ISO 19143) to define standard HTTP interfaces for publishing, searching, and querying geospatial metadata across distributed networks.

Key CSW operations include:

• GetCapabilities: Queries the catalog service to discover supported operations, filter parameters, and metadata output formats.
• GetRecords: Executes structured queries against the catalog using spatial bounding boxes, temporal windows, and attribute keyword filters, returning summary or full metadata records.
• GetRecordById: Retrieves a specific metadata document using its unique identifier (UUID).
• Harvest: An automated mechanism allowing a central clearinghouse (such as Data.gov or a state spatial data portal) to periodically crawl remote servers, extract updated metadata records, and index them into a federated catalog.

                      FEDERATED METADATA HARVESTING
                      
   [Municipal GIS Server] ---> (Publishes ISO 19139 XML) ----+
                                                               |
   [County Water District] -> (Publishes OGC CSW Endpoint) ---+--> [State Geospatial Clearinghouse]
                                                               |      (Automated OGC CSW Harvest)
   [State DOT Geoportal] ----> (Publishes Metadata Catalog) --+                 |
                                                                                v
                                                                      [National Data.gov / NSDI]

---

6. GISP Exam Traps & Pitfalls

• Trap: Conflating Dataset Date with Metadata Date: Section 1 (Identification) contains the Time Period of Content (e.g., aerial photography captured on October 12, 2022). Section 7 (Metadata Reference) contains the Metadata Date (e.g., the metadata file was authored or revised on January 15, 2024). Confusing these two dates is a classic exam trick.
• Trap: Misunderstanding Conditionality Rules: Candidates frequently assume that non-mandatory elements can simply be skipped. If an element is Mandatory-if-Applicable, you must populate it whenever the condition exists (e.g., if a dataset has attribute tables, attribute definitions in Section 5 are required for a conformant record when applicable, not merely optional).
• Trap: Abstract vs. Purpose in CSDGM Section 1: The Abstract describes what the dataset contains and its basic geographic coverage. The Purpose explains why the data was created and the specific business requirements or legal mandates that motivated its production. The exam often tests your ability to distinguish an abstract statement from a purpose statement.