CF checker errors suddenly yields 2 errors after being converted to NetCDF4
Added by Werner dietsche 8 months ago
The Subset step appears to be working. When we save to a different file format (BEAM-DIMAP), it can be opened by SNAP without any issues.
How can we subset our dataset and also produce a valid NetCDF file?
Update: I also tried using NetCDF4-BEAM. The NetCDF can be read into a NetCDF visualization software, and I can view the band information. However, the lat lon coordinates don’t appear to have been subset (they have the original lat/lon), and the dimensions of the band are called y1 and x1 instead of lat lon or x y…
Update 2: I should also mention that we’ve previously used Sentinel-3A products which were subset and exported to NetCDF4-BEAM (using snappy rather than GPT) and had no issues, so it seems to be either a Sentinel-1 or GPT-related issue.
Replies (1)
RE: CF checker errors suddenly yields 2 errors after being converted to NetCDF4 - Added by Estanislao Gavilan 8 months ago
Hi Wegner,
Have you tried to use nco to correct the attributes of your nc file? There are many examples on the forum.
Kind regards,
Estanislao