Search found 17 matches
- Thu Aug 28, 2025 4:04 pm America/New_York
- Forum: Home
- Question: Error downloading PACE OCI L1b
- Replies: 4
Error downloading PACE OCI L1b
Getting the following error downloading PACE OCI L1b. Is earthdata limiting data downloads now? Traceback (most recent call last): File "/explore/nobackup/people/zfasnach/miniconda3/envs/gpu/lib/python3.11/site-packages/earthaccess/store.py", line 696, in _download_file with session.get(ur...
- Fri Aug 08, 2025 11:30 am America/New_York
- Forum: Home
- Question: ODAAC Timeout Error
- Replies: 1
ODAAC Timeout Error
I'm getting a new timeout error trying to download some MODIS OC L2 files. Any idea what causes this? Traceback (most recent call last): File "/explore/nobackup/people/zfasnach/miniconda3/envs/gpu/lib/python3.11/site-packages/earthaccess/store.py", line 696, in _download_file with session....
- Fri Aug 01, 2025 3:28 pm America/New_York
- Forum: Home
- Question: Problems with GOCI L1b files
- Replies: 3
Re: Problems with GOCI L1b files
I've discovered the the GOCI L1b files on earthdata are gunzipped, but for whatever reason do not have the .gz file extension. They only have a .he5 file extension. Is there a way to fix this?
- Thu Jul 31, 2025 10:02 am America/New_York
- Forum: Home
- Question: Problems with GOCI L1b files
- Replies: 3
Problems with GOCI L1b files
Does anyone know if there are problems with the GOCI L1b files on earthdata? They seem to be hdfeos-5, but they don't seem to be able to be read by any hdf5 or netcdf4 libraries. h5ls -r /explore/nobackup/projects/omi/GOCI/L1/2019/04/01/COMS_GOCI_L1B_GA_20190401071643.he5 /explore/nobackup/projects/...
- Sun Jul 20, 2025 9:52 am America/New_York
- Forum: Home
- Question: intermittent download success
- Replies: 4
Re: intermittent download success
I have similar intermittent download issues. I can download a few files, then it hangs and fails out after a while. I work on the NASA NCCS machines, not clear to me whether this is a NCCS network issue or if earthdata is simply throttling user downloads. That said, it doesn’t seem to happen based o...
- Fri Jul 18, 2025 2:07 pm America/New_York
- Forum: Home
- Question: PACE OCI CLD NRT File Missing on July 4, 2025
- Replies: 1
PACE OCI CLD NRT File Missing on July 4, 2025
Looks like there is a PACE OCI CLD NRT file missing on July 4, 2025
I found the file...
PACE_OCI.20250704T115704.L2.CLDMASK.V3_0.NRT.nc
but there is not corresponding
PACE_OCI.20250704T115704.L2.CLD.V3_0.NRT.nc
I found the file...
PACE_OCI.20250704T115704.L2.CLDMASK.V3_0.NRT.nc
but there is not corresponding
PACE_OCI.20250704T115704.L2.CLD.V3_0.NRT.nc
- Wed Jul 16, 2025 4:39 pm America/New_York
- Forum: Home
- Question: PACE OCI Cloud Products
- Replies: 1
PACE OCI Cloud Products
I see the PACE OCI cloud products are now in earthdata, but they are several weeks behind real time. Are there plans to release the nrt cloud products through earthdata?
- Fri Jul 04, 2025 8:35 pm America/New_York
- Forum: Home
- Question: Earthaccess Download timeouts CMR error
- Replies: 1
Earthaccess Download timeouts CMR error
I'm all of a sudden getting timeout errors trying to access any data with the earthaccess tools An example is >>> import earthaccess >>> earthaccess.login(persist=True) <earthaccess.auth.Auth object at 0x7f9474b5b0d0> >>> start_date = '2024-04-01 00:00:00' >>> end_date = '2024-04-01 23:59:59' >>> mi...
- Tue Jul 01, 2025 6:21 pm America/New_York
- Forum: Home
- Question: PACE L1b and Cloud Granule Timestamp mismatch
- Replies: 4
Re: PACE L1b and Cloud Granule Timestamp mismatch
Thanks for the clarification. Just to confirm, this means users need to match L1B and L2 files based on a time window rather than a one-to-one file id match? That approach seems a bit fragile, especially for automated processing or algorithm development that relies on synchronized L1B reflectances a...
- Mon Jun 30, 2025 11:28 am America/New_York
- Forum: Home
- Question: PACE L1b and Cloud Granule Timestamp mismatch
- Replies: 4
PACE L1b and Cloud Granule Timestamp mismatch
I've been working with PACE OCI data and finding that there are some PACE OCI granule for which the L1B and cloud product have different time stamps. Any idea the cause? What's the best way to match granules if the time stamps don't match up? An example.... PACE_OCI.20240401T021445.L1B.V3.nc PACE_OC...