Begin with the decision and the observable target
The practical question is: Where do newly exposed slope patches merit landslide investigation? Work with landslide candidate scars as the reporting unit and define the observation period before choosing an image or algorithm. Fresh scars, deposits and vegetation removal can provide observable evidence after intense rainfall.
Hazard monitoring should distinguish an observed process, the exposure of assets and verified consequences. A satellite footprint can show what was observable at an acquisition time, but it may miss the event maximum or changes occurring between overpasses. Asset overlap adds another evidence layer; it does not automatically describe damage, service interruption or personal impact. Keep these stages separate in the data model so later field assessments can update consequences without rewriting the original observation. Pre-event baselines need careful review because seasonal water, earlier disturbance and outdated asset records can create false event changes. When the image cannot support an assessment, preserve an unknown class. Response and planning decisions also need source timestamps: a technically correct layer can become operationally stale quickly. Let the responsible authority determine warning or action levels using its broader evidence. The role of the satellite workflow is to supply timely, traceable observations and clearly state the uncertainty that remains.
Select observations with suitable physical and temporal support
Optical surface reflectance is a useful starting point for many land-cover questions because it reduces some atmospheric effects before comparison. Landsat and Sentinel-2 are common candidates, but select an actual product whose bands, quality information and spatial support fit the target. Apply the documented scale and offset before interpreting values, and mask cloud, cirrus, shadow and other invalid observations according to the product guidance. A resampled raster does not gain new physical detail: placing a coarser band on a finer grid changes its sampling, not the instrument resolution. Check image alignment near narrow boundaries and use an appropriate common grid for multitemporal work. Review whether the available clear observations cover the biologically or operationally important period. A visually attractive composite can combine dates that do not describe one real state, so retain the contributing acquisition information when timing affects the decision.
Build a compact data manifest before processing. Record the area of interest, acquisition times, product identifiers, processing versions, bands or variables, units, scale factors and quality criteria. Check the actual usable coverage over the target rather than relying only on scene-wide quality percentages. Preserve the original masks and define how missing values propagate into derived layers. If several dates or sensors are combined, keep their support information available in the project. These details make it possible to repeat a measurement and to explain why a later run changes after a product revision. They also help a colleague decide whether an apparent disagreement comes from the environment, the observation conditions or a processing choice.
Build an analysis rule that can be reviewed
Compare pre-event land cover, inspect terrain context and classify candidate scars separately from independently confirmed landslides.
Object mapping requires an explicit rule for what counts as one feature. Specify minimum detectable size, splitting and merging behavior and how uncertain boundaries are handled. A connected image patch may represent several management units, while one physical feature can be divided by shadows or missing data. Check object counts and areas separately because a method can achieve reasonable total area while splitting the inventory incorrectly. Retain stable identifiers through updates and preserve links to the source observation. Review a representative sample of candidate objects and noncandidate surroundings so evaluation can reveal both false detections and missed features. When exact boundaries are unsupported, use a candidate zone or point for inspection rather than drawing a precise-looking polygon whose geometry the imagery cannot defend.
Start with a small, independently reviewed subset before applying the rule across the full geography. Inspect inputs and intermediate layers at both overview and local scales, checking that units, masks and coordinate alignment behave as intended. Keep a named version of the analysis configuration and retain a concise explanation of every consequential threshold. When the workflow moves to another region or season, revisit those assumptions instead of assuming that successful execution proves scientific transfer. A repeatable pipeline is valuable because its choices can be inspected and revised, not because automation makes the interpretation automatically correct.
Interpret the result without hiding alternative explanations
Construction, quarries and cloud artifacts can resemble landslides, while canopy or shadows hide other failures.
Keep the target interpretation distinct from the evidence used to support it. For landslide candidate scars, ask whether the observed pattern persists under a reasonable alternative baseline, quality mask or aggregation. Review apparent successes and plausible counterexamples together. If competing explanations cannot be separated with the available observations, record the finding as a candidate for investigation. This preserves useful spatial information while showing exactly which part of the conclusion still depends on independent evidence. The next observation should be chosen to resolve that uncertainty, rather than simply to reproduce a similar-looking map.
Validate with independent evidence before scaling
Use geological field surveys and independent detailed imagery where available.
Design the reference sample to represent the intended map use, including difficult boundaries and locations the classifier did not flag. Keep the sample independent of training and threshold adjustment. If rare target classes are deliberately oversampled, retain selection probabilities so population-level estimates can be calculated appropriately. Build a confusion matrix using a consistent reference definition and report omission as well as commission error. Check observer agreement where labels require interpretation. Report results by meaningful context, such as terrain, target size or season, when performance differs. A map evaluated only on easy interior examples cannot justify claims about narrow edges or mixed landscapes. Keep the reference evidence available for audit and distinguish uncertain reference labels from certain ones rather than forcing every sample into a definitive category.
Deliver a usable GIS evidence layer
Deliver a candidate inventory with detection scale, confidence and confirmation status.
For GIS delivery, retain stable feature identifiers, source observation dates, the physical variable, units, valid support area, uncertainty and review status. Use a suitable coordinate reference for any area or distance calculation and document the transformation when joining outside layers. Separate measured or observed attributes from modeled and field-confirmed attributes so users can update one evidence type without overwriting the others. Include an unknown or unsupported state in summaries and preserve the denominator used for percentages. A map legend, concise data dictionary and accessible source links make the result useful to colleagues who did not run the analysis. Export formats should match the actual downstream workflow, with attribute encoding and geometry checked before handoff.
Turn the method into a practical iT Sensing workflow
iT Sensing brings satellite discovery, raster analysis, machine learning, GeoAI, visual model workflows and Python experimentation into a cloud remote sensing workspace. Use its documented tools to organize the inputs, test appropriate raster operations and connect evaluated results to a project-aware GIS workflow. The existence of a general tool does not guarantee that every specialist retrieval described here is available as a ready-made operation. Check the documentation and, where necessary, bring independently processed and evaluated products into the project with their provenance intact. A practical next step is to test the workflow on a representative area, review the evidence with domain specialists and choose the workspace plan that fits the team’s real storage, collaboration and processing needs.