Hello, I am new to Emlid and working in stop and go mode. I am generating the position file with the Rover and Base but when I upload my survey, I am getting that “0/16 points were averaged converted.”
Is there another way that I can correct the survey .csv file using the corrected base output? Thanks!
Would need more detail here. Can you share the base/rover ublx files and CSV?
You may want to check out this post too: PPK Post-Processing Issue - #4 by inkar.madikyzy.
Thank you! This is helpful. I checked the csv files and they are in chronological order, but similar to the other post, I only averaged for 5 s on each point.
Here is a link to the files: Reach_Rover_20241026140102 - Google Drive
We also had some connection issues with the rover (from going under buildings), which I think caused it to disconnect and may have turned off (?) the rover recording.
We’ll be back to the site next month, so it’s easy enough for me to retake these points. Do you recommend any settings with the rover files to make sure the points can be processed as “fix”?
Really appreciate your time and expertise.
Hi Tori,
Welcome to the community!
Thanks for sharing the data. I checked the data, and on the rover side, it seems that it just activated the GPS satellite. Is this on purpose? I will start enabling all the satellites to gather more data for the calculation.
Hello, thank you so much for checking! This was not on purpose - I will enable the rest of the satellites!
Also, what is the capture mode in Emlid Flow? Are you taking an average over a certain time or is the point capture set to Instant?
If the latter, Emlid Studio will not process the points in stop&go. You can verify by taking a look at the collection start and end time columns in the CSV output from your project. If the timestamps for both are identical, it will not post-process.
Hi Gabriel, this is helpful - thank you! We had set the collection time to 5 s, but from reading some other posts and advice, it sounds like I should bump that up to a minute or so to get better data.
If you’re locating non-important points like edges of roads and fences in clear sky conditions 5 sec is fine as long as you have a good “fix” conditions.
If you’re anywhere near obstructions like trees or buildings, use with care and increase your observation times to a 1 minute minimum with a good “fix” confidence.
If locating important items like land boundary corners, 5 minutes minimum if you have clear sky conditions.
All above are based on wether or not you have a local base onsite using radio RTK or RTN networks. As I’ve said on this forum many times, short baselines are your friend. Even if you’re using an RTN, it’s good to have a local base onsite logging at 1 sec rate minimum. In case you lose cell coverage, you still can post process your baselines. In the case of losing cell coverage, increase you observation times to 1 minute minimum based on how important your point is. Keep in mind also, you can’t post process with 5 seconds of data. The longer observation times you have, the better you will have a final computed solution.
Bryan, this is incredibly helpful information - thank you so much! That makes sense and definitely, I’ll increase the observation times. Also, it’s helpful to know about the short baselines. We have a base station on site but I think we were pushing too far away on some of the points. Thank you again for sharing these tips!
I’ve posted this before, use as a guide even though it’s from a different manufacturer; we use their equipment for the last 10 years as well as Emlid’s:
This is helpful, Bryan! Thank you for sharing the guide.
