I don't have TBC here to play with, but I do have a TSC3 with Trimble Access. Can someone give me the low-down with regards to trimble coding, attributes and linework. I am quite happy with point attributes, but I'm not quite sure how Trimble handles linework with attributes.
Can I make a linework code with attributes in TBC?
Do I then use that linework code with the traditional B E, etc, linework commands?
When do you assign attributes to the line? Is it only on the first point, or do the attributes stay loaded while you're surveying that line, and update for the entire line if you change any of them?
What options are there for exporting the line to CAD/GIS software?
Sorry for the potentially vague questions. I hope to get hold of some software that can generate feature libraries so I can answer some of these myself, but till then.
I think attributes are code bases, so when you make a linework code with attributes you will be prompted for the attributes every time you use this code. (Not tested myself - but check the manual - I'll add part of it 5MB limit)
Not sure if you will have attributes when you make your library in General Survey, I think you needed TBC, at least in older versions.?ÿ
?ÿ
?ÿ
Even if you don't have TBC, you can download and use the Feature Definition Manager, which is a standalone (and still free I believe). It can be a little annoying to use, as it is due for a major update, but if you don't care too much about linetypes or CAD blocks for points (it can get pretty involved with scaling, rotation, etc.) then it is pretty quick to set up a library.
Attributes for linework are pretty much the same as for points. Select a "base" code, i.e. FNC for fence, and create attributes for it in FDM. In the field, make sure you have "Use attributes of base code" checked, and then you can string a code FNC01 or FNC02, etc. and it will prompt for the same attributes.
Line control codes are up to you; some of our offices use B for begin, others BEG. You can have multiple codes for the same control function in a feature code library.
I almost always use drop down lists for attributes as that makes it faster for the crew to click on a selection rather than type something into a blank field.
?ÿ
Data can be exported to DWG and DXF formats, up to 2018 format. Although TBC cannot create elevated curves like C3D, the 3D polylines work well for most purposes. You can also flatten them on export and just use the 2D linework.
Most anything in TBC can be exported to GIS shapefiles, or KML, etc. If you really want to get fancy, the GIS Module is pretty cool. One of the most underutilized tools in TBC. You can push data to and from a file geodatabase, and if attributes have already been defined in the GDB, you can generate a feature library that pulls those attributes from the GDB.
Thanks Christ, Rover. Some great information here. The Feature Definition Manager will be very useful.
Just returning to this query. Is it possible to assign attributes to a line, and update them as you work you way down the line feature?
E.g., could I have an attribute for "SUI", and set it to "Class-D" for the start of the line. Then, once the other end of the line has been found, set it to "Class-C", or will it simple use the attributes from the first point of the line (That seems to be the most common behaviour).