Sentinel-1 GRD reprocessing

To everyone using the s3://sentinel-s1-l1c bucket:

1 Like


Thanks for your efforts in maintaining these datasets.

Can you please clarify if the GRD data within these buckets are Cloud Optimized Geotiffs or not?

I recently found out about Planetary Computer and that Sentinel 1 GRD COGs are being put up there, and that the data is being managed by Sinergise.

Hence I wanted to know if the AWS Sentinel-1 bucket is also COGs like in Planetary Computer.


Yes, S1 GRD on AWS bucket is in COGs. The structure (and content) is actually very much alike the one in the Planetary Computer.

1 Like

Oh ! Well… is there any documentation that mentions that it these are COGs?

Sorry but I couldn’t find it anywhere in the documentation.

It does indeed not say anywhere, but they are. It should not be too difficult for you to check this by loading a tiff and checking it…

Right, thanks @gmilcinski.

I haven’t checked it coz I dont have an AWS account yet. When I use no-sign-request it stops at Access Denied.

But thanks again for confirming. Its really nice to know about this.

Please do consider adding a “COG” mention somewhere for anyone else sifting through the datasets. Thank you!


Just tried a on one of the Sentinel-1 GRD files in the Requester-Pays bucket.


with open and “src.meta” gives the following output.

{'driver': 'GTiff', 'dtype': 'uint16', 'nodata': 0.0, 'width': 25983, 'height': 19359, 'count': 1, 'crs': None, 'transform': Affine(1.0, 0.0, 0.0,
       0.0, 1.0, 0.0)}

I then tried rioinfo on it which gave a similar answer -

AWS_REQUEST_PAYER=requester GDAL_DISABLE_READDIR_ON_OPEN=YES CPL_VSIL_CURL_ALLOWED_EXTENSIONS=.tiff AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY AWS_REGION=eu-central-1 rio info  /vsis3/sentinel-s1-l1c/GRD/2021/4/21/IW/DV/S1B_IW_GRDH_1SDV_20210421T004331_20210421T004356_026558_032BE8_BD44/measurement/iw-vv.tiff

The output is big, hence please check the public link below -

then I also tried a simple gdal_translate, which gave the following output-

gdal_translate /vsis3/sentinel-s1-l1c/GRD/2021/4/23/IW/DV/S1B_IW_GRDH_1SDV_20210423T002140_20210423T002209_026587_032CCC_D1C4/measurement/iw-vh.tiff output.tif \
    -projwin_srs EPSG:4326 \    
    -projwin -97.42469787597656 42.83292607575776 -97.39688873291016 42.85407131053984 \ 
    -co COMPRESS=LZW \                               
    --config AWS_ACCESS_KEY_ID xxxx \                        
    --config AWS_SECRET_ACCESS_KEY xxxxx \
    --config AWS_REQUEST_PAYER requester

Input file size is 25983, 19359
ERROR 0: -projwin_srs ignored since the dataset has no projection.
ERROR 1: Error: Computed -srcwin -98 42 0 0 has negative width and/or height.

In all cases the CRS seems to be null.

But the “gcps” key in the above “rioinfo” output has EPSG:4326 as CRS.

Oddly when I downloaded the whole COG file and opened it in QGIS, it was correctly projected to EPSG:4326.

Please do let me know your thoughts.


Hi @sid_141,
note that the community on this forum focuses on access to data via Sentinel Hub. I can therefore not guarantee you will get an answer to your question. Perhaps Stack Overflow or similar would be better.

Just wanted to confirm if its related to the dataset in anyway. That’s all.


The above issue listed by me, does not occur on other requester pays buckets, such as Landsat Collection 2 in AWS.

Please let me know where I can contact folks from Sinergise. Maybe they can answer my question. Because this is the link kept in AWS Sentinel-1 Bucket page -

I will withdraw the post from here in that case.

Well, we are Sinergise folks… But note that our replication of data to AWS bucket is a voluntary project and we have no resources to provide support to AWS users.
The data, as they are available, work perfectly fine for us and for many other users of AWS.

Sorry for not being able to help you.

1 Like

And no need to withdraw post from the Forum. It might still happen that someone will answer you. Just wanted to inform you that there is a chance nobody will.

1 Like

Okay great. Thank you.

After lots of searching I have ended up with the following link , that helps in creating a code for querying Sentinel-1 data from AWS -

Leaving it here for anyone looking for a similar solution.

Thanks to @gmilcinski for informing me that the datasets are working fine. :slight_smile: