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

60 seconds #70

Closed
labonocl opened this issue Oct 19, 2020 · 1 comment
Closed

60 seconds #70

labonocl opened this issue Oct 19, 2020 · 1 comment

Comments

@labonocl
Copy link

Hi there,

One of the sp3 files for ESA's Swarm mission (ftp://swarm-diss.eo.esa.int/Level1b/Latest_baselines/GPSxNAV/, Satellite A, file for November 26th 2013) contains the following line:

  • 2013 11 26 0 1 60.00000000

When trying to read this line with load_sp3, the datetime library complains with the following error:

ValueError: second must be in 0..59

The error is of course correct (this one file alone contains this error 64 times), so I see two options here:

  1. Put on my Don-Quijote-hat and try to convince ESA that this is an error and that they should debug their data product processing chain and reprocess the entire seven years of Swarm data; or
  2. check for such errors in sp3dt, and fix them there.

Now, I know what I am going to do. So the real question becomes: would you be interested in pulling such a correction of wrong times into the georinex package, or is your position that whoever is responsible for producing sp3 files should take care of this issue, and it is not the responsibility of georinex to handle other people's mistake?

Cheers
Lasse

@scivision
Copy link
Member

I think this is something georinex should tolerate. There are all kinds of quirks in RINEX that are non standard compliant

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

No branches or pull requests

2 participants