Geospatial Data Standards: OGC, ISO, and US Federal Requirements

Geospatial data standards govern how spatial information is defined, encoded, exchanged, and integrated across organizations, software platforms, and government systems. Three primary standards regimes shape the US landscape: the Open Geospatial Consortium (OGC) technical specifications, the ISO/TC 211 geographic information standards family, and federal requirements issued through bodies including the Federal Geographic Data Committee (FGDC) and the National Geospatial-Intelligence Agency (NGA). Compliance with these frameworks affects procurement eligibility, interoperability with federal datasets, and the legal defensibility of spatial data products used in infrastructure, emergency management, and environmental monitoring.

• Definition and scope
• Core mechanics or structure
• Causal relationships or drivers
• Classification boundaries
• Tradeoffs and tensions
• Common misconceptions
• Checklist or steps
• Reference table or matrix
• References

Definition and scope

Geospatial data standards are formal specifications that define how geographic features, coordinate reference systems, metadata, and spatial services behave in interoperable environments. They operate at multiple levels: schema standards define data models, encoding standards define serialization formats, service standards define API behavior, and metadata standards define discovery and lineage documentation.

The Federal Geographic Data Committee (FGDC) serves as the primary US interagency body responsible for coordinating geospatial data standards across civilian federal agencies, as established under OMB Circular A-16. The FGDC's mandate was reinforced by the Geospatial Data Act of 2018 (Title VII of Public Law 115-254), which formalized agency responsibilities for spatial data collection, standardization, and public access through The Geospatial Platform.

The Open Geospatial Consortium (OGC) produces consensus-based international technical standards for spatial data services and encodings. ISO/TC 211, the ISO technical committee for geographic information and geomatics, maintains a parallel family of more than 60 published standards, many of which are harmonized with OGC specifications. Both bodies produce standards that are referenced — and in federal contexts often mandated — by procurement regulations, agency policy, and data-sharing agreements.

The scope of these standards reaches into spatial data management, GIS platform selection, and enterprise GIS implementation, where interoperability between vendor systems and federal data repositories is a procurement requirement rather than an optional design consideration.

Core mechanics or structure

OGC Standards Architecture

OGC standards are organized into abstract specifications, implementation standards, and community standards. The most operationally significant include:

• WMS (Web Map Service, OGC 06-042): Delivers rendered map images over HTTP; does not expose raw feature geometry.
• WFS (Web Feature Service, OGC 09-025r2): Delivers vector feature data with full geometry access; supports transactional operations.
• WCS (Web Coverage Service, OGC 17-089r1): Delivers raster or gridded coverage data including elevation, satellite imagery, and climate grids.
• WMTS (Web Map Tile Service, OGC 07-057r7): Pre-rendered tile delivery optimized for web mapping clients.
• OGC API standards: A next-generation family built on OpenAPI 3.0, including OGC API – Features (the successor to WFS), OGC API – Tiles, and OGC API – Maps.
• GML (Geography Markup Language, OGC 07-036): XML-based encoding for geographic features; basis for many government data exchange formats.
• KML (OGC 07-147r2): XML-based format for geographic visualization, originally developed by Google and adopted as an OGC standard in 2008.

ISO/TC 211 Standards Architecture

ISO geographic information standards are numbered in the 19100 series. Foundational standards include:

• ISO 19101: Reference model establishing conceptual framework for geographic information.
• ISO 19103: Conceptual schema language.
• ISO 19111: Spatial referencing by coordinates — the basis for coordinate reference system (CRS) definitions.
• ISO 19115 / ISO 19115-1:2014: Metadata schema for geographic datasets; directly referenced in FGDC metadata requirements.
• ISO 19139: XML implementation schema for ISO 19115 metadata.
• ISO 19157: Data quality principles and evaluation procedures.

US Federal Standards

The FGDC publishes the Geospatial Metadata Standards framework, which includes the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) and its successor alignment with ISO 19115. The National Geospatial-Intelligence Agency (NGA) issues additional standards through the NGA Standardization Documents program, including standards for coordinate reference systems (NGA.STND.0036) and imagery formats used in defense and intelligence contexts.

Causal relationships or drivers

The proliferation of geospatial standards across multiple bodies results from distinct institutional drivers operating in parallel rather than in coordination.

Federal data-sharing mandates created demand for machine-readable metadata before ISO 19115 was mature, which led FGDC to publish the CSDGM in 1994. When ISO 19115 was finalized in 2003, the US government maintained both systems for over a decade, producing a dual-standard environment that still affects legacy dataset discovery.

Defense and intelligence requirements drove NGA to maintain separate coordinate reference system and imagery standards aligned with NATO STANAG specifications. The transition from the North American Datum 1983 (NAD83) to the World Geodetic System 1984 (WGS84)-aligned frameworks, and eventually to geometric reference frames compatible with the International Terrestrial Reference Frame (ITRF), introduced persistent datum transformation requirements in civilian-federal data exchange.

Commercial web mapping growth accelerated OGC's development of REST-based API standards. The dominant commercial tile scheme — the "XYZ" or Slippy Map format used by platforms including OpenStreetMap — was not an OGC standard but became so prevalent that OGC API – Tiles was drafted partly in response. This reflects how commercial practice can drive standards bodies rather than the reverse.

Geospatial Data Act compliance requires federal agencies to document spatial data assets in a manner consistent with FGDC standards. Agencies must publish metadata to GeoPlatform.gov and align with the National Spatial Data Infrastructure (NSDI) framework, creating regulatory pressure on data producers across all 50 states that receive federal grant funding tied to spatial data deliverables.

Classification boundaries

Geospatial standards divide into five functional categories with distinct scopes and non-overlapping domains:

1. Coordinate Reference System (CRS) Standards: Define how coordinates map to real-world positions. ISO 19111 and its OGC alignment (OGC Abstract Specification Topic 2) define CRS components. EPSG codes — maintained by IOGP (International Association of Oil and Gas Producers) — serve as the de facto registry. NAD83 (EPSG:4269) and WGS84 (EPSG:4326) are the most frequently referenced in US federal work.

2. Data Encoding Standards: Define serialization formats. GML, GeoJSON (IETF RFC 7946), Shapefile (Esri specification, de facto standard), GeoPackage (OGC 12-128r18), and FlatGeobuf represent distinct encoding families. GeoJSON is not an OGC standard; it is maintained by the IETF.

3. Service Interface Standards: Define how spatial services expose data over networks. OGC WMS, WFS, WCS, WMTS, and OGC API standards are the primary service specifications. INSPIRE Directive service specifications in the EU share OGC foundations but add European-specific requirements.

4. Metadata Standards: Define discovery, lineage, and quality documentation. ISO 19115-1:2014 and ISO 19139:2007 (XML implementation) are the current international baseline. FGDC CSDGM remains active for legacy US federal datasets.

5. Quality and Accuracy Standards: Define how spatial accuracy, completeness, and logical consistency are measured and reported. ISO 19157:2013 is the primary international framework. The National Standard for Spatial Data Accuracy (NSSDA) provides the US federal methodology for positional accuracy reporting.

Tradeoffs and tensions

The relationship between OGC standards, ISO standards, and US federal requirements is not fully harmonized, producing operational friction in three areas.

CSDGM versus ISO 19115: FGDC formally endorsed ISO 19115 adoption for federal agencies, but FGDC guidance acknowledges that the CSDGM remains widely used in existing systems. The two schemas do not map cleanly to each other — the CSDGM's mandatory elements do not correspond 1:1 with ISO 19115 mandatory elements — meaning automated crosswalks lose information in both directions.

GML versus GeoJSON: GML is the formally standardized OGC encoding and is required for WFS 2.0 compliance. GeoJSON (IETF RFC 7946) has become the dominant web API encoding due to its simplicity and native JSON structure. GML's verbosity creates performance problems at scale; GeoJSON's limited coordinate precision (double-precision floating point) and lack of native CRS flexibility create accuracy constraints in high-precision applications. Neither standard fully satisfies both web developer and precision surveying communities simultaneously.

