Canonical routes currently exposed in the sitemap.
Trust
How the lookup works
This site turns analyst-grade federal electricity datasets into consumer-facing pages. That requires normalization, route canonicalization, and some deliberate limits on what the numbers should mean.
The current production app resolves addresses into ZIP-based near pages. Distances are still ZIP-centroid estimates, not parcel-level measurements.
Active plants currently shown in the public catalog.
Nationwide ZIP coverage loaded into the search layer.
Search resolves to a nearby ZIP page even when the starting input is a street address.
Search resolution
Inputs resolve into canonical routes before results are shown.
Five-digit ZIPs go directly to a canonical near page. Cities resolve to a representative ZIP page, counties resolve to county pages, and states resolve to state pages.
Street addresses are geocoded through ArcGIS on the server side. If the result includes a ZIP, the request is redirected into that canonical ZIP page. If it does not, the site falls back to the nearest ZIP centroid in the loaded location table.
The indexed route is always the ZIP-based near page.
Autocomplete is optional in the browser; final geocoding happens server-side.
The site prefers state-qualified city or county queries over guessing across multiple states.
Plant inclusion
The public catalog starts from EIA plant inventory and filters to active plants.
EIA Form 860 provides the plant and generator inventory. The site loads plant metadata, generator rows, and ownership context into SQLite, then builds the public catalog from active records.
Plant pages are not just one source row copied onto the web. They are assembled from plant metadata, generator rows, fuel-mix rollups, ownership shares, and emissions or generation tables when those are available for the same plant code.
Plant code, name, city, state, county, sector, and generator inventory.
Ownership shares are rolled up from the imported EIA 860 ownership workbook.
Generator detail is preserved so plant pages can show technology and online year context.
Generation and emissions
Operational context comes from separate federal datasets with different release schedules.
EIA Form 923 is used for generation and fuel reporting. EPA eGRID is used for plant-level emissions and intensity context. Those releases do not always land on the same schedule, so a plant page can legitimately pair a newer generation vintage with an older emissions vintage.
If a source is missing for a specific plant code, the page still renders with the data that is available rather than pretending to know more than the imported records provide.
Imported from the currently loaded EIA 923 vintage.
Imported from the currently loaded EPA eGRID vintage.
Being near a plant page does not mean the site is estimating personal health impact or plume dispersion.
What not to infer
These pages are context pages, not parcel analysis or regulatory determinations.
Distance
Not a rooftop measurement
The near-page model is ZIP-centric today. It is useful for regional context, not for telling you how many feet your front door is from a fence line.
ZIP-centroid estimateEmissions
Not a personal exposure estimate
Plant emissions totals and rates are useful for understanding scale and fuel type, but they are not a substitute for monitoring, dispersion modeling, or health advice.
Context, not diagnosisOwnership
Not corporate due diligence
Ownership shares are presented to answer a practical consumer question about who runs or owns a site. They should not be treated as a complete legal ownership history.
High-level attributionRelated routes
Supporting pages
Sources
Data freshness and source list
See which datasets are currently loaded and what each one contributes.
Source pagePrivacy
Privacy and third parties
See what requests hit third-party services and what the app does not currently collect.
Privacy pageContact
Report a data or route issue
Use the contact page if a plant, county, or search behavior looks wrong.
Contact page