Atmospheric hazards
The Quarto build for Computational Geography renders chapter HTML under /computational-geography/. This stub demonstrates the chapter chrome — book navbar above, sticky chapter TOC on the left, reading progress bar at the top, and chapter pagination at the bottom — so you can iterate on chrome and typography without rebuilding the book.
Working with messy data
Most of what follows is about building reliable workflows. Coordinates are not numbers — they're agreements about projection and datum. Datasets disagree. The first job of an analyst is to make the disagreements visible, not to hide them.
Worked example
Consider a stream-network polyline draped over a 10 m DEM. The DEM was sampled at one resolution, the polyline derived at another, and the cells under the line do not match the line's reported elevation. There is no "right" answer; there is only the answer you choose to defend, and the audit trail you leave behind.
Where this leads
The next chapter takes this further into hydrology, where the same disagreements compound into watershed boundaries that move depending on which DEM you used. We will build the pipeline together.