I would like to report a recent issue related to the download of Sentinel-3 satellite images.
My study area is Lake Titicaca, and since December I have been experiencing inconsistencies during data download.
For example, when attempting to download the image dated January 15, 2025 (20250115), the system actually downloads the image from January 14, 2025 (20250114). This creates confusion for the user and also causes a southward displacement of the study area in the downloaded image.
In addition, when using SNAP version 13 on a MacBook Pro M3 and applying the C2RCC OLCI processor, the resulting products—particularly chlorophyll-a—show visible line artifacts. When repeating exactly the same workflow (same date and same parameters) on an Alienware computer running Windows 11, these artifacts do not appear.
I am reporting this issue for awareness, as other users may be experiencing similar problems, particularly on macOS systems with Apple Silicon.
For reference, I am currently working on a MacBook Pro M3.
Hello, can someone tell me when we are doing calculations in band math, is it automatically masking the 0 value pixels? I experienced this when I calculated the index of NDI using Sentinel 3. First I tried it using Python code in Google Colab, and then I tried it by the use of the SNAP band math function. The outputs are different. Please answer if someone knows what has happened there. Thank you.
I would like to report a recent issue related to the download of Sentinel-3 satellite images.
My study area is Lake Titicaca, and since December I have been experiencing inconsistencies during data download.
Could you please confirm whether you are downloading the data via the SNAP Product Library, and which repository is being used?