Merging jobs using multiple LS’s

Darren Clemons

Well-Known Member
We have used multiple LS’s on several jobs for a couple years now and with reading about Matthew getting a second and doing it also, it now may be becoming popular enough to become a topic for discussion.

Up to now, we’ve mostly used a 2nd and sometimes 3rd LS to collect side features such as road center lines, buildings, power lines,and topo shots while doing most (if not all) the boundary collection in the “main” rover. This, of course, is because we can only archive and keep all the integrity of the initial LS together in the job. The data collected from a 2nd or 3rd base is absolutely reliable and very useful, especially with the process of being able to process PPK and the “recover base” process being improved, but there’s not a way, that I’m aware of, to completely merge ALL the data (screenshots, time stamps, etc)of the points collected with multiple rovers into ONE single job file to then be archived.

As of now, if I use multiple rovers on a job and want a printed job report of accuracy and precision on my completed boundary I MUST shoot all the boundary with rover would be extremely helpful if I were able to utilize rover two and three while still maintaining my ability to print out my final job reports.

Jon Gramm

I have been thinking about this one myself.

I sometimes work on projects with tens or even hundreds of thousands of points, several hundred square miles of mapping/GIS data, and a bunch of other stuff. (That last part is the technical talk.)

I can see it being possible if all of the data was stored in something like a SQLite database with hyperlink fields, and photo fields, then having the capability to export an archive file for merging with data from other units. You could append the data from each unit to the Master Database Table or Container on a daily basis, or whenever you deemed it necessary. It could be a single flat file rather than a relational database.
You could then query the final merged file based upon chronological order, code, shape tags, or any other field(s) you would like to arrange the data around, and generate a final report.

I do not know if it would be desirable to do this in an LS though. (The merging of the archives. A lot of overhead, and the process could be very time consuming.)

I would prefer a post processing/project management package on a PC to handle this. Along with the ability to export a merged file without all of the screenshots, photos, time stamps for importation back into the LS.

It could get a little heavy though if you did this on a nightly basis, which is something a fool like me would be doing.

Clay Davidson

Active Member
I think it would be nice if you could just simply export the boundary points with their gededitc data (or any other data that would need to be associated with such points) and import that file into a LS. Then check the reletive accuracy.

I just use 1 LS, but someday I may run more crews. I think this is a problem that should be addressed.