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
Hi,
in July 2020 CryoSat-2 was moved to a new orbit (see https://earth.esa.int/eogateway/missions/cryosat/cryo2ice).
The new mission phase, however, is not covered in the RADS database (neither in the directories nor the nc data attributes). As a consequence, tracks with the same pass number are no longer collinear (after July 2020).
The text was updated successfully, but these errors were encountered:
I am getting strange results when I try to use rads2nc with CryoSat and a --region or --lat, --lon specifiers.
For example, this returns no data:
rads2nc --lat=30,40 --lon=-130,-120 --sat=c2/a --ymd=20230303,20230710 -r any --var time_mjd,lon,lat,sla
but if I remove the geographic limits, I can see plenty of data in this region.
I noticed that if I shift the date, the above command appears to work during and prior to 2020:
rads2nc --lat=30,40 --lon=-130,-120 --sat=c2/a --ymd=20200303,20200710 -r any --var time_mjd,lon,lat,sla
but it does not return data for dates after 2020.
I wonder if this could be related to computed vs actual pass coordinates or something like that.
I'm running rads2nc, version 4.6.2, and I rsync'd to the delft server a few days ago.
Hi,
in July 2020 CryoSat-2 was moved to a new orbit (see https://earth.esa.int/eogateway/missions/cryosat/cryo2ice).
The new mission phase, however, is not covered in the RADS database (neither in the directories nor the nc data attributes). As a consequence, tracks with the same pass number are no longer collinear (after July 2020).
The text was updated successfully, but these errors were encountered: