Notifications
Clear all

Trimble Access: Linked vs Importing a file in a Job

5 Posts
4 Users
0 Reactions
1 Views
(@gisjoel)
Posts: 234
Registered
Topic starter
 

Hello,
After searching on previous questions and opinions of linking files, https://surveyorconnect.com/community/threads/im-in-access-hell.307237/#post-307608 I want an opinion of which method I should be using in my workflow.

After my last TBC class the instructor preferred importing files. Previously, others suggested linking files was the way to go. I understand that Linked files cannot be edited (like a TerraSync backround file), but importing allows editing (like a TerraSync IMP data file). The analogy with linked files in Access blurs with TerraSync since more than coordinate files can be linked to a job. That's pretty cool.

I want CAD/Imagery as backgrounds in Access and control files that I can navigate too. Sounds like I want only linked files? I also have ologists that don't use this everyday, so simple is better.

Thanks in advance

Joel

 
Posted : April 17, 2017 9:40 pm
(@lee-d)
Posts: 2382
Registered
 

CAD and/or imagery as a background isn't the same as a linked file; linked files are JOB or ASCII files that you want to have access to the points from but don't want to necessarily import. CAD and imagery files are loaded as background maps.

The main reason for linking a file rather than importing it is that when you link it only the points that you actually use get brought into the job file. I usually just import control; where I would link a file might be if I was given an ASCII file with hundreds or thousands of points in it and only needed to actually use a percentage of them.

By the way, TSC3s and ESPECIALLY TSC2s don't have the horsepower to contend with large CAD or imagery files. I tell our PMs to keep DXF files under 1MB.

 
Posted : April 18, 2017 4:48 am
(@christ-lambrecht)
Posts: 1394
Registered
 

We only use linking. Be aware that linked does not always mean the linked data is always used. By used I mean copied into job.
When you key in the name of the linked point for a station setup or backsight the point is automatically copied into the job. You can verify bij tapping CTRL-R or Review Job.
When you are in Topo mode shooting Topo points you will just record the newly shot point and no data is copied. To avoid this, after linking we copy all linked points in the new job by selecting all points in the map view and calculating the area (compute + subdivide area option) that way all points are copied in the job. There is probably a more elagant way of doing this ...

 
Posted : April 18, 2017 10:29 am
(@squowse)
Posts: 1004
Registered
 

Lee D, post: 424053, member: 7971 wrote: CAD and/or imagery as a background isn't the same as a linked file; linked files are JOB or ASCII files that you want to have access to the points from but don't want to necessarily import. CAD and imagery files are loaded as background maps.

The main reason for linking a file rather than importing it is that when you link it only the points that you actually use get brought into the job file. I usually just import control; where I would link a file might be if I was given an ASCII file with hundreds or thousands of points in it and only needed to actually use a percentage of them.

By the way, TSC3s and ESPECIALLY TSC2s don't have the horsepower to contend with large CAD or imagery files. I tell our PMs to keep DXF files under 1MB.

Linked files are similar to CAD files in that you can see them on the map, but the data is only imported to the job when you use it.

 
Posted : April 19, 2017 1:05 am
(@gisjoel)
Posts: 234
Registered
Topic starter
 

Thanks Squowse, Lee D and Christ,

I'm back to relying on Linked files per this discussion.

Linking files inside my jobs is the way to go for me.

thanks.

 
Posted : April 19, 2017 7:28 pm