Shoreline Change

What is a shoreline baseline in transect-based erosion analysis?

A grassy coastal bluff eroding above a sandy beach, with waves meeting the shore below.

If you've run shoreline change rates through DSAS (the Digital Shoreline Analysis System) or a similar transect-based workflow, you've already placed a baseline, even if nobody called it that on the drawing. The baseline is the reference line you draw landward or seaward of every shoreline position you're going to measure. Everything else in the analysis, the transects, the cast distance, the rate calculation, gets built off that one line.

It sounds like a small setup step. It isn't. A baseline drawn wrong, or a baseline that drifts between study years, quietly throws off every retreat and accretion number downstream of it.

What the baseline is actually for

DSAS and most transect tools work by casting perpendicular lines, transects, out from the baseline at a set interval. Each transect crosses your digitized shoreline positions (1998, 2004, 2010, whatever years you have), and the software measures the distance from the baseline to each shoreline crossing along that transect. Change rate between years at that point is just the difference in those distances over time.

So the baseline itself carries no erosion information. It's a ruler's zero mark, not a measurement. But because every transect's geometry depends on it, an unstable or oddly shaped baseline produces transects that don't stay perpendicular to a curving shoreline, and you get measurement error that has nothing to do with real coastal change.

Most agencies draw the baseline on the landward side, set back from the most landward shoreline position in the study (usually a dune toe, bluff edge, or armoring structure), so every transect only has to cast seaward. Some shops draw it offshore instead, particularly where accretion has pushed shorelines out past an old reference. Either approach works, but the baseline has to hold still: the same line, over the same study area, every single year you re-run the analysis.

Baseline offset distance and transect spacing

Two settings decide how much of the coast your baseline actually constrains.

Baseline offset distance is how far back the baseline sits from the shoreline it's measuring. Set it too close and a baseline drawn before a storm event can end up landward of a post-storm shoreline position, which breaks the perpendicular cast. Set it too far back and the baseline smooths over local curvature, so transects stop tracking the actual shape of an inlet or a headland. A common approach is to offset far enough that even the most eroded or accreted historical shoreline in your dataset stays on the correct side of the baseline, with some margin for the next survey.

Shoreline transect spacing is the distance between each perpendicular cast, often 50 m, sometimes tighter (10 to 25 m) around inlets, groins, or other features where the shoreline bends sharply over short distances, and looser along long straight beach stretches where one segment behaves like the next. Tighter spacing gives you more data points and a finer-grained erosion picture, but it also means more transects to QA, more crossings to check, and a heavier baseline-and-transect file to maintain every time you add a year.

Where this gets tedious for actual agency work

None of this is conceptually hard. Drawing one baseline, generating transects, and checking that they cross each annual shoreline cleanly is a reasonable afternoon in ArcGIS or QGIS, for one study reach, for one year. The grind shows up when you're maintaining this for a county's worth of coastline, re-digitizing the waterline from new imagery every year, and re-checking that your existing baseline and transects still behave for shorelines that have since moved.

That's the part Shoreline Change is built around: extracting a consistent waterline from each year's high-res satellite pass so the shoreline positions feeding your transects are already there, segment by segment, instead of re-traced by hand against last year's baseline.

If your baseline and transect network are solid and the shoreline layer is the part eating your time every cycle, it's worth seeing what an annual waterline layer does to that workload.

Get started

← Back to the blog