stac-navigation

Traverse STAC catalogs to determine dataset availability across root and sub-collections.

4|1|Updated Feb 24, 2026

Search Tags:#data-management #dataset-discovery #stac #web-links #catalog-navigation #stac-browser

Ready to run

npx skills add https://github.com/boettiger-lab/agent-skills --skill stac-navigation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stac-navigation
Source: https://github.com/boettiger-lab/agent-skills/tree/main/stac-navigation
Command: npx skills add https://github.com/boettiger-lab/agent-skills --skill stac-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps determine dataset availability in STAC catalogs by exhaustively traversing the catalog tree, preventing premature conclusions of missing data.

Core Features & Use Cases

Decode STAC Browser URLs to reveal underlying JSON endpoints and fetch catalogs in a safe order.
Follow the prescribed navigation order (root, then child links, while validating parents) to locate datasets and verify presence across root and sub-collections.
Use cases include verifying catalog completeness before data analysis, auditing datasets across STAC endpoints, and ensuring correct data provenance in geospatial projects.

Quick Start

Fetch the root STAC catalog, enumerate all child links, and walk into sub-collections as needed to locate the target dataset.

Frequently Asked Questions about stac-navigation

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

FAQPage Schema

How do I traverse a STAC catalog to verify dataset availability?▼

To traverse a STAC catalog and verify dataset availability, fetch the root catalog, enumerate all child links, and walk into sub-collections. This exhaustive traversal prevents premature conclusions of missing data.

Why does my STAC catalog traversal miss sub-collections?▼

STAC catalog traversal misses sub-collections when link-following is incomplete. You must follow the prescribed navigation order—root first, then child links, while validating parents—to ensure comprehensive discovery across the entire catalog tree.

What is the correct navigation order for walking STAC catalog links?▼

The correct navigation order for STAC catalog links starts at the root catalog, proceeds to child links, and validates parent relationships. Following this STAC-relations guidance ensures robust link-following behavior and complete dataset discovery.

Can I decode a STAC Browser URL to fetch the underlying catalog JSON endpoint?▼

Yes, you can decode STAC Browser URLs to reveal underlying JSON endpoints. This allows you to fetch STAC catalogs in a safe order and begin the traversal process from the root catalog down to sub-collections.

When do I need to exhaustively traverse a STAC catalog tree?▼

You need to exhaustively traverse a STAC catalog tree when verifying catalog completeness before data analysis, auditing datasets across endpoints, or ensuring correct data provenance in geospatial projects to prevent missing data.