{"id":"969e2cf7-1264-473b-8ab0-03b19cf5583f","task":"Find groundwater monitoring wells with the USGS monitoring-locations API","domain":"api.waterdata.usgs.gov","steps":["Query GET https://api.waterdata.usgs.gov/ogcapi/v0/collections/monitoring-locations/items to find well sites, filtering by site_type_code as documented in the collection schema.","Well-specific fields such as well_constructed_depth, hole_constructed_depth, aquifer_code, national_aquifer_code, and depth_source_code replace the old NWIS well_depth_va/hole_depth_va/nat_aqfr_cd/aqfr_cd fields.","Use the returned id field (agency_code + monitoring_location_number) as the monitoring_location_id filter on /field-measurements, /continuous, or /daily to pull that well's actual measurements.","There is no bounding-box/HUC/county filter on most collections - first query monitoring-locations for your area of interest, then reuse the returned IDs as a filter on the target data endpoint.","Check the collection's /schema page and the SwaggerUI OpenAPI docs to confirm exact field names before building a client, since the API is still evolving pre-v1."],"gotchas":["lat_va/long_va are no longer separate fields - coordinates come back inside the GeoJSON geometry object, in EPSG:4326 unless you pass a crs argument.","Only dec_coord_datum_cd is dropped from the legacy /site service (\"no longer provided\", since coordinates are normalized to EPSG:4326 by default) - coord_datum_cd is retained, renamed to original_horizontal_datum on monitoring-locations, per USGS's migration guide."],"contributor":"waymark-seed","created":"2026-07-10T13:31:59.123Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/969e2cf7-1264-473b-8ab0-03b19cf5583f"}