Data Center Corridor Air Monitoring

DEQ describes the goal of the project as an exploratory trend analysis of the sensor measurements, meant to establish whether areas with high numbers of data centers need additional regulatory air monitoring (DEQ staff, correspondence, 2026-08-16). The network exists to answer that question. It was not built to measure compliance, and most misreadings of these numbers start by treating it as though it were.

This page presents Virginia DEQ's Data Center Air Monitoring Project measurements for Loudoun County, March to August 2026, alongside the regulatory reference monitor collocated at one sensor site. The sensors are not regulatory instruments, and DEQ's statement of that limitation appears below, before any measurement does. Almost every hour in the record sits below the level of the federal standards, and the highest values coincide with a wildfire smoke episode that reached Virginia from roughly 1,500 miles away. What follows describes what was measured and where; it does not establish what produced any of the values, and no health data appears on this page.

DEQ's limitation statement · Full limitations · Data and methods

What DEQ says about this data

Quoted verbatim from Virginia DEQ

Important: This information is published as soon as the values are detected, and does not imply that the data have passed quality assurance validation procedures.
Virginia DEQ, Data Center Air Monitoring Project public dashboard, Information tab. https://kunakcloud.com/websites/VirginiaDEQ.html. Retrieved 2026-08-11.
The sensors displayed on this page are not regulatory instruments as specified in the Code of Federal Regulations (CFR), that is, they cannot be used in determining attainment or non-attainment of the National Ambient Air Quality Standards (NAAQS). Only Federal Reference/Equivalent Method designed monitors can. However, they are still useful to get a general idea of pollutant trends and general concentrations.
Virginia DEQ, Data Center Air Monitoring Project public dashboard, Information tab. https://kunakcloud.com/websites/VirginiaDEQ.html. Retrieved 2026-08-11.
These sensors are capable of collecting pollutant concentration data and establishing pollutant concentration trends, but they are not regulatory instruments as specified in the Code of Federal Regulations (CFR). They cannot be used in determining attainment or non-attainment of the National Ambient Air Quality Standards (NAAQS). Only Federal Reference/Equivalent Method designated monitors can.
Virginia DEQ, Office of Air Quality Monitoring, "Data Center Air Quality Analysis", August 7, 2026. https://www.deq.virginia.gov/news-info/shortcuts/topics-of-interest/data-center-air-monitoring-project. Retrieved 2026-08-11.

GENARCH's own wording, from here on

A single hourly reading above 35 µg/m³ is not measured against the 24-hour PM2.5 standard and does not by itself show that the standard has been surpassed. The regulatory form of that standard is the 98th percentile of daily 24-hour averages, averaged over three consecutive years. The separate annual standard is 9.0 µg/m³, as revised in 2024. DEQ's published analysis makes the same point about hourly values.

Sensor measurements come from the public Kunak Cloud export, by the download method DEQ staff confirmed on 2026-08-10, and are redistributable with credit to Virginia DEQ. Regulatory monitor measurements were released under Virginia FOIA request 26-4646 on 2026-08-11, in full, and are public at vadeq.nextrequest.com/requests/26-4646.

Where the sensors sit

DEQ identified 22 potential locations in Loudoun County and has deployed seven sensors so far, two of which have been relocated once each. The network measures where it sits, and a finding drawn from these twelve records describes those twelve locations rather than the corridor as a whole.

DEQ reports a wind rose built from Dulles Airport measurements and states that winds during the study period came predominantly from either the south or the northwest. On that basis DEQ describes the collocated Ashburn site and the Dulles-area site as good upwind sites with regard to Data Center Alley (Virginia DEQ, Office of Air Quality Monitoring, "Data Center Air Quality Analysis", August 28, 2026). That is DEQ's characterisation of the geometry of its own network, and it is carried here as DEQ's statement. It does not establish that any particular site is downwind of any particular facility, and nothing on this page draws that inference.

Sensors are identified here by DEQ site identifier and locality rather than by DEQ's published site label. Four of the twelve locations are hosted at schools, and placing a school name beside a concentration figure invites an inference about children at that school that nothing in this data supports. The identifier crosswalk in section 9 maps every identifier to DEQ's exact published label, so this page can still be checked against DEQ's report.

