This command turns data collector field notes into a final AutoCAD drawing by matching the descriptions of the field points with user-defined codes. The points are brought into the drawing with attributes defined by the code, including the layer, symbol, size and linetype. Draw Field to Finish also uses an improved coding method.
Two files are used in Draw Field to Finish - a coordinate file and a field code definition file. The coordinate file consists of x,y,z points with text description fields. The description fields contain codes for the Draw Field to Finish processing. The coordinate file can be a Carlson coordinate (.CRD) file, C&G CRD file, C&G CGC file, Land Desktop MDB file or Simplicity Systems ZAK file. An ASCII data file can be converted into a coordinate file using the Import Text/ASCII File command. The field code definition file defines the layer, symbol, size and other actions to apply with each code. These file names are displayed at the top line of the Draw Field to Finish dialog box.
Draw Field to Finish can translate the field points into Carlson points (also called coordinate geometry points or cogo points) with a symbol, layer, and size defined by the code. The point settings of whether to label the description, point number, and elevation and whether to locate the point at zero or at the real Z can be found in the Additional Draw Options of the Draw Field to Finish dialog box. The Draw-Locate Points command has these point settings stored separately in the Point Defaults menu. Draw-Locate Points provides a simpler method for drawing points compared with Draw Field to Finish.
There are two different methods for connecting linework. One method creates line work by connecting points with the same code. The linetype is defined by the code as either points only (no line work), lines, 2D polylines, both 2D and 3D polylines, or 3D polylines (breaklines). Distinct lines with the same code are defined by adding a group number to the end of the code name in the data file. With this method, all points with the description CODE1 will be one line while points with CODE2 will be another line. Both CODE1 and CODE2 use the definition for CODE. For example, the code EP could be a code for edge of pavement that is to be connected as 3D polylines. If there are two separate edge of pavement lines on the left and right sides of a road, all the points for the left side could have the description EP1 and the points on the right side could be EP2.
The second method is the PointCAD format. This method also connects points with the same code. The difference is that instead of using a number after the code for distinct lines, you use the same code with an additional code for starting and ending the line. For example, +0 is used to start a line and -0 to end. So the coding for a segment of edge of pavement could be EP+0, EP, EP, EP-0. Another special code that has been added to Field to Finish is +7, -7. This 7 code will use the linetype definition of line, 2D polyline or 3D polyline defined by the Draw Field to Finish code. For example, if EP is defined as a 3D polyline, then the coding EP+7, EP, EP, EP-7 will create a 3D polyline. Otherwise codes like +0, -0, which is defined as start and end line, will draw EP as a line. Other PointCAD special codes are: +4 starts a curved 2D polyline, *4 starts a closed curved 2D polyline, +1 begins a 3-point arc, +5 starts a 3D polyline, *5 starts a closed 3D polyline, +6 starts a 2D polyline, *6 starts a closed 2D polyline, +7 starts a line whose type is specified by the field code definition, -05 starts a curved 3D polyline section, -50 ends that section, +8 starts a 2D and 3D polyline combination, *8 starts a closed 2D and 3D polyline combination, -08 starts a 2D and 3D polyline combination curved section, -80 ends that section. //, followed by a field code, concatenates that field code's description on to the point's description. For example, OAK//04 might become LIVE OAK TREE 4" if the field code OAK translates to LIVE OAK TREE and the field code 04 translates to 4".
The advantage to the PointCAD method is that you don't have to keep
track of line numbers.
For example, if you are surveying 50 curb lines, the first method would
require you to use 50
distinct curb numbers. The advantage to the first method is that you
don't have to use the start and
end codes. Also the Nearest Found connection option applies to the
Range of Points: Specify the range of points to draw.
Point Group: Specify
the point group(s) to process.
Entities To Draw: The Points option
only the points and point attributes. The Lines option
draws only the linework and the Symbols draws only the symbols. Any
combination of these options can be processed as well as individual
processing of each entity.
Point Label Settings: Specify whether you want Draw Field to Finish to label the Point Numbers, Descriptions, and/or Points Notes which are contained in the note (.NOT) file that is associated with the coordinate (.CRD) file.
Elev Label Settings: Specify the elevation labeling options.
The Label Zeros option will
label the elevations of points with z=0. Use Parentheses will
parenthesis around the
elevation text. Use '+' and Use '-' will place the appropriate
symbol in front of the elevation.
Locate Points on Real Z Axis: Choose between locating all the points at real Z elevation, all at zero elevation or to use the real Z setting as defined in the individual codes.
PC-PT Curve Type: Sets the method for drawing curves with more than 3 points. The Bezier option draws a smooth polyline through all the curve points. The Tangent Arcs method draws multiple arcs with arc end points at each of the curve points. These arcs are tangent to the preceding line segment.
Layer Prefix: Optional layer prefix added to all entities drawn with Draw Field to Finish.
Erase Existing Draw Field to Finish Entities: When checked,
option will erase from the
drawing any old entities created by previous Field-To-Finish runs
drawing the new entities.
In Range: This option
only erases and redraws those Draw Field to Finish entities that are
the specified range of points to process.
Creating Point Groups: Point
Groups can be created in one or two different ways. Each field code
definition can specify a Point Group that all point numbers that use
that code will be added to. Multiple field codes can use the same Point
Group name. Check the By Code Definition checkbox for that option. The
second method is to automatically create Point Groups for each code
that is processed. Check the Automatically By Code checkbox for that
option. Ignore Code Suffix, if checked, will cause the codes to be
considered after removing the numeric suffix. For example, points with
the EP10 and EP11 codes will both be automatically added to the Point
Group named EP. No matter how the Point Group is created, the Group
Name Prefix can be used to add a prefix to the group name. Note: if the
Point Group already exists, it will be erased first before being
created again by either of these two methods.
Pause on Undefined Codes: When checked, Draw Field to Finish will pause if it encounters a description that is not defined in the code table.
Abort without drawing anything: This stops the command. Run Draw Field to Finish again to correct the code table.
Use the default settings for this point: This option draws a point in the "MISC" layer with no linework. To set your own default, define a code called "SC_DFLT".
Use default settings for all undefined codes: This option will draw all undefined codes in the "MISC" layer by default or a user specified layer as defined in the "SC_DFLT" code. A good way to check the data file for unmatched descriptions is to use the Print Table command and choose the Data Points and Distinct Code options. This command will print the different codes in the data file and identify any undefined codes.
Preview Only: When checked, this option will temporarily draw the points and linework and allow you to review it with zoom and pan.
Auto Zoom Extents: When checked, this will force a zoom extents after Draw Field to Finish is done.Report Codes/Points: This routine prints the code table or the data file to the screen, file, or printer. A useful option here is to print the data file (CRD Points) and choose Sort by Codes which will group the data points by distinct codes.
Code Table Settings: These options provide tools for defining the coding method to be used for processing of the point data. Various import tools allow for the importing of codes from different software packages. Controls for handling multiple codes are located on this dialog. All special codes can be replaced to other characters defined by the user. The special codes are listed and edited on this dialog.
Set: Choose this button to specify a new code table. The name of the current table is shown in the field to the right of this button.
Process Carlson Coding: When
checked, this option interprets and processes coordinate files based
upon the Carlson Coding method and data collection method.
Process Eagle Point Coding: When checked, coordinate files
are processed based on the Eagle Point Data
Collection method. When selected the Eagle Point Codes button
becomes available for selection and displays the following
dialog. This dialog allows for customization of the eagle point
Currently the supported designators include, "Field Code", "Point-On-Curve", "Close Line", "Line End", "Insert Description" and "Bearing Close". Also supported is the ability to recognize overwriting of descriptions just as Eagle Point does by using the space separator instead of the "Insert Description" designator. Examples of supported coding are as follows:
.TC Places a node and or line per the field code
TC Places a node and or line per the field code library.
-TC Specifies a point on a curve.
TC- Specifies a point on a curve.
..TC Stops the line.
TC! Stops the line.
.TC+ Closes the line back to the starting point.
TC+ Closes the line back to the starting point.
.TC# Typically coded on the third corner of a rectangle to close the figure with having to locate the fourth corner.
TC# Typically coded on the third corner of a rectangle to close the figure with having to locate the fourth corner.
WV.W1 Places a node as specified by the code "WV" in the field code library and then begins a line as specified by code "W" in the field code library.
.TC.EP.FL Results in three lines coming together.
TC1.TC2.TC3 Results in three lines coming together. All three lines are specified by the definition of the single code "TC" in the field code library.
TC.TC1 When used in conjunction with the "Draw Field Codes Without a Suffix as Points Only" toggle, "TC" will be recognized as the node and "TC1" will be recognized as the line so that if the code "TC" in the field code library is defined as a polyline, line or 3D polyline, duplicate lines will not be unintentionally placed when this shot only pertains to a single element. Keep in mind that all line work must have a numeric suffix when using this toggle.
TREE * OAK Result on screen would be: TREE OAK
TREE OAK * Result on screen would be: OAK TREE
TREE OAK Result on screen would be: OAK
TC1!.TC2-.VLT6# Stops "TC1", continues "TC2" as a point on a curve and closes VLT6 as a rectangle using the "Bearing Close" code.
Note: The use of the "Use Multiple Codes for Linework Only"
toggle is recommended
when using Eagle Point Coding.
Process CAiCE Coding: When
checked, coordinate files are processed based on the CAiCE Data
Collection method. Examples of supported coding are as follows:
169 is just the code 169.
145C10 is the code 145 and line #10.
169C25C is the code 169, line #25, and the point is on a curve.
172C12B is the code 172, line #12, and this point closes the line.
Multiple codes are defined by including each code in the point
description field separated by
a space. A single data point can be used in different lines by
assigning it multiple codes. For
instance, a point might be part of both a curb line and a driveway line
with a description of "CURB DRW".
Field-to-Finish uses spaces as the delimiter for multiple codes. You
should avoid spaces in
the descriptions except for where multiple codes are intended or after
the "/" character. For
example, a code for light post should not be "LGT POST" but instead
should be "LGTPOST".
There are three options for the handling of multiple codes when
encountered. The All option
will split all multiple codes and process each code based upon their
code definition. When None
is select both codes will be processed based upon their code
definition. If the Prompt option
is checked on, when
Field-to-Finish detects multiple codes on a point the following dialog
will be displayed with options for handling the codes.
Import Land Desktop Desc Key: This
option imports and converts a Land Desktop Description Key
into a Carlson Draw Field to Finish (fld) code definition file. The
Desktop Description Key file is a mdb file and is found in the
Land Desktop Project file path. It is located in the under the
Import TDS Codes: This
option imports TDS codes into the Carlson Draw Field to Finish (fld)
Draw Field Codes Without a Suffix
as Points Only: This option is useful for when wanting to
use a field code sometimes for linework and sometimes for just points
but it is preferred to number the lines rather than using start and
stop codes. For example, if the field code EP is defined to use
the Line Entity type, then EP25 will be drawn as a Line, however if
just EP is used, no linework will connect to that COGO point.
Use Multiple Codes for Linework Only: When checked, and
multiple codes are detected,
only linework will be drawn for the secondary codes. Points are only
created based on the
primary code. If you want symbols for all multiple codes, then this
setting should not be checked.
Max Delta-Height for Linework: Use this option to specify the maximum elevation difference that Draw Field to Finish should draw any section of linework. This option is for use with 3d polylines and lines.
Max Length for Linework: Specify the maximum length that Draw
Field to Finish should draw
any section of linework.
Special Codes: This section allows you to substitute the
existing predefined special codes and characters with your own. Draw
Field to Finish recognizes several special codes. A special
code is placed before or after the
regular code with a space separating the code and special code.
Here is a listing of the
default special codes and characters.
The characters (*, -, +, /, and _) can be used and substituted in
Draw Field to Finish. The way these characters are used is that when
the file is processed the description field is searched for these
characters. If the "+" symbol was changed to "-" then the program
would look for "-" and change it to "+". This is useful when a
particular data collector may not have all the symbols available. With
these substitutions you can make a character that is provided on
data collector generate the symbol needed. Multiple characters
can also be used. For example "--" can be used to in order to
produce a "/" character or any of the characters listed above.
Carlson points in the
drawing have point attributes including a
Field-to-Finish draws the points, the point description from the
coordinate file is processed to match a code.
The code then defines the description that is drawn with the point. For
example, consider a code of
"UP" with a description of "POLE" and a data point with the description
"UP". The data point
description "UP" would be matched with the code "UP" and the point
would end up being drawn with
the description "POLE". A special character "/" (the forward slash or
divide key) can be
used for an
unprocessed description to append. Everything after the "/" is added
directly to the point description and
is not considered a code and no further substitution is done on it. For
example, a data point with the
description "UP / 150" with the same
code "UP" definition above would be drawn with the description "POLE
This special code causes text after the "//" to be interpreted
as a field code. That field code's description is then appended to the
first field code's description. For example, if the field code 02 has
the description 2" and the
field code OAK has the description oak
tree, then 02//OAK will result in the point
having the description of 2" oak tree.
If the "/" character has been replaced with a different
character, for example with a & character, then the "//" code would
This code begins a three point arc or a curved line when used with the "PT" code (see below). The point with this special code is the first point on the arc. The next point with the code is considered a point on the arc, and third point with the code is the arc endpoint. For example (in point number, X, Y, Z, description format),
10, 500, 500, 0, EP PC - start curve
11, 525, 527, 0, EP - second point on curve
12, 531, 533, 0, EP - end point of curve
This is a special code that can be used with "PC" to define a curve
with more than three
points or a tangent two-point curve. Starting at the point with the
"PC", the program will look for
a "PT". If the "PT" is found,
all the points between the "PC" and "PT" are used for the curve which
is drawn as a
smoothed polyline that passes through all points and only curves the
polyline between points. If no
"PT" is found, then the regular three point arc is applied as explained
above. If no points are found between the "PC" and "PT", then the point
prior to the "PC" and the point after the "PT" are used to create
tangents for the resulting curve.
This code forces the lines drawn between a series of points with the same code to close back to the first point with the same code. For example, shots 1-4 all have the BLD description with the exception of point 4. Its description is BLD CLO. This will force the linework drawn for the BLD code to close back to point 1 which is the first point with the description of BLD.
This code represents no elevation. A point with this special code is located at zero elevation.
This code indicates that the point should be "non-surface"; that is,
that it should be ignored when contouring or creating surfaces. This
can also be controlled per-field code by turning on the Non-Surface
toggle in the Edit Field Code Definition dialog box.
OH & OV
The codes "OH" and "OV" stand for offset horizontal and offset vertical. These offset codes apply to 2D and 3D polylines. A single set of offset codes can be used to offset the polyline a set amount. For example,
10, 500, 500, 100, EP OH2.5 OV-.5
11, 525, 527, 101, EP
12, 531, 533, 103, EP
This would create a polyline connecting points 10,11 and 12 and an offset polyline with a 2.5 horizontal and -0.5 vertical offset. The direction of the horizontal offset is determined by the direction of the polyline. A positive horizontal offset goes right from the polyline direction and a negative goes left. The horizontal and vertical offset amounts apply starting at the point with the offset codes until a new offset code or the end of the polyline. Only one horizontal and vertical offset can be applied to 2D polylines. For 3D polylines, multiple offset codes can be used to make a variable offset. For example,
10, 500, 500, 100, EP OH2.5 OV-.5
11, 525, 527, 101, EP OH5.5 OV-.75
12, 531, 533, 103, EP OH7.5
This would offset the first point horizontal 2.5 and vertical -0.5, the second point horizontal 5.5 and vertical -0.75 and the third point horizontal 7.5 and vertical -0.75.
This code is used to set a different symbol size. The value of the new symbol size is specified after the SZ (example SZ0.2). This value is a size scaler that is multiplied by the current drawing scale to determine the actual drawn size. For example, a drawing scale of 50 and a symbol size scaler of 0.2 would make the drawn symbol size 10. Two dimensional scales can be accomplished by using an `X' between the horizontal and vertical scales (e.g., "SZ0.2X3.5"). If no number follows the SZ special code, then the next point with the same field code as the current point will be used to determine the scale factor.
This code is used to set the rotation of the point symbol. If a point number follows the ROT code, then angle from the current point to this point number is used for the rotation. For example, "ROT45" would rotate the symbol towards point number 45. If there is no point number after the ROT code, then the rotation point is the next point number with the same code as the current point. ROT can also be used to rotate towards an angle clockwise from north by using `+' or `-' in front of the number. For example ROT+45 rotates the point symbol to the northeast and ROT-90 rotates the point symbol to the west.
This code is used to smooth the polyline.
AZI & DIST
The AZI and DIST codes are used together to locate an offset point. The AZI sets the offset azimuth and DIST sets the distance. The values should directly follow the code. For example, AZI25 DIST4.2 would draw the point offset 4.2 at an azimuth of 25 degrees.
The "JOG" special code allows for additional points to be inserted into the line work at perpendicular or straight offsets. Only offsets should follow the JOG code. Positive numbers indicate a jog to the right and negative numbers indicate a jog to the left. Alternatively, "R#" and "L#" can be used where # is the distance to either the right or the left. Finally, "S#" can be used to make an offset straight ahead by using a positive # or behind by using a negative #. For example, "BLDG JOG S10.1 R5 L12.2 L5 L12.2" or equivalently "BLDG JOG S10.1 5 -12.2 -5 -12.2" advances 10.1 units and then draws a closed rectangle on the right hand side of an existing line. The offsets are always done in the X-Y plane. If the current line is vertical, an offset to the right is along the positive X-axis.
The "JPN" (Join to Point Name) special code joins to the point named immediately after the code. For example, "JPN205" causes a line to be drawn from the current point to the point "205".
The "RECT" special code causes a rectangle to be formed on a 2D or
using one of two different methods. If a number follows "RECT" (e.g.,
rectangle will be drawn 10 units to the right of the last two points
ending on the point with
the "RECT" code. Use a negative offset to place the rectangle on the
left side (e.g.,
"RECT-2.5"). For example if locating the left side of a 10'
rectangular concrete pad using the code conc for concrete, the
description of the two left points would be (conc) for the first point
and (conc rect10) for the second. If no number follows "RECT",
then the polyline will be
closed by shooting
right angles from the first point of the polyline and the current point
and creating a new
point where those two lines cross. This method requires three
points be established on the pad.
The "CIR" special code stops the linework on the previous point and
causes this point to create a circle in one of three different ways.
The first way uses just the current point as the center with the CIR
special code followed immediately by the radius. For example "CIR5.0"
will create a circle centered on this point with radius 5 and at the
elevation of the current point. The second method uses two points, the
first point specifying the center and the elevation, and the second
point specifying the radius. The third method uses 3 points that
specify the perimeter of the circle in 2D with the first point
elevation. The "CIR" code can be used with all of the linetypes
including "points only". The circles are always parallel to the X-Y
For Multi-Point 2ND Code
When used on the first point of a multi-point symbol, the "2ND" code indicates that the second point of the sequence (i.e., the next point after the current one) should be used as the second symbol insertion point for a multi-point symbol. Please refer to Symbol Pts in the Edit Field Code Definition section below.
For Multi-Point 3RD Code
When used on the first point of a multi-point symbol, the "3RD"
code indicates that the third point of the sequence should be used as
the third symbol symbol insertion point. The "3RD" code should be used
with the "2ND" code. Please
refer to Symbol Pts in the Edit Field Code Definition section
3D Special Codes
Below are the special codes that can be used for
the easy creation of 3D surfaces. The resulting AutoCAD 3D face
entities can be viewed in the Carlson 3D viewer by entering "cube" on
the command line.
Makes a triangle mesh of 3D face entities by triangulating points starting with the current point and continuing until the line ends or another 3D special code is found. The points must be ordered along the perimeter. Although the mesh will be built if the points are clockwise or counterclockwise along the perimeter, the visible side in the Carlson 3D viewer, "cube", is the clockwise side by default. On the Advanced tab, the shading mode may be set to Shade both or Shade back if you would prefer to see both sides or just the counter-clockwise side.
Makes an exclusion area within the triangle mesh
identified by the point number following this code (e.g., “HOLE3D101”
will start a hole in point # 101). If no point number is given
(“HOLE3D”), the exclusion area is applied to the last mesh or if there
is a mesh in the process of being constructed by the current sequence
of points, it is ended and the hole is applied to it. Note that a hole
can only be applied to a mesh that was created by FACE3D (not BLOCK3D
or WALL3D). Note also that it can be difficult to predict what the
“last mesh” was if it used a different field code since the points of
the coordinate file are processed by order of field code first and then
point number. There is no limit to how many holes can be applied to a
FACE3D mesh. The points of the hole itself are not added to the FACE3D
mesh; they are projected on to the best plane that contains the FACE3D
mesh and then the hole is cut-out.
2500 HOUSE1 FACE3D /front of house
2505 VENT1 HOLE3D2500 /applies 2505-2508 as a hole to last mesh that uses point #2500. So any point in the range 2500-2504 would have the same effect.
2500 HOUSE1 FACE3D /front of house
2505 HOUSE1 HOLE3D /stops the above mesh and applies 2505-2508 as a hole
2500 HOUSE1 FACE3D /front of house
2505 WINDOW1 FACE3D HOLE3D2503 /applies 2505-2508 as a hole to above mesh 2500-2504 and starts a new mesh using the WINDOW field code.
Example 4 (same result as Example 3):
2500 HOUSE1 FACE3D /front of house
2505 WINDOW1 FACE3D /starts a new mesh using the WINDOW field code.
2508 WINDOW1 HOLE3D2504 /makes the mesh 2505-2508 also be a hole in the mesh 2500-2504.
Makes a set of 3D faces to make a 3d block using the height value entered after the code (e.g., “BLOCK3D2.3” with height 2.3). Heights can be positive or negative. With 3 points, makes a parallelogram base that is extruded up (or down if height is negative) to form a 6-sided block, including top and bottom. With 4 or more points, makes a closed polygon for the base that is then extruded by the height. The points can be laid out in clockwise or counterclockwise order around the perimeter. The perimeter or base does not have to be a convex polygon.
Makes a set of 3D faces above the polyline using a height value
entered after the code (e.g., “WALL3D2.3” with height 2.3). The
height can be negative if the points on the top of the wall have been
shot. If no parameter exists, then the height is determined by the
distance from the current point to the next point. This is a signed
distance so the surveyor can shoot either the top of the wall or the
bottom of the wall. Both sides of the wall will have triangles and so
both sides will always be visible in the Carlson 3D viewer “cube”.
Example 5 -- 6' high wall shot along the bottom:
1000.000 1060.000 100.000 WALL1
WALL3D6.0 /wall 6'
2001 1100.000 1060.000 100.000 WALL1
2002 1100.000 1160.000 100.000 WALL1
Example 6 -- 6' high wall, height specified by 1st to 2nd point,
shot along the top:
1100.000 1160.000 100.000 WALL2
WALL3D /height by 2nd pt
2021 1100.000 1160.000 106.000 WALL2
2022 1000.000 1160.000 106.000 WALL2
Code Table (continued)
Sort Table - This sorts the code table by either code name
Report Codes/Points - This routine prints the code table or the data file to the screen, file, or printer. A useful option here is to print the data file (CRD Points) and choose Sort by Codes which will group the data points by distinct codes.
Code Table by CRD - This command will create code table definitions based on the coordinate file field descriptions. This is useful when creating a code table from scratch.
Save: Saves the Draw Field to Finish field code definition (.FLD) file.
Save As: Reacts the same as Save but allows for specification of file name and location to save to.
Edit: If only one field code is selected, then this command
opens the Edit Field Code Definition
dialog box. If multiple field codes are selected (by holding down the
control key or shift key and clicking on the rows), then the Multiple
Set dialog box will open.
Field-to-Finish will layerize the points and linework according to the code definitions. If the layers to use are not already defined, Field-to-Finish will create the necessary layers and assign different colors. To have the same colors for these layers in all your drawings, define the layers in the prototype drawing. The prototype drawing is the default drawing that is loaded whenever a new drawing is created. To define layers in the prototype drawing, save your current drawing and then start a new drawing with the New command. Don't give the new drawing a name, just click OK. Then define the layers as desired with the Layer command. When you are done creating layers, use the Save As command and change to Drawing Template (.DWT) under Save as Type. The default drawing template that is used is named 18SCDRAW.DWT. This template name will correspond to the version of AutoCAD that is being used, for example 16SCDRAW for AutoCAD 2004 users. You can overwrite this default template or make a new drawing template. If you make a new one, you may want to edit the Carlson icon to use the new one. To edit the icon, highlight the icon with one click and then click the right mouse button. Choose Properties and then Shortcut and change the drawing template name.
Category: This is an optional field that can to used to help organize your codes. A category is not used for processing and only is useful in viewing and printing.
Processing ON: This toggle controls whether this code will be
Sequence: This specifies a sequence type code. Sequences are a way to simplify field entry of a sequence of codes. For example, a road cross-section could be SHD1 EP1 CL EP2 SHD2. Instead of entering these different descriptions, one sequence definition can store these descriptions in order. Then just the sequence code (such as RD) is used in the field. The cross-section can be shot in left to right then left right order, right to left then right to left order, or alternating left to right then right to left order. The alternating method is known as the Zorro style. The one restriction is that the shots always start from a right or left edge.
To set up a sequence, choose the Sequence toggle in the Edit Code
dialog. Then pick the
Define Code Sequence button. This brings up a dialog for entering the
sequence codes in order.
These sequence codes should be defined as normal codes somewhere else
in the Draw Field to Finish code
table (ie SHD as a 3D polyline). In the field, the one template
code is used for all the
cross-sections shots (ie RD for all the
points). Then Draw Field to Finish will substitute this template code
the sequence codes (ie substitute
RD with SHD).
Resulting points and linework showing Zorro style template
Define Code Sequence: This sets the code names that make up
Companion Codes: This
option allows different codes to connect when defined as line, polyline
or 3d polyline. For example, a main line power pole code may be
defined as PP while a service utility pole may be defined as UP. When
processing Draw Field to Finish, it may be desired to connect all PP
and UP codes together. This could be accomplished by defining a
companion for UP as PP and a companion code for PP as UP. Each
code needs to reference the other as a companion code.
Code: This is the key name that identities the code and
is matched with the field
data descriptions. It is important to note that the * character, used
in this field, is regarded as a wildcard or "match anything"
code. For example, a field code definition with the code defined
as TREE* will be used for any raw description of TREE. Raw
descriptions of TREEA, TREE12, TREE, etc. will match the TREE code
definition. This will always be the case unless there is a more
specific code is found. For example is there was a code TREEA in
the code definition file, then that code would be used instead of the
Full Name: This is an optional field that describes the code for viewing.
Layer: The point and line work for the code will be created
in this layer.
Description: This value is assigned to the point description
attribute when the point is drawn. This description can be
different than the field description. An additional
description can be added to a point by entering it after a forward
slash in the data description field.
Use Raw Description: This option turns off the Description
described above. Instead the points
will be drawn with their original unprocessed descriptions.
Dual 3D Polyline Layer:
Displays the layer that the 3d polyline will drawn on when using an
Entity Type of 3D and 2D. The layer name can be typed in this
Set 3D Layer: Sets the layer that the 3d polyline will drawn on when using an Entity Type of 3D and 2D. The layer can be selected from the list or typed in at the bottom of the dialog box.
Set Linetype: Line work can be drawn in any of the special linetypes or with the linetype for the layer ("BYLAYER"). The spacing and size of the special linetypes is determined by the AutoCAD LTSCALE system variable and by the field code settings Line Type Spacing Scaler and Line Type Text Scaler. The special linetype "hedge" is drawn with a user specified width. The special linetype "userdash" is drawn with user specified distances for the length of the dash and the length of the gap between dashes. You will be prompted for this information when you select that linetype.
Set Symbol: This is the point symbol for the code. To avoid
drawing a symbol, use the Carlson symbol named SPT0.
Symbol Pts: For each code definition, the symbol insertion points can be defined with up to three points. To define the symbol insertion points, choose the Symbol Pts button in the Edit Code Definition dialog box. By default, the symbol insertion is defined by one point at the symbol center (0,0). A one point insertion definition can be used to insert a symbol offset from the center. With a two insertion point definitions, the program will rotate and scale the symbol. For example, two insertion points can be used to insert a tree symbol to size the tree, where the first point is for the tree center and the second is for the drip line. With three insertion point definitions, the program will rotate and scale the symbol in both X and Y. For example, three points can be used to insert a car symbol with the first point being the front drivers side, the second point as the back driver side (to rotate and scale the length) and the third as the back passenger side (to scale the width). Besides the insertion point coordinates, you can define a description for each point which is used for the drawn point description and is used for prompting in the Insert Multi-Point Symbol command and in Carlson Field data collection.
Three Point Symbol Drawing
The coordinates for the insertion point definitions are for the
symbol at unit size. To figure
these coordinates, you will need to open the symbol drawing (.DWG)
file. By default, the symbols
are located in the Carlson SUP directory. For example to make an
insertion point for the tree
drip line, open the tree symbol drawing and find the coordinate at the
edge of the tree symbol (in
this case 0.5,0.0).
Two Point Symbol Drawing
Not all of the symbol insertion points need to be used when drawing
the points. If a code
definition has a three insertion points, it is possible to use just the
first two or first one. There are special
codes to associate multiple points to the same symbol. The first code
point is used as the first
symbol insertion point. The "2ND" code is used to specify the second
symbol insertion point. A
point number can follow the "2ND" to identify a specific point.
Otherwise without the point number,
the program will use the next point with the current code. The "3RD"
code is used to specify the
third symbol insertion point and similar to the "2ND" code, a point
number after the "3RD" is
optional. The "2ND" and "3RD" codes should be assigned to the first
point. For example, consider a
code of "CAR" with a three point symbol insertion definition. If point
#1 has a description of "CAR
2ND 3RD", then point #1 will be used as the first symbol insertion
point and the next two points
with the "CAR" description will be used as the second and third symbol
Multi Point Symbol Drawing
Set Color: The line work will be drawn in this color. The default is BYLAYER.
Text Size: This is a scaler value that is multiplied by the
horizontal scale to obtain the
Symbol Size: This is a scaler value that is multiplied by the
horizontal scale to obtain the
actual size in AutoCAD. The horizontal scale can be set in
Line Width: This controls the width for the linework. Only
applies to 2D polylines.
Line Type Spacing Scaler:
This is a scaler value that is multiplied by the AutoCAD LTSCALE system
variable to give the distance between symbols in the line.
Line Type Text Scaler: This is a scaler value that
is multiplied by the AutoCAD LTSCALE system variable to give the size
of the text in a line.
Unit Symbol: This option will draw the point symbol at unit
(1:1) scale. For example, this
option could be used for a symbol that is already drawn to actual
dimensions such as a car symbol.
Set Template: For 3D polyline codes, this option allows you to assign a template (.TPL) file to the code. The code points act as the centerline for the template and the program will drawn parallel 3D polylines for each break point (grade ID) in the template. The template file is defined in the Civil Design module.
Entity Type: This defines the line entity to be created.
only does not create any line
work. 3D Polyline can be used for breaklines. 3D and 2D entity
type selection creates a 3d polyline in the layer specified in the Dual
3d polyline layer setting and a 2d polyline in the layer identified in
the Layer setting. Since 3d polylines do not display linetypes,
this is useful when needing linework in 3d for design work while also
needing to display linetypes for final plotting of the drawing. This
provides an easy and quick way to turn off all 2d polylines or all
3d polylines by using the layer control dialog or the appropriate
toggles in the Draw Points dialog.
Hard Breakline: This will tag the 3D polylines created with this code as hard breaklines. In Triangulate & Contour, contours are not smoothed as they cross hard barriers.
Separate Layers: This controls the layers of the point and symbol attributes. With "None" the point layers are the standard layers, "PNTNO", "PNTELEV" and "PNTDESC", and the symbol layer is "PNTMARK". With "Points" or "Both" the point attribute layers begin with the layer for the code followed by the attribute type. For example, the "DWL" code shown in this dialog has a layer name "DRIVEWAY". The point attributes would then be "DRIVEWAYNO", "DRIVEWAYELEV" and "DRIVEWAYDESC". With "Symbols" or "Both" the symbol attribute layer begins with the layer for the code followed by "MARK".
Smooth Polyline: This applies a modified Bezier smoothing to the polyline. The smoothed polyline will pass through all the original points.
Connection Order: The points of a distinct code can be connected in their point number order or by nearest found which makes the line by adding the next closest point.
Tie: When checked the linework drawn with this code will always close. For example if you have points 1, 2, 3, and 4 with the code BLDG and Tie is checked on for the code BLDG, then the linework will be drawn from point 1 to 2 to 3 to 4 and then back to point 1, closing the figure.
Elev Decimals: This controls the display precision for the elevation label.
Attribute Layout ID: Controls the location of the point
number, elevation and description.
These attribute layouts are defined in AutoCAD drawings that are stored
in the Carlson SUP directory with the file name of SRVPNO plus the ID
SRVPNO1.DWG, SRVPNO2.DWG, etc.). If you want to change the attribute
positions for a layout ID, then
open and edit the associated SRVPNO drawing.
Locate Pts on Real Z Axis: This option will draw the points at the actual point elevation. Otherwise the points are drawn at zero elevation. For example, you could turn this option off for the FH for fire hydrant code to drawn them at zero. Then the GND code could have this option on to draw the ground shots at their elevations.
Random Rotate: This option will randomly rotate the symbol.
For example, this option
could be used for tree symbols to have the trees drawn in various
Distinct Point Layer: When this toggle is selected, the line
work is created in the layer
defined in the Layer field and the points are created in the specified
distinct point layer. For
example, you could have DRIVEWAY for linework and DRIVEWAY_PNT for the
Code Definitions (continued)
Select All: This
option selects all the codes. This can be used when only wanting
to process a couple of codes. For example, use the select all
option to select all the codes and then turn them off. Now select
the codes for processing and turn them on. Also it can be used to
make a global change to all the codes.
Add: The new code definition is inserted in the list in the
position after the currently selected
one. If none are selected for positioning, the new code is placed at
the top. Only one code
definition may be highlighted before running this routine.
Copy: This option copies the
definition of a selected code. It opens the Edit Field Code
Definition dialog and copies the definition of the selected code to the
appropriate settings. It does not copy the name of the
code. It is a time saving tool to use when creating codes that
are similar with only a couple of differences.
Cut: This command will remove the highlighted code definitions from the list and puts them in a buffer for retrieval with Paste.
Paste: This command will insert the code definitions put in the buffer by the Cut command. These codes will be inserted after the row of the currently highlighted code or at the top.
Search: Allows you to search for a specific code in the list.
Set CRD File: This command allows you to specify a coordinate (.CRD,.CGC,.MDB,.ZAK) file to process.
Edit Points: This command opens the Edit Points spreadsheet editor. See Edit Points for more details.
Draw: This command returns to the Draw Field to Finish dialog
Example drawing results using the example points and example code definitions
Pulldown Menu Location: Survey
Keyboard Command: fld2fin
Prerequisite: A data file of points with descriptions
File Names: \lsp\finish.arx, \lsp\field.dcl, \lsp\deffield.lsp