Cases for New Field Codes

WV

Agree with Brad and apply K.I.S.S. why complicate things. You may never use the unique code again.

Code should be WV, use notes (or attributes) to add more of a description if needed.

?ÿ

We have two codes for unlisted features or lines.

• Def?ÿ (Default point code, then use the note to describe the point feature)
• Strng (Default line string code, then use note at first point to describe the line feature)

?ÿ

Thingamabob

Posted by: @leegreen

You may never use the unique code again.

True. It's all related to a potable water system, so WV will suffice. The survey won't be used by engineers to redesign the system, so there's no need to be more specific.

@holy-cow?ÿ

I prefer thingamajigger.

In my field coding system I have a "miscellaneous waterline feature" code for such things. And similar codes for all other types of utilities. I'd expect a detailed booked description to accompany the use of these codes. Nowadays there may be no book, so perhaps an emailed photo might do. Or something. But some sort of follow up, for sure.

Concerning cases for field codes, I've found Pelican cases (indestructible) best for small amounts of field codes; they come in a myriad of sizes but are expensive.?ÿ If your field codes are temperature sensitive Yeti makes sturdy insulated top load containers but are bulky and only hold a few hundred.?ÿ If you're really bulked up with thousands of field codes with 3 level deep subcodes, etc., most of which you'll never use, a river rafting dry bag will hold them and it's as big as a garbage can.

It becomes inscrutable for the field party if there's more than a hundred or so codes so the KISS principal should apply.

????

Well said.

@Field_dog please read between the lines of what Mike Mark said.

BTW?ÿ Field dog I will be coming to Orlando in February to provide traing to some contractors and surveyors in your area.?ÿ

WV and note in field book

Posted by: @leegreen

BTW?ÿ Field dog I will be coming to Orlando in February to provide traing to some contractors and surveyors in your area.

Thank you for the information!

My problem is I sometimes come across an unusual situation, make up a code which seems logical, and that evening I'll have no idea what "bglbyfnc" means. I can't be the only one.

I would agree with FD on the whole coloring outside the lines deal.?ÿ Spending an extra twenty seconds spelling out 'Gate Valve 20" - Water'?ÿ for a unique feature that will probably happen only once or twice, makes sense.

?ÿ

My codes all have an attribute for additional notes.?ÿ Even better, I can take a photo with the CS20 & it will attach the point number to the image name.?ÿ The image is then Xrefed into the resulting CAD file so the engineers get to figure out what the hell it is.

Code it as a "normal" feature and add an attribute note. Then IF it needs to be a separate new feature change it, otherwise it is still coded as something intelligent.

Our biggest annoyance are clients who insist on using combinations of letters which generally accepted to mean a specific feature by the industry in general as something else. Causes no end of confusion in the field if you have to remember what coding system you are using on any particular day.

Our "solution" - created by lethargy rather than intellectual brilliance - has been to continue using the numeric codes we first started with back in the 1980s (note to youngsters - keyboards then only had 0-9, On/Off, measure!) and have a small office programme which automatically converts those numbers to client specific alphanumerics. It has the added field advantage that you only have to press ten keys, rather than 26.

The original system had codes 1-30 to cover the basic features back then, arranged in a logical order to aid memory (started at 1 for spot, 2 for strung spots, etc up to 30 for building). We increased those using multiple batches of 30, so that a feature in each batch was similar (28 was a wood rail fence, 58 became wire fence, 88 became a palisade or boarded fence), but you still really only needed to remember the first 30, the rest followed the pattern. Stick a minus "-" in front and the two points make a rectangle (cover, small building, large gatepost).

Not really too much work in learning and it's stood the test of time, nearly 40 years. Most importantly, if we dig anything out of archive from any date the codes are instantly understandable, no trying to remember when the letter codes were changed.

Yes, as others are saying, when I add a slash-space ƒ??/ ƒ?? after any of my codes, Carlson then appends the descriptor in my dwg file. ?ÿFor example if my field code is:

WV/ NEAT COOL

Then the dwg draws a water valve symbol and the point descriptor says:

WV NEAT COOL

Used to work with a guy that liked "BFMT" - big ******** maple tree. You get the picture.?ÿ