us-water-quality-data for Python
Versioned U.S. water-system evidence by ZIP for Python. Its bundled JSON is generated from the same open export as the JavaScript package and preserves measured zero, measured false, and unavailable evidence as different states.
import us_water_quality_data as water
record = water.lookup("10001")
print(record)
print(water.meta["total_zips"])
The package provides lookup, get_state, get_worst, get_best, states, count, zips, and search_city. Read coverage counts, source vintage, and field definitions from water.meta; they vary by version.
The copper field is copper_action_level_exceedance, not a concentration. It is True only when an accepted CU90 exceedance record exists and None when unknown. Nullable violation, CCR, enforcement, lead, radon, score, and grade fields must not be converted to reassuring zeros or false values.
Schema v5 has 55 ordered fields. ccr_accepted_evidence is None unless an
accepted CCR record is source-bound to its identity, period/date status,
typed lead result, copper semantics, evidence URL, and SHA-256.
lead_level_mg_l is normalized only from a source row with an explicit supported unit. Values at or above 1 mg/L are held for source review and are never divided by 1000 automatically. contaminant_count and health_contaminant_names are None when water_data_available is false.
Home Safety Score fields follow the model version recorded by the source export and remain unavailable when required domain coverage is incomplete. The data is system-level and geographically joined evidence, not tap-level sampling, a property inspection, or a guarantee of safety.
License: CC BY 4.0. Full source and methodology details: zipcheckup.com.
1 maintainer
Metadata
1 maintainer
Release files for us-water-quality-data 2026.10.21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| us_water_quality_data-2026.10.21.tar.gz | 6.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| us_water_quality_data-2026.10.21-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.5 MB
Release files / us_water_quality_data-2026.10.21.tar.gz
| Download URL | us_water_quality_data-2026.10.21.tar.gz |
|---|---|
| Size | 6.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6b67c453e475a2e82bf8414fb2a1ff593f48edb2e59a7688f3f5fbd5505cbf9
|
|
BLAKE2b-256 checksum How to use checksums |
726ff0e2c699009aee4946385261fc606f5e9e5b3bdd95dea503976403eb6b22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / us_water_quality_data-2026.10.21-py3-none-any.whl
| Download URL | us_water_quality_data-2026.10.21-py3-none-any.whl |
|---|---|
| Size | 6.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa50f44abd6cc1be3d344472718bc5a7b1ab66d8f0c4bb129bf4dd0273fd333d
|
|
BLAKE2b-256 checksum How to use checksums |
4b63183f9e026d29e53fe5378aa61038896ae77ced82f7f3a9bfc8d8edff958c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for us-water-quality-data 2026.10.21
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
