Community Signals + Public EPA Records
EcoSignal separates community incident reports, EPA ECHO compliance records, and EPA TRI toxic release inventory data into distinct intelligence layers for screening, research, and responsible referral.
What changed in V21.2?
V21.3 adds Supabase EPA cache sync on top of the live EPA display and cache layer: live ECHO results can be saved as structured cached records, reviewed in a cache table, exported for audit, and later synchronized into Supabase without confusing public regulatory records with community complaints.
Three-Layer Data Architecture
The commercial value comes from integrating multiple trusted data layers while keeping each source type clear and defensible.
Field Observations
Structured reports from residents, NGOs, or local organizations. Best for early signals, local awareness, and potential case leads.
Regulatory & Compliance Layer
Facility compliance, inspections, violations, and enforcement context from EPA public records.
Toxic Release Layer
Facility-reported toxic chemical release and waste management data for long-term risk profiling.
Report an Environmental Incident
Submit observable facts. Do not speculate or accuse without evidence.
V21.1.1 Intake Principle
Community reports remain open and low-friction, while EPA records are imported separately through verified public data connectors.
Anonymous reporting remains available
Do not force registration at the reporting stage. Registration should be optional for tracking, following cases, and receiving alerts.
EPA data is not a complaint
ECHO/TRI records are public regulatory records. They should support context and risk screening, not be treated as direct allegations.
Environmental Intelligence Database
Filter community reports, ECHO regulatory records, and TRI toxic release records in one database while preserving source identity and evidence logic.
United States Integrated Environmental Layer
Color = source layer. Click a marker or row to open record detail.
| ID | Source | Title / Facility | Location | Category | Status | Evidence | Trust | Key Data | Last Updated |
|---|
Select a record
Click a marker or table row to inspect record source, evidence, trust score, and interpretation limits.
—
—
—
—
Interpretation Limit
Community reports are signals; ECHO records are compliance context; TRI records are facility-reported release inventory data. Do not merge them into a single allegation.
EPA ECHO + TRI Connector Blueprint
V21.3 adds Supabase EPA cache sync on top of the live EPA display and cache layer on top of live EPA ECHO search so selected public records can be stored, reviewed, exported, and later synchronized into Supabase with clear source attribution.
Search Nearby EPA Facilities
Enter an address, city, or ZIP code to screen for nearby EPA-regulated facilities and compliance context. This V21.3 module queries EPA ECHO through the EcoSignal Cloudflare Worker and displays live public compliance context.
Cached EPA Records
Save selected live EPA search results into a reviewable cache, then sync the cached records into Supabase.
| Facility | Location | Compliance Metrics | Source | Cached At |
|---|
Sync Cached EPA Records to Supabase
V21.3 prepares real database ingestion. Create the epa_cached_records table first, then sync cached EPA records.
Required Supabase table
Temporary demo RLS policy
EPA ECHO
Use ECHO as a facility compliance and enforcement context layer. It should not be labeled as a new pollution incident.
EPA TRI
Use TRI as an annual toxic release and waste management inventory layer. It supports risk screening and trend analysis.
EPA Data Connector Dashboard
A production-facing blueprint for importing EPA ECHO and EPA TRI data into EcoSignal through backend sync jobs, normalized database tables, and source-aware interpretation rules.
Connector Status
V21.2 uses a Cloudflare Worker to query EPA ECHO live, then caches selected EPA records with source attribution before Supabase ingestion.
EPA ECHO Connector
Facility compliance, inspections, violations, and enforcement context. Recommended sync: daily or weekly depending on usage.
EPA TRI Connector
Annual toxic release and waste-management data. Recommended sync: annual full refresh plus correction update checks.
Unified Intelligence View
Community reports, ECHO records, and TRI records remain separate tables, then appear together through a normalized geospatial intelligence view.
Recommended Data Pipeline
This is the pipeline that keeps the platform credible, fast, and defensible.
Fetch
Call EPA API or download CSV files from authoritative sources.
Validate
Check required fields, coordinates, dates, and duplicate facility identifiers.
Normalize
Convert ECHO/TRI fields into EcoSignal's shared record model.
Store
Save raw source data and normalized records in PostgreSQL/PostGIS.
Display
Expose clean API endpoints to the website map, table, and detail pages.
Field Mapping
The key design rule: do not force ECHO, TRI, and community reports into the same meaning. Normalize them for search and mapping, but preserve interpretation limits.
| EcoSignal Field | Community Reports | EPA ECHO | EPA TRI | Purpose |
|---|---|---|---|---|
| source_layer | Community Report | EPA ECHO | EPA TRI | Prevents mixing complaints with regulatory records. |
| record_type | Incident Signal | Compliance / Enforcement Record | Toxic Release Inventory Record | Clarifies what the record actually represents. |
| facility_id | Optional / unknown | EPA registry or facility identifier | TRI facility identifier | Supports facility-level aggregation. |
| category | Water / Air / Dumping / Spill | Air / Water / RCRA / SDWA compliance | Chemical release media | Allows filtering without implying identical data type. |
| geom | Reporter-provided location | Facility coordinates | Facility coordinates | Enables map display and radius search. |
| interpretation_limit | Unverified public signal | Regulatory context, not a new incident | Annual self-reported release inventory | Reduces legal and scientific overstatement. |
Suggested Database Schema
Use separate source tables and a unified read-only view. Keep raw imports for auditability.
Website API Endpoints
The front-end should query your own API, not EPA directly.
Example Sync Log
A production dashboard should show when each connector last ran, how many records were imported, and whether validation passed.
How the Platform Works
The key is not collecting more noise. The key is separating, scoring, and interpreting environmental signals responsibly.
1. Collect
Accept public reports and import authoritative public datasets.
2. Normalize
Convert records into a shared schema: source, location, category, date, evidence, trust, and interpretation limits.
3. Score
Apply evidence quality and trust scoring differently for community reports, ECHO records, and TRI data.
4. Map
Display records on geographic layers without claiming every public record is an active incident.
5. Analyze
Identify hot zones, repeated patterns, facility context, and possible referral candidates.
6. Refer
Route high-quality signals to NGOs, attorneys, consultants, or researchers when appropriate.
About EcoSignal V21.2
EcoSignal is an independent bilingual environmental intelligence platform prototype. V21.2 demonstrates how public reporting, EPA compliance data, and toxic release inventory data can be fused into a disciplined environmental risk intelligence database.
The goal is not to replace regulators or emergency services. The goal is to organize public signals and records into reviewable, searchable, and responsibly interpreted environmental information.
Important Disclaimer
EcoSignal does not provide emergency response, legal representation, environmental remediation, or regulatory enforcement. EPA ECHO and TRI records are public data sources and must be interpreted with care. For emergencies, call 911 or local authorities.