DSAS vs. satellite-derived waterline extraction: what's the difference?

If you've spent any time in the shoreline change literature, you've run into DSAS. The USGS's Digital Shoreline Analysis System has been the default stats engine for coastal erosion studies since the 1990s, and most state coastal management plans cite it somewhere. So when someone asks "DSAS or satellite-derived waterline extraction," it's worth stopping to sort out what each one is, because they do different jobs in the same workflow.
DSAS is a calculator, not a mapmaker
DSAS doesn't find your shoreline. It's an ArcGIS add-in that takes shoreline positions you already have, lays down a baseline, casts transects perpendicular to that baseline at whatever spacing you set, and calculates rate statistics at each transect: end-point rate, linear regression rate, net shoreline movement, and a few others depending on the version. Feed it two shorelines from different years and it gives you a rate between them. Feed it ten and it runs a regression across all of them.
What DSAS needs from you, every time, is a set of shoreline vectors, one per date, already digitized. It has no opinion about where those vectors came from. That's the part people conflate with "satellite-derived waterline extraction."
Waterline extraction is how you get the input DSAS runs on
Waterline extraction is the upstream step: taking imagery and tracing where land meets water. For decades that line got digitized by hand off aerial orthophotos, pulled from a lidar-derived high-water mark, or walked with GPS-RTK gear at low tide. All three produce a shoreline vector that's DSAS-ready, regardless of which extraction method produced it. An automated extraction run on a satellite pass produces the same kind of vector. That's the piece people mean when they say "satellite-derived."
The real difference between hand-digitizing and automated extraction sits upstream of DSAS entirely: how consistently the waterline gets defined from one year to the next, and how much labor it takes to produce that vector for a long stretch of coast, every single year.
Why the input method changes what DSAS tells you
DSAS rate statistics are only as good as the shoreline positions you feed it. If one year's shoreline was digitized by an analyst tracing the wet/dry sand line, and the next year's came from someone else tracing the base of the dune, your "erosion rate" partly reflects two people reading a photo differently rather than the coast moving. Manual digitizing is slow enough that a lot of coastal programs only refresh their baseline shorelines every few years, which flattens out the year-to-year swings that matter when you're trying to flag a segment before it turns into a problem.
Running the same extraction logic against a new satellite pass every year, instead of asking a different person to trace a different photo each time, is what keeps the input to DSAS, or any transect-based shoreline tool, consistent enough to trust segment by segment.
That's the gap Shoreline Change was built to close. It extracts the waterline from an annual high-resolution multispectral satellite pass, consistently, year after year, and hands back an annual waterline layer plus a retreat or accretion rate per segment you define, without sending a crew out to re-survey the coast each season. You can see how that works before deciding whether it fits your monitoring program.
So which one do you need
If you already run DSAS, or any transect-based shoreline tool, for your rate statistics, you still need a reliable source of annual shoreline vectors to feed it. That's a waterline extraction question as much as a DSAS question. Satellite-derived extraction and DSAS sit at two stages of the same workflow: one produces the shoreline vector, the other calculates rates across a stack of those vectors over time.
The question worth asking for your program is whether your current shoreline-vector pipeline gives you the annual consistency a transect-based tool needs to produce a rate you'd stand behind in a planning document.
If an annual, consistently extracted waterline for your stretch of coast sounds like the missing piece, get in touch with Shoreline Change.