-
Notifications
You must be signed in to change notification settings - Fork 19
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
Near-duplicate epochs in some mission data #189
Comments
Ludwig, |
Hi Eric,
However, in 2010 there was no leap second. Furthermore, these are no consecutive epochs. There are randomly scattered along the orbit. I fear the problem is somewhere else. |
I finally took some time to look at this, and traced it down to the original CryoSat (GOP version C) products from ESA. So I suggest we just live with the limitation and close this issue. |
Hi,
the altimeter data in RADS is supposed to be at a rate of 1Hz. However, for CryoSat2, Geosat, Jason1-3 and Saral there are some observations which differ by far less than a second and are likely duplicates or near-duplicates. As an example here are some points of c2p0377c004.nc:
The epoch
2010-07-16T00:17:16.069442
differs only by 1e-6 seconds from the previous point and the remaining parameters are exactly the same. For the other missions (Geosat, the Jasons and Saral) they don't seem to be exact duplicates as also the position differs by some hundreds of meters. I have checked all the missions for epochs with dt<0.1s and attached a list with the result. This list contains a row with a summary and an example for each year of each mission. The columns are "mission", "year", "number of near-duplicates" and "time stamps of first near duplicate of this year". For all the other missions I didn't find any epochs with dt<0.1s.It seems that there is either a bug in the original data or in the scripts that translates these file to the RADS format.
near_duplicate.txt
The text was updated successfully, but these errors were encountered: