Open data · CC BY 4.0

Use the evidence.
Keep the boundaries.

Download a table, query one permit or cite a stable record without asking permission. Every reuse path keeps the controlling document, source page and QA status within reach.

Open the JSON API →Download current CSV ↓

199issued-permit records

199page-cited documents

4ready reuse paths

CC BYreuse license

START WITH YOUR USE

One source layer.
Four practical paths.

The same permit can support a news check, a research join, a community filing or a software integration. The claim boundary stays the same.

Reporting

Link the exact record, open the controlling DEQ document and cite the page carrying the field you use.

Find a permit →

Research

Pin the release date, retain qa_status and join on the full permit identifier rather than a guessed facility owner.

Inspect Release 2 →

Community records

Use a permit as evidence of authorized terms—not proof of construction, routine operation, actual emissions or harm.

Read the permit guide →

Software and maps

Filter the public API by permit, locality, operator, year, QA tier or text search. CORS is enabled for direct public use.

Inspect the response →

PUBLIC JSON API · V1

Query records
without scraping.

The collection endpoint returns bounded, paginated records. The permit endpoint adds the available equipment, operating-scope and emission-limit transcriptions.

permit — exact permit identifier
locality and operator — case-insensitive text filters
year — four-digit issuance year
qa — verified, second-reviewed or machine
q — facility, permit and program search
limit and offset — pagination, maximum 200

Collection example

GET https://publicevidence.org/api/v1/permits
  ?locality=Loudoun%20County
  &qa=verified
  &limit=5

One permit

GET https://publicevidence.org/api/v1/permits/74235-2

Run example ↗Open one permit ↗

MACHINE DISCOVERY

Use the format
your workflow expects.

These are parallel access paths to the same bounded release, not separate datasets.

CSVCurrent normalized permit index↓JSON APIFiltered collection and permit detail↗DCAT JSON-LDMachine-readable data catalog↗Data PackageFrictionless schema and checksums↗CSL-JSONReference-manager metadata↗BibTeXCopy or import the current web release↓RISZotero, EndNote and compatible tools↓RSSVerified source-snapshot changes↗

ATTRIBUTION

Cite the release
you actually used.

Public Evidence Project. (2026). Virginia Data Center Air Permit Index: Virginia DEQ issued-permit snapshot (2026-07-27) [Data set]. https://publicevidence.org/data

The DOI currently identifies the earlier 198-row Harvard Dataverse snapshot, not this current 199-row web release. The exports therefore cite the current landing page until a matching repository version is published.

Use the evidence.Keep the boundaries.

One source layer.Four practical paths.