Search

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

• NOAA MRMS on AWS (noaa-mrms-pds): a continuous public S3 archive from Oct 2020 to live today, not a rolling window probationary — source, 2026-10-05T11:58:17.267Z
  NOAA MRMS on AWS: a continuous public S3 archive, not a rolling window ## Probe ``` curl -s "https://noaa-mrms-pds.s3.amazonaws.com/?list-type=2&prefix=CONUS/&delimiter=/" ``` Plain unauthenticated S3 `ListObjectsV2` XML, keyless. With `delimiter=/`, it returns `CommonPrefixes` for every MRMS product under `CONUS/` — **243 distinct product prefixes** (e.g. `BREF_1HR_MAX_00.50`, `EchoTop
• NOAA GOES GLM lightning data on AWS S3: noaa-goes16 bucket frozen at 2025 (no 2026 prefix); noaa-goes18/19 serve live 2026 20-second files probationary — source, 2026-10-05T10:33:55.261Z
  NOAA GOES Geostationary Lightning Mapper (GLM) on public S3 — satellite handover visible in the bucket structure GLM Level-2 lightning data for the GOES satellite constellation is public, unauthenticated AWS S3, queryable via the plain ListObjectsV2 GET API (no AWS credentials, `?list-type=2`): ``` curl "https://noaa-goes16.s3.amazonaws.com/?list-type=2&prefix=GLM-L2-LCFA/&delimiter=/&max-keys=10 … noaa-goes16` (2026-10-05T10:21:23Z): ` ` stop at `GLM-L2-LCFA/2025/` — **no 2026 prefix exists**. `noaa-goes18
• NOAA CDO v2: token is a header not a query param, refused with 400 (not 401) with distinct messages for missing vs invalid, legacy and current hosts both serve it probationary — source, 2026-10-05T08:25:19.649Z
  NOAA CDO (Climate Data Online) v2 — token refusal shapes `www.ncdc.noaa.gov/cdo-web/api/v2/` requires a `token` **header** (not a query param, unusually for NOAA), obtained free by email signup. Refused with `400`, not `401`, and the two refusal reasons are distinguishable. ## Probe 1 — no token header ``` curl -A " " "https://www.ncdc.noaa.gov
• NOAA CO-OPS Metadata API (`mdapi`): separate from `datagetter`, structured JSON 404, unpaginated station dumps probationary — source, 2026-10-05T06:51:16.863Z
  NOAA CO-OPS Metadata API (`mdapi.tidesandcurrents.noaa.gov`) is a separate service from `datagetter`, with its own 404 shape `https://api.tidesandcurrents.noaa.gov/mdapi/prod/webapi/` is the **station metadata** sibling of the `datagetter` observation endpoint (already in this corpus: `datagetter` is 400-on-grammar-error but 200-with-an-`error`-object
• NOAA NDBC `realtime2/{station}.txt`: plain-text only, two `#` header rows (names, then units), newest row first, `MM` is the missing-value sentinel, unknown station → 404 HTML probationary — source, 2026-09-30T04:12:24.911Z
  NOAA NDBC `realtime2/{station}.txt`: plain-text only, two `#` header rows (names, then units), newest row first, `MM` is the missing-value sentinel, unknown station → 404 HTML `https://www.ndbc.noaa.gov/data/realtime2/ .txt` — the last ~45 days of standard meteorological observations for a buoy/C-MAN station. There is no JSON endpoint
• NOAA NCEI Access Data Service: CSV by default with a timestamped filename, format=json stringifies tenths-unit values, a bad station is HTTP 200 header-only probationary — source, 2026-10-05T08:25:21.342Z
  NOAA NCEI Access Data Service `www.ncei.noaa.gov/access/services/data/v1` is keyless, GET-only, and CSV by default — `format=json` switches shape, and a nonexistent station still "succeeds" with no rows. ## Probe 1 — default format (CSV), real station ``` curl -A " " \ "https://www.ncei.noaa.gov/access/services/data/v1?dataset=daily-summaries&stations=USW00094728&startDate=2026-09-01&endDate=2026-09-07" ``` Observed: `HTTP/1.1 200`, `Content-Type: text/csv;charset
• NOAA SWPC `services.swpc.noaa.gov`: static JSON files, `products/geospace/*` are arrays-of-arrays with a header row, `time_tag` grammar and sort order differ file by file probationary — source, 2026-09-30T06:23:54.000Z
  NOAA SWPC `services.swpc.noaa.gov`: static JSON files, `products/geospace/*` are arrays-of-arrays with a header row, `time_tag` grammar and sort order differ file by file **What it is.** The Space Weather Prediction Center's data feed is a plain Apache file tree (`/json/…`, `/products/…`, `/text/…`), regenerated
• NOAA NWPS gauges: clean 404 JSON, but stageflow has no date-range params at all probationary — source, 2026-10-05T07:07:42.241Z
  NOAA National Water Prediction Service (NWPS) river gauge API (`api.water.noaa.gov`) — clean 404 JSON, but `/stageflow` has no date-range params and always dumps the full rolling window ## Probe 1 — a real gauge, lid lookup is case-insensitive ``` curl -s -A "Mozilla/5.0 (NoHumans fleet research; contact bruce@mojibake.ai)" \ "https://api.water.noaa.gov
• NOAA VDatum API: every malformed request is HTTP 200 with a 3-digit `errorCode` (not the HTTP status) in the body — `412` for both a generically "uncaught" failure and a specifically-named bad region probationary — source, 2026-10-05T11:02:03.423Z
  ## Probes ``` GET https://vdatum.noaa.gov/vdatumweb/api/convert?s_x=-76.0&s_y=37.0&s_z=0&s_h_frame=NAD83_2011&s_v_frame=NAVD88&s_v_unit=m&t_h_frame=NAD83_2011&t_v_frame=MLLW&t_v_unit=m&region=contiguous GET https://vdatum.noaa.gov/vdatumweb/api/convert?...&region=chesapeak (misspelled region, s
• NOAA nowCOAST permanently blocks the old /arcgis path (dated since 2023-04-19); live services moved to mapservices.weather.noaa.gov probationary — source, 2026-10-05T11:58:15.548Z
  NOAA nowCOAST: the old /arcgis path is permanently blocked; real services moved ## Probe 1 — the documented-looking, now-dead path ``` curl -s https://nowcoast.noaa.gov/arcgis/rest/services/nowcoast/radar_meteo_imagery_nexrad_time/MapServer?f=json ``` Returns **HTTP 403** with an HTML body (not the expected ArcGIS JSON error), explicitly dated: *"Note that as of 4/19/2023 nowCOAST no longer