What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

SAR images can look warped, grainy, banded, or partly blank because radar records a scene from the side and forms an image from coherent radar returns—not from a camera looking straight down. The right correction depends on the symptom: terrain correction addresses geographic displacement, radiometric terrain correction addresses slope-related brightness, speckle filtering trades detail for smoother appearance, and sensor-specific noise removal can target bands or seams. None can recreate radar information that was never recorded.

First identify what kind of distortion you are seeing

Before processing an image, check its sensor, acquisition mode, polarization, product level, orbit or look direction, coordinate system, and processing history. Determine whether it is raw or slant-range data, geocoded data, or already terrain-corrected. An unusual appearance does not by itself mean a correction is missing; applying the same correction twice can create new problems.

Separate a visual artifact from a quantitative error. A scene may look uneven without every pixel being incorrectly located, and a visually smooth image may still contain unreliable or unobserved areas. The pattern, terrain, viewing direction, and product metadata help distinguish the causes.

What you see Likely cause What to consider
Compressed, overlapping, or reversed-looking terrain features Foreshortening or layover from side-looking geometry Use DEM-based geocoding/terrain correction for map positioning; retain geometry masks.
Very dark areas behind terrain facing away from the radar Radar shadow Flag as unobserved or unreliable; correction cannot supply missing returns.
Grainy texture throughout the image Coherent speckle Consider multilooking or a filter only if the loss or alteration of detail is acceptable.
Bands or interswath seams, especially in Sentinel-1 VH/HV or ocean scenes Potential thermal noise Check product-specific noise-removal guidance before filtering the image generally.
Uneven brightness across slopes Geometry-dependent backscatter, among other possible causes Assess whether radiometric terrain flattening is appropriate for the comparison task.

How terrain creates geometric artifacts

Foreshortening

Because SAR looks obliquely at the ground, a slope facing the sensor can appear compressed: points along the slope are mapped into a shorter distance in the radar image than their ground distance. The amount and location depend on terrain and viewing geometry.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Layover

On a sufficiently steep sensor-facing slope, the return from the upper part of a feature can arrive ahead of the return from its lower part. Their apparent order can overlap or reverse. This is not simply a misplaced pixel that a general warp can reliably put back: the measurements may be mixed.

Shadow

Terrain that faces away from the radar can block the beam from reaching an area. A shadow is therefore a region the sensor did not illuminate, not merely a dark patch needing brightness adjustment. Changing viewing geometry can change where these artifacts occur; the same terrain observed from another orbit may look different.

The NASA SAR Handbook and the Alaska Satellite Facility SAR User Guide describe these geometry effects and their limits. A viewing angle that reduces foreshortening or layover can make shadow more prominent. Terrain at or below the image resolution scale can also create locally unrecoverable distortion.

Choose the correction that matches the problem

For geographic placement: DEM-based geocoding or terrain correction

Geocoding uses a digital elevation model (DEM) to place radar measurements in a geographic coordinate system and address terrain-related geometric displacement where possible. It is the relevant step when the goal is to align a SAR layer with a map or other GIS data. The NASA Earthdata workflow, SAR Data Pre-Processing Steps, distinguishes this work from optional speckle reduction and radiometric terrain flattening.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The DEM is part of the correction, not a minor setting. Its coverage, resolution, and quality affect the result. Check the DEM and output pixel spacing, and do not assume that output pixel spacing equals the sensor’s actual resolution. ASF’s MapReady Manual 3.1.22 documents DEM-dependent correction and mask output.

For slope-related brightness: radiometric terrain correction

Geometric correction and radiometric correction solve different problems. Radiometric terrain flattening or normalization adjusts brightness differences associated with terrain geometry; it does not serve as a substitute for placing the image in geographic coordinates. Consider it when comparing backscatter across slopes, and use a workflow designed for the sensor and product rather than assuming every uneven brightness pattern has the same cause.

For grainy appearance: multilooking or filtering

Speckle is inherent to coherent SAR imaging. Multilooking reduces it by spatial averaging, but that averaging also reduces spatial resolution. Filtering is another option, with effects that depend on the method and application. Either can alter small features or measurements, so a smoother result is not automatically a more accurate one. For small targets or fine-scale change analysis, weigh the detail loss carefully.

For possible Sentinel-1 seams: check thermal noise

Thermal noise can resemble a processing seam. Esri’s Sentinel-1 Thermal Noise Removal documentation for ArcGIS Enterprise 11.5 says it is most apparent in cross-polarization VH/HV and low-backscatter data, and may appear as interswath discontinuities, especially in ocean scenes. This is Sentinel-1-specific guidance, not a diagnosis for every SAR sensor or banded image; verify the product and apply an appropriate noise-removal workflow.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

A practical workflow for correcting common artifacts

  1. Verify the input: record the sensor, acquisition mode, polarization, product level, orbit/look direction, coordinate system, and prior processing. Confirm whether the image is raw/slant-range, geocoded, or already terrain-corrected.
  2. Diagnose the pattern: in rugged terrain, look for compressed sensor-facing slopes, overlapping or reversed ridge shapes, and dark areas facing away from the radar. For bands or seams, check polarization, backscatter level, and coverage, particularly for Sentinel-1 VH/HV and ocean scenes.
  3. Set the goal: for GIS overlay, select DEM-based geocoding/terrain correction. For backscatter comparisons across slopes, assess radiometric terrain flattening. For grainy texture, decide whether averaging or filtering is compatible with the target size and analysis.
  4. Check the DEM and output settings: confirm DEM coverage and quality, and choose output pixel spacing with the distinction between pixel spacing and sensor resolution in mind.
  5. Use product-specific processing: follow the relevant sensor and software workflow. NASA Earthdata lists a GAMMA-based recipe for radiometrically terrain-correcting Sentinel-1 data in its Sentinel-1 C-SAR resources; software interfaces and versions can change, so confirm current documentation before following exact menu steps.
  6. Inspect outputs and masks: review intermediate results and retain layover/shadow masks. Treat masked areas as unreliable or unobserved; interpolation can make a display look continuous but does not turn missing observations into measurements.

What correction cannot fix

Terrain correction can improve geolocation and address some geometry-dependent effects, but it is not universal dewarping. It cannot recover returns absent from shadow or reliably separate information irreversibly mixed by layover. Interpolating these areas may help visual continuity, but any such pixels must not be represented as radar observations.

Every choice also has trade-offs: the DEM influences terrain correction, speckle reduction can sacrifice resolution, and viewing geometry may reduce one terrain artifact while increasing another. For quantitative work, preserve the masks and processing context alongside the corrected image so downstream users can distinguish measured data from weak or missing information.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.