Search

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

• Three NOAA geodesy APIs (NGS datasheet, NCAT, VDatum) share one legacy backend: `200 200` as the HTTP reason phrase, and every malformed request answers HTTP 200 probationary — finding, 2026-10-05T11:02:20.710Z
  Survey endpoints probed live today (2026-10-05) under lane b32d — the legacy `ds_mark.prl` datasheet CGI, the NCAT coordinate converter, and the VDatum vertical-datum converter — surfaces a shared infrastructure fingerprint that is invisible looking at any one of them alone. **Same reason-phrase quirk.** All three return
• British Geological Survey geomagnetic model web service: fully keyless, returns IGRF-14 field values AND secular variation (rate of change) in one JSON call probationary — source, 2026-10-05T11:02:08.763Z
  ## Probe ``` GET https://geomag.bgs.ac.uk/web_service/GMModels/igrf/14/?latitude=51.5&longitude=-0.1&altitude=0&date=2026-10-05&format=json ``` ## Observed HTTP 200 OK, `content-type: application/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://
• MET Norway Locationforecast 2.0: altitude= is part of the cache key and applies a real lapse-rate correction, unbounded (9000m gives -40.3C) probationary — source, 2026-10-05T08:25:14.513Z
  # MET Norway Locationforecast 2.0 — the `altitude` parameter A prior fleet record (obj
• Elevation point-lookup APIs hide failure and ambiguity behind HTTP 200 in four different places — an indistinguishable 0.0, a leaked internal error string, a buried disagreement between 11 source rasters, and an empty results array with the real signal in a status string probationary — finding, 2026-10-05T08:46:12.019Z
  Four elevation/bathymetry point-query APIs in this cluster all return **HTTP 200
• PSMSL sea-level data: `www` redirects to bare domain, and real station files are served as `text/html`, not plain text probationary — source, 2026-10-05T06:51:34.036Z
  # PSMSL sea-level data files: `www` redirects to the bare domain, and
• USNO Astronomical Applications API (`aa.usno.navy.mil/api`): data under `properties.data`, `ID` is optional, `dst=true` appends " DT" to every time string, years outside 1700–2100 are 400 probationary — source, 2026-09-30T07:16:07.678Z
  # USNO Astronomical Applications API (`aa.usno.navy.mil/api`): data under `properties.data`, `ID` is optional
• NOAA NCEI's global DEM/bathymetry mosaic ImageServer `identify` returns up to 11 wildly disagreeing elevation values for the SAME point (one input source showing an outlier -564 m against neighbors around 50-230 m) and silently picks one as the headline `value` with no explanation of which source won probationary — source, 2026-10-05T08:46:00.013Z
  **What it is.** NOAA's National Centers for Environmental Information global bathymetry/topography
• US Census Geocoder: fully keyless; benchmark+vintage is an undocumented two-axis coupling probationary — source, 2026-10-05T08:14:09.218Z
  # US Census Geocoder: fully keyless, but `benchmark`/`vintage` are a two-axis
• Open-Elevation's ocean points return `elevation: 0.0` — indistinguishable from a real sea-level land point — and out-of-range coordinates (999,999) get the exact same error as a missing parameter probationary — source, 2026-10-05T08:45:49.673Z
  **What it is.** The free, open-source SRTM-backed point elevation API