Code Attributes

[Jim Campi]

Gentlemen,

I am interested in using code attributes, but having a problem with implementation. When creating attributes we are presented with 2 columns and several rows, all of which are initially empty. Let's say I want to differentiate between 2 types of valves, each with 3 sizes and different materials. For example valve, gate, pvc or brass - 1, 2 or 3 inches vs valve, ball, pvc or brass - 1, 2 or 3 inches. How is this entered on the point attributes page?

Any comments or direction is appreciated.

 

[Shawn Billings]

I absolutely love building attribute tables in J-Field. Makes my life much simpler.

Your Code in this case is probably not Valve. What is the valve connected to? A water system, gas system, etc. The answer to this question will probably dictate the Code you'll want to use. Think CAD layer here. So maybe the Code is something like Water System or Gas System. Once you decide what the Code is then you'll start filling out the attributes.

The first column is the name of the attributes, such as "Object", "Type", "Size", "Condition". The second column will be the default values for these attributes. If you don't have a particular attribute that stands out as most common, I would leave these blank. If you do have one that is most prevalent, then you could go ahead and enter it. Once you start collecting points and entering attributes, the things you enter will become part of your library of attributes.

In your case I'd enter the attribute names as:
Object
Type
Size
Material

Then entry will be something like:
Object: Valve
Type: Gate
Size: 2"
Material: PVC

And you could add another attribute if you want. We limit you to 5, and then I use the description as a catch all comment field for things that don't fit my attributes well, "Buried 2 feet" "Lid is broken" etc.

 

[Jim Campi]

Thanks Shawn, I wasn't thinking about code attributes from a system perspective. Of course it makes much more sense when the capability exists. This will follow through to Civil3D, making point groups more efficient.

Thank you . I may have a question or two as I go through set up. My bet is that few are using this feature to it's full potential.

 

[Jim Campi]

One more point/question. Up until now I have been exporting points as space delimited. Are you using comma delimited for PNEZD and space for attributes?

 

[Shawn Billings]

Yes. Exactly. Unless you are populating a database, then use commas all the way through.

 

[Joe Paulin]

Codes and attributes are awesome - very flexible and you set it up for what you need. I used to do a lot of sewer mapping - we would have a sheet we would fill out for every manhole with all the inverts, etc. Cumbersome, messy and everything was on paper. After a while, I developed a code/attribute system in the DC for this eliminating the paperwork, it was great. Now I do mostly boundary with the LS and I have codes and attributes for monuments, fence, etc. You can quickly store a lot more info compared to using descriptions.