load-gis-data

Ingest GIS datasets into PostGIS via seed workflow and ogr2ogr commands.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/ogc-maps/storybook-components --skill load-gis-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: load-gis-data
Source: https://github.com/ogc-maps/storybook-components/tree/main/.claude/skills/load-gis-data
Command: npx skills add https://github.com/ogc-maps/storybook-components --skill load-gis-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamline the ingestion of GIS data into the project's PostGIS database and publish it through the tipg OGC API via /collections, handling CRS reprojection, schema selection, indexing, and restart-based catalog refresh.

Core Features & Use Cases

  • Ingest multiple GIS formats (Shapefile, GeoPackage, GeoJSON, FlatGeobuf, KML, CSV with WKT) into PostGIS
  • Reproject to EPSG:4326 and enforce schema compatibility so data appears in the correct place
  • Make new collections visible by restarting tipg and updating TIPG_DB_SCHEMAS as needed

Quick Start

Place your GIS data into GISData/ and run the seed workflow to ingest it into PostGIS and publish it via tipg.

Frequently Asked Questions about load-gis-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ingest Shapefile and GeoJSON data into a PostGIS database?

To ingest Shapefile or GeoJSON into PostGIS, place your files in GISData/ and run the seed workflow, which uses ogr2ogr commands to load data, reproject to EPSG:4326, and enforce schema alignment.

What is the best way to publish PostGIS collections through an OGC API?

Publishing PostGIS collections through an OGC API is best handled by ingesting data via the seed workflow and exposing it through tipg, making new collections visible by restarting tipg and updating the TIPG_DB_SCHEMAS environment variable.

Does this GIS data ingestion workflow support KML and FlatGeobuf formats?

Yes, the GIS data ingestion workflow supports KML and FlatGeobuf formats, alongside Shapefile, GeoPackage, GeoJSON, and CSV files containing WKT geometry, ensuring all are reprojected to EPSG:4326.

Why are my newly ingested PostGIS collections not showing up in tipg?

Newly ingested PostGIS collections may not appear in tipg because the service requires a restart to refresh the catalog, and you may also need to update the TIPG_DB_SCHEMAS environment variable to include the new schema.

Can I use CSV files with WKT geometry for PostGIS data ingestion?

Yes, you can use CSV files containing WKT geometry for PostGIS data ingestion, as the seed workflow supports this format alongside Shapefile, GeoPackage, GeoJSON, FlatGeobuf, and KML for database loading.