Water System Violation Counts by County, EPA-Sourced
Pricing
from $5.00 / 1,000 results
Water System Violation Counts by County, EPA-Sourced
For environmental compliance consultants: one validated CSV row per public water system with violation counts, filtered by state or county from live EPA SDWIS data.
Pricing
from $5.00 / 1,000 results
Rating
0.0
(0)
Developer
US Tech Automations
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
16 days ago
Last modified
Categories
Share
For environmental compliance consultants advising public water systems on Safe Drinking Water Act (SDWA) compliance, this actor turns a state or county search into one validated row per system with violation counts already tallied.
Read a bounded selection of active US public water systems from EPA SDWIS and return one row per matching system with its validated violation count. The actor reads Envirofacts at run time; the result is limited by the input cap and a single monotonic run deadline. It does not promise a complete national catalogue or a cached snapshot.
It returns facilities only. A public water system is identified by EPA's PWSID, an organisation identifier. Operator names, emails, phone numbers and street addresses are dropped; town and state are retained.
Inputs and limits
state is a two-letter code. systemType is CWS, NTNCWS, or TNCWS.
populationMin is 0 through 2,147,483,647. maxItems defaults to 25 and may be
set explicitly through 5,000 (this is a hard ceiling; a single run cannot exceed it).
timeoutSeconds defaults to 120 and may be set through 30-3,600.
County filtering keeps systems whose EPA-reported service geography matches the
input county or town. When a county is supplied, the actor looks up Envirofacts
GEOGRAPHIC_AREA with bounded inclusive ROWS/start:end pages on
COUNTY_SERVED/CONTAINING/{term} and CITY_SERVED/CONTAINING/{term}, then
reads WATER_SYSTEM and VIOLATION only for those matching PWSIDs. It does
not walk every water system in the state and does not infer county from the
system's mailing city.
Matching is EPA CONTAINING / substring text on county_served and
city_served (AJO also matches NAVAJO). That is EPA-reported service
geography only, not a complete geographic census and not a mailing-address
guess. A blank county means the whole state and skips the geography lookup.
Active systems are requested with PWS_ACTIVITY_CODE=A.
The actor follows EPA's inclusive ROWS/start:end ranges and continues through pages
when local filters leave a sparse page. A malformed response, provider request error,
deadline, repeated page/ID, or protective page cap raises a run failure rather than an
unproved partial result.
Output
The output fields are pwsid, pws_name, state, city, population_served,
service_connections, water_source, owner_type, violations_total,
violations_health_based, and source_url. When a county filter is set, matching
rows also include matched_county, matched_town, and geography_source_url. No
personal operator fields are emitted.
Try a small search
Run with {"state": "AZ", "systemType": "CWS", "maxItems": 25} and open the Results
dataset. Every row cites its own source_url back to EPA Envirofacts.
Provider and platform terms
Usage is billed through Apify at $0.50 per GB of actor memory for the actor-start event (minimum one event; this actor defaults to 1 GB) plus $0.005 per result. A run returning no results still incurs the minimum $0.50 actor-start charge. At the default 1 GB, a run returning 5,000 results has configured event charges of $25.50. Check the listing's current pricing before starting a run.
Data source and limitations
The source is EPA Envirofacts SDWIS (WATER_SYSTEM, VIOLATION, and GEOGRAPHIC_AREA
when a county is supplied) at https://data.epa.gov/efservice. This actor is not
affiliated with EPA and is not legal, engineering, health, or professional advice.
Refund and support
Refunds: if a run returns zero rows for a valid input, email operations@ustechautomations.com within 7 days and we refund that run. Support: same address, replies within 2 business days.