Skip to content
View geospatial-compliance's full-sized avatar

Block or report geospatial-compliance

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Geospatial Compliance & Metadata Automation Hub

Geospatial Compliance & Metadata Automation Hub

A technical reference for automating license tracking, metadata generation, catalog synchronization, and compliance validation for spatial datasets.

🌐 www.geospatialcompliance.org

Geospatial compliance is an engineering problem long before it is a legal one. Every dataset a GIS team publishes carries obligations that have to survive automation: a license whose share-alike terms propagate through every derived product, metadata that must validate against ISO 19115 or DCAT-AP before ingestion, attribution that has to be generated — not remembered — and an audit trail that can reconstruct exactly how a figure was produced months later. When any of those steps is manual, compliance drifts, licenses conflict silently, and an audit finds gaps no one can explain.

This site is a deep, code-first reference for the GIS data managers, open-source maintainers, Python automation builders, and government and agency technical teams who build those pipelines. Every article leads with runnable Python and anchors each pattern to the specific obligation it satisfies — SPDX license identifiers, ODbL and Creative Commons compatibility rules, ISO 19115 / FGDC / STAC / DCAT-AP metadata schemas, and CI/CD enforcement gates that keep non-compliant data out of production.

What it covers

The library is organized into four areas, spanning 52 in-depth pages:

Who it's for

  • GIS data managers proving spatial data compliance to auditors and stakeholders.
  • Open-source maintainers who need attribution and license propagation to be automatic and correct.
  • Python automation builders wiring metadata generation and validation into ETL and CI/CD.
  • Government and agency technical teams meeting ISO 19115, FGDC, DCAT-AP, and open-data mandates.

How it's built

A static site generated with Eleventy, authored in Markdown with hand-built inline SVG diagrams, structured data (JSON-LD), and a strict quality bar — every page is validated for accessibility (WCAG 2 AA), structured-data correctness, internal-link integrity, and mobile performance before it ships. The site is deployed on Cloudflare Workers.

npm install
npm run build     # build to _site/
npm run dev       # local preview

License & contributions

The content is published for the geospatial engineering community as a reference resource. Issues and suggestions are welcome via the repository's issue tracker.


Built and maintained by geospatial-compliance · www.geospatialcompliance.org

Popular repositories Loading

  1. geospatial-compliance geospatial-compliance Public

    Automating license tracking, metadata generation, catalog sync, and compliance validation for spatial datasets — www.geospatialcompliance.org

    Nunjucks