Data collection - Feature and string codes?

> How do you code your points when using a data collector?
In our system there are three broad classes of point codes. Some points are always represented by an individual symbol (manholes, catchbasins, lamp standards, etc) Those points are coded with a two or three letter description. The second group are points which are always part of a breakline or a linear feature (paint lines, gutters, edges of pavement or concrete, fences, overhead wires, etc) These points also have two or three letter codes with 1-3 digit suffixes. The third group includes random ground shots and some other rarely used codes. Typically none of these have string numbers but I will accept them and draw the linework manually if appropriate.

> Do you use an alpha or numeric description?
Years ago we used numbers, but all of the current hardware used for D/C that I can think of includes either a full hardware keyboard or an on-screen touch keypad. We switched to alphabetic descriptions quite some time ago.

> Do you include string codes with the description or use a separate field?
String numbers are required for those codes which are typically used for linework. I am importing point data into Civil3D for processing the linework, surface modeling and drafting so I must have the string number directly attached to the raw description.

Examples:
BB55 - Bottom of bank string
TB1 - Top of bank string
PV1 - Edge of pavement
PV2 - Another edge of pavement
CBS - Side inlet Catchbasin
DWY11 - Edge of Doorway
BVD - Beaver Dam
GND - Random ground point

> How do you code your points when using a data collector?
> Do you use an alpha or numeric description?
> Do you include string codes with the description or use a separate field?

Alpha descriptions that are interpreted for layer and symbol assignment. Numeric string code, if any, is appended to the alpha description. The "*" character indicates the start of the string code.

Thanks Steve amd Jim - I think I'm on the right track.
In FreeCOGO codes are accepted in the form of the examples below.
----------
1. Feature and String code combined:-

(a)Alpha code [up to 10 characters] with Suffixed string code 1-3 digit[fixed length].
Road01 (2 digit string code - must be the same length for all strung points).
TopBank01
Tree00 (00=point feature not strung - no. of digits must be the same as strung pts).
Sign00

(b)Alpha code [up to 10 characters] with Prefixed string code 1-3 digit[fixed length].
01Path (no. of digits must be the same for all strung pts).
02Toe
Tree (with prefixed codes numeric string unnecessary for point features).
Pole

2. Feature and String codes in separate fields.

Alpha code with string code [any length inc. empty] in a separate field].
Road , 4 (1 digit string code - number of digits can vary in file).
TopBank , 10 (2 digit string code)
Tree , 0 (0=point feature not strung or empty field as below).
Sign , (empty string field)

The feature codes become layers and the strings are joined in processed order.
-----------
Jim

The * separator could be used but it has a special function with Topcon D/C.
02BLD*C Close to start of Building string
01EB*AS Start of arc
01EB*AE End of arc
00TR*S4 Tree spread 4 diam
Currently these are treated as prefixed string codes with the input following becoming the layer name. They can be fixed up manually after import.
-----------

Barry Graham
Melbourne, Australia

"Do you use an alpha or numeric description?"
Alpha coding for the features, + number for the line number

"Do you include string codes with the description or use a separate field?"
Some string codes come with the description, the simple ones (ST, CL, PC, PT, ...)
Those string codes that may have numerical parameters are put in a different NOTE field. (P -0.5 -0.2 GUT = draw parallel line 0.5 m. to the left, 0.2 m lower and with a feature code Gutter)
We use the same technique for Right Turns, offsets, ...

Chr.