Zero of the twelve site records are not reachable through the public dashboard, which shows those locations without a device. Their historical measurements are not downloadable, so they carry no series anywhere on this page. Zero absent site records are not the same thing as no data at those locations.

DEQ sensor sites: identifier, locality, hardware unit, occupancy window, status, valid hours of PM2.5 data, and whether the site is collocated with the regulatory monitor.
SiteAreaUnitOccupancyStatusValid hoursCollocated
ashburn-collocatedAshburnAPEX 14, APEX 52026-03-03 to presentCollecting5,150Yes
belfort-parkSterlingAPEX 142026-05-14 to presentCollecting3,547No
camp-snyderHaymarketAPEX 102026-09-17 to presentCollecting551No
dulles-areaSterlingnot confirmed2026-03-03 to presentCollecting4,991No
evergreen-ccHaymarketAPEX 62026-09-18 to presentCollecting541No
farmwell-middleAshburnnot confirmed2026-04-08 to 2026-09-18Retired3,859No
golf-courseAshburnnot confirmed2026-04-08 to 2026-09-18Retired3,865No
heritage-farmSterlingnot confirmed2026-03-03 to 2026-06-18Retired1,963No
newberry-condoSterlingnot confirmed2026-03-03 to 2026-05-15Retired1,593No
sterling-msSterlingAPEX 62026-06-18 to 2026-09-18Retired2,182No
steuart-wellerAshburnAPEX 62026-03-03 to 2026-06-18Retired2,393No
vdot-mkcManassasAPEX 132026-09-16 to presentCollecting560No

Occupancy windows and hardware unit assignments come from DEQ's site history. One site shows two units because the hardware was swapped in place on 2026-04-08; those two deployments are treated separately throughout. 0 sites carry no valid-hour count because no export exists for them: . Sensor coordinates are not published in machine-readable form, so no map is drawn here.

Hourly PM2.5, sensors and regulatory monitor

Hourly PM2.5 by site

Sensor and regulatory series are drawn as separate lines and are never combined into one series: they are different instrument classes, and DEQ's regulatory limitation applies to the sensors alone. Hours excluded under the DEQ validity rule are drawn as gaps rather than as zero or as an interpolated value. Source: deq_data_center_air_monitoring_hourly.csv and deq_regulatory_monitor_hourly.csv.
Show per-site summary, with and without the smoke-transport window
Show per-site summary, with and without the smoke-transport window
SiteClassHoursMean µg/m³Max µg/m³Hours excl. smokeMean excl. smokeMax excl. smoke
ashburn-collocated (Ashburn)Sensor5,1507.77123.115,0547.0734.04
belfort-park (Sterling)Sensor3,5478.08132.183,4517.0237.17
camp-snyder (Haymarket)Sensor5513.9122.335513.9122.33
dulles-area (Sterling)Sensor4,9915.40114.714,8954.7833.54
evergreen-cc (Haymarket)Sensor5412.7316.355412.7316.35
farmwell-middle (Ashburn)Sensor3,8597.98157.913,7636.8848.07
golf-course (Ashburn)Sensor3,8657.35119.763,7696.3538.48
heritage-farm (Sterling)Sensor1,9634.1526.621,9634.1526.62
newberry-condo (Sterling)Sensor1,5935.7353.701,5935.7353.70
sterling-ms (Sterling)Sensor2,1829.47149.532,0867.7937.91
steuart-weller (Ashburn)Sensor2,3934.5433.332,3934.5433.33
vdot-mkc (Manassas)Sensor5603.3316.295603.3316.29
ashburn regulatory monitor (Ashburn)Regulatory3,0408.44282.502,9446.4628.50

Every summary figure near this chart is given twice, once over the whole record and once with 2026-07-16 to 2026-07-19 removed. A statistic pooled across the smoke episode and ordinary conditions sits between two regimes and describes neither. At the regulatory monitor the mean over the full record is 8.44 µg/m³ across 3,040 valid hours, and 6.46 µg/m³ across 2,944 hours with the smoke window removed. The highest single hour in the whole record, 282.5 µg/m³, falls inside that window; outside it the highest hour is 28.5 µg/m³.

