Dataset validation
EPA ECHO Enforcement CSV Sample
A validation sample for a possible environmental compliance feed built from public EPA ECHO facility, inspection, violation, enforcement, and penalty records. It is source-linked data infrastructure only, not legal, environmental, or compliance advice.
observed_at,facility_id,facility_name,city,state,program,compliance_status,enforcement_action,penalty_usd,source
2026-07-04,SAMPLE-FRS-001,Sample Chemical Works,Houston,TX,CAA,significant_noncompliance,formal_action,24500,EPA ECHO
2026-07-04,SAMPLE-FRS-002,Example Plating Facility,Cleveland,OH,RCRA,violation_identified,informal_action,0,EPA ECHO Data Downloads
2026-07-04,SAMPLE-FRS-003,Demo Food Processing,Modesto,CA,CWA,resolved_violation,penalty_assessed,8300,EPA ECHO Web Services
CSV Schema
The fields are intentionally simple so buyers can inspect the shape in spreadsheets, BI tools, and lightweight data pipelines.
observed_atfacility_idfacility_namecitystateprogramcompliance_statusenforcement_actionpenalty_usdsource
Monetization Hypothesis
This sample tests dataset and report-style demand before we invest in ingestion, export automation, or marketplace onboarding.
- CSV/report subscription for environmental due diligence, insurance, supplier-risk, and ESG teams.
- API subscription for facility watchlists, permit-program filters, and enforcement alerts.
- Build only after tracked request, download, or exact-intent signals appear.
Public Sources
The full product would normalize public records into stable datasets and API endpoints only after validation gates are met.
- EPA ECHO web services
- EPA ECHO national data downloads
- EPA ECHO Exporter facility summary file