Stop and Go EFlow averaged data

Good morning,

It’s been a while since I last wrote on the forum because, honestly, everything has been running smoothly with my RS2 in my daily workflow. I always work with a fixed base in RTK using a data connection, so I’ve never needed to do post-processing… until yesterday!

The survey area had no cell coverage, so I decided to use Emlid Studio to process my corrected points. After following the tutorial (Stop & Go with Emlid Flow | Emlid Studio), the software couldn’t fix the floating points to FIX, and I didn’t get a results file.

While searching the forum for similar issues, I came across this thread (Emlid Studio "Stop and Go with Emlid Flow" ZERO POINTS FOUND - #3 by kirill.pavlyuchuk), where @kirill.pavlyuchuk says:
“The reason is that the points in the CSV file weren’t averaged but collected instantly. They must be averaged for the Stop & Go workflow.”

I suppose that’s the issue because my data collection mode was set to “Instant.” In that thread, they resolved it by editing the CSV file to add 1 second to the averaging end, but I’m unsure how to do this.

Any ideas?

The solution to this issue is in the reply from @kirill.pavlyuchuk that I referenced in my post. I edited the CSV to add 1 second to the “Averaging end,” and by doing so, when processing with the Stop and Go workflow in Emlid Studio, I was able to get the expected results.

To correctly edit the CSV, you need to consider your Windows regional settings. In my case, in Spain, we use commas for decimals, while the CSV uses periods. Therefore, to edit the CSV file in Excel and add 1 second to the time, I had to follow several steps.

In Excel, the commands I used to automatically add 1 second to the time were LEFT, VALUE, and RIGHT to break down the text string in the “Averaging end” cell. Once the 1 second was added, I concatenated the result using the & command.

I saved everything back into a CSV file, and when processing it again, I was able to get all the points in FIX.

If anyone needs an Excel example to make this modification, feel free to message me privately. Cheers!

3 Likes

Hi @Naeblis,

That’s good to hear you found a solution, and thank you for sharing a detailed explanation—this will definitely be helpful for other users!

Yes, in this cases we advise add one second to the “Averaging end”. We also recommend, before collecting data, avoiding collecting points instantly and instead allowing time for averaging to ensure better accuracy.

3 Likes

Looking at the results I’ve obtained, the final CSV only provides ellipsoidal height and not orthometric height. Is there any way to get it directly without having to perform a subsequent transformation? During data collection, I made sure to indicate the application of a geoid model in the app.

1 Like

Hi @Naeblis,

After you have the corrected CSV, let’s follow these steps to obtain the local height for the points:

  1. Create a new project in Emlid Flow 360 in the desired coordinate system and vertical datum.

  2. Import the corrected CSV.

  3. The local coordinates and height will be automatically calculated based on the geographic coordinates and the selected projection.

You’ll find the new coordinates among the details of the points.

2 Likes

Thank you for your response. Honestly, I wasn’t used to working with Emlid Flow 360 and had always relied on Emlid Studio. This way, I managed to get the corrected points list easily and directly.

2 Likes

@Naeblis,

Glad to hear it helped!

1 Like