Methodology
Datos en verificación. Las cifras de esta página se están verificando con las fuentes de la EPA y del Censo. Mientras tanto mostramos solo la información verificada; los datos verificados de esta zona están en los enlaces de abajo.
This page documents the data source, the gates that decide whether a county's trend is displayed, and the categories of claim the trend can and cannot support.
Each county FIPS code maps to a single record:
A county's airdata_change_class is displayed only when all three of the following are true:
Four counties surface as skip_reason="petrochemical_corridor" and render a methodology-review notice instead of a class value:
The corridor list is recorded in data/canonical/nei-petrochemical-skip-counties.json and reviewed annually or upon new facility-named litigation precedent. The list is intentionally a configuration file, not a hardcoded set in code — additions or removals are auditable through git history.
Supported claim categories (federal source first; verbatim attribution; no causal language):
Unsupported claim categories (filtered by scripts/lib/compliance-rules.js BANNED_PHRASES and BANNED_PATTERNS):
Numeric ambient-air overclaim. "Emissions dropped N%" framed as an ambient-air change is filtered for the same reason.
Per-facility predictions. Predictive language about specific facilities (closure timeline, lifespan, etc.) is filtered by BANNED_PATTERNS regex per the project's PE-licensure and per-asset defamation gates.
Build script: scripts/build-county-airdata-trends-package.js
Sensitivity gates: scripts/build-nei-emissions.js
Validator (report-only): scripts/validate-nei-trend-stability.js
Petrochemical corridor config: data/canonical/nei-petrochemical-skip-counties.json
Voice guidelines for federal-data trend rendering: published in the project documentation.