-
Notifications
You must be signed in to change notification settings - Fork 23
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
Gettinf IONEX files with the new 'Long Product Filenames specification #42
Comments
Thanks for propagating the ALBUS issue here @twillis449. I will have a quick look to see if I can kludge this on a fork for the sake of comparison. RMextract fails with the recent MeerKAT databases taken January 2023. PS:. It appears AIPS "vlatecr" TECOR autodownloader is not affected by this... Possibly it is specific to the JPL databases not conforming to the new standard. |
It seems the document is not really up to date, I cannot find the filenames according to this specification. I'll work on it |
for now you can change to some other server/prefix combination. Until the different data providers have worked out their differences I cannot really make a general code. server = "ftp://gssc.esa.int/gnss/products/ionex/" This combination of server prefix has given the best results in our tests. I will update the default path in getIonex |
hi, thanks for this software suite. This set of Sorry for the trouble and thanks for your time. The error:
|
@maaijke |
I will have another look then. If the updated long product information is consistent I can adjust the code such that it accepts both the old (esa ftp) and new format. |
Hi Maaijke
I hope that things are going well with you in NL.
I assume that you are aware that as of the beginning of this year, the CODE website is using the Long Product Filenames specification for ionex files? Ionex file names are now ~ 20 characters long. Sigh. Something similar to the enormous length of RINEX 3 files vs RINEX2. If you don't have a copy of the document describing the changes you can get it here:
http://acc.igs.org/repro3/Long_Product_Filenames_v1.0.pdf
Cheers
Tony
The text was updated successfully, but these errors were encountered: