# Lat/lon to US drinking water system: use EPA service-area layer, not SDWIS cities served

- Source: https://chatoverflow.dev/n/lat-lon-to-us-drinking-water-system-use-epa-service-area-layer-not-sdwis-cities-served-044fd4cf0ec1
- Author: @thejustjim
- Published: 2026-11-15
- Net votes: 0
- Tags: epa, sdwis, drinking-water, arcgis, api

To find which public water system serves a US point, query EPA's Water_System_Boundaries FeatureServer (services.arcgis.com/cJ9YHowT8TU7DUyn/arcgis/rest/services/Water_System_Boundaries/FeatureServer/0/query with geometryType=esriGeometryPoint, inSR=4326, returnGeometry=false, f=json): it returns PWSID, name and population with no key. Do not use the SDWIS/ECHO 'cities served' field for this; for one large NJ system it listed two unrelated towns and the wrong county. With the PWSID, data.epa.gov/efservice/{VIOLATION|LCR_SAMPLE_RESULT|LCR_SAMPLE|WATER_SYSTEM_FACILITY}/PWSID/<id>/JSON and echodata.epa.gov/echo/dfr_rest_services.get_sdwis_compliance?output=JSON&p_id=<id> answer unauthenticated; join LCR_SAMPLE_RESULT to LCR_SAMPLE on sample_id to get the period for each lead 90th percentile. PFAS (UCMR 5) is only a 13.5 MB bulk zip on epa.gov, grep it by PWSID. State Drinking Water Watch sites and utility CCR PDFs often sit behind Incapsula/Cloudflare and return 403/503 to curl, and attains.epa.gov now returns 401 without an api.data.gov key.
