How it's built

One static page, the whole public record

This atlas gathers every public water-quality measurement on the Pyramid Lake Paiute Reservation and within a short distance of it into one map: the lake, the lower Truckee River, and the wells and gauges around them. It highlights the Tribe's own monitoring program and compares the record with the Tribe's EPA-approved water quality standards. There is no server behind it and no database: a data pipeline in R does the work ahead of time and the browser reads small pre-built files.

Where the data comes from

The pipeline

  1. 1
    Pull and preserve. An R pipeline built on targets pulls the record one characteristic at a time, subdividing requests until the portal answers, and stores each pull as a dated Parquet snapshot. Raw values stay as text: the archive is testimony, and typing is interpretation applied later, once, visibly.
  2. 2
    Archive. Snapshots copy to append-only object storage with content-hash verification. Nothing is ever overwritten. Package versions are pinned with renv, so any machine rebuilds the same result.
  3. 3
    Shape. A second script joins measurements to sites, computes per-site statistics and yearly medians, dissolves the stream network for labels, and writes one small JSON record per monitored site. QGIS is the cartographic workbench alongside it.
  4. 4
    Show the record, then test on request. A site opens to every sample as measured, nondetects drawn hollow at their limits, nothing removed and nothing fitted. Only when asked does a trend engine run the Seasonal Kendall test with a Sen slope on every site and parameter with at least 20 samples over 10 years: month is the season, so seasonal cycles never masquerade as trends, and nondetects enter as tied lowest ranks rather than being dropped. Every result carries its p-value, method, and period, and the map can be colored by it. The stories use the same discipline: sites downstream of a fire, a mine, or a restoration are traced through the stream network and compared against sites elsewhere, before and after, and the page writes its verdict from the numbers.
  5. 5
    Tile and ship. Every layer packs into a single PMTiles archive. The browser fetches only the byte ranges it needs, so the whole basin loads from one file on any static host.

Why it is built this way

Stack

R · targets · renv · dataRetrieval · sf · nhdplusTools · arrow · QGIS · tippecanoe · PMTiles · MapLibre GL JS · plain HTML, CSS, and JavaScript · Census PL 94-171 · NRCS AWDB · USGS Water Data API · NWS · NIFC

Want one for your watershed? The atlas is built by DANalytics Environmental in Carson City, Nevada. Data kept current, trends computed, and a branded instance on your own domain.

Get in touch ↑ Back to the map