-
Trimble RTK: Import to TBC without Duplicating Vectors
I’m assisting another firm with a control project in which they’re making RTK observations using 5800 and R8 receivers and (I think) Survey Controller. They’re providing daily .job files to me, which I bring into TBC. I understand how to control point merging, but I haven’t figured out how to prevent RTK vectors from getting duplicated without individually deleting the duplicates. Any hints?
Thanks!
-
23 Replies
-
Remove ALL the vectors and replace with missing line between the merged controls as needed ?
-
jim.cox, post: 346459, member: 93 wrote: Remove ALL the vectors and replace with missing line between the merged controls as needed ?
I want to keep all the RTK vectors so I can adjust them, but I only want the original of each one — I don’t want to import the same vectors repeatedly.
-
Search these topics in the HELP:
Import Multiple File Versions
Preconfigure Options for Importing Multiple File Versions
-
LRDay, post: 346461, member: 571 wrote: Search these topics in the HELP:
Import Multiple File Versions
Preconfigure Options for Importing Multiple File Versions
I’ve read those. The Import Multiple File Versions topic states that with Preserve Office Edits, “if the same object exists in both versions of the file, the existing version of the object is the one that is saved.” But when I choose Preserve Office Edits I end up with multiple instances of the same RTK vector, one for every version of the file I import (the importer appends a dash and an increment number to the copies). I’ve monkeyed around with different merge options, and still get multiple vector copies. I’m stumped.
-
If you’re receiving job files that are started new each day, there should be any duplicates?
-
I was having the same issue with duplicate points and ended up going to Settings/Computations/Point Tolerances and changed the Merge on Import to “By Station Point”, this solved my issues and only imports new vectors. I use DC files to import new points though, that way we have a log of a digital field book and I’m able to make edits if needed, there’s no way to make edits to a job file outside of TBC.
-
Plumb Bill, post: 346489, member: 226 wrote: If you’re receiving job files that are started new each day, there should be any duplicates?
The field crews are using the same job files each day, adding more observations to them. That’s what I always do; is that unusual?
-
CJRob1693, post: 346493, member: 7671 wrote: changed the Merge on Import to “By Station Point”, this solved my issues and only imports new vectors.
That doesn’t seem to be working for me. I set “By Station Point” in the project options, and tried every variation of the merge dialog (disalbe on merge, overwrite, preserve, ask) but keep getting duplicate vectors.
-
Jim Frame, post: 346497, member: 10 wrote: The field crews are using the same job files each day, adding more observations to them. That’s what I always do; is that unusual?
It would be highly unusual to the way I work. I have the crews link the file from the previous day, this only copies in the needed control points.
This allows me to process the project as it comes together daily. If one file will contain all of the information, it is easiest to just process it once at the end of the project.
Or use project explorer and manually delete previous data. It seems to me that adding into the same file continually will always create extra work, though.
It wouldn’t be near as cumbersome for a solo operation, but as you add crews it becomes more aggravating exponentially.
-
Our typical work flow is to upload a job file and link the control / section corners, then at the end of the day we use data transfer to download the DC file (which includes the job file) into a specific folder. I should also mention that we require the crew chief to put the date and their initials on each uploaded job file, so the downloaded DC file would be NDak113015CR. This allows me to see which crew chief worked on that specific job and which day they were there. Any time we have new control I’m able to import the DC file into TBC, using the settings from above and don’t have duplicate points or vectors. I like having the the DC files because it’s our digital field book, it becomes hard to write in a physical field book when it’s -20 outside. We also use a specific point range for each crew chief and I’ll renumber any control after its been imported. Hopefully this helps, it took some trial and error for us to come up with an easier workflow for our guys.
-
Plumb Bill, post: 346500, member: 226 wrote: I have the crews link the file from the previous day, this only copies in the needed control points.
That is how we do it too. A separate file per crew per day, each day linked back to one control file for the whole job
-
I’ve had this problem but the ” Preserve Office Edits” works for me. I also always select “keep the TBC control over the use the imported file -whatever.”
There is some setting somewhere that needs to be changed I suppose. You could just delete the previous download and then download the new but then you would lose any adjustments you may have done. Seems like the more features and complexity there is in the software the more trouble it may be to use it.
Its easy to delete any previous download file in TBC. Sometimes things get sort of clogged up and I’ll do that – delete some of the imports and just reload what I need. TBC is getting like any other CAD, you need to use it a lot to keep current on how to use it. I’m actually encouraged because I think it is finally going to make me just use TBC for everything to final product and replace my TerraModel. I really like TerraModel but its in a time warp since about 2001.
I spent literally months reading the manual and testing to learn TerraModel. Sorta going to be the same with TBC except I know what it should do just need to discover the right clicks.
-
Maybe this will help.
http://surveysupport.seilerinst.com/2015/10/20/trimble-access-export-only-one-days-work/ -
makerofmaps, post: 346538, member: 9079 wrote: Maybe this will help.
http://surveysupport.seilerinst.com/2015/10/20/trimble-access-export-only-one-days-work/Alas, that technique is also aimed at the user who only wants to see coordinates.
Trimble data collection software doesn’t seem very friendly toward those who are more interested in observation data.
-
Jim Frame, post: 346560, member: 10 wrote: Alas, that technique is also aimed at the user who only wants to see coordinates.
Trimble data collection software doesn’t seem very friendly toward those who are more interested in observation data.
I see that now. Usually I don’t get the jobs until they are done with it. I wonder if using the access sync will only bring in the new stuff. We have jobs that last months and I sure don’t want to deal with daily job files.
-
Jim Frame, post: 346497, member: 10 wrote: The field crews are using the same job files each day, adding more observations to them. That’s what I always do; is that unusual?
That is exactly how we do it and have done it for a decade. Most of the time the crews will use the same .JOB file throughout the entire job (daily downloads for backup purposes) knowing that I am not going to import it until they are substantially complete while other require immediate download for a variety of purposes. Next time they go back to the job I would provide them another JOB file with the exact name which is always Job#(add a 1 or 2 here if there are multiple crews on the same job).JOB, just like we’ve always done.
When we first started using TBC and started importing files with the same names I would get the “this file has already been imported…” followed by the duplicate oberservation checklist of options. TBC seems to want you to create a new file for each day and too me that seems overly cumbersome and unneccessary and inefficient.
-
Are these “duplicate” vectors different than or the same as the old ones? If you are making edits that change the vectors perhaps you should get the crews onto your “good” control.
-
vern, post: 346698, member: 3436 wrote: Are these “duplicate” vectors different than or the same as the old ones?
They’re the same — not new observations, just the old data being imported again along with the new. I don’t understand why TBC doesn’t recognize them as duplicate and ignore them, like it does when you try to import static data more than once.
-
It works for me.
You can import from a file directory or directly from the data collector (device pane).
There may be differences in TBC versions, I’m running 3.61.
When importing from a file directory when you select the file from the list in the Import pane down at the bottom of the pane there is a Versioned files box. If it has a plus click it so it shows a minus. In the pane there you should be able to select how to handle the import of multiple data. I select ÛÏPreserve Office EditsÛ. It then only imports any data that is not already in you project. Or you can set it to ÛÏAsk me on importÛ and you will get a inquiry at import on which option you want.
When I hook directly to the data collector the Versioned files box isn’t there but at import it asks me what I want to do.
Again, It works for me!
-
LRDay, post: 346711, member: 571 wrote: . I select ÛÏPreserve Office EditsÛ. It then only imports any data that is not already in you project.
I can get this to work with points, but not with vectors. Do you store the QC data? That’s the stuff I’m interested in, but every time I import the file I get another copy of all the vectors I’ve already imported. When I open the Properties pane and click on a vector, I get choices like 115112, 115112-1, 115112-3, etc., each representing a copy of the same vector. That wouldn’t be a problem in itself, but when I export to an .asc file for import into Star*Net, the duplicated vectors all come over as independent observations, which they’re not.
Log in to reply.