OGC REST APIs versus legacy XML services: The OGC API family is architecturally incompatible with the WMS/WFS/WCS service family. Organizations maintaining production infrastructure built on WMS and WFS must run parallel service stacks to support both legacy consumers and modern REST clients. The mapping technology stack implications are significant for agencies with long procurement cycles.

Datum epoch management: The adoption of time-dependent reference frames (ITRF2020, NAD83(2011) epoch-adjusted) means that a single latitude/longitude pair without an explicit epoch and CRS declaration is technically ambiguous at the millimeter-to-centimeter level — an operationally significant gap in applications including lidar mapping, autonomous vehicle positioning, and utility infrastructure mapping.

Common misconceptions

Misconception: WGS84 and NAD83 are the same coordinate system.
WGS84 (EPSG:4326) and NAD83 (EPSG:4269) differ by up to approximately 1 meter depending on location and epoch. For most web mapping applications the difference is negligible, but for mapping data accuracy and validation in survey-grade or infrastructure contexts, treating them as interchangeable introduces errors that exceed standard positional accuracy thresholds.

Misconception: An OGC-compliant service guarantees interoperability.
OGC conformance testing (OGC CITE testing framework) verifies that a service implements the standard's required operations. It does not validate the semantic consistency of the data, the accuracy of coordinate transformations, or the completeness of attribute schemas. Two OGC-compliant WFS services can return geometrically inconsistent results if they use different source datums without declaring them.

Misconception: ISO 19115 metadata is only required for federal datasets.
State and local agencies receiving federal grant funding for spatial data programs — including those under FEMA's Hazard Mitigation Grant Program and USGS National Geospatial Program cooperative agreements — are typically required by grant terms to deliver data conforming to FGDC/ISO 19115 metadata standards. This extends the requirement well beyond direct federal agency data production.

Misconception: GeoJSON is an OGC standard.
GeoJSON is an IETF standard (RFC 7946, August 2017), maintained by the Internet Engineering Task Force, not the OGC. OGC references GeoJSON in its API standards but does not govern its specification.

Misconception: Shapefile is a standard.
The Shapefile format is an Esri proprietary specification published as a technical description document. It is not an OGC, ISO, or FGDC standard. Its near-universal adoption in the geospatial industry reflects market dominance, not formal standardization. GeoPackage (OGC 12-128r18) was developed specifically to provide an open, standards-based alternative for vector and raster data exchange.

Checklist or steps

The following sequence describes the conformance verification phases applied when a spatial data product or service is assessed for compliance with OGC, ISO, and US federal requirements.

Phase 1 — CRS Declaration Audit
- Confirm that all datasets carry an explicit CRS declaration (EPSG code or WKT definition).
- Verify datum name, ellipsoid, and epoch are documented where positional accuracy requirements apply.
- Confirm projection parameters for projected CRS datasets (e.g., State Plane, UTM zone).

Phase 2 — Metadata Schema Validation
- Identify whether FGDC CSDGM or ISO 19115-1:2014 (via ISO 19139 XML) is the governing metadata schema.
- Validate against schema using FGDC's Metadata Parser (mp) for CSDGM or an ISO 19139 schema validator for ISO metadata.
- Check mandatory elements: dataset title, abstract, publication date, originator, geographic extent, and projection information.

Phase 3 — Encoding Format Verification
- Confirm encoding format against delivery specification (GeoPackage, GML, GeoJSON, Shapefile).
- For OGC API – Features deployments, verify responses conform to OGC API – Features Core Part 1 (OGC 17-069r4) via the CITE test suite.

Phase 4 — Service Interface Conformance Testing
- Submit WMS, WFS, or OGC API services to OGC CITE automated testing for the applicable standard version.
- Document test run outputs and retain passing test certificates for procurement or audit records.

Phase 5 — Positional Accuracy Reporting
- Apply NSSDA methodology to compute Root Mean Square Error (RMSE) at the 95% confidence level.
- Document accuracy statistics in dataset metadata per FGDC NSSDA reporting format.

Phase 6 — GeoPlatform Registration (federal datasets)
- Register dataset metadata to GeoPlatform.gov per FGDC submission requirements.
- Assign dataset to the applicable NSDI Theme category.

Reference table or matrix