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.
Environmental Incident Reporting
Submit environmental observations, community concerns, and field evidence to support responsible environmental awareness and follow-up review.
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.
Understand the Environmental Conditions Around Any Address
Search an address, ZIP code, city, or current location to identify nearby regulated facilities, compliance history, community signals, and environmental risk indicators.
Analyze Environmental Conditions Near a Location
Start with what users actually care about: a home address, school area, ZIP code, city, or current location. EcoSignal then organizes nearby EPA records, community reports, and environmental indicators into a readable screening profile.
Environmental Snapshot
Give users a fast answer first: what is around this location, what deserves attention, and how the area compares with broader environmental context.
Preliminary score based on regulatory records, toxic release indicators, community signals, and data completeness.
Interactive Environmental Map
Map nearby EPA-regulated facilities, violation indicators, TRI facilities, and community reports around the searched location.
This score helps prioritize review. It is not a health-risk determination or legal conclusion.
How the Score Is Structured
EcoSignal separates data sources before generating a preliminary area-level screening score.
Compare This Area With Broader Community Context
Users need more than a raw facility list. Comparison helps answer whether the searched area appears higher, lower, or similar to the surrounding county baseline.
Your Area vs. County Average
Example comparison for the searched radius.
Interpretation
A higher count does not automatically mean the area is unsafe. It means the location has more nearby records that may deserve review. EcoSignal should explain whether the issue is facility density, compliance history, toxic release reporting, or community concern signals.
Nearby Facilities Ranked by Relevance
After a search, results should be sorted by distance and then flagged by violations, enforcement, TRI reporting, or community reports nearby.
Southern California Gas Company - Aliso Canyon
Example Industrial Facility
Facility Profile Preview
Clicking a facility should open a detailed profile with source-aware interpretation.
0.8 mi
72
ECHO
Review
Production profile should include facility name, address, EPA programs, inspections, violations, enforcement actions, TRI releases, and nearby community reports.
Environmental History Timeline
Users understand risk better when records are organized over time, not just listed as disconnected data points.
Example: significant community concern or publicly known incident relevant to area context.
Facility-level regulatory activity can be shown when available from EPA records.
Nearby public observations can be displayed as separate signals, not as EPA violations.
What EcoSignal Uses for the Analysis
Each source is useful, but each means something different. EcoSignal must keep those meanings separate.
EPA ECHO Compliance Records
Facility compliance and enforcement context, including inspections, violations, enforcement actions, and EPA identifiers.
EPA TRI Toxic Release Inventory
Annual facility-reported chemical release and waste-management data for long-term environmental screening.
Community Reports
Local observations submitted by residents or community users. These are signals, not regulatory determinations.
Admin Tools: Cache / Export / Supabase Sync
Cached EPA Records
Use this controlled review layer before syncing selected EPA records into Supabase.
| Facility | Location | Compliance Metrics | Source | Cached At |
|---|
Sync Cached Records to Supabase
Administrative ingestion control for EPA cached records. This should remain a controlled workflow in production.
Important Regulatory Notice
EPA records represent regulatory information, facility reporting, and compliance history. Community reports represent public observations. Appearance in an EPA dataset does not by itself establish contamination, health risk, or legal liability. EcoSignal uses these records as context for screening, community awareness, follow-up investigation, and historical compliance review.
Environmental Intelligence Methodology
A structured framework for integrating community observations, regulatory records, environmental datasets, and professional interpretation.
Data Sources & Integration
EcoSignal preserves source identity while converting community reports, EPA ECHO records, and EPA TRI data into a reviewable environmental intelligence workflow.
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.
Environmental Intelligence Workflow
This workflow supports transparent screening, defensible interpretation, and clear separation between observations, public records, and analytical context.
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.
Interpretation Principles
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 EcoSignal Works
From community observations to environmental intelligence: collect, normalize, score, map, analyze, and responsibly refer environmental signals.
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.
Environmental Intelligence Platform
EcoSignal integrates community observations, EPA public records, geospatial screening, and source-aware environmental interpretation.
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.