Stop and Go

[John Noonan]

This is just general questions on the best approach for conducting Stop and Go collection.
Should it be done with the LS as a stand alone or should it be used with the T2?
What should be the minimum recording time and how long should the point be occupied.
Would you store GPS data and post process or just use LS points derived points

 

[Matt Johnson]

Hi John, currently Stop and Go collection is not supported by J-Field but it is planned to be implemented soon. The details of how to use it will be provided after it is implemented.

 

[John Noonan]

So currently post processing of GPS data collected would be the only way to do this.
Next question is what should be the shortest occupy time over a point and the collection interval for good results.

 

[Kelly Bellis]

@ John - FWIW - I've not played with it much yet, but the Triumph-2 using JMT for Android currently offers Stop and Go.

@ John and Matt - For my own understanding, please explain what Stop and Go means to you. While we roam the countryside collecting and recording RTK data, if the LS is verifying without resetting its engines, maintains lock, aren't we then performing in effect this so-called Stop and Go?

 

[Matt Johnson]

Kelly here is what I have suggested the development team implement:

I think what we need is the ability to continuously record the GNSS file while collecting points if Stop and Go is enabled. It should tag the observation window in the file for each point collected so it can be post processed. The points should still be stored in J-Field. If we do not have a fix for the point, I had suggested making the point red in the Points list.
​

Comments are welcome.

 

[John Noonan]

I am going to down load the app and see but may need a youtube class to get it up and running

 

[Matt Johnson]

So currently post processing of GPS data collected would be the only way to do this.
Next question is what should be the shortest occupy time over a point and the collection interval for good results.

Yes you currently would need to post process the observations.

Here are the current recommended settings for collecting points. We are still working on testing and refining these:

 

[John Noonan]

Hi Matt, The image did not come accross would you email jlnoonan@noonanmcdowell.com

 

[Matt Johnson]

John is it visible now?

 

[John Noonan]

Yes thanks

 

[Jim Campi]

Hi Matt,
What is the consistency counter and where is that setting?

 

[Matt Johnson]

It is found in the Verify settings in the quick setup menu. The built in help screens explain it. Hopefully Kelly can post an updated manual or at least this portion of it that explain it in more detail.

 

[Kelly Bellis]

Jim,

Here's the current draft:
Users Guide to the Triumph LS - RTK Verification - Draft 4

 

[John Noonan]

If you are doing stop and go would you do this with the T2 or just the LS by its self.
I would think that if it is done with the LS alone then I would need to post process the GPS data with local GNSS control.

 

[Matt Johnson]

You could do it with two Javad receivers or one receiver and data from a CORS station. Both methods would require post processing.

 

[John Noonan]

With two Javad receivers one placed over a known point T2 and the other used to walk to various points LS.
What would suggest as the minimum recording GPS time (ie 1sec , 4sec?) and how long should the point be occupied.

 

[Matt Johnson]

Occupation times would depend on the accuracy you desired and the environment of the point (multipath or open sky). We have been working on test in different environments with varying occupation to show how it affects accuracy and will release the results once the test are completed.

 

[Nistorescu Sorin]

Hi,

Stop and Go method can be useful in some areas, with two receivers or only with one receiver and post processing.

For a L1 receiver: 10min for initialization(about 1m between base and rover), 10sec for collection of points for under 1km radius from base.
For L1/L2 receiver no need for initialization and 5sec/points.

VRS raw data file can be generated at a specified time and coordinate (about 1m from the rover), using multiple CORS at 1sec raw data for example.

May be it would be helpful if DPOS could generate VRS raw data files at a specified time and coordinate.

I could easily generate a 2hours - 1sec VRS raw data, in Ellsworth city at January, 03, 2015, using the following CORS stations: BAR HARBOR (BARH), BANGOR (MECC), MACHIAS (MEMA), WALDO (MEWA).

Anyway RTK techniques are more and more powerful every year.

Regards,

Happy New Year!