The Sentinel-1 imagery is provided by two polar-orbiting satellites, operating day and night performing C-band synthetic aperture radar imaging, enabling them to acquire imagery regardless of the weather. Main applications are for monitoring sea ice, oil spills, marine winds, waves & currents, land-use change, land deformation among others, and to respond to emergencies such as floods and earthquakes.
Sentinel Hub currently supports Sentinel-1 Level-1 GRD (Ground Range Detected) products only. See other Sentinel-1 products offered by ESA.
Observation scenario defines the acquisition mode and polarization with which the Sentinel-1 will acquire data over certain area. When searching for the data the observation scenario can be helpful when selecting a combination of values of different parameters. Below is an example of observation scenario but it may vary through time depending on requirements. The full archive of observation scenarios is available.
The Sentinel products are released under the license available here.
The following describes the way Sentinel-1 GRD data is processed in Sentinel Hub. For information on how to set processing parameters, see Processing Options.
- Original or multilooked source chosen (depending on the resolution level; multilooking is done in ground range. Also see.)
- Calibration to the chosen backscatter coefficient and thermal noise removal applied.
- (Optional) Radiometric terrain correction using Flattening gamma is performed. The Mapzen or Copernicus DEM is used (see the example).
- (Optional) Orthorectification using Range-Doppler terrain correction using the Mapzen or Copernicus DEM.
- The orbit files used are the ones bundled in the products themselves. We find these more than sufficient for GRD use. Non-realtime products typically contain restituted orbit information.
- The areas of border noise are not displayed by Sentinel Hub.
- No speckle filtering is applied at any stage. However, you can do multitemporal averaging to reduce speckle.
- Radiometric terrain correction can only be performed if orthorectification is enabled. The DEM oversampling parameter is by default set to 2 and can be user adjusted. For low resolution requests (many meters per pixel) increasing it to 3, for example, can be worthwhile to reduce artifacts. Integer values are recommended. See also the S1GRD API Reference.
- The DEM, if used, is resampled using bilinear interpolation, and the same DEM is used for both radiometric terrain correction and orthorectification, provided both are enabled.
To access data you need to send a POST request to our
process API. The requested data will be returned as the response to your request. Each POST request can be tailored to get you exactly the data you require. To do this requires setting various parameters which depend on the data collection you are querying. This chapter will help you understand the parameters for S1GRD data. To see examples of such requests go here, and for an overview of all API parameters see the S1GRD API Reference.
|services.sentinel-hub.com/api/||Global since January 2017|
|eocloud.sentinel-hub.com/v1/||Global since October 2014|
|shservices.mundiwebservices.com/api/||Rolling policy of 48 months for Europe |
Rolling policy of 12 months for World
- @ services.sentinel-hub.com/api/ : Zooming out will use multi-looked sources at an appropriate resolution to your viewing level. You can therefore expect high quality results at all zoom levels.
- @ shservices.mundiwebservices.com/api/ : Zooming out will use multi-looked sources at an appropriate resolution to your viewing level. You can therefore expect high quality results at all zoom levels.
- @ eocloud.sentinel-hub.com/v1/ : Zooming out will NOT use multi-looked sources. Zooming out is therefore more of a convenience preview as the images will be excessively noisy. If this is an issue consider using the AWS service instead.
- @ services.sentinel-hub.com/api/ : We support all backscatter coefficients.
- @ shservices.mundiwebservices.com/api/ : We support all backscatter coefficients.
- @ eocloud.sentinel-hub.com/v1/ : We support gamma0 backscatter coefficient (GAMMA0_ELLIPSOID). Radiometric terrain correction is not supported.
S1GRD as the value of the
input.data.type parameter in your API requests. This is mandatory and will ensure you get Sentinel-1 GRD data.
This chapter will explain the
input.data.dataFilter object of the
|HIGH||10m/px for IW and 25m/px for EW|
|MEDIUM||40m/px for IW and EW|
A full table of resolutions is available (here)
Sentinel-1 operates in four different acquisition modes (more).
|SM||Stripmap mode (more ).||HH+HV, VV+VH, HH, VV|
|IW||Interferometric Wide (IW) swath mode (more ).||HH+HV, VV+VH, HH, VV|
|EW||Extra Wide (EW) swath mode (more ).||HH+HV, VV+VH, HH, VV|
|WV||Wave mode (more ).||HH, VV|
This table contains information about the polarization two letter code used by ESA and the product's contained polarizations.
|DH||HH+HV||Typical for EW acquisitions|
|DV||VV+VH||Typical for IW acquisitions|
|HH||Partial Dual, HH only||HH+HV was acquired, only HH is available in this product|
|HV||Partial Dual, HV only||HH+HV was acquired, only HV is available in this product|
|VV||Partial Dual, VV only||VV+VH was acquired, only VV is available in this product|
|VH||Partial Dual, VH only||VV+VH was acquired, only VH is available in this product|
|ASCENDING||Data acquired when the satellite was traveling approx. towards the Earth's North pole.|
|DESCENDING||Data acquired when the satellite was traveling approx. towards the Earth's South pole.|
This chapter will explain the
input.data.processing object of the
|upsampling||The same as for S2L1C.|
|downsampling||The same as for S2L1C.|
|orthorectify ||Enables/disables orthorectification||TRUE - Orthorectified|
FALSE - non-Orthorectified
|TRUE on EOCloud, FALSE on AWS and Mundi|
|demInstance||Selects DEM instance.||MAPZEN - Mapzen DEM |
COPERNICUS - Copernicus DEM 10m and 30m 
COPERNICUS_30 - Copernicus DEM 30m 
COPERNICUS_90 - Copernicus DEM 90m
sigma0_ellipsoid use an ellipsoid earth model. Radiometric terrain correction can be enabled by setting the backscatter coefficient to
gamma0_terrain; orthorectification must be enabled in this case.
: For orthorectification, we use the DEM instance specified in demInstance field or Mapzen DEM by default. The Copernicus DEM is generally of higher quality and recommended in most cases. The non-orthorectified products use a simple earth model as provided in the products themselves. This may be sufficient for very flat target areas and is faster to process.
: It has 10m resolution inside the EEA-10 extent and 30m elsewhere.
: The Copernicus 30m DEM has global coverage if used for the processing of Sentinel-1 data.
Information in this chapter is useful when defining
input object in evalscript. Any string listed in the column Name can be an element of the
input.bands array in your evalscript.
|VV||Present when the product polarization type is one of SV, DV or VV.|
|VH||Present when the product polarization type is VH or DV.|
|HV||Present when the product polarization type is HV or DH.|
|HH||Present when the product polarization type is one of SH, DH or HH.|
|localIncidenceAngle||The local incidence angle for each output pixel. Only available if orthorectification is enabled.|
|scatteringArea||The normalized scattering area for each output pixel. Used for conversion of beta0 to terrain corrected gamma0. Only available if radiometric terrain correction is performed.|
|shadowMask||Flags output pixels which are in or near radar shadow. Is |
|dataMask||The mask of data/nodata pixels (more).|
The data values for each band in your custom script are presented in the default units as specified here. In case more than one unit is available for a given band, you may optionally set the value of
input.units in your evalscript
setup function to one of the options. Doing so will present data in that unit. The
Source Format specifies how and with what precision the digital numbers from which the unit is derived are encoded. The
Typical Range indicates what values are common for a given band and unit, however outliers can be expected.
For Sentinel-1, data values are linear power in the chosen backscattering coefficient. To specify the backscattering coefficient, set
GAMMA0_ELLIPSOID (default) or
GAMMA0_TERRAIN as the value of
input.data.processing.backCoeff in your request. The default is
|Band||Unit||Source Format||Typical Range||Notes|
VV, HH, VH, HV
|Linear power in the chosen backscattering coefficient||UINT16||0 - 0.5||Can reach very high values (such as 1000); for visualizing a large dynamic range consider converting to decibels: |
|localIncidenceAngle||degrees||N/A||0 - 180||Computed for each output pixel. Requires that orthorectification is enabled|
|scatteringArea||unitless||N/A||0 - 2||Can reach high values on foreslopes|
|shadowMask||N/A||boolean||0 - likely not radar shadow |
1 - likely in/near radar shadow
|dataMask||N/A||boolean||0 - no data|
1 - data
ORBIT mosaicking types are supported.
- Noise: All products on both services have thermal noise reduction applied.
- Decibel units: For decibel outputs, a conversion is necessary within your evalscript, see an example here. We offer pre-defined evalscripts, which return S1GRD values in decibel units, as products in the Configuration Utility for your convenience.
- Orbit state vectors: We currently use the orbit state vectors provided in the products themselves as we find these sufficient for GRD use.
To access Sentinel-1 GRD product metadata you need to send search request to our Catalog API. The requested metadata will be returned as JSON formatted response to your request. This chapter will help with understanding Sentinel 1 GRD specific parameters for search request.
|services.sentinel-hub.com/api/v1/catalog/collections/sentinel-1-grd||Global since January 2017|
|shservices.mundiwebservices.com/api/v1/catalog/collections/sentinel-1-grd||Rolling policy of 48 months for Europe |
Rolling policy of 12 months for World