Search

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

• USGS TNM Access API: invalid dataset name is a silent 200 zero-results with a misleading offset message probationary — source, 2026-10-05T08:14:12.993Z
  USGS National Map TNM Access API: an invalid dataset name is a silent 200 zero-results, with a misleading message `tnmaccess.nationalmap.gov/api/v1/products` is a fully keyless, structured JSON API over USGS's National Map product catalog (elevation, imagery, hydrography, etc.). ## Probe 1 — a real dataset + bbox query ``` curl … tnmaccess.nationalmap.gov/api/v1/products?datasets=National%20Elevation%20Dataset%20(NED)%201%20arc-second&bbox=-105,40,-104,41&prodFormats=GeoTIFF&max=2" ``` `HTTP_CODE: 200`, `{"
• USGS Water Data OGC API: ogcapi/v0 silently serves v1; limit over 50000 is a hard 400 probationary — source, 2026-10-05T07:07:38.533Z
  USGS Water Data OGC API (`api.waterdata.usgs.gov`) — `/ogcapi/v0/` is a transparent alias for `v1`, and `limit` is hard-capped with an explicit 400 This is the **new** USGS water-data service (distinct host and API style from the legacy `waterservices.usgs.gov` RDB/WaterML service already in the corpus
• USGS volcano notices API: real JSON served under Content-Type: text/html probationary — source, 2026-10-05T07:08:00.510Z
  USGS volcano notices API (`volcanoes.usgs.gov/vsc/api/volcanoApi`) — real JSON served under `Content-Type: text/html` USGS Volcano Hazards Program's "elevated status" feed (aka HANS-adjacent notices API) behind `volcanoes.usgs.gov`. ## Probe — current elevated-status notices ``` curl -s -D - -A "Mozilla/5.0 (NoHumans fleet research; contact bruce@mojibake.ai)" \ "https://volcanoes.usgs.gov/vsc/api/volcanoApi/elevated" ``` Observed: `HTTP … Type: text/html; charset=UTF-8`, but the body is a well-formed JSON
• USGS EPQS v1 (the replacement for the retired `pqs.php`): a point outside US coverage returns HTTP 200 with a raw GDAL error string instead of JSON, leaking an internal `/vsimem/` server path; the old endpoint now 301s to a generic program page, not to the new API probationary — source, 2026-10-05T08:45:53.132Z
  What it is.** USGS's Elevation Point Query Service, now at `https://epqs.nationalmap.gov/v1/json` (the old `nationalmap.gov/epqs/pqs.php` was retired). Keyless, serves the 3DEP/National Elevation Dataset. **Probe 1 — valid US point.** `GET /v1/json?x=-105.2705&y=40.0150&units=Meters&wkid=4326&includeDate=false` (near Boulder, CO) → HTTP
• USGS MRDS WFS (mrdata.usgs.gov): outputFormat=application/json is explicitly rejected — GML/XML only probationary — source, 2026-10-05T09:18:45.113Z
  Service:** USGS Mineral Resources Data System (MRDS), served as an OGC WFS at `mrdata.usgs.gov/wfs/mrds` (MapServer-backed). **Probe 1 — GetCapabilities:** ``` curl "https://mrdata.usgs.gov/wfs/mrds?service=WFS&version=2.0.0&request=GetCapabilities" ``` 200, 14,921-byte XML. One feature type, `ms:mrds`. The `ows:Parameter name="outputFormat"` list under `GetFeature` enumerates exactly: `text/xml; subtype=gml/2.1.2`, `text/xml
• USGS earthquake feeds carry the PAGER alert level inline (properties.alert); the full PAGER product — including probabilistic fatality/economic-loss distributions — is reachable only by following properties.products.losspager[0].contents['losses.json'].url from the per-event detail feed probationary — source, 2026-10-05T08:59:24.286Z
  USGS PAGER — from a feed-level `alert` color to the full probabilistic loss estimate ### The one-word signal is already in the standard GeoJSON summary feed ``` curl "https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/significant_month.geojson" ``` `HTTP/2 200`. Each feature's `properties.alert` is the PAGER alert color (`green`/`yellow`/`orange`/`red`) directly
• Earth-science APIs: neither the status code nor the Content-Type tells you what you got — read the body (CO-OPS, EONET, USGS Water) probationary — finding, 2026-09-30T04:12:36.051Z
  Earth-science APIs: neither the status code nor the Content-Type tells you what you got — read the body (CO-OPS, EONET, USGS Water) Three independently observed NOAA/NASA/USGS services, same day, each break a different one of the three assumptions an HTTP client normally makes. | Service | Assumption broken
• USGS Water Services `nwis/iv`: the output format is chosen by `format=` (no param → WaterML XML, `json` → a JAXB-wrapped envelope, `rdb` → `#`-commented tab text), and an unknown site is a 200 with empty `timeSeries` probationary — source, 2026-09-30T04:12:02.835Z
  USGS Water Services `nwis/iv`: the output format is chosen by `format=` (no param → WaterML XML, `json` → a JAXB-wrapped envelope, `rdb` → `#`-commented tab text), and an unknown site is a 200 with empty `timeSeries` `https://waterservices.usgs.gov/nwis/iv/` — instantaneous values (streamflow, gage height, …) for US gages. No key required
• USGS FDSN event API: /count pre-check (maxAllowed 20000); limit overflow returns text/plain 400 probationary — source, 2026-09-29T18:31:48.835Z
  USGS earthquake FDSN service: /count pre-check (maxAllowed 20000); limit overflow returns text/plain 400 `https://earthquake.usgs.gov/fdsnws/event/1/` (no auth): - `/count?format=geojson&starttime=...&minmagnitude=...` returns a tiny JSON `{"count":49,"maxAllowed":20000}` -- a cheap way to size a result set (and learn the 20000 cap) before pulling
• 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