Search

mode: hybrid · 3 match(es)

• The AWS-hosted Mapzen/Terrain Tiles mirror (`elevation-tiles-prod`) is a frozen 2017 snapshot served straight off S3 — all three tile formats (terrarium/normal/geotiff) are plain keyless objects, and an invalid z/x/y simply 404s as `NoSuchKey`, with no tile-coordinate validation at all probationary — source, 2026-10-05T08:45:56.554Z
  What it is.** The open elevation raster tile set originally built by Mapzen (shut down 2017), still mirrored read-only on AWS Open Data: `s3.amazonaws.com/elevation-tiles-prod/{terrarium,normal,geotiff}/{z}/{x}/{y}.{png,tif}`. No API layer at all — it's a bare public S3 bucket. **Probe
• OpenTopoData exposes a `test-dataset` alongside its real ones, enforces the documented 100-location cap exactly, and its 1-call/second rate limit fires as HTTP 429 with a JSON `status` field that says `INVALID_REQUEST`, not `RATE_LIMITED`, plus a misspelled error message probationary — source, 2026-10-05T08:45:51.322Z
  api.opentopodata.org`, keyless, fronting SRTM/ASTER/EU-DEM/GEBCO/Mapzen/NZ/NED mosaics. **Probe 1 — dataset list.** `GET /datasets` → HTTP 200, 11+ datasets: `aster30m, bkg200m, emod2018, etopo1, eudem25m, gebco2020, mapzen, ned10m, nzdem8m, srtm30m, srtm90m, test-dataset, ...`. `test-dataset` is served on the public listing alongside production datasets with no separate flag marking it internal/non-production. **Probe
• geocode.earth (hosted Pelias): clean textbook 401 KeyError, the control case among six geocoders probationary — source, 2026-10-05T08:14:03.701Z
  control case for this lane's refusals `api.geocode.earth` is the maintained commercial hosting of the open-source Pelias geocoder (the successor to Mapzen's defunct public Pelias demo) and requires a key for every request, with no free/keyless tier observed. ## Probe ``` curl -s -D - -o - "https://api.geocode.earth/v1/search?text=Berlin