Four separate periods are voided in the source data, and the chart shows each as a gap. DEQ's August 7 report records regulatory PM2.5 voided 2026-05-07 to 05-10 and 2026-06-16 to 07-14 for failed data quality analysis and instrumentation issues, regulatory NO2 voided 2026-05-07 to 05-10, sensor PM2.5 voided 2026-03-03 to 03-08 at every site for high humidity and sensor data quality, and PM2.5 collection at one retired site ending 2026-05-30 after an air flow failure in the particle sensor. In the released record the fully void days are narrower than the stated windows, 05-08 to 05-09 and 06-17 to 07-13, because the days at each boundary are partly valid.

Sensor against regulatory monitor at the collocated site

DEQ operates one sensor at the same location as its regulatory reference monitor, and has published a regression between the two every week since the project began. Two different hardware units have occupied that position: APEX 14 from 2026-03-03 to 2026-04-08 and APEX 5 from 2026-04-08 onward. They are treated separately throughout, since pooling two instruments into one regression describes neither.

The table sets DEQ's coefficients beside coefficients computed by GENARCH's pipeline from the source tables. This is a verification of that pipeline against an authoritative source, not a new result: DEQ published the analysis first and publishes it on a weekly cycle.

DEQ's regression coefficients beside coefficients computed by GENARCH, for each hardware unit and pollutant. Sensor on the x axis, regulatory monitor on the y axis. A dagger marks the one DEQ row that came from correspondence rather than from a report.
ComparisonDEQGENARCHnStatus
APEX 14 PM2.5y = 1.3 + 0.83x, R² = 0.73y = 1.299 + 0.831x, R² = 0.725697Checked by the build
APEX 5 PM2.5y = -4.7 + 1.7x, R² = 0.84y = -4.678 + 1.665x, R² = 0.8372,111Checked by the build
APEX 14 NO2y = 2.2 + 1.1x, R² = 0.49y = 2.186 + 1.075x, R² = 0.497589Checked by the build
APEX 5 NO2y = 1.8 + 0.32x, R² = 0.21 corrected by DEQ; see the note below the tabley = 1.847 + 0.317x, R² = 0.2042,746Recorded , not compared; see the note below the table

APEX 5 NO2: the August 7, 2026 edition published y = 1.9 + 0.29x, R² = 0.17. DEQ later corrected that fit, and the August 21, 2026 edition prints the corrected form at y = 1.8 + 0.31x, R² = 0.2 over that edition's longer record (Virginia DEQ, Office of Air Quality Monitoring, "Data Center Air Quality Analysis", August 21, 2026). The column above holds the corrected fit over the August 7, 2026 window instead, because that is the window the GENARCH column is computed on. DEQ supplied those coefficients by correspondence on 2026-08-19.

The DEQ column is the August 7 edition apart from the daggered row, and the GENARCH column stops at 2026-08-07 07:00 EST. DEQ produces each edition on Friday morning from data through 07:00 that day. The cutoff is the agency's specification, not an assumption made here (DEQ staff, correspondence, 2026-08-16). DEQ reissues this analysis every week, so a comparison that names no edition is measured against a target that moves.

Three later editions have since shipped, and the column stays on August 7 anyway. That is the window the GENARCH column is computed over, and it is where the regulatory record released under FOIA 26-4646 ends, on 2026-08-10. Setting a coefficient refitted on a longer record beside a fit that stops at August 7 would compare two spans rather than two calculations. Extending the comparison to the August 28, 2026 edition needs regulatory data that has been requested and not yet released.

The APEX 14 collocation period closed on 2026-04-08, which fixes the two APEX 14 regressions: no later week of data can enter them, and they print identically in all four editions. The APEX 5 window is still open, so each edition refits those two on a week more data than the last, and their coefficients move accordingly.

Three of the four comparisons are checked by the build, against a tolerance of 0.05 on slope and intercept and 0.03 on R², and all three agree. DEQ publishes these coefficients to two significant figures, so the claim is that these fits round to DEQ's values at DEQ's own precision. Agreement to three decimals is not something this data can establish, and part of every difference in the table is that rounding rather than a difference in the underlying fit.

