Dear Amalia,
Polymer requires some python module, as listed in the file "environment.yml". Please refer to README.md for more information.
Kind regards,
François
Search found 319 matches
- Fri Dec 22, 2023 10:22 am
- Forum: Support
- Topic: MacOS Ventura problems to run the polymer
- Replies: 1
- Views: 13001
- Tue Oct 24, 2023 8:19 am
- Forum: Support
- Topic: Landsat 5, 7, and 9?
- Replies: 4
- Views: 49683
Re: Landsat 5, 7, and 9?
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...
- Tue Oct 24, 2023 8:15 am
- Forum: Support
- Topic: GSW httperror for 180E tiles
- Replies: 1
- Views: 52662
Re: GSW httperror for 180E tiles
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 ...
- Mon Aug 21, 2023 1:14 pm
- Forum: Support
- Topic: Error Processing Landsat-8
- Replies: 9
- Views: 216038
Re: Error Processing Landsat-8
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
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
- Mon Aug 21, 2023 1:10 pm
- Forum: Support
- Topic: Landsat 5, 7, and 9?
- Replies: 4
- Views: 49683
Re: Landsat 5, 7, and 9?
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 ...
- Mon Aug 21, 2023 12:59 pm
- Forum: Support
- Topic: error of processing sentinel-2
- Replies: 3
- Views: 33823
Re: error of processing sentinel-2
Thanks Tiago, I will check and update the dependencies in next release.
- Mon Aug 21, 2023 12:51 pm
- Forum: Support
- Topic: Inconsistencies in tau_r, K_O2, and K_NO2 coefficients
- Replies: 2
- Views: 28978
Re: Inconsistencies in tau_r, K_O2, and K_NO2 coefficients
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
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
- Mon Aug 21, 2023 12:41 pm
- Forum: Support
- Topic: MSI2 Sline Endline command error
- Replies: 4
- Views: 32782
Re: MSI2 Sline Endline command error
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...
- Mon Aug 21, 2023 12:34 pm
- Forum: Support
- Topic: Assigning a Bounding Box
- Replies: 1
- Views: 26138
Re: Assigning a Bounding Box
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...
- Mon Aug 21, 2023 10:37 am
- Forum: Support
- Topic: Incorrect latitude and longitude values while processing S3_OL_1_EFR
- Replies: 1
- Views: 27529
Re: Incorrect latitude and longitude values while processing S3_OL_1_EFR
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...