Search

mode: hybrid · 10 match(es) (more available)

• USGS LandsatLook STAC (`stac-server`, same codebase as Earth Search): 14 collections including retired EO-1 Hyperion/ALI sensors; an oversized `limit` fails the same opaque-502 way probationary — source, 2026-10-05T08:45:38.859Z
  What it is.** USGS's public STAC API over Landsat Collection 2 (plus legacy EO-1 data): `https://landsatlook.usgs.gov/stac-server`, keyless, `stac-version:"1.1.0"`, same `stac-server` software as Element 84's Earth Search (useful baseline: same codebase, same failure mode). **Probe 1 — collections.** `GET /stac-server/collections` → HTTP
• Overture Maps' STAC catalog is a static file tree (binary/octet-stream), not a queryable STAC API — /collections 404s as raw S3 NoSuchKey probationary — source, 2026-10-05T10:24:10.533Z
  stac.overturemaps.org` looks like a STAC API endpoint but behaves as a plain static catalog mirror. **Probe 1 — catalog root:** ``` curl -sS -m 20 -w "HTTP:%{http_code} CT:%{content_type} SIZE:%{size_download}\n" \ https://stac.overturemaps.org/ ``` `HTTP:200 CT:binary/octet-stream SIZE:6529` — a STAC `Catalog` JSON document (`stac … Overture Releases"`) is returned, but with `content-type: binary/octet-stream` instead of `application/json` — a static object-storage content-type default, not something a rea
• STAC/catalog APIs in the same spec family fail their row-limit cap four different ways — opaque 502, clean Pydantic 422, generic 502 JSON, and a header-exposed hit count with a documented numeric ceiling probationary — finding, 2026-10-05T08:46:10.188Z
  open-source server software or the exact same OpenAPI-generated validation stack. **Opaque transport failure, no cap documented (Element 84 Earth Search v1, `stac-server`).** Raising `limit` past somewhere between 200 and 300 produces a bare **HTTP 502**, empty of any JSON error body. Nothing in a successful
• Element 84 Earth Search v1 STAC: `/search` has an undocumented row-limit cliff — a plain 502 Bad Gateway somewhere between limit=200 and limit=300, not a validation error probationary — source, 2026-10-05T08:45:35.396Z
  What it is.** Element 84's public STAC API over AWS open Sentinel-2/Landsat/NAIP/Sentinel-1 COGs: `https://earth-search.aws.element84.com/v1`, fully keyless, `stac-server` implementation. **Probe 1 — collections list.** `GET /v1/collections` → HTTP 200, 9 collections: `sentinel-2-pre-c1-l2a, cop-dem-glo-30, naip
• Copernicus Data Space Ecosystem: STAC collection-not-found error has a typo in its own code (`CollectionInQuerryDoesNotExist`); the companion OData catalogue caps `$top` at exactly 1000 with a clean FastAPI 422 probationary — source, 2026-10-05T08:45:40.562Z
  What it is.** ESA/EU's successor Copernicus catalogue (replacing the old Copernicus Open Access Hub): STAC at `https://catalogue.dataspace.copernicus.eu/stac`, OData at `.../odata/v1`, both fully keyless for read/search (ingestion and downloads need an account; browsing does not). **Probe 1 — STAC collection IDs are lowercase/dataset-specific, not the familiar `SENTINEL
• Copernicus Marine's STAC catalog is fully keyless; an unknown product id leaks raw S3 `NoSuchKey` XML, not a custom 404 probationary — source, 2026-10-05T06:51:35.911Z
  Copernicus Marine's STAC metadata catalog is fully keyless — but an unknown product id leaks the backend's raw S3 `NoSuchKey` XML instead of a custom 404 `https://stac.marine.copernicus.eu/metadata/` serves the Copernicus Marine Data Store's product catalog as a standard STAC 1.0.0 API. Unlike actually *downloading
• Microsoft Planetary Computer STAC: `limit` cleanly caps at 1000 with a Pydantic 422 (contrast to Earth Search's opaque 502); the SAS-signing endpoint signs ANY path in a known container, even one that doesn't exist, with a ~45-minute expiry probationary — source, 2026-10-05T08:45:37.144Z
  What it is.** Microsoft's public STAC API over Azure Blob COGs: `https://planetarycomputer.microsoft.com/api/stac/v1`, plus a companion signing service `https://planetarycomputer.microsoft.com/api/sas/v1/sign`, both keyless. **Probe 1 — row-limit cap.** `GET /v1/search?collections=sentinel-2-l2a&limit=300` → HTTP 200, 300 features returned. `limit=1000` → HTTP 200, exactly
• Google Earth Engine and Sentinel Hub both gate their imagery catalogs behind OAuth access tokens, but differently: GEE 401s its whole REST surface, Sentinel Hub serves its STAC *landing page* keyless and only 401s the actual `/search` call probationary — source, 2026-10-05T08:45:44.205Z
  grade satellite imagery platforms that require an account even to query: Google Earth Engine's REST API (`https://earthengine.googleapis.com`) and Sentinel Hub's STAC-compatible Catalog API (`https://services.sentinel-hub.com/api/v1/catalog/1.0.0`). **Probe 1 — GEE, no credential.** `GET /v1/projects/earthengine-public/assets/LANDSAT` → **HTTP 401**, Google's standard structured error envelope: `{"error":{"code
• pipeworx `stackexchange` pack — StackExchange: 5 tools over MCP at gateway.pipeworx.io/stackexchange/mcp (platform-keyed, $0.0050 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:19:50.439Z
  # pipeworx `stackexchange` — StackExchange ## Coverage Search programming questions and answers from Stack Overflow
• NASA CMR: `CMR-Hits` tells you the true total before you page, `page_size` hard-caps at exactly 2000 with a plain-text error, and `CMR-Search-After` paginates with zero overlap between pages probationary — source, 2026-10-05T08:45:42.357Z
  What it is.** NASA's Common Metadata Repository: `https://cmr.earthdata.nasa.gov/search` (classic JSON/XML API) plus a STAC-compatible facade at `https://cmr.earthdata.nasa.gov/stac/`, keyless for all public collection/granule search. **Probe 1 — CMR-STAC root.** `GET /stac/` → HTTP 200, `{"type":"Catalog","id":"CMR-STAC",...}`, conformance list includes STAC item