Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsFor most backscatter mapping projects, start with Sentinel-1 data and choose a documented radiometric terrain-corrected (RTC) product if you want observations already geocoded and terrain-normalized. Use single-look complex (SLC) or coregistered SLC (CSLC) data when your analysis needs radar phase, such as interferometry. In either case, treat radar brightness as a measurement shaped by the surface and viewing geometry—not as a direct land-cover label.
Choose a SAR product that fits the mapping question
Synthetic aperture radar (SAR) actively transmits microwave energy and measures the signal returned from the ground. Sentinel-1 is a practical starting point for many mapping tasks, but its products are not interchangeable: some retain only detected backscatter, while others preserve phase information needed for interferometric analysis.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Satellite Remote Sensing Technologies (Space Science and Technologies) | $191.46 | Buy on Amazon |
| 2 |
|
Practical Handbook of Remote Sensing | $64.59 | Buy on Amazon |
| 3 |
|
Satellite Remote Sensing for Forest and Environmental Monitoring (Earth Observation) | $171.94 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
| Product | Best suited to | What it contains and what to watch |
|---|---|---|
| Sentinel-1 GRD | Backscatter analysis when you want to choose or apply additional processing. | Ground-range detected imagery that has been focused and multilooked. Phase is discarded. Copernicus Data Space documentation describes processing choices for calibration, terrain treatment, and orthorectification; check which were applied to the product you select. |
| Sentinel-1 RTC / OPERA RTC-S1 | General backscatter mapping and comparisons where terrain normalization is useful. | OPERA RTC-S1 is derived from Sentinel-1 SLC inputs, normalized to gamma-nought through radiometric terrain correction, and projected onto UTM or polar stereographic grids. NASA JPL documents a 30 m posting, GeoTIFF imagery, and HDF5 metadata. RTC remains backscatter, not a land-cover classification. |
| SLC / OPERA CSLC | Interferometry and other analyses that require phase. | SLC preserves complex radar data; ASF describes CSLC as precisely coregistered complex imagery that retains amplitude and phase. It requires a phase-aware processing workflow and is not a drop-in substitute for an RTC backscatter map. |
| Copernicus monthly mosaic | Broad-area visualization or compositing. | Copernicus documents IW and DH mosaics with different polarization, coverage, and nominal grid spacing: 20 m for IW and 40 m for DH. A monthly composite is not equivalent to a single dated acquisition when the timing of an event matters. |
These product descriptions and grid specifications are documented by Copernicus Data Space, ASF DAAC, and NASA JPL. Grid spacing or posting describes the delivered raster, not a guarantee that features of the same size can be distinguished reliably.
Where to find Sentinel-1 and OPERA data
Copernicus Data Space Ecosystem
Use Copernicus Data Space to search Sentinel-1 collections and review available processing options. Its documentation covers Level-1 GRD, RTC options, and monthly mosaics. Before building a time series, verify that the area, dates, acquisition mode, and polarization you need are actually available, and record the processing definition.
#1 Best Overall
Alaska Satellite Facility (ASF) DAAC
ASF provides access to OPERA Sentinel-1 RTC and CSLC products through Vertex, asf_search, and SearchAPI. ASF’s product manual describes near-global RTC coverage over land excluding Antarctica from 2023 to the present, and North America CSLC coverage from 2014 to the present, as documented when accessed. These are broad coverage descriptions, not guarantees that every date or polarization exists for a particular project footprint.
NASA Earthdata Search
NASA JPL identifies ASF DAAC and Earthdata Search as access routes for validated OPERA RTC products. Use the archive records to confirm the specific collection, time range, and files available for your study area.
Rank #2
Plan the mapping workflow
- Define the map question. Specify the feature or change you want to map, the area and period, the output scale, and whether the analysis needs backscatter or phase. A deformation workflow, for example, has a different data requirement from a general backscatter map.
- Find comparable observations. For a time comparison, keep polarization and processing choices consistent. Record acquisition date, orbit direction, acquisition mode, polarization, and product version. Differences in terrain and look direction can change how a surface appears.
- Search an authoritative archive. Search Copernicus Data Space for Sentinel-1 collections and processing options, or use ASF/Vertex and ASF search tools for OPERA RTC or CSLC. Check actual coverage and dates for your footprint rather than assuming a broad coverage statement means every acquisition is present.
- Select the processing level deliberately. Consider RTC for geocoded, terrain-normalized backscatter mapping. Choose SLC or CSLC when the method depends on phase. GRD has discarded phase and cannot serve as phase-preserving input.
- Inspect product metadata and geometry. Check polarization, acquisition mode, orbit direction, incidence geometry, projection, grid spacing or posting, backscatter coefficient, terrain-correction method, and any filtering or compositing. NASA JPL documents geometry information, including local incidence angle, among OPERA static layers.
- Make the map and document decisions. Record any masks, thresholds, and assumptions used to create the output. For an important claim, compare the result with independent reference information appropriate to the mapping objective.
Interpret backscatter without treating brightness as a label
Microwave imaging can acquire data in darkness and through cloud cover, unlike optical imaging conditions. But a SAR return is still shaped by the target and the radar’s geometry. NASA JPL describes OPERA RTC signals as being “largely related to the physical properties of the ground scattering objects, such as surface roughness and soil moisture and/or vegetation.”
Recommended Free Tools
- Surface properties matter. Roughness, soil moisture, and vegetation structure can affect the return. A bright or dark pixel does not uniquely identify a surface class.
- Polarization matters. Different polarization channels are different measurements. Keep channels consistent when comparing dates, and do not interpret values from different channels as if they were directly equivalent.
- Viewing geometry matters. Orbit direction and incidence or look geometry influence the signal. Layover and radar shadow in particular can make terrain appear misleadingly bright or dark.
- Terrain correction has limits. RTC helps geocode imagery and reduce terrain-related radiometric effects; it does not remove every geometric difficulty or make steep terrain straightforward to interpret.
Use contextual information or independent reference data when a map depends on assigning a meaning—such as a land-cover class—to a radar return. The product’s backscatter values alone do not establish that class.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check resolution and validation claims against your use
Product grid spacing is not the same as effective detail or thematic map accuracy. Copernicus documents nominal monthly mosaic grids of 20 m for IW and 40 m for DH; NASA JPL documents 30 m posting for OPERA RTC-S1. These specifications describe product grids, not a promise that every feature at that size can be resolved.
NASA JPL’s OPERA RTC-S1 page, accessed in 2026, lists requirements of less than 6 m absolute and relative geolocation error for 80% of validation data considered, and less than 1 dB foreslope-to-backslope difference for 80% of validation data considered. JPL reports that 100% of the validation data met each listed requirement. Those are product validation and specification statements, not universal guarantees for every scene or map made from the data. They also do not establish the accuracy of an arbitrary SAR-derived classification or change map.
Quick Recap
Common choices that lead to misleading comparisons
- Using a mosaic to time a specific event: a monthly composite represents a compositing period, not necessarily one acquisition date. Use an individual acquisition when event timing is central to the analysis.
- Mixing processing definitions across dates: different calibration, terrain correction, filtering, or compositing can complicate a time series. Check and record those choices before comparing values.
- Comparing different polarizations as one continuous measurement: polarization affects the return, so keep it consistent or explicitly account for the difference in the analysis.
- Reading bright and dark areas as fixed classes: surface properties and viewing geometry both affect intensity; validate map interpretations with contextual or independent information.
- Trying phase analysis with a detected product: GRD has lost phase. Select SLC or CSLC and use a processing workflow designed for phase-based analysis.
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.
