It means that a code for reading the data should be written. These files are the Level1* files in the polymer folder. I don't know the structure of L9 data, but I doubt that it will involve the program "L8_angles", which purpose is to generate the geometric data (sun and view angles) for Landsat8. C...

Hello, Many thanks for reporting this issue with GSW tiles, we will have a look. The OLCI products have already a land/water mask in the Level1 products, and it is used by default (landmask='default'). So you shouldn't need to use GSW for OLCI. By passing landmask=None, you disactivate land masking ...

Hi Sydney,
It is the "l8_angles" command that should be used in the first place to generate the angles files, not polymer_cli.py.
polymer_cli.py should be run afterwards, once the angles file is present.
Cheers,
François

Hello, These sensors are currently not supported. L5 and L7 are not supported and Polymer's applicability to these sensors may be limited due to the available spectral bands. L9 could be supported, and would require the development of a reader. I am currently not planning to work on it in the short ...

Thanks Tiago, I will check and update the dependencies in next release.

Hi Guillaume,

Thanks for this. Indeed the absorption coefficients would require some more up-to-date and consistent information. I will include this in next Polymer release.
Cheers,
François

Hi, The answer to your question is in the Level1_MSI docstring ; I agree it may not be the most visible ;) sline, eline, scol, ecol refers to the coordinate of the area to process: * in the 1830x1830 grid at 60m resolution * in the 5490x5490 grid at 20m resolution => eline-sline and ecol-scol must b...

Hi, Indeed it is possible, but the bounding box has to be specified in pixel coordinates. All Level1 objects support the following arguments: sline, eline, scol, ecol, which provide the start and end lines and columns for the bounding box. For Sentinel-2, the coordinates also depend on the chosen re...

Hi Tiago and sorry for my late reply. Thanks for providing a test image and location, I can reproduce the issue of lat/lon unicity on this file. The lat/lon in Polymer are directly copied from the level1 datasets, located in the "geo_coordinates.nc" file (no tie points are involved). I initially sus...

Hello, To process HICO, you can use the same logic as with the other sensors, using the Level1_HICO class. The resulting python script would look like : from polymer.level1_hico import Level1_HICO from polymer.main import run_atm_corr from polymer.level2_nc import Level2_NETCDF run_atm_corr( Level1_...