Forum

Hi,

There are several missing MODIS-Aqua granules/orbits from 8 to 13 October.
Do you know the reason and when the missing data will be available? or are the gaps definitely lost?
We didn't found any communication concerning this issue.

Thanks,
Julien
Copernicus Marine OCTAC Service

Hi, I've done several new tests, and it appears that now, surprisingly, requests with a larger period range are significantly more efficient than smaller ones. I can now easily scan, for instance, over 3 years of data for a sensor in a single request, and it takes less than 30 seconds, when scanning...

Is the missing data from July 10-15 definitely lost or will it be recovered later?
Thanks,
Julien

I see also a change concerning the unit of the par variable from: "einstein m^-2 day^-1" to "mol photon m^-2 day^-1" and the new unit is not recognized by the udunits lib and so not compliant with the CF convention (you can check with the udunits2 utility and cut/paste the unit)....

I also see that the attribute processing_version changed from "R2022.1" to "R2022.0.1" which seems very suspect?

It seems that only MODIS-A L2 ares affected for the moment, both VIIRS did not change.
We use cntl_pt_rows to detect the start of a MODIS bowtie using this equation ((cntl_pt_rows - 1) % 10) == 0
How can we detect bowtie with the new L2 format without cntl_pt_rows?

Hi, It seems that recently there was a change in the format of the OC Level-2 products, for example the /navigation_data/cntl_pt_cols variable and pixel_control_points dimension was removed, do you confirm this (example: AQUA_MODIS.20240708T033001.L2.OC.NRT.nc)? Are these format change specified som...

Thank you Tommy, yes on our side we use this metada to differentiate NASA reprocessings.
Julien

Hi, Our automatic download chain got this file: JPSS1_VIIRS.20240626T040600.L2.OC.NRT.nc which contains: :processing_version = "CI" :pversion = "CI" instead of :processing_version = "R2022.0" :pversion = "R2022.0" Was it an error and do we need to delete it on...

Hi, Since this night around 2h UTC the same issue came back: usually our File Search API requests by 5-days periods are instantaneous (~2 seconds) and now they take more than 2 min, with timeouts because sometimes more than 3 min. I just tried to reduce to 2-days period but no improvement, then I tr...