The current UTF-8 CSV with facility, permit, issue date, program, locality, regional office and agency-document URL.
Download CSV ↓Research and reporting kit
Use the record.
Keep its limits visible.
Direct links for researchers, journalists, librarians and public-interest organizations that want to inspect, cite or reuse the Virginia permit index.
DIRECT MATERIALS
Start with
the artifact
Field meanings and the transformation applied to every exported column.
Download dictionary ↓Monitoring statistics, sensor deployments, field definitions and the facility-identity review queue in one versioned file.
Download workbook ↓A citable nine-page statement of the acquisition, transcription, identity-resolution and quality-assurance method.
Open publication →CFF for repository workflows and CSL-JSON for reference managers describe the current site snapshot. Repository publication status is shown separately.
Download CITATION.cff ↓Open CSL-JSON →A Frictionless descriptor with file sizes, SHA-256 hashes, field types and stable download URLs.
Open package metadata →Acquisition, validation, normalization, change detection, known limitations and correction rules.
Inspect methodology →Repository release, source snapshot, row count and the condition for publishing a later version.
Open version history →SUGGESTED CITATION
Public Evidence Project. (2026). Virginia Data Center Air Permit Index: Virginia DEQ issued-permit snapshot (2026-07-20) [Data set]. https://publicevidence.org/data
The DOI identifies the repository record. When a conclusion depends on an individual permit, also cite the controlling Virginia DEQ document linked in that row.
A dated agency index
The collection records Virginia DEQ issued-permit listings and preserves the agency identifiers and document links shown in the source snapshot.
Dataset details →Operation or harm
A permit row does not prove construction, current operation, actual emissions, compliance, exposure, ultimate ownership or environmental harm.
Interpretation boundary →Show the source trail
External use is listed only when a public article, resource page, paper or reproducible analysis links to the dataset or DOI.
Citation register →COMPLEMENTARY VIRGINIA RESOURCES
Different layers.
Different claims.
These sources help readers place permit records beside official documents, project geography, public-health research and community-facing regulatory guidance. They are included for their editorial usefulness; no reciprocal link, partnership or endorsement is implied.
Virginia DEQ issued permits
The official issued-permit table and linked agency documents control over this project’s normalized summaries.
Boundary A listing does not by itself establish construction, current operation, actual emissions, compliance, exposure or harm.
Open Virginia DEQ ↗Piedmont Environmental Council maps
PEC’s Virginia project map and diesel-generator map add compiled spatial and land-use context to the permit-record layer.
Boundary The maps are not the controlling permit record and should not be read as proof of operation or measured emissions.
Virginia Climate Center assessment
This exploratory assessment reviews potential health pathways associated with Virginia data-center growth and identifies evidence gaps.
Boundary Research context does not establish facility-specific causation, permit status or actual emissions.
Read the assessment ↗Community & Environmental Defense Services
CEDS provides community-focused guidance on data-center siting, approvals, air quality and neighborhood impacts.
Boundary It is an advocacy and assistance resource, not a regulator or a substitute for the underlying agency records.
Open the CEDS resource ↗LINKING AND REUSE
No reciprocal
link required.
Researchers and publishers may link directly to the dataset, DOI, methodology or a relevant record page. A link does not imply partnership or endorsement in either direction.
Public Evidence Project may link to a complementary map, official source or research resource when it materially helps readers. Inclusion is editorial, not conditional on a backlink.
For a factual correction, identify the affected URL or field and provide the strongest primary source available.
Need a precise source path?
Ask about the dataset, a methodology review or an institutional resource listing without granting a blanket endorsement.