Today we want to talk about the Stop & Go workflow with Emlid Flow in more detail. This workflow allows you to improve positions of points collected without a real-time correction link between the base and the rover. This can happen due to insufficient line-of-sight for LoRa, lack of internet connection, unavailability of NTRIP service, etc.
Before performing Stop & Go, you need to determine the type of accuracy you need for your project—absolute or relative. If you want absolute, you need to know the coordinates of your base. Learn more in the Choosing a Base Setup Method guide.
The workflow includes two stages performed in the field and in the office, one after another:
In the field
- Place your base. Learn more from the Placement guide.
- Configure your base and rover to record logs as it is shown in our How to record logs for Stop & Go with Emlid Flow guide. We recommend recording them in the RINEX format. Enable recording.
- Create a project in Emlid Flow. You can learn more in the project preparation guides.
- Measure all unknown points with a rover using the averaging option which is required for Stop & Go to work properly.
In the office
- Download the recorded logs. You will need RINEX observation files from both the base and the rover, and a RINEX navigation file from either the base or the rover.
- Download your project from Emlid Flow in the CSV format. Note that CSV PENZD is not supported by Emlid Studio.
- Go to Emlid Studio, choose the Stop & Go with Emlid Flow workflow, upload the files, specify your base’s coordinates if necessary, and process the data to get separate points. Learn more from the Stop & Go with Emlid Flow guide for Emlid Studio.
Note that you’ll obtain points with geographic coordinates as a result. To get projected ones, follow the steps from our previous support tip.
If you have any questions or would like to share your experience using Stop & Go, let us know in the comments below. For help, you can always contact us at email@example.com.
P.S. Don’t forget to check out our latest post about the importance of the Reach Firmware updates.