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

GNSS Blackout in UrbanNav-HK-Medium-Urban-1 #11

Closed
tipf opened this issue Mar 3, 2022 · 7 comments
Closed

GNSS Blackout in UrbanNav-HK-Medium-Urban-1 #11

tipf opened this issue Mar 3, 2022 · 7 comments

Comments

@tipf
Copy link

tipf commented Mar 3, 2022

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

@DarrenWong
Copy link
Member

DarrenWong commented Mar 4, 2022

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,
Darren

@tipf
Copy link
Author

tipf commented Mar 4, 2022

Dear Darren,
thanks for your fast response. I plotted the visibility of all satellites over time and there is a big gap of 120s.
I understand that such things can happen in urban canyons, but 120s while driving in a medium-urban environment?
Isn't it unlikely that all satellites drop out simultaneously?

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.
Could it be a receiver malfunction or a glitch in the data recording?

GNSS_UrbanNav_HK_Light_Visibility

GNSS_UrbanNav_HK_Light_ClockError

@DarrenWong
Copy link
Member

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,
Darren

@ivannhf
Copy link

ivannhf commented Mar 10, 2022

Dear Tim,

Seems there is a malfunction on the receiver, could be a connection lost during that period.
We suggest avoiding that period or using another F9P receiver connect to a geodetic-grade antenna.

Best regards,
Ivan

@tipf
Copy link
Author

tipf commented Mar 10, 2022

Dear Darren and Ivan,

could you maybe add a note to inform potential users about that glitch?
(And can decide whether they want to avoid it or not.)

Best Regards
Tim

@DarrenWong
Copy link
Member

Dear Tim,

Thank you for your suggestion. Notification of this issue is added to the description of the medium urban. e6c236a

Best Regards,
Darren

@tipf
Copy link
Author

tipf commented Mar 10, 2022

Thanks a lot Darren!

@tipf tipf closed this as completed Mar 10, 2022
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

3 participants