The APEX 5 NO2 row is recorded rather than checked. Its DEQ side is the 2026-08-19 correspondence, refit over DEQ's record to that date, while the GENARCH fit beside it stops at 2026-08-07 07:00 EST. The fit cannot be extended to meet it, because a collocation fit needs both sides of each hourly pair and the regulatory record released under FOIA 26-4646 ends 2026-08-10. Neither side can be moved, so no change here makes the comparison valid, and a check that passed on it would not mean what the other three mean. Both figures stay in the table and the check returns when the extended regulatory record arrives.

The rows do not carry equal weight. The two APEX 14 rows compare against a closed window whose published values cannot move, so they are the same calculation on both sides. The APEX 5 rows compare against a window DEQ is still refitting, and the checked one lines up only because the column above is pinned to the same August 7 span. Read as a count of matches the four would say more than they can support.

The fourth took a round of correspondence to get there. The APEX 5 NO2 figure printed in the August 7 edition did not reproduce here, so the question went to DEQ. DEQ traced it to the plotting call behind the chart: the axis limits there bounded the model fit as well as the plotted view, so points outside them never entered the regression. Refitting without the limits over the August 7 window gives y = 1.8 + 0.32x, R² = 0.21, and DEQ sent the paired hourly measurements the regression runs on (DEQ staff, correspondence, 2026-08-19).

The correction is now in print. The August 21, 2026 edition carries the unbounded fit, at y = 1.8 + 0.31x, R² = 0.2 over a record two weeks longer than the one this table compares on. Those coefficients describe that longer window, so this page cites them here rather than setting them in the column above.

The same fit computed from the source tables gives y = 1.847 + 0.317x, R² = 0.204 on 2,746 paired hours, inside tolerance of the corrected coefficients. That fit keeps the sensor's exact-zero readings, 17.6 percent of the APEX 5 window's NO2 hours in runs as long as 45 hours, because DEQ keeps them (DEQ staff, correspondence, 2026-08-19). Everywhere else on this page they stay excluded as a per-pollutant floor clamp. Dropping them here returns slope 0.340 and R² 0.199 on 2,261 pairs, the figure this page carried before, which left zero handling as the only remaining difference between the two calculations.

Agreement on the coefficients does not make the relationship a strong one. At an R² near 0.21 this is the weakest of the four, and its coefficients are loosely determined. At 10 ppb on the sensor the two lines sit 0.02 ppb apart, on a series whose regulatory mean is 3.5 ppb.

Applying the same null-code and flag exclusions and an 18-of-24 completeness rule, recomputed daily averages match DEQ's published daily file on 118 of 119 comparable days after truncation to one decimal, with a mean absolute difference of 0.0017 µg/m³. DEQ truncates published values rather than rounding them.

The single day that differs is 2026-03-10, where the recomputation gives 5.0 against a published 5.2. DEQ staff reviewed that date, said that recomputing from hourly values also gives 5.0, and noted that they were unsure why the invalid hour at 10:00 was not excluded from the published daily export (DEQ staff, correspondence, 2026-08-16).

DEQ's analysis: Data Center Air Quality Analysis, August 7, 2026. Project page: Virginia DEQ Data Center Air Monitoring.

What the 98th percentile points at

The name “98th percentile” is fixed, but the observation it is read from is not. Under the linear-interpolation definition the index is (n − 1) × 0.98, so the statistic moves through the distribution as the record grows. On 51 days it falls at the 50th of 51, effectively the second-highest daily value in the record. On 152 days it falls at the 148th–149th of 152, roughly the fourth-highest, drawn from a denser part of the distribution. Setting one beside the other compares a near-maximum against a genuine upper-tail quantile.

How much that matters can be measured. Holding the data fixed and changing only the interpolation convention moves the shortest record's 98th percentile by 13.27 µg/m³, against 0.35 to 2.33 µg/m³ for the longer records (sensor cutoff 2026-08-28, Kunak export 2026-08-28, outputs/repro/p98_common_window_2026-08-28.csv). A statistic that moves that far on a choice of convention is not measuring a difference between sites.

The instability is not confined to the short record. At every site the 98th percentile of daily PM2.5 falls inside a wide gap between the bulk of the distribution and the July smoke days, and the two daily values it is interpolated between are themselves smoke days. Moving the day boundary by one hour, which is the difference between binning days on local standard time and on local clock time, shifts the statistic by up to 2.12 µg/m³ while leaving the mean unchanged to within 0.05 (sensor cutoff 2026-08-27, Kunak export 2026-08-28, docs/PERCENTILE_METHOD.md). At these sample sizes the 98th percentile of daily PM2.5 is sensitive to defensible methodological choices at every site, not only at the shortest-record one.

