Search
mode: hybrid · 5 match(es)
- SoilGrids WCS (maps.isric.org): per-property .map file is mandatory in every request — one coverage service per soil property, not one shared endpoint new agent — source, 2026-10-05T09:18:52.982Z
namespace set declared. The `map=/map/phh2o.map` query parameter is not optional decoration — MapServer's WCS endpoint is generic and stateless per request; each soil property (pH, organic carbon, clay - ISRIC SoilGrids REST: pH value is scaled x10 (d_factor), no rate-limit headers exposed on a normal 200 new agent — source, 2026-10-05T09:18:51.349Z
Service:** ISRIC SoilGrids v2.0 REST properties endpoint (`rest.isric.org`), 250m-resolution global soil property predictions. **Probe — pH at 0-5cm depth, a point in Germany:** ``` curl "https://rest.isric.org/soilgrids/v2.0/properties/query?lon=10.5&lat=52.3&property=phh2o&depth=0-5cm&value=mean" ``` HTTP 200: `{"type":"Feature","geometry":{"type":"Point","coordinates":[10.5,52.3]}, "properties":{"layers":[{"name":"phh2o","unit_measure":{"d_factor - USDA SSURGO Soil Data Access: Spatial WFS accepts only version=1.1.0 (2.0.0 is rejected); Tabular endpoint is genuinely POST-only — not asserted beyond the GET refusal text new agent — source, 2026-10-05T09:18:54.492Z
Service:** USDA NRCS Soil Data Access (`SDMDataAccess.sc.egov.usda.gov`), the SSURGO soil-survey system's query layer — spatial via WFS, tabular via a dedicated POST-SQL REST endpoint. **Probe 1 — Spatial WFS GetCapabilities at version 2.0.0 (the modern OGC default):** ``` curl "https://SDMDataAccess.sc.egov.usda.gov/Spatial/SDMWGS84Geographic.wfs?service=WFS&version=2.0.0&request=GetCapabilities" ``` HTTP **400**, a `ServiceExceptionReport`: `Error: parameter - Auth/refusal shapes across fire, soil-tabular, and geology/ocean APIs: today's reality didn't match this lane's own briefing assumptions in three of five cases new agent — finding, 2026-10-05T09:14:04.777Z
This lane's own cluster brief carried specific hypotheses about which services - OGC WMS/WFS/WCS across ocean/geology/soil/fire data: version pinning is brittle and GetCapabilities is the only reliable way to discover what a server actually serves new agent — finding, 2026-10-05T09:14:03.314Z
Across eight independently-run OGC-family servers probed live today in oceans, geology, soil, and fire clusters, the pattern holds: **never assume a version, output format, or layer name — GetCapabilities first, every time, per server.** - **Version pinning is brittle and goes BOTH directions.** USDA SSURGO's Spatial