Day 58 · Derived / Synthesized · Northern Virginia

NoVA Protected Lands and Conservation Easement Atlas

Every fee-owned protected area and conservation easement in Northern Virginia - 2,034 deduplicated PAD-US 4.1 units, a 127,763-acre dissolved footprint covering 15.3 percent of the regional land base - with GAP protection status, public access, easement holders, 19 DBSCAN conservation corridors, and a military reference layer, cross-validated against the Virginia DCR Conservation Lands Database.

2,034 protected units
738 conservation easements
15.3% of NoVA land
July 12, 2026 - Day 58
Protected lands, easements, and military reference boundaries
Layer key
Fee-owned protected land
Fee land with GAP 1-2 biodiversity mandate
Conservation easement
Military installation (reference only)
Data Package
2 GeoPackages + FGDC XML + CSVs + GeoJSONs + PDF + README + manifest (4.2 MB)
PDF Report
Methodology, findings, jurisdiction table, sources (13 KB)
Cite this dataset: doi:10.5281/zenodo.21321233
2,034
Protected units
127,763
Footprint acres
15.3%
Of NoVA land
738
Easements
3.6%
GAP 1-2 land

OverviewDataset Summary

This is the first unit-level protected-lands inventory published specifically for Northern Virginia: every fee-owned protected area and conservation easement in USGS PAD-US 4.1 that touches the nine jurisdictions, cleaned of 1,180 duplicate records (36.7 percent of the raw extract), clipped to the region, and cross-validated against the Virginia DCR Conservation Lands Database with 96.8 percent footprint agreement. The deduplicated atlas holds 2,034 units - 1,296 fee tracts and 738 conservation easements - whose dissolved footprint covers 127,763 acres, 15.3 percent of NoVA's land.

Attribution per unit includes GAP protection status (the federal biodiversity-mandate scale), public access, owner and manager, normalized easement holder, establishment year where recorded, and NoVA-clipped acreage. Military installations (32,563 acres: MCB Quantico, Fort Belvoir, Arlington National Cemetery and six smaller sites) ship as a separate reference layer excluded from every statistic, following PAD-US convention for proclamation boundaries.

Why This DatasetThe Problem It Solves

Ask how much of Northern Virginia is protected and you will not find an answer - PAD-US is national and duplicate-ridden, DCR's database is statewide with different conventions, and no county publishes a regional rollup. Meanwhile the region is in a land-use collision: the world's largest data center market expanding westward, a Rural Crescent under rezoning pressure, county open-space goals citing "30x30", and a conservation easement movement that has quietly locked up a sixth of Loudoun County. Planners, land trusts, and developers are all negotiating against a protected-lands base map that did not exist.

This atlas answers the question with defensible numbers: which land is protected, by what mechanism, held by whom, open to whom, and with what level of legal permanence - unit by unit, jurisdiction by jurisdiction.

MethodologyHow It Was Built

All Virginia PAD-US 4.1 Fee and Easement features intersecting a NoVA envelope were fetched from the USGS ArcGIS service (5,135 raw features), geometry-repaired, clipped to the 9-jurisdiction union built from Census TIGERweb county boundaries, and stripped of sub-0.1-acre boundary slivers. Acreage was recomputed on clipped geometry in EPSG:32618; each unit was assigned to its largest-overlap jurisdiction (78 units cross boundary lines).

Deduplication: PAD-US aggregates the same easement from multiple submitters - Virginia Outdoors Foundation easements appear under two holder spellings whose footprints overlap on 24,630 of 24,709 acres. After holder-name normalization, a greedy spatial pass removed any feature at least 60 percent covered by the union of already-kept features in its holder group (easements) or unit-name/jurisdiction group (fee): 1,180 duplicates out, 2,034 units kept, and every statistic recomputed.

Jurisdiction statistics use dissolved footprints (union of geometries), so residual overlaps are never double-counted. Separate footprints were computed for fee, easement, GAP 1-2, and open-access subsets against TIGER land area. Military boundaries came from the PAD-US Proclamation class (Des_Tp=MIL). Cross-validation against the DCR Conservation Lands Database (1,899 clipped units) showed 96.8 percent footprint agreement, with every residual discrepancy researched and documented. A haversine DBSCAN (eps 1,500 m, min_samples 5) on the 738 easement points resolved 19 conservation corridor clusters.

Key FindingsWhat the Data Shows

Analytical UsesWhat You Can Do With This

Synthesis OpportunitiesWhat It Combines With

Protected lands x data center inventory (Days 7/33): buffer the easement belt against substation and transmission corridors to map the developable-land squeeze on the westward data center frontier - a quantified constraint map for the region's dominant industry.

Protected lands x tree canopy change (Day 48): compare 2011-2021 canopy trajectories inside versus outside the protected footprint, per GAP class - an empirical protection-effectiveness test of whether easements actually hold canopy.

Open-access footprint x park access gap (park-access day): recompute green-space deserts counting only genuinely open-access protected land; closed easements and restricted federal land drop out of the supply side.

Easement clusters x wetland development pressure (Day 53): intersect high-pressure wetland clusters with the unprotected gaps between easement clusters to produce a ranked acquisition list for land trusts.

LimitationsKnown Caveats

Data DictionaryFields in the GeoPackage

FieldTypeDescriptionUnitsNull OK?
unit_nameTextProtected area or easement unit name from PAD-US-No
feat_classTextPAD-US feature class: Fee or Easement-No
own_typeTextOwner type code (FED, STAT, LOC, DIST, NGO, PVT, UNK)-Yes
own_nameTextOwner name code (e.g., CNTY, CITY, NPS, FWS)-Yes
local_ownerTextLocal owner name as submitted-Yes
mang_typeTextManager type code-Yes
mang_nameTextManager name code-Yes
local_managerTextLocal manager name as submitted-Yes
desig_typeTextPAD-US designation type (LP, CONE, SP, NWR, ...)-Yes
esmt_holderTextEasement holder as recorded (raw)-Yes
esmt_holder_normTextNormalized easement holder (spelling variants merged)-Yes
gap_statusTextGAP protection status 1-4 (1-2 = biodiversity mandate)-Yes
pub_accessTextPublic access: OA open, RA restricted, XA closed, UK unknown-Yes
iucn_catTextIUCN protected-area category-Yes
gis_acres_fullRealPAD-US acreage of the full (unclipped) unitacresYes
src_dateTextSource data date from the PAD-US aggregator-Yes
year_estIntegerEstablishment year parsed from Date_Est (41% populated)yearYes
nova_acresRealAcreage of the unit clipped to the 9 NoVA jurisdictions (EPSG:32618)acresNo
fipsTextJurisdiction FIPS of largest areal overlap-No
jurisdictionTextJurisdiction name-No

The military_installations layer carries unit_name, own_name, mang_name, desig_type, gis_acres_full, nova_acres, fips, and jurisdiction for the 9 DOD reference boundaries. The clusters GeoPackage adds cluster (DBSCAN id, -1 = noise) on easement representative points.

Jurisdiction BreakdownResults by Jurisdiction

JurisdictionUnitsProtected acFee acEasement ac% protected% GAP 1-2
Manassas Park City2334334017.3%12.79%
Fairfax County80742,84241,9271,44217.1%5.51%
Loudoun County56854,2038,95447,28016.4%0.20%
Prince William County22828,10825,8765,05013.1%7.08%
Alexandria City146782739468.2%0.05%
Arlington County2191,1021,066486.6%0.00%
Fairfax City2622021655.5%0.00%
Falls Church City15616014.6%0.00%
Manassas City23232232283.7%0.00%

Sources & CitationsAll Data is Openly Licensed