Example Collections

The examples in this repository are reference STAC collections for the Monty API and the fixtures the CI pipeline validates documentation against.

Collections

Grouped by Monty type; each links to its example directory on GitHub. This listing is generated from sources.yml — the single source of truth described on the Data Sources page — and included here verbatim, so adding a collection there surfaces it on this page automatically.

Events

• alerthub-events — AlertHub
• cems-events — Copernicus Emergency Management Service — Rapid Mapping
• charter-events — International Charter on Space and Major Disasters
• desinventar-events — DesInventar
• emdat-events — EM-DAT
• gdacs-events — GDACS
• gfd-events — Global Flood Database (GFD)
• glide-events — GLIDE
• ibtracs-events — IBTrACS
• idmc-gidd-events — IDMC — Global Internal Displacement Database (GIDD)
• idmc-idu-events — IDMC — Internal Displacement Updates (IDU)
• ifrcevent-events — IFRC DREF
• pdc-events — Pacific Disaster Center (PDC)
• reference-events — Reference Events
• usgs-events — USGS Earthquake Catalog

Hazards

• alerthub-hazards — AlertHub
• cems-hazards — Copernicus Emergency Management Service — Rapid Mapping
• charter-hazards — International Charter on Space and Major Disasters
• emdat-hazards — EM-DAT
• gdacs-hazards — GDACS
• gfd-hazards — Global Flood Database (GFD)
• glide-hazards — GLIDE
• ibtracs-hazards — IBTrACS
• ifrcevent-hazards — IFRC DREF
• pdc-hazards — Pacific Disaster Center (PDC)
• usgs-hazards — USGS Earthquake Catalog

Impacts

• cems-impacts — Copernicus Emergency Management Service — Rapid Mapping
• desinventar-impacts — DesInventar
• emdat-impacts — EM-DAT
• gdacs-impacts — GDACS
• gfd-impacts — Global Flood Database (GFD)
• idmc-gidd-impacts — IDMC — Global Internal Displacement Database (GIDD)
• idmc-idu-impacts — IDMC — Internal Displacement Updates (IDU)
• ifrcevent-impacts — IFRC DREF
• pdc-impacts — Pacific Disaster Center (PDC)
• usgs-impacts — USGS Earthquake Catalog

Response

• cems-response — Copernicus Emergency Management Service — Rapid Mapping
• charter-response — International Charter on Space and Major Disasters

How the examples are used

The example collections serve two important purposes:

1. Reference Collections for Monty API
2. Collection Documentation Validation

Reference Collections for Monty API

The example collections in this repository serve as reference implementations for the Monty API. They demonstrate:

• Proper STAC collection structure for various data sources
• Correct implementation of the Monty extension
• Valid use of field values and data types
• Relationships between different types of data (events, hazards, impacts)

Each data source has its own set of collections:

1. Events Collections

   • Define disaster events from various sources
   • Example: Reference Events Collection
   • Used for event correlation and data integration

2. Hazards Collections

   • Contain hazard-specific data
   • Example: GDACS Hazards Collection
   • Define severity, intensity, and other hazard characteristics

3. Impacts Collections

   • Document the effects of hazards
   • Example: IDMC GIDD Impacts Collection
   • Track casualties, displacement, and other impact metrics

Collection Documentation Validation

The example collections play a crucial role in the CI/CD workflow:

1. Schema Validation

   • Examples are validated against the JSON Schema
   • Ensures compliance with the STAC specification
   • Verifies Monty extension requirements

2. Documentation Testing

   • Examples are used to test documentation accuracy
   • Verify that documentation reflects actual implementation
   • Ensure examples are in sync with schema changes

3. Integration Testing

   • Used to test the Monty API's ability to:
     • Parse different collection types
     • Handle various data structures
     • Maintain relationships between items

CI/CD Process

The validation process in the CI/CD workflow:

graph TD
    A[Push to Repository] --> B[Validate JSON Schema]
    B --> C[Test Example Collections]
    C --> D[Check Documentation]
    D --> E[Generate API Documentation]
    E --> F[Deploy if All Tests Pass]

    B -- Fail --> G[Report Schema Errors]
    C -- Fail --> H[Report Collection Errors]
    D -- Fail --> I[Report Doc Inconsistencies]