Hi
I downloaded Sentinel-3/OLCI, WFR data and when I am opening it in SNAP-11, then I find that the data is not geo-corrected.
How can I geo-correct it? I want to analyze chl_NN and other products for my study area and I am unable to do it!
Are you opening the NetCDF files directly?
Better use the zip directly or xfdumanifest.xml inside the extracted folder.
The geo-coordinates are stored in a separate geo_coordinates.nc file and not included in the other nc files. When loading the whole product SNAP is taking care of also loading the geo-coordinates.
I tried both ways in SNAP 11. What it is doing, that for few seconds it shows that it is opening the file (the blue color in the lower task bar moves like opening the file). But after few seconds when the blue color in the lower task bar stops, no file opens in the Product explorer panel.
1 Like
Can you reproduce this behaviour and attach the messages.log file (Help → Show Log Directory). It seems there is some problem.
Alternatively, if you have the free EOMasters Toolbox installed you can create a System Report. This includes necessary information and the last 100 log lines, which is usually sufficient.
Thanks Marco. I could do it. In fact file was corrupted. I downloaded the file again and could open it.
Another concern is that suppose while doing any operation, if any file is giving Java null point error then can we solve this error in the SNAP? e.g. I am mosaicking two scenes of any satellite data and while importing the data in mosaic widget it gives Java null point error then what may be the cause and what would be the solutions for it?
Good that you were able to solve this issue.
You probably have the same problem as others with the mosaic.
- SNAP 11 error when mosaicking resampled Sentinel-2 L1C
- Mosaicking problem on SNAP 11 - Optical Toolbox - STEP Forum
This needs to be fixed by the developers.
A NullPointerException always indicates a developer mistake. Only in rare cases you can get around e.g., by selecting another option. So unfortunately, I think you need to wait till SNAP 12 or maybe the devs release an intermediate update. Which would be appropriate, I think, seeing that multiple have reported this issue already.