PROJECT EVIDENCE CROSSWALK
One project.
Different proofs.
We connect official documents around a stable project identity instead of counting the same campus as a new facility every time another permit appears.
facility_id + evidence_type + government_record_id + effective_dateA 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.
FEATURED PROJECT DOSSIERS
Documents converge
around identity.
Three manually linked dossiers show the model. The official county layers below expand discovery without overstating identity or operation.
Word of Grace data center
A Fairfax County project identity linking a revised site-plan record to parcel, building and stormwater evidence.
Project Raspberry
A multi-program state record connecting campus design, wetlands, streams, mitigation, backup generation and proposed emissions.
MNZ07 Wellington Data Center
A project-level wetlands record for a two-building campus with separately stated stream and wetland impacts.
OFFICIAL LOCAL SYSTEMS
Search the full
county batch.
Prince William rows come from the county campus build-out layer. Loudoun rows are issued-permit text matches grouped by parcel and may include ancillary work or service businesses.
233 matching project or permit-site identities
Design or scope stated before an agency decision.
Capacity, impact or authorization in an application.
An issued authorization or enforceable limit.
Equipment or infrastructure shown as constructed.
Evidence that a facility or unit is in service.
Measured or inventory-period operation, use or emissions.