Hello Rolf, The different ancillary data modules (NASA, ERA-Interim, ERA5) should already download the necessary ancillary files by themselves. Please have a try; the error messages should guide you if any further action is required on your side. If anything is unclear, let me know of the error mess...

Hello, Thanks for your feedback. A few comments about HICO processing with Polymer (which is considered experimental): About the evaluated physical quantity: if you are expecting remote sensing reflectances in sr-1, be aware that Polymer provides dimensionless water reflectance, which explains a fac...

Hi, As stated in the readme, a part of Polymer source code is coded in cython. You need to convert this source code to c using cython, and then compile this c code to a python module. On linux this is done using Polymer's makefile, but I have not tested it on windows - although, it should be possibl...

Hi Joao, These arguments are to be passed to the function "run_atm_corr", which is the main function called in polymer_cli.py. You can modify the last lines of polymer_cli.py like so: run_atm_corr(Level1(args.input_file), Level2(filename=args.output_file, fmt=args.fmt), calib=None, bands_corr=[412,4...

The patch is included in v4.13, just released.

Fixed in v4.13.

By downloading Polymer you agree to the licence terms and conditions.

This release fixes some bugs (see here, here and here), and does not involve product modification (except when using ERA5 ancillary data).

See more details in the changelog.

Hi Blake,

Indeed there is a bug when applying Ancillary data to OLCI.
Please see this thread for how to fix it : viewtopic.php?f=7&t=41
I will make a release shortly with a few fixes including this one.
Cheers,
François

Oh, I see...I was wrong, there was no problem with your NetCDF library.
The problem is that you have used the older Level1 format. You should use the HICO Level1 files in NetCDF format. Like this one :
https://oceandata.sci.gsfc.nasa.gov/hic ... L1B_ISS.nc
Cheers,
François

Dear Joao,
Good to see that you could fix it !
There will be a fix in next version.
Cheers,
François