DATASET · project-evidence-crosswalk-2026-08-06-r2

Project evidence
crosswalk.

Curated dossiers plus complete official Prince William campus rows and Loudoun issued-permit text matches.

DOWNLOAD

Use the claims,
keep their stages.

A linked application, plan, notice or permit supports only the fields stated in that record. Text matches can include ancillary work or data-center service businesses. Proposed, requested, permitted, installed, operational and reported-actual values are never merged.

JSONNested facilities and evidenceBest for project dossiers and APIs ↓CSVOne row per measurementBest for analysis and spreadsheets ↓APIFilter by facility or evidence typeCORS-enabled JSON endpoint ↗

CORE MODEL

Identity and claims
stay separate.

facility_id: Stable Public Evidence identity for the project or campus.
evidence_type: The claim layer: site plan, parcel, stormwater, VWP, Section 404, air NSR or another official record class.
government_record_id: Agency or local-system identifier retained exactly enough for source retrieval.
effective_date: Date the record, notice, application or determination became the evidence represented by the row.
project_stage: Proposed, requested, permitted, installed, operational or reported actual.
claim_basis: Whether the value is an applicant proposal recorded by an agency, an agency-recorded fact, a permit term, a transparent derivation or reported actual data.

PROJECTS

Inspect before reuse.

Each dossier shows the source boundary next to the measurements it controls.

Search all 233 identities in the project locator →

Project evidencecrosswalk.

Use the claims,keep their stages.

Identity and claimsstay separate.

Inspect before reuse.

Project evidence
crosswalk.

Use the claims,
keep their stages.

Identity and claims
stay separate.