You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other details about your setup that could be relevant: working of the "ssusi_bug" branch of pysatNASA, now in "develop"
Additional context
Going through the DMSP SSUSI data I found that this issue is caused by having files were there are duplicated times. This isn’t great, obviously, and is something that CDAWeb needs to resolve.
Description
DMSP SSUSI SDR-Disk data for F18 has a file issue that results in the duplicate time error.
To Reproduce this bug:
Steps to reproduce the behavior:
Test configuration
Additional context
Going through the DMSP SSUSI data I found that this issue is caused by having files were there are duplicated times. This isn’t great, obviously, and is something that CDAWeb needs to resolve.
The culprits:
dmspf18_ssusi_sdr-disk_2014029T230313-2014030T004504-REV22086_vA8.2.0r000.nc2019-02-11 14:0621M
dmspf18_ssusi_sdr-disk_2014029T231055-2014029T235808-REV22086_vA8.2.0r000.nc2019-02-11 13:5411M
In directory: https://cdaweb.gsfc.nasa.gov/data/dmsp/dmspf18/ssusi/data/sdr-disk/2014/029/
Pysat is only finding ONE unique time in the two files: 2014-01-29 23:40:27.824444
However, the top file’s global info states starting stopping times of:
:STARTING_TIME = "2014029230313" ;
:STOPPING_TIME = "2014030004504" ;
And the bottom file’s global info says:
:STARTING_TIME = "2014029231055" ;
:STOPPING_TIME = "2014029235808" ;
So, nominally, the second file shouldn’t exist. Does CDAWeb has a place that this can be reported?
The text was updated successfully, but these errors were encountered: