Remote Sensing Labs
Browse all docs

Infrastructure Monitoring

Infrastructure monitoring is a repeated-observation workflow: watch corridors and assets — power lines, pipelines, roads, rail, dams — for change or exposure in the surrounding land that may warrant an inspection, maintenance visit, or risk review. What makes it a workflow rather than a single map is the word monitoring: the deliverable is not a snapshot of an asset but a comparison over time around it, run on a cadence, that turns a vast network no crew can walk into a short, ranked list of segments worth looking at. The asset owners and utility operators who work that list sit among the audiences in Urban Analysis, and the exposure overlay below serves the operators described in Disaster Response.

Frame the asset, the corridor, and the action threshold

A monitoring program is only as useful as the decision it triggers, so fix that decision first. Name the asset class and its corridor geometry — a buffer around a line, a polygon around a facility — because everything downstream is measured inside that zone rather than across the whole scene. Set the cadence (how often you re-observe, driven by how fast the relevant change happens) and the change types of interest: vegetation encroaching on a right-of-way, new construction inside a protected buffer, erosion or surface disturbance, flood or fire exposure, or ground movement near a slope or over subsiding ground. Then set an action threshold — how much change, or how much exposure, escalates a segment to a human. A geometry, a cadence, and a trigger are the difference between an alert queue an inspector trusts and a wall of noise they learn to ignore.

Assemble asset geometry and comparable imagery

Two inputs anchor this workflow: where the assets are, and imagery you can compare across dates. Asset locations and corridor buffers must be accurate, because a right-of-way offset by a few meters attributes change to the wrong segment or misses it entirely — align every layer to one grid following the Coordinate Systems concept, and treat the Raster vs Vector join between the vector network and the raster scenes as a first-class step, not an afterthought. For imagery, let the smallest change you must catch drive sensor choice through the tradeoff the Resolution concept sets out: a finer pixel resolves a single new structure or a narrow encroachment but often revisits less frequently (commercial constellations are the exception), while a coarser, more frequent sensor tracks a long corridor’s rhythm but blurs asset-scale detail. Use calibrated surface reflectance, as the Digital Imagery concept explains, and lean on the Spectral Bands that separate vegetation, bare ground, and built surfaces.

Be clear about what each source can actually answer. At 10 m, Sentinel-2 can screen a corridor for changes in canopy cover or new bare ground on a regular cadence, but it cannot tell you whether vegetation has grown within a safe distance of a conductor: clearance is a three-dimensional height-and-distance question, and utilities answer it with airborne LiDAR or very-high-resolution stereo imagery. When a screened segment has to be interpreted at asset scale, US projects can use NAIP (regular cycle over the conterminous United States, refreshed every few years); elsewhere that means national aerial programs or commercial imagery. Where cloud defeats optical imagery, or the question is ground and structure movement, radar is the complement: SAR sees through cloud, and its phase is the basis of the interferometric methods described below. Gather the context layers now too — terrain from a DEM, land cover, hazard maps, and any maintenance or inspection records that later serve as ground truth.

Build repeatable observations around each asset

The heart of monitoring is comparability: an alert only means something if the before and after differ because the ground changed, not because the processing did. Screen every optical date for cloud, shadow, and haze before comparing anything — an unmasked cloud edge over a right-of-way reads as a spurious disturbance — following the Cloud Masking concept. Then fix a repeatable recipe and apply it identically every cycle: the same corridor buffer, the same seasonal window, the same masking rules, and an explicit comparison pairing (this pass versus the last, or versus a stable baseline). This is the Time Series concept applied to a fixed network: the value is in the trend and the persistence, not any single scene. Summarizing within the buffer rather than the whole scene keeps the measurement focused on the asset and cuts the data volume enough to run the network on a schedule. Once the cadence is real the recipe stops being something a person runs and becomes something that has to survive one unusable date, or one segment that fails, without putting the whole network back through the cycle. That operating problem is what the raster processing pipeline note takes up.

Detect change and exposure against a baseline

With comparable observations in hand, measure change rather than re-describe a single date, using the routes the Change Detection concept frames. Index or band differencing against a prior date flags vegetation growth into a right-of-way or new bare ground from construction and erosion; classifying each date and taking the difference names the transition where you need the category.

Radar adds two distinct signals that are easy to conflate. A loss of interferometric coherence between two acquisitions means the surface changed in a way that scrambled the radar return — construction, vegetation growth, disturbance, or damage — so coherence loss flags change, not movement. Ground or structure displacement is measured from the interferometric phase: stacks of acquisitions processed with persistent-scatterer or small-baseline methods can track millimeter-to-centimeter motion at stable reflectors such as buildings, bridges, and rock. Those measurements have limits to respect. They record motion only along the radar’s line of sight, relative to a reference point; vegetated ground decorrelates quickly at C-band; atmospheric water vapor adds phase delays that can mimic motion; a difference in motion of more than roughly a quarter wavelength between neighboring measurement points within one revisit interval (about 1.4 cm at C-band) cannot be unwrapped reliably; time-series methods need a long stack of scenes; and Sentinel-1’s roughly 5 × 20 m resolution cells limit how much detail a single asset can show. Results should be checked against GNSS or leveling where they drive a decision. Ready-made displacement products such as the European Ground Motion Service and NASA’s OPERA DISP-S1 can replace in-house processing where they cover your area.

Exposure is the second half of this workflow and is a spatial overlay rather than a temporal one: intersect the corridor with a current hazard footprint — a flood extent or a burn-severity map produced by the sibling workflows — to report which segments now sit inside a hazard. Both kinds of result are anchored to the asset geometry and to a baseline, so the output is new encroachment or newly exposed segments since the last review, not a static inventory.

Separate true alerts from confounders, then validate

Infrastructure monitoring lives or dies on its false-alarm rate, because an inspector will abandon a queue that cries wolf. Before believing any flag, rule out the ordinary explanations: normal seasonal green-up read as encroachment, cloud or shadow the mask missed, temporary equipment or materials staged in a corridor during works, view-angle and illumination differences between dates, and — most commonly — poor asset geometry putting the buffer over the wrong ground. As in NDVI monitoring, treat each flag as a hypothesis and require it to persist across more than one pass before it escalates. Then validate the survivors explicitly — against higher-resolution reference imagery for the two dates, against a sample checked by eye, or against maintenance and inspection records — and express accuracy honestly, the same discipline the Classification Basics concept applies to any labeled output. Because true changes along a corridor are rare relative to its length, report the change class’s own reliability, not just an overall figure that a mostly unchanged corridor makes look flattering.

Produce a prioritized review queue and make it repeatable

A run is built for action: a review map of flagged segments, a priority table by asset, segment, owner, or inspection route, and a QA note stating which dates were thin, where the mask worked hardest, and which flags rest on weak asset geometry or few validation points. Rank by the action threshold you set at the start so the crew works the corridor in the order that matters. Record the asset layer and buffer, the cadence and comparison window, the exact dates and sensors, the masking and reflectance products, the change, displacement, and exposure methods and thresholds, and the baseline, so the next cycle repeats this one exactly.

Sources