-
Notifications
You must be signed in to change notification settings - Fork 103
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
KINEMATIC PPP PROCESSING PROBLEM #29
Comments
Hi Giorgio, I tried running your RINEX file on my PC. I'm using PRIDE v3 with the Sept. 2024 update on Ubuntu 22. I got a different error though and the position was not obtained. Here are the files: Cheers, John |
Hello, I apologize for the previous message. I didn't know that you were asking for kinematic processing. However, I still get the same error (no resolvable ambiguities) after doing so. Can I see your config settings? |
Hi Both, PRIDE PPP-AR is developed for geophysical studies and asks for relatively high-quality data. Data collected on phones can hardly be processed well. |
Thank you for the reply. I'll take note of this in the future. |
Hello to everyone ! :)
I'm testing the low-cost u-blox receiver C099 F9P by processing the u-blox raw measurements using PRIDE PPP-AR.
The RINEX is obtained converting the .ubx observation file using Emlid Studio software.
The acquisition is done by fixing the antenna in the top roof of a car and driving for about 3 hours with 1 second of time interval.
Unfortunately, PRIDE PPP-AR is not able to get the solution, and the following error message is displayed:
I tryed to process the same RINEX using the online web-service CANADA PPP (CSRS-PPP) and it works, without fixing the ambiguity, but it works.
I have this problem only in the processing of kinematic survey, because if I process static surveys performed with the same receiver, with the same settings, PRIDE is able to get a solution.
I attached the RINEX file in zip compressed format:
GIOR3130.zip
Could it be a PRIDE limit for too much noisy observation files ?
Thank You so much in advance for every kind of answer.
The text was updated successfully, but these errors were encountered: