S1 Tiling with images from Planetary Computer

Hello all,

I would like to use S1 Tiling in my research work, and I’ve took some time to read the documentation, but I still have a small doubt regarding the Sentinel-1 images providers compatibility with this tool. To be more precise, I have a pipeline for retrieving Sentinel-1 GRD data from Microsoft Planetary Computer, but I’m not totally sure that those images can be integrated into S1 Tiling as it would with images from CDSE or GEODES for example.

I saw that the documentation explains that S1 Tiling can be used with images from several providers, and also that the EODAG tool can be used to download the images of interest when using S1 Tiling too. The EODAG documentation also states that it can retrieve Sentinel-1 GRD data from Planetary Computer. So from here, I understand that , on principle, I can use Sentinel-1 GRD images retrieved from Planetary Computer in S1 Tiling to preprocess them and align them with Sentinel-2 images.

However, I couldn’t find any information or forum thread regarding the use of Sentinel-1 images from Planetary Computer in S1 Tiling, and especially if some issues were encountered, or are to be expected. Which is why I’m still having a small doubt regarding this. I understand that you may find this a little bit silly, and that your answer would be “well, just try and see for yourself !”. However, I’m completely new to S1 Tiling and Orfeo ToolBox, and handling the tool will take me some time. So I would just like to know if someone already used S1 Tiling with images from Planetary Computer, and confirm that, indeed, S1 Tiling can be used with images from that provider.

Best,

Andréa GERAUD

Hello Andréa,

In S1TIling, we defer the retrieval of S1 images to eodag. As a consequence we support (*) the data providers it supports.

Regarding Microsoft Planeraty Computer, indeed, so far we are not aware of people using this data provider. You’ll have to try it. :slight_smile:

An offline mode is also possible. In this mode we don’t rely on eodag. The idea is that you can download S1 products, unzip them in the /s1_images/ directory, and then execute S1Tiling in offline mode. Beware that in this mode we cannot correctly identify situations where S1 products are missing, and react accordingly.

If you have a doubt about directory organization, you just need to extract the S1 products directly in the /s1_images/ directory. For instance if I put products in data_raw/, I will have something like:

data_raw/
└── S1A_IW_GRDH_1SDV_20250330T060920_20250330T060945_058530_073E06_0810
    ├── annotation
    │   ├── calibration
    │   │   ├── calibration-s1a-iw-grd-vh-20250330t060920-20250330t060945-058530-073e06-002.xml
    │   │   ├── calibration-s1a-iw-grd-vv-20250330t060920-20250330t060945-058530-073e06-001.xml
    │   │   ├── noise-s1a-iw-grd-vh-20250330t060920-20250330t060945-058530-073e06-002.xml
    │   │   └── noise-s1a-iw-grd-vv-20250330t060920-20250330t060945-058530-073e06-001.xml
    │   ├── rfi
    │   │   ├── rfi-s1a-iw-grd-vh-20250330t060920-20250330t060945-058530-073e06-002.xml
    │   │   └── rfi-s1a-iw-grd-vv-20250330t060920-20250330t060945-058530-073e06-001.xml
    │   ├── s1a-iw-grd-vh-20250330t060920-20250330t060945-058530-073e06-002.xml
    │   └── s1a-iw-grd-vv-20250330t060920-20250330t060945-058530-073e06-001.xml
    ├── manifest.safe
    ├── measurement
    │   ├── s1a-iw-grd-vh-20250330t060920-20250330t060945-058530-073e06-002.tiff
    │   └── s1a-iw-grd-vv-20250330t060920-20250330t060945-058530-073e06-001.tiff
    ├── preview
    │   ├── icons
    │   │   └── logo.png
    │   ├── map-overlay.kml
    │   ├── product-preview.html
    │   ├── quick-look.png
    │   └── thumbnail.png
    ├── S1A_IW_GRDH_1SDV_20250330T060920_20250330T060945_058530_073E06_0810.SAFE-report-20250330T065307.pdf
    └── support
        ├── s1-level-1-calibration.xsd
        ├── s1-level-1-measurement.xsd
        ├── s1-level-1-noise.xsd
        ├── s1-level-1-product.xsd
        ├── s1-level-1-quicklook.xsd
        ├── s1-level-1-rfi.xsd
        ├── s1-map-overlay.xsd
        ├── s1-object-types.xsd
        └── s1-product-preview.xsd

(*) However, currently data filters only work with PEPS: see the issue Invalid parameter used in eodag search request for polarisation mode (#168) · Issues · s1-tiling / S1Tiling · GitLab . We hope to see it fixed soon. EODAG team has harmonized polarization and orbit direction. We haven’t checked yet their develop branch, nor updated our code in consequence. I don’t known whether their Microsoft Planetary Computer plugin has been harmonized as well.

Regards,

Luc Hermitte

Hello Luc,

Thank you for that quick and detailed answer !

Regards,

Andréa