Point Code reaction to description

[654work]

Is there a way to have a point code react based on the description?  As an example, using point code 200 for a manhole, if a description is applied of elec for electric or tele for telephone, can the manhole be placed on an electric layer when elec is used and on the telephone layer when tele is used.

[jae.kwon]

I feel like saying that you can use a description key set to assign layers to points based on the description but... I also feel like I'm missing something maybe.

What do you mean by "point code"? Are we talking about cogo points?

[Anonymous]

I think they're talking about survey field point codes.

I like numeric codes, too. Much easier to key in outside in the cold once you memorize them. We used to use something like 200 for generic MH, 201 for SAN, 202 for STM, 203 for TEL, 204 for ELEC, etc.If you have unique codes it'd be easy to set up the description keys.

[ChicagoLooper]

The key to doing this is consistency by those who input the points.

If one user uses Elec, another Electric, and a third uses EL, then you might, or might not, have issues because you'll need to know all variations of electric that's being used.

You could do it using the cogo point properties. Create a new point group that'll be dedicated to electric points. Next go to the new group's Properties. On the  the Include tab, you can specify that raw descriptions with Elec will be included in this point group. Description with Tele will be excluded and remain in their current point group. You may also use wild card(s) such as *Elec* which will permit the entries Electric and 101Elect to be included in the Elec group.  

Image-1 

As an alternative, you can use a numbering system such that Electric entities have Point Numbers from 1001 thru 1999 and Telephone entities are numbered from 2001 thru 2999.

Your point group inclusion criteria would now be based on the With numbers matching instead of With raw descriptions matching.  So for electric you can type in 1001-1999. For telephone, a separate group apart from Elec, you can type in 2001-2999. You don't need to have exactly 999 individual entities. As long as the Point Number falls within the range specified, it'll be included.

[jae.kwon]

Oh ok, so that would be a description key set...

code   format   layer

201    SAN      V-NODE-SAN

202    STM      V-NODE-STM

...

And if you wanted to "translate" a point file from number description to letter/word descriptions you would just create a point file format that's PNEZF (where F is full description instead of raw description) and use that file format to export to point file.

[cwr-pae]

Its generally easier to use the description keys to change a code (raw description) to full description (description format) and more versatile by using parameters following the code for scaling, rotation, etc.

[654work]

I’ll attempt to explain this a little better.  The survey crew collects data based on PNEZD, with a note.  We import the survey file and use the description keys to assign the layers.  I was wondering if there is a way to use the note from the field file to force the point to a layer, as opposed to the Code.  In the example, the survey field code is 200 for manhole.  The crew enters 200 for the D with a note of elec or tele (see below using a PNEZD format), can the note be used to designate the layer, instead of the point code?

1,700603.09,2363832.793,566.049,200,ELEC

2,700821.494,2363687.927,564.463,200,TELE

[cwr-pae]

If you enter the text as part of the code (no comma; 200 elec or 200elec) you can specify that code 200 elec or 200elec be placed on the desired layer. Note that descriptions are not case sensitive. You can use both for different cases and have each on its on layer.

[rl_jackson]

The format your using is actually PNEZDA where A is an attribute (You can have as many values of A as you want A1 A2 A3 etc....) But the D is what tells C3D what layer to place the Point Block on subordinate to how the Point style is set up. I have separate codes for each type of manhole SMH DMH EMH TMH WMH etc.... and each code goes on it's respective utility layer. As previously suggested you would be better suited to have different numeric codes for each type to achieve the similar results as I do above.\

NOTE: The Attribute code can be set up to be used and consumed by using a User-Defined Property Classification.

[jae.kwon]

I made a Dynamo script for you that you can try.

Run it with the Dynamo player. Use the file browser to select a CSV file that has the format PNEZDn (comma delimited, n=note) and run it. It should import the points and assign each point according to the note. The point format was based on the sample that you posted earlier:

1,700603.09,2363832.793,566.049,200,ELEC
2,700821.494,2363687.927,564.463,200,TELE

[jae.kwon]

oops, that was supposed to say "It should import the points and assign each point *a layer* according to the note"