Does TBC have an option to concatenate feature attributes? Trying to create a single feature description based on multiple attributes.
If this is for the visualization within TBC, you may design a point label style so all the attributes will be labeled in one line.
If this is for export, you could use the Export Format Editor to define a proper format:
If these are not the scenarios you're looking for, let me know. Thank you.
Thank you for your quick response. We use these features currently and they are great!
We are looking to concatenate the values of SIZE_IN, OWNER and COVER_FT to read as “10 ABC123 2.3” into a blank attribute line. The goal is export shapefiles or a CAD drawing with the newly created blank attribute line.
Interesting workflow. I haven't seen it before and I'm not aware of an easy way to change our current exporter settings for SHP or CAD. Just curious, why would you like to have all attributes joined in one line instead of having them separated?
It streamlines our workflow to produce deliverables. Combining feature attribution at the source omits this process downstream for CAD and/or ArcGIS users.
I'm not sure if it is a TBC Exporter or AutoCAD limitation that when Exporting to DWG with the "Export point as Point Block" & "Export attributes" Options enabled - only POINT_NUMBER, DESCRIPTION (CODE) & ELEVATION are passed through to the Point Block Attributes - none of the Attributes are passed though to the exported DWG.
Point Descriptions has this same problem too of not passing through to DWGs.
The more data we can pass through on these Exports to DWG (attributes and/or descriptions please) I'd suggest would greatly enhance many workflows & end user deliverables to our clients.
Can Trimble investigate if this is a TBC or AutoCAD limitation?
When we export DWG including attributes, the attributes come from the feature code will be exported and can be viewed in C3D Properties -> Extended Data.
However, the point description 1 and description 2 fields are not considered attributes and they will not be exported. If this is the problem you're referring to, the workaround would be to define a "description" attribute field in your feature code. Could you give it a try and let me know?
Retrieving data ...