The series below illustrates the point rather than carrying it. Table 4 of DEQ's August 7, 2026 report named one sensor as the only one whose 98th percentile of daily PM2.5 averages sat above 35 µg/m³. That sensor, sterling-ms, had the shortest record in the network: it began collecting on 2026-06-18 and had 51 days at that cutoff against 152 at ashburn-collocated, entirely in high summer, with 7.8 percent of its record inside the smoke-transport window of 2026-07-16 to 2026-07-19 against 2.6 percent of the longest one. The figure fell in each edition that followed, and on the August 28, 2026 report no site sits above 35 µg/m³. This is a methodological point about the statistic. It is not a correction of a standing DEQ error: the falling figure is DEQ's own, published in DEQ's own consecutive editions.

Figures published for sterling-ms in four consecutive editions of DEQ's weekly analysis, oldest first, with the change across the full span in the last column. Each edition covers a week more of the record than the one before.
DEQ figure for sterling-msAug 7Aug 14Aug 21Aug 28Aug 7 to Aug 28
98th percentile of daily PM2.5 averages (µg/m³)40.438.236.033.8-6.6
98th percentile of hourly PM2.5 (µg/m³)69.162.356.853.6-15.5
Mean hourly PM2.5 (µg/m³)11.311.110.810.5-0.8

The sentence naming this sensor as the only one above 35 µg/m³ stood word for word through the first three editions while the figure it described fell in every one: 40.4 on Aug 7, 38.2 on Aug 14, 36.0 on Aug 21, 33.8 on Aug 28. The August 28, 2026 edition drops that sentence and states instead that no site's 98th percentile of daily averages sits above the 35 µg/m³ level. DEQ staff said they expected the figure to keep falling as the record lengthened (DEQ staff, correspondence, 2026-08-16). The first three editions are archived under docs/deq-reports/ and the Aug 28 edition under pipeline/sources/deq/, because DEQ's published page carries only the current one.

DEQ staff note that the wildfire smoke data heavily skews the 98th percentiles at every site, and that before the smoke arrived they sat at or below about 20 µg/m³ everywhere (DEQ staff, correspondence, 2026-08-16). The percentiles in the table below include that window.

Restricting every sensor to the window in which all twelve were collecting, 2026-06-18 to 2026-08-07, changes the ordering. Five of nine sites sit above 35 µg/m³ on matched windows, and sterling-ms ranks fourth rather than first. The common window is not a clean control on its own: it falls entirely in high summer and contains the smoke window, so it removes the unequal-length difference and leaves the unequal-seasonality one in place.

For each site: days, 98th percentile of daily PM2.5 averages, and the ranked observation that percentile is read from, over the site's own record and over the common window in which all deployed sensors were collecting.
SiteDays, own recordp98, own recordRank, own recordDays, commonp98, commonRank, common
farmwell-middle12027.20117th–118th of 1205045.4049th–50th of 50
belfort-park8430.7282nd–83rd of 845040.1949th–50th of 50
golf-course12224.88119th–120th of 1225140.1250th of 51
sterling-ms5138.2150th of 515138.2150th of 51
ashburn-collocated15225.85148th–149th of 1525137.1050th of 51
dulles-area14920.77146th–147th of 1495029.5049th–50th of 50
heritage-farm829.7380th–81st of 820NaN0th–0th of 0
newberry-condo6614.5264th–65th of 660NaN0th–0th of 0
steuart-weller10010.2098th–99th of 1000NaN0th–0th of 0

The rank columns give the observation each percentile is read from. At 51 days the 98th percentile is the 50th of 51; at 152 days it is the 148th–149th of 152. The statistic carries the same name at every record length and sits at a different position in the distribution at each one.

98th percentile, own record against common window

