Landsat

Landsat is the memory of open Earth observation. Running continuously since the early 1970s through a succession of satellites, it is the longest unbroken civilian record of the land surface, and that longevity — not any single technical specification — is what makes it indispensable. When a question is about change over decades rather than the state of things this week, Landsat is usually the source that can answer it, because it was already watching. This page is about what the program contributes as a data source: why a long, consistent archive is worth so much, what its measurements can and cannot do, and how you reason about using imagery that spans several instrument generations. As with every source here, the ideas hold regardless of the platform you eventually open the data on.

What the long record contributes

The defining feature of Landsat is continuity. A single date of imagery tells you what a place looks like now; a multi-decade archive of comparable dates tells you how it got there, and that is a different and often more valuable kind of knowledge. Because the program has maintained broadly consistent bands, geometry, and calibration across its satellites, you can line up an image from decades ago against one from this year and treat the difference as signal about the ground rather than an artifact of switching instruments. That is exactly the multi-date reasoning the Time Series concept develops and the foundation the Change Detection concept builds on. For historical baselines — what a forest, coastline, or city edge looked like before a disturbance — there is frequently no substitute, simply because no other open optical record reaches as far back.

Strengths for long-term monitoring

Landsat’s strengths follow directly from that continuity. It excels at land-cover history and trend analysis: mapping how forest, cropland, water, and built-up surfaces have shifted over years and decades, and distinguishing a durable trend from a one-off anomaly because there are enough dates to see the difference. Its Spectral Bands span the visible, near-infrared, and shortwave-infrared, and later satellites in the series also carry thermal bands, so the same archive supports vegetation indices, water mapping, snow and burned-area work, and surface-temperature studies. And because it is systematically acquired and openly distributed as calibrated products, it is well suited to building consistent regional and national baselines that others can reproduce — the kind of durable, auditable reference the applied workflows depend on.

Limitations to design around

Landsat’s limitations are the honest counterpart to its reach, and workflows should be designed around them rather than surprised by them. Its spatial resolution is coarser than newer optical missions, which the Resolution concept frames as a deliberate trade-off: a moderate pixel covers ground efficiently and has stayed stable across the program, but it blurs small fields, narrow rivers, and individual buildings. Its revisit is moderate — each satellite returns to a given path on a fixed multi-day cycle rather than daily — so the effective cadence of clear looks is sparser still once clouds remove dates, which is why Landsat is often paired with a denser source for near-real-time monitoring. And because it is optical, clouds, shadow, and haze contaminate scenes exactly as they do for any reflected-sunlight sensor, so masking is not optional. The subtlest limitation is generational: the archive is assembled from several instrument eras with slightly different bands, radiometry, and behavior, and treating them as perfectly interchangeable without care can inject spurious steps into a long series.

Products, QA, and harmonizing across eras

Turning the raw archive into a comparable measurement is a matter of choosing the right processing and reconciling the sensor generations. Landsat imagery is distributed in versioned collections and at different processing levels, and for any cross-date comparison the atmospherically corrected surface-reflectance product is what makes values mean the same thing from one year to the next — the calibration argument the Digital Imagery concept makes in general. Each scene ships with quality-assessment information that flags clouds, shadow, water, and fill, and every date should pass through a mask built from it before anything is computed, following the Cloud Masking concept. The step unique to a multi-generation archive is harmonization: when a time series crosses from one satellite era to another, small differences in band response have to be reconciled — through published cross-sensor adjustments or by comparing indices that are relatively robust to them — so that a change in instrument does not read as a change on the ground. Getting products, QA, and harmonization right is what lets the long record behave like one continuous measurement instead of a stack of loosely related snapshots.

Where Landsat fits across the workflows

Because it reaches back furthest, Landsat is the source of choice wherever history matters. It anchors long-baseline studies of deforestation and land-cover trend, underpins the multi-decade built-up growth in the Urban Expansion workflow, and supports water-extent change, agricultural history, and fire work such as Burn Severity Mapping, where its shortwave-infrared bands and long archive let you compare a burn against years of prior condition. Its moderate, stable pixel also makes it a natural backbone for the vegetation reasoning in NDVI Monitoring when the question spans many seasons. Its most productive pairing, though, is with Sentinel-2: Landsat provides the deep historical baseline and Sentinel-2 the finer detail and denser recent revisit, and combined — carefully harmonized — they yield a longer, tighter time series than either alone.

Accessing the data

Landsat is open, and as with other sources the access method is a choice of track, not a limit on the data. A browser-based environment such as Google Earth Engine exposes the collections ready to query, which is a convenient way to try masking, compositing, and cross-sensor comparison without downloading anything — but it is one track. The same products are hosted and distributed by the USGS and mirrored in several cloud data catalogs, often described by STAC metadata, which is the route a Python pipeline typically takes, pulling only the scenes, bands, and dates a job needs. Whatever the entry point, the durable reasoning is identical: select scenes over an area and time window, pick the right collection and reflectance level, mask by QA, and — for anything spanning eras — harmonize before you compare. The collection identifiers change with the platform; the logic of building one honest long record does not, and that logic is what carries a Landsat workflow from one environment to the next.