If it's between different TBC installations then "VCL Project Link Exporter" is the one to use. It's at the very bottom on the "Construction" Tab of the exporter.
That will automatically include all dependencies into the export. I.e. you only select a corridor surface, it'll include the alignments, string lines, templates that have been used to create/define it.
We also use it to import auto-drafted underground service pickups (points with attributes, symbols, linework) from the actual day job TBC project into one big master project.
The only thing to be aware of is that it is just one single file, it doesn't bring across data attached files like georeferenced images, scan data, PDF, Photos attached to a point. It will bring over the Link to the original file, but if the 2nd TBC machine doesn't have access to that source you only have an empty frame.
You'd have to test, it seems to be a bit different with each image type.
Photos attached to a point i.e. are copied into a subfolder of the 1st TBC Project and then only a relative link into that Subfolder is kept. If you get those points via VCL into the 2nd TBC project this relative link is transferred. The 2nd TBC project then tries to find them in it's own subfolder. I wrote us a macro that is replacing this relative link with an absolute link to the original file location in the day job folder on our server. Since we all have access to this location the images are always viewable, no matter how often we "VCL"
With georeferenced images it seems to be different. If the 2nd TBC project has access to the original source file, it will copy it from there into its subfolder.
------------------------------
Ronny Schneider
------------------------------
Original Message:
Sent: 09-21-2021 07:22
From: Julius Newman
Subject: TBC Import Export
Hi, we're looking for some assistance / thoughts on a relatively simple process.
What's the best format for exporting data from TBC to another user with TBC such that all of the attributes are maintained in the process.
I understand that this may be dependent on the workflow and the discipline and therefore not a one solution fits all scenario. i.e. survey data / civils setout / modelling surfaces / cad / tables, etc.
I note earlier comments on various threads in regard to landXML and loss of texture, etc. Obviously CAD is an attribute killer. IFC can be ok, but you can lose faces, etc on 3d surfacing.
A default TBC (Ascii) type exporter could be handy here.
Kind regards,
Julius
------------------------------
Julius Newman
------------------------------