-
Notifications
You must be signed in to change notification settings - Fork 68
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
GNSS Blackout in UrbanNav-HK-Medium-Urban-1 #11
Comments
Dear Tim, Yes, some receivers cannot receive signals well in short period in urban canyons. You can try other sensors if you want to have continuous measurements, e.g, 20210517.light-urban.tste.ublox.f9p.splitter.obs which another F9P uses a geodetic antenna Best Regards, |
Dear Darren, I added furthermore a plot of the pseudorange residual over time. You can see the phenomenon there too, and there is no increase in the error before and after the blackout. |
Dear Tim, Yes, I think this F9P sensor very possibly has some receiver issues in these 120s. Let me involve one colleague which an expert in GNSS to help this issue @ivannhf Best Regards, |
Dear Tim, Seems there is a malfunction on the receiver, could be a connection lost during that period. Best regards, |
Dear Darren and Ivan, could you maybe add a note to inform potential users about that glitch? Best Regards |
Dear Tim, Thank you for your suggestion. Notification of this issue is added to the description of the medium urban. e6c236a Best Regards, |
Thanks a lot Darren! |
Hi everyone,
there seems to be a GNSS blackout in the "20210517.light-urban.tste.ublox.f9p.obs" file of the "medium urban" dataset.
Exactly between:
> 2021 5 17 2 42 30.0050000 0 28
and
> 2021 5 17 2 44 41.0050000 0 29
During this period, no observation exists in the RINEX file.
Other files like "20210517.light-urban.tste.ublox.f9p.splitter.obs" or the m8t files do have observations in this period.
Is this a known property of the dataset or a problem in the post-processing?
Best Regard
Tim
The text was updated successfully, but these errors were encountered: