On the Subject of ONE base, and multiple rovers.... and DPOS

[Nate The Surveyor]

The way it has been, is ONE ROVER starts the base, then that same rover downloads the base raw data file, and then DPOS is used, to adjust the base point, to be on SPC. Good. We will call this the PRIMARY ROVER.

Now, we want to run multiple rovers, off that base.

Why not do it this way:

Combine them through DPOS.

The DPOS server RETAINS all the base files, that are uploaded, for one month. In this base file, is the rover name, date, point desc. Screen shot, and Antenna Height. Etc.


When ANOTHER rover wants to dpos, that did not start the base, the user connects to DPOS. Then, tells the ROVER (secondary) that it's looking for a file posted by a PARTICULAR rover NUMBER. Presses search. While connected. A calendar pops up, showing the last 30 days, of uploads, from that particular PRIMARY ROVER. And, if there is RAW data in the SECONDARY rover, that corresponds, to what if finds on the DPOS server, that is, the DATES and TIME match, then, we get that day highlighted. Click it, and it shows a graph of overlaps time, when BOTH have data. Select, Upload, and process.
When finished, the BASE RAW data, is SENT from DPOS to the secondary rover, and comes fully processed. This way, the BASE numbers are 100% identical. It's faster for the user. Less processing time.

Seems useful.
Of course, I'm not a programmer.

But, this would work very well, for the long term big picture.

This would also make all the shifts 100% identical, even though they may be a week apart, and using precise orbits, with the later DPOS, of the secondary rover.

Just thinkin'....... What's your thoughts?

N

 

[Phillip Lancaster]

I like that Nate thinks up solutions to other peoples problems. I like his solution first but if takes too long then at least having an option in "batch export" to export the current job base file. That way I could dropbox/gdrive the file. Then all rovers would have access to the file since we are all connected to the same dbox/gdrive account.

 

[Nate The Surveyor]

Well, it may be "other peoples problems".
But, likely will become my problem, eventually.
The way this is being solved NOW, (assuming all goes well), is:
Recover base point...
Download raw data, from base, multiple times.
Dpos multiple times.
With a cluster of 3 LS units, this could take time, when all goes right.....
Plus, tie up the server at dpos, more.
I want it all fast and slick. Who doesnt?
My idea, or Phillip's method would perhaps be easier, from a programmers view point. Plus, less tech support.
That seemed good...
Nate

 

[Darren Clemons]

Both of these ideas seem like good options.
And, yes Nate, with a cluster a three LS's, as I have done a few times, this is quite a tedious process.....
That being said, what we've typically accomplished in one day with RTK/PPK from three different rovers all running off one base is sometimes absurdly ridiculous, so the time it takes to get those points processed is well worth it.

I've heard that this process may be undergoing some changes in the future to make it a bit smoother.

The key in doing this process successfully is knowing the location of the base GNSS file, retrieving it easily (for me I've started choosing to just copy it on a flash drive when I get back to the office instead of downloading multiple times in the field) and then copying it in the correct place in the second/third rover.

The other thing I've chosen to do that eliminates a couple of steps is after setting the base in the original rover, I do a quick "archive current project" onto a flash drive and then unpack archived project from that flash drive onto the additional rovers.

This actually gets the current days base file in all rovers and it's ready to "attach GNSS file" back at the office..
Also very helpful if the current job has a grid/ground scale factor set, so as to copy that adjusted coordinate system into the additional rovers.

 

[Shawn Billings]

Both of these ideas seem like good options.
And, yes Nate, with a cluster a three LS's, as I have done a few times, this is quite a tedious process.....
That being said, what we've typically accomplished in one day with RTK/PPK from three different rovers all running off one base is sometimes absurdly ridiculous, so the time it takes to get those points processed is well worth it.

I've heard that this process may be undergoing some changes in the future to make it a bit smoother.

The key in doing this process successfully is knowing the location of the base GNSS file, retrieving it easily (for me I've started choosing to just copy it on a flash drive when I get back to the office instead of downloading multiple times in the field) and then copying it in the correct place in the second/third rover.

The other thing I've chosen to do that eliminates a couple of steps is after setting the base in the original rover, I do a quick "archive current project" onto a flash drive and then unpack archived project from that flash drive onto the additional rovers.

This actually gets the current days base file in all rovers and it's ready to "attach GNSS file" back at the office..
Also very helpful if the current job has a grid/ground scale factor set, so as to copy that adjusted coordinate system into the additional rovers.

The student becomes the master, grasshopper.