@marpet do i have to remove that “_M” in all rasters?
did you stick to the BEAM DIMAP format or select any other type, e.g. GeoTiff
yes just used the BEAM DIMAP format
Yes, Unfortunately. It is a shame.
But you can open the *.dim file in a text editor and do the change by search&replace.
OK, thanks for help, i’m going to check what to do.
Nice trick.
1 Like
We need to define a recommended workflow for S1/S2 collocation.
2 Likes
As per this tutorial, I collocated Sentinel 1 and Landsat 8 image. But after collocation, while opening any band, an error pops up.
How can I solve this?
coud you please show a screenshot of the band properties (right-click) of the opened band?
and in the “flags_S” band?
I am searching for the “flags_S.designated_fill_S” expression somewhere in the band properties which causes the error.
Maybe under collocationFlags?
Let me check sir.
I didn’t find the expression “flags_S.designated_fill_S” under collocation flags either.
has this error occurred already before you created the dB bands?
Yes Sir. I can’t open any of the bands after collocation. The same error occurs for all bands.
I tried to reproduce the error with the following steps
- Subset and resample L8
- Subset and multi-look S1
- Terrain Correction of S1 (same UTM zone as L8 product)
- Collocation with S1 as primary product
I get the same error:
It is caused by a mask band which was part of the L8 product before Collocation but now has no longer a function…
I delete all masks in the Mask Manager and then save the changes (File > Save product).
Afterwards you can open all bands as usual.
That’s actually a pretty old issue, but it should be fixed with the next release.
https://senbox.atlassian.net/browse/SNAP-662
@ABraun Can you provide the two products you have used for the collocation?
Then I can try with the current development build and check if it is really fixed.
I’ll send you a location wher yuo can upload the data.