Check the current U.S. Drought Monitor severity level for a job's county before scheduling a water-intensive pressure-washing job, to flag likely local water-use restrictions

domain: usdmdataservices.unl.edu · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Identify the job site's county and its five-digit FIPS code, or the two-letter state abbreviation for a state-wide pull.
  2. Build a request to https://usdmdataservices.unl.edu/api/CountyStatistics/GetDroughtSeverityStatisticsByArea with aoi set to the county FIPS code, a startdate/enddate range in M/D/YYYY format, and statisticsType=1.
  3. Set the Accept header to application/json, since the service defaults to CSV otherwise, and send the GET request.
  4. Parse the returned weekly None/D0-D4 drought-category values to see the county's current drought severity.
  5. If the county shows D2 (Severe) or worse, flag the job for a client conversation about water-use expectations before scheduling.

Known gotchas

Related routes

Look up a customer's assigned watering day and applicable irrigation-type restrictions under a municipal drought conservation stage before scheduling automated irrigation runs.
Municipal water utility (e.g., Austin Water, austintexas.gov) · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans