at least in most radar-related modules, metadata which is required for the correct execution of the tool is lost when not sticking to BEAM DIMAP.
But I have to admit, as a fresh user of SNAP I was also a bit confused because I didn’t know this format yet and also tended to select more relatable formats for my output at first, because I feared reduced compatibility with other programs. If it would become more clear that this format is advised/required for the data to maintain its meta-information, some of these problems could be prevented/avoided:
- Following error
- SAR product
- SAR Oil spills - Minimum cluster size
- Creating geotiff for snap toolbox, how to include "spectral wavelength" metadata?
- Ellipsoid Correction error: Metadata range_spacing has not been set
- Files are too big after preprocess
- Problem in apply orbit file
How about adding ‘recommended’ after BEAM-DIMAP in the dialogue where the output file type can be selected, or some sort of warning that metadata might get lost?