Planet makes available select imagery for major disaster events, including major earthquakes, floods, storms, wildfires, and human-made disasters. These are available here in a STAC Catalog under a CC-BY-NC license. See the Planet Disaster Data page for more information.
You are looking at a Portolan / STAC collection (collection.json, STAC 1.1.0, Portolan profile v0.1.0) — inside Disaster Data Releases from Planet Labs PBC: Planet Crisis Response imagery for major disaster events.
PlanetScope PSB.SD imagery acquired 11 August 2026 at 16:04 UTC over the Quindío coffee axis on the western flank of the Cordillera Central — Armenia, Calarcá, Circasia, Montenegro, Quimbaya and La Tebaida — roughly 70 km east-south-east of the epicentre. Two consecutive scenes from a single strip (satellite 252e, strip 8956803) form one continuous north-east to south-west swath running from the valley floor up to the Los Nevados massif. Acquisition is near-nadir (2.8 degrees off-nadir) with a high 71 degree sun elevation, so building lean and shadowing are minimal. 89% of this footprint was already imaged by the 10 August PlanetScope pass, so the collection pairs with planetscope-2026-08-10 for same-sensor 24-hour change detection at 3 m, as well as against the near-nadir Q2 2026 basemap. Cloud is low but not absent: 9% and 7% cloud with a further 4% and 1% light haze, leaving 83% and 89% of the two scenes clear. Almost all of it sits along the eastern, higher-elevation edge of the swath over the cordillera flank, so the populated valley floor is effectively clear — check the UDM2 before radiometric work or automated change detection. Visual and surface-reflectance (analytic_sr + UDM2) products support landslide and damage mapping across the steep, wet coffee-growing slopes. 2 scenes; each Item carries the available visual, analytic_sr, udm2 assets.
Everything is plain HTTPS — no credentials, no signing, no request-payer.
Two caveats worth knowing before you write a fetch loop:
Python-urllib User-Agent. Send a
browser or curl UA if you use urllib; requests, curl, GDAL/rasterio, rio-tiler and
DuckDB all work as-is.aws s3 ls; navigate the STAC
links instead — every object links to its parent, children and items.Each collection publishes a STAC-GeoParquet mirror of its items — one row per item, with geometry and all properties. Query it directly, no download:
That is almost always faster than walking the rel:"item" links, which are there for
STAC clients and for humans clicking through the browser.
Every raster is a cloud-optimized GeoTIFF, so read the window you need rather than the file:
Asset keys on each item (visual used above):
visual — Visual (true-colour RGB) ortho COG (roles: data, visual)analytic_sr — Analytic 4-band surface-reflectance ortho COG (roles: data, reflectance)udm2 — Usable Data Mask (UDM2) — per-pixel quality (roles: data, snow-ice, cloud, cloud-shadow)thumbnail — Thumbnail (roles: thumbnail)file:size and file:checksum (sha256 multihash, 1220-prefixed) so a download can be verified.proj:code.