Environmental data · regulated-facility intelligence

Facilities, modeled by identity and program.

Regulated-facility data spans EPA program systems — the Facility Registry Service, TRI chemical releases, ECHO enforcement, and eGRID plant emissions, each with its own keys. Sloe joins them on FRS identifiers into one source-backed research layer. Facility signals are not legal conclusions — program, permit, and violation facts stay source-scoped.

Available now. The environmental lane is built and source-backed — facility identity, releases, enforcement, and emissions joined by FRS identifiers, with high cross-source coverage.

AnchorFRS ID
SourcesEPA FRS · TRI · ECHO · eGRID
SignalsReleases · enforcement · emissions
StatusAvailable
FRS
Facility Registry Service identifiers tie sites across EPA programs.
TRI
Toxics Release Inventory chemical releases by facility and year.
ECHO
Enforcement and Compliance History records, kept source-scoped.
eGRID
Plant emissions and generation, joined where identifiers align.
The model

Environmental & Regulated-Facility is its own structure.

The environmental model anchors on FRS facility identifiers, then joins TRI releases, ECHO enforcement, and eGRID emissions as separate source-backed layers. Program, permit, violation, and enforcement facts stay source-scoped — a signal is not a legal conclusion.

Facility identity.

The Facility Registry Service resolves a site across EPA programs; ownership is reviewed, not inferred from names.

Chemical releases.

TRI releases keep chemical, medium, year, and facility attached — never summed into a single 'pollution score.'

Enforcement history.

ECHO compliance and enforcement records stay program- and date-scoped.

Plant emissions.

eGRID emissions and generation are joined where plant identifiers align with FRS.

Operator review.

Parent / operator relationships are promoted only on source-backed identifiers, not brand or address.

Affordable access.

Site selection, vendor diligence, and compliance research at a price smaller teams can justify.

Source spine

Built on the primary public record.

The environmental layer is built around official EPA public data first, joined by FRS identifiers. Facility signals are kept source-scoped; none are presented as legal conclusions.

FAQ

Common questions.

What sources is the environmental data built from?

Official EPA public data — the Facility Registry Service, the Toxics Release Inventory, ECHO enforcement, and eGRID plant emissions — joined on FRS identifiers.

Are facility signals legal conclusions?

No. Program, permit, violation, and enforcement facts are kept source-scoped. A signal is a public record, not a legal conclusion.

Can I screen facilities by enforcement history?

Yes. ECHO compliance and enforcement records stay program- and date-scoped so you can screen and rank facilities.

How do I get access?

Access for site selection, vendor diligence, or bulk export is by request, priced so smaller teams can justify it.

Get access

Tell us what environmental data needs to do.

Site selection, facility diligence, vendor screening, or bulk export — share the workflow and we'll get you access, including custom cuts.

More lanes

Related datasets.

Every Sloe lane is built on the same source-backed pipeline. Explore an adjacent dataset.