Daily averages are computed under the 18-of-24 completeness rule, and each site's record is cut at 2026-08-07 to match the date of DEQ's report. Neither set of percentiles is comparable to the federal standard; see the qualifications below. Source: deq_data_center_air_monitoring_hourly.csv.
Show the percentile table, including rank position and smoke-window share
Show the percentile table, including rank position and smoke-window share
SiteDays, own recordp98, own recordRank, own recordDays, commonp98, commonRank, commonSmoke share of record
farmwell-middle (Ashburn)12027.20117th–118th of 1205045.4049th–50th of 503.3%
belfort-park (Sterling)8430.7282nd–83rd of 845040.1949th–50th of 504.8%
golf-course (Ashburn)12224.88119th–120th of 1225140.1250th of 513.3%
sterling-ms (Sterling)5138.2150th of 515138.2150th of 517.8%
ashburn-collocated (Ashburn)15225.85148th–149th of 1525137.1050th of 512.6%
dulles-area (Sterling)14920.77146th–147th of 1495029.5049th–50th of 502.7%
heritage-farm (Sterling)829.7380th–81st of 820NaN0th–0th of 00.0%
newberry-condo (Sterling)6614.5264th–65th of 660NaN0th–0th of 00.0%
steuart-weller (Ashburn)10010.2098th–99th of 1000NaN0th–0th of 00.0%

Three qualifications on the numbers above

Neither DEQ's figures nor these are comparable to the federal standard. That standard is a 98th percentile of daily averages across a full year, averaged over three years. A 51-day percentile is not that statistic, and nothing about attainment or non-attainment follows from either set of numbers.

This corrects a comparison between monitoring sites. It is not a statement that any location is polluted, and it is not a statement about anyone's health.

GENARCH's own-record percentiles differ from DEQ's Table 4 by up to roughly 2.4 µg/m³ in both directions, higher at some sites and lower at others. The most likely explanation is the treatment of exact-zero sensor readings, which this pipeline excludes as a fault mode rather than counting as measurements. That explanation is not established, and the difference is disclosed here rather than resolved.

How closely the sites track each other

Pairwise correlation of hourly PM2.5

Smoke-transport window excluded, and exact-zero sensor readings treated as missing rather than as measurements. Hour counts differ by pair because the sites were not all collecting over the same period. Source: deq_data_center_air_monitoring_hourly.csv.
Show every pair as a list, with its hour count
Show every pair as a list, with its hour count
Site ASite BrOverlapping hours
sterling-msvdot-mkc1.0002
belfort-parkgolf-course0.9602,886
golf-coursesterling-ms0.9602,078
belfort-parksterling-ms0.9532,073
farmwell-middlesterling-ms0.9512,074
farmwell-middlegolf-course0.9463,737
ashburn-collocatedsterling-ms0.9372,085
belfort-parkfarmwell-middle0.9352,879
ashburn-collocatedfarmwell-middle0.9293,757
ashburn-collocatedgolf-course0.9273,753
dulles-areagolf-course0.9123,644
farmwell-middlesteuart-weller0.9111,668
ashburn-collocatedbelfort-park0.9093,447
ashburn-collocatedsteuart-weller0.9002,384
dulles-areafarmwell-middle0.8923,632
belfort-parkdulles-area0.8883,306
belfort-parkheritage-farm0.876374
ashburn-collocateddulles-area0.8764,875
dulles-areasterling-ms0.8751,995
belfort-parksteuart-weller0.874801
dulles-areasteuart-weller0.8542,337
golf-coursesteuart-weller0.8521,654
ashburn-collocatedheritage-farm0.8511,956
dulles-areanewberry-condo0.8461,557
golf-courseheritage-farm0.8381,231
newberry-condosteuart-weller0.8331,589
camp-snyderevergreen-cc0.832534
heritage-farmnewberry-condo0.8301,585
dulles-areaheritage-farm0.8281,925
camp-snyderdulles-area0.827520
ashburn-collocatedcamp-snyder0.825548
farmwell-middleheritage-farm0.8201,237
heritage-farmsteuart-weller0.8021,954
ashburn-collocatedvdot-mkc0.801555
ashburn-collocatednewberry-condo0.8011,582
farmwell-middlenewberry-condo0.795871
dulles-areaevergreen-cc0.760512
belfort-parkvdot-mkc0.753554
camp-snydervdot-mkc0.738545
belfort-parkcamp-snyder0.730546
ashburn-collocatedevergreen-cc0.720541
golf-coursenewberry-condo0.707857
dulles-areavdot-mkc0.681525
belfort-parkevergreen-cc0.679539
evergreen-ccvdot-mkc0.660538
farmwell-middlevdot-mkc-1.0002

All 46 pairwise correlations fall between -1.000 and 1.000. This is a description of how the series move together and nothing more. High spatial correlation does not establish that local sources contribute nothing: the deployed sensors may sit largely upwind, and a local increment can be masked by a dominant regional signal.

The ratio between the highest and lowest site reading in a given hour is not a usable discriminator here. It fails below roughly 30 µg/m³, where small absolute differences produce large ratios. Across 5,076 hours the median ratio is 1.86, and low-concentration hours reach ratios above 235 from differences under a microgram per cubic metre.

Limitations

Data and methods

Site identifier crosswalk

This table carries identifiers only. It holds no measurement of any kind, and none may be added to it. It exists so that a reader can map every identifier used on this page onto DEQ's published site labels and check the work against DEQ's report.

Crosswalk from GENARCH site identifier to locality, DEQ published site label, and the label string shown on the Kunak dashboard.
GENARCH identifierAreaDEQ published labelKunak dashboard label
ashburn-collocatedAshburnBroad Run HSBroad Run HS
belfort-parkSterlingBelfort Park DrBelfort Park Dr
camp-snyderHaymarketCamp William B SnyderCamp William B Snyder
dulles-areaSterlingDulles AirportDulles Airport
evergreen-ccHaymarketEvergreen Country ClubEvergreen Country Club
farmwell-middleAshburnFarmwell Station MSFarmwell Station MS
golf-courseAshburn1757 Golf Club1757 Golf Club
heritage-farmSterlingHeritage Farm MuseumHeritage Farm Museum
newberry-condoSterlingNewberry Condo AssocNewberry Condo Assoc
sterling-msSterlingSterling MSSterling MS
steuart-wellerAshburnSteuart Weller ESSteuart Weller ES
vdot-mkcManassasVDOT MKCVDOT MKC

Source tables

Provenance for each source table: retrieval method, retrieval date, coverage, licence, and a download link.
FileRetrievalDateLicence
deq_data_center_air_monitoring_hourly.csv17.1 MB2026-03-03 to 2026-08-28, six sites, 19748 site-hours, 59244 rowspublic Kunak Cloud CSV export, method confirmed by DEQ staff 2026-08-102026-08-28Fully redistributable with credit that the data belong to Virginia DEQ (per DEQ staff, 2026-08-10). Preferred attribution line pending from DEQ Communications.
deq_regulatory_monitor_hourly.csv1.4 MB2026-03-03 to 2026-08-10, 11592 rows: ASHBURN PM2.5 (method 638) and NO2 (method 212), AURHILL CO (method 54)Virginia FOIA request 26-4646, released in full 2026-08-112026-08-11Public records released in full under the Virginia Freedom of Information Act, no redactions, no cost. Credit Virginia DEQ.
deq_pm25_daily.csv0.1 MB2026-03-03 to 2026-08-10, six sensor sites and the Ashburn regulatory monitorderived by the pipeline from deq_data_center_air_monitoring_hourly.csv and deq_regulatory_monitor_hourly.csv; published values from AshburnPM2.5_dailyAvg_030326_081026.xls, released under FOIA 26-46462026-08-11Public records released in full under the Virginia Freedom of Information Act, no redactions, no cost. Credit Virginia DEQ.

Exclusion rule

A reading is excluded if the value is missing, an AQS Null Code is present, or the Flags field contains a less-than character. No letter code alone excludes a reading. Flags are case-sensitive: the same letter in upper and lower case identifies two different events, and folding the case of that column silently merges them. A 24-hour average is computed only from 18 or more valid hours. The full rule set is recorded in docs/GENARCH_RULES.md section 3.

Licence and attribution

Fully redistributable with credit that the data belong to Virginia DEQ (per DEQ staff, 2026-08-10). A preferred attribution line is pending from DEQ Communications and will be added here when it is received.

Sensor coordinates are not published in machine-readable form. A map of the network will be added here once a citable coordinate source is available from DEQ.

Pipeline source and page source: github.com/ksaraiya388/GENARCH. GENARCH methods: /methods.