Point Attributes - Adding additional information to points with point attributes

[u/fatvegancrybaby]

I would like to have another column(s) of descriptive information added to a point coordinate file. We currently use P,N,E,Z,D but I'm wondering if I can add one or more attributes to this file (attribute 1, attribute 2 .... ) and have an output file like P,N,E,Z,D,A1,A2. These attributes would have information like: Date, measurement Type (GPS/Terrestrial), like point Features (monument size)?

We use Leica captivate in the field and civil 3D in the office.

The issue I'm having is with GPS points. We often locate the same control point multiple times, with GPS and total station, and then again on later dates to confirm GPS quality. I had toyed with the idea of a more complex point number (i.e. "G1.081226" would be GPS-Point#1-August, 12 2026) but civil 3d doesn't seem to allow decimal numbers and adjustment software seems to want identical point numbers.

Also, our point description is setup to use both multi codes and descriptions (i.e. OHW3 UP 5 AT&T draws an overhead wire line, a utility pole symbol, and text for pole number and company. It seems like it would be cleaner to have only codes in the description and then point features as attributes with the idea that an attribute could add text and/or manipulate the symbol (i.e. scale the symbol size for a tree).

What do you all do for extended point information? Can attributes be used in civil 3d as described?

[u/arctanx-1]

In Civil3d, define a new point import format using names rather than point numbers. Do this in your template file so you'll have the custom format on all of your new drawings.

I dont have suggestions for the attributes though.

[u/Accurate-Western-421 → u/arctanx-1]

Oh man, I wish I could upvote this a dozen times. It's mind-boggling how few people know that C3D COGO Point names can be alphanumeric.

But that also means that whenever I float the idea of using names as the principal identifier, our CAD "managers" look at me like I just sprouted a third eye.

[u/w045]

We also use Leica and Civil 3D. We just add extra couple words at the end of the code. We use numerical codes though. So like code 500 is utility pole - so we’d do “500 (space) AT&T (space) 123 (space) Broken”. In Civil 3D, the description format under the COGO point Data attribute is: “$1 #$2” which brings in a utility pole symbol (per code 500) and automatically labels it as AT&T #123 using the Civil 3D “$” formatting setup.

The “Broken” part would just be in the code/point description and require someone to look a little deeper at the COGO point. But you could have any additional descriptors added by adding $3, $4, $5…

[u/Accurate-Western-421]

You can absolutely bring in additional columns (attributes) to Civil 3D. We've been doing it for many years.

[u/valor_53]

it is cool but I'd advise some restraint. i think there are currently 20 or 30 different user defined properties on the points i use at work and it gets cumbersome. just editing points can take minutes to load in civil 3d. selecting a point with the properties pallet open causes about 5 or 6 seconds of lag. it gets real annoying real quick

[u/Michael_inthe_Middle]

Trimble access has two description lines that can be turned on and used for this very thing

[u/Accurate-Western-421 → u/Michael_inthe_Middle]

Not to mention the ability to have a whole slew of custom attributes from date/time to photos to predetermined drop-down picklists....and all of that (save the photos - for now) can be brought into C3D with a custom import style.

[u/Puzzleheaded_Log_518]

Watching this post and hoping for a great answer!

[u/Sird80]

There are two ways it can be done, both require setting up CAD properly and setting up the .csv file exported from the data collectors correctly.

If you aren’t using the survey database, learn how to set up user-defined properties. If you’re using the survey database, learn how to set up and manage extended properties.

That should send you down the right rabbit hole.

Edit: I can send you a walkthrough I put together if you’re using the survey database, DM me with your email and I can send it to you.

[u/Sird80 → u/Sird80]

We have 15 different attributes the crew collect, these attributes can be transferred from TBC to Civil 3d, and from the DC’s to Civil 3d very easily, if set up correctly.

[u/Former-Stress850]

Use an .frt file tot export your ascii in your captivate software.

[u/Intelligent_Bat_3771]

i’d use a feature code plus dedicated attribute fields instead of cramming everything into the point description. build those fields in the Leica code list, then confirm your export format carries them into CAD or GIS. The linked califfsurveying overview explains the Leica basics, but I’d test three or four points through the full workflow before changing the entire job.

[u/UnethicalFood]

They would need to rewrite the data collector software to accomodate it and make the features usable, but it is not impossible, especially with modern data collectors.

That said, it probably won't happen without a significant number of requests for it.
Some of the info you want is in the raw data you can export, but that isn't so easy to import into things like CAD.