Collections

The curated catalogue of collections exposed by the ADAM API today. The authoritative list is always the live /api/collections endpoint — this page is a reading guide on top of it.

Current count: 13 collections across three hazard modules plus their supporting geometry layers.

Earthquakes

adam.adam_eq_events

Point features, one per monitored earthquake. Upstream data from GDACS and USGS.

Typical properties include magnitude, depth, event date, source. Features carry dynamic fields linking to ShakeMap rasters, population impact tables and shapefile bundles — see Fetch Event Outputs.

Floods

Four complementary collections covering observed events, live alerts, seasonal forecasts and hydrological gauge predictions.

adam.adam_fl_events

Polygon features, one per observed flood event. Satellite-derived footprint within 72h of onset; weekly updates for long-duration episodes.

adam.adam_fl_alerts

Active flood alerts. Near real-time trigger stream derived from upstream forecast systems.

adam.adam_fl_alerts_mom_forecast

Seasonal flood forecast alerts — longer-range outlooks used for anticipatory action.

adam.adam_fl_glofas_gauges_forecast

GLOFAS hydrological gauge forecasts. Point features at gauge locations with time-series predictions.

Tropical Storms

The richest module: events plus multiple geometry layers (tracks, buffers, nodes) and a parallel "disturbance" set for developing systems that have not yet been classified as named storms.

Primary event geometries

• adam.adam_ts_events — one feature per tracked cyclone; carries dynamic fields to rainfall rasters, population impact tables, WFP facility exposure reports
• adam.adam_ts_tracks — line geometries, one per forecast/analysed track
• adam.adam_ts_buffers — polygon impact zones around the tracks (typically categorised by wind speed)
• adam.adam_ts_nodes — point geometries at each forecast time step along a track

Disturbance (pre-classification) variants

Same geometry breakdown for disturbances — weather systems that may become named storms:

• adam.adam_ts_disturbance_events
• adam.adam_ts_disturbance_tracks
• adam.adam_ts_disturbance_buffers
• adam.adam_ts_disturbance_nodes

Using a collection

Every collection supports the same uniform set of operations. Pick the collection id, then:

• Inspect metadata → GET /collections/{id}
• Discover filterable fields → GET /collections/{id}/queryables
• Query features → GET /collections/{id}/items with bbox/datetime/filter (see Query Features)
• Render on a map → Display on a Map
• Drill into a single event → GET /collections/{id}/items/{itemId} and follow dynamic fields (see Fetch Event Outputs)

When the catalogue changes

Collections may be added, removed, or renamed as ADAM evolves. Treat this page as a snapshot; for anything programmatic, call /collections at runtime and read the id list from there rather than hard-coding it.