ogc-api-troubleshoot

Diagnose OGC API stack issues from container status to data flow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose problems with a local OGC API stack by guiding users through a deterministic triage flow from container uptime to data discovery and CORS configuration.

Core Features & Use Cases

  • Structured, step-by-step triage across the stack (gateway, tipg, PostGIS, seed, admin-app, map-client) to identify where data isn't reaching the browser.
  • Top-down and bottom-up symptom analysis with clear remediation steps and health checks.
  • Use cases include deciding why a map is empty, why a collection isn't listed, or why tipg returns 404, and how to fix CORS or gateway routing.

Quick Start

Walk me through a top-to-bottom triage of the OGC API stack in my local environment to identify the root cause of data not appearing in the browser.

Frequently Asked Questions about ogc-api-troubleshoot

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

FAQPage Schema
Why is my OGC API map empty and how do I triage the stack?

To triage an empty OGC API map, run a structured diagnostic workflow checking container uptime, service health, database schemas, tipg catalog state, and CORS configuration to identify where data fails to reach the browser.

How do I fix CORS errors when connecting to my tipg OGC API?

Fix CORS errors by inspecting the nginx gateway configuration and tipg service health within the OGC API stack, verifying routing rules and headers to ensure the browser receives proper cross-origin permissions.

Why does tipg return a 404 for a missing collection in PostGIS?

tipg returns a 404 for missing collections when the PostGIS database schema lacks the expected tables or the tipg catalog state fails to recognize them, requiring a bottom-up schema and catalog verification.

What is the best way to diagnose an OGC API admin app connection failure?

The best way to diagnose an admin app connection failure is a top-down triage checking the nginx gateway routing, seed container uptime, and tipg service health to pinpoint the broken data flow link.

Can I use this triage workflow for a local PostGIS and nginx gateway stack?

Yes, this triage workflow applies directly to a local OGC API stack, running deterministic health checks across PostGIS, the nginx gateway, seed container, and tipg to safely guide recovery steps.

What should I do when OGC API data is not reaching the browser?

When OGC API data is not reaching the browser, execute a layer-by-layer diagnostic workflow starting from container status down to gateway behavior and database schemas to isolate and resolve the blockage.