Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CryoSat-2 mission phase for "cryo2ice" orbit #183

Open
ludwigus785 opened this issue Jul 8, 2022 · 1 comment
Open

CryoSat-2 mission phase for "cryo2ice" orbit #183

ludwigus785 opened this issue Jul 8, 2022 · 1 comment

Comments

@ludwigus785
Copy link

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).

@ezaron
Copy link

ezaron commented Apr 29, 2024

Hi Remko, Eric,

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.

-Ed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants