Good day, welcome back to another TBC Tip of the Week! In this weeks tip, we will look into how TBC handles the drag and drop importing of files. Do you use it already? Did you know you can often skip the import pane all together? Let’s look into how this works and how to tell that dragging and dropping is the way to go!
When a file is imported using the Drag and Drop method, the default import settings for that file type is always used. If you know which file types you want to use the default settings for, those types can always be dragged and dropped into TBC!
With a TBC project open, I want to import a .JOB file from Trimble Access. I will first check the import for .JOB files to see what settings exist for these files. Select Import from the Quick Access Toolbar.
In the Import command, select the ellipses and browse for the folder containing the files you wish to import.
Below I have examples of a .JOB Trimble Access file, a .T02 GNSS observation file, and a .JXL jobXML file from an SX10. Clicking on each one, I can see the available settings for importing these files, and what the defaults are for those imports.
.JOB file (left), the option to merge the data contained in the file on import with other project data. Ask me on import is the default.
.T02 (middle), what type of data is this? Static or Kinematic? If you always process one type, you can force TBC to read the .T02 as that data type. Both of these can be set later in TBC.
.JXL (right), the option to merge the data contained in the file on import with other project data. Ask me on import is the default.
So! You might say “I want to be asked on import”, or “I occasionally bring in Static and Kinematic GNSS data”. Then do we have a solution for you! Instead of navigating in the pesky import pane, you likely have a File Explorer window open with your data already. Simply Drag and Drop the data into the TBC Plan view window! You can select multiple files and drag them in at once.
The order in which data is selected to import can affect project computation results, typically when points have overlapping point numbers. In the GIF above, I am prompted for a scale factor because the .JOB file I am importing was created with either a Local Site or Scale Only coordinate system.
And there we go! What did you think of this one? Let me know in the comments below.
TBC - From Field to Finish (and back!) with Confidence