Different opening options for S1 and S2 SAFE datasets in SNAP

Both Sentinel-1 data and Sentinel-2 data are delivered in SAFE format and therefore a regular user could expect that the they can be opened in exactly the same way in SNAP. However, this is not the case and in fact the opening options are almost inverted for S1 and S2 data. For example, it is possible to open .SAFE directory with S2 data but not with S1 data while a zipped directory with S1 data can be opened but with S2 data cannot.

To make it even more confusing, the recent GDAL 2.1 release now includes drivers for S1 and S2 datasets but the opening options are once again almost the opposite of what is possible in SNAP. I have tried to summarize the situation in the table below:

I realize that the internal implementation of S1 and S2 SAFE formats is different, but from the user perspective it would be good if the opening options could be standardized (preferably by enabling all opening options for both S1 and S2).


1 Like

This is a good point. These kinds of things happen when different development teams and different communities are involved.
It won’t be a big deal for the S1 reader to accept the folder as input, find the manifest and continue as usual.
However, it’s still easiest to work with the zips directly since this is how they are distributed.

Thanks for the reply Lveci. I agree that it’s easiest to work with zips so it would be great if this option was added for S2 reader. But it would still be nice if S1 reader could accept folder input, at least for consistency with S2 reader and GDAL.

The update to the S1 reader has been done and will be part of the next release.