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 layer, symbol, size, line type, etc. Field to Finish replaces PointCAD. Field to Finish uses an improved coding method but still handles the PointCAD method which should make switching to Field to Finish easier for PointCAD users.
Two files are used in Field to Finish - a data file and a code file. The data file consists of x,y,z points with text description fields. The description fields contain codes for the Field to Finish processing. The data file can be either a coordinate (.CRD) file or an ASCII file. The code 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 Field to Finish dialog box.
Field to Finish can translate the field points into Carlson TakeOff 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 are defined in the Point Defaults routine under the Points menu. The Draw-Locate Points command provides a simpler method for drawing points compared with Field to Finish.
There are two different methods for connecting linework. One method creates line work by connecting points with the same code. The line type is defined by the code as either points only (no line work), lines, 2D 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 line type definition of line, 2D polyline or 3D polyline defined by the 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.
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 first method.
The main Field to Finish dialog box allows you to load the data and code files, view and edit the code definitions, and then process the files. The top section displays the code definitions. The middle section has two rows of buttons for changing the selected code definitions. The bottom section has three columns of functions.
Carlson TakeOff points in the drawing have point attributes including a description. When Field-to-Finish draws the points, the point description from the data 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 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. For example, a data point with the description "UP / 150" with the same code "UP" definition above would be drawn with the description "POLE 150".
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 could be "LGTPOST". When Field-to-Finish detects spaces in the descriptions at start up, there is an option of whether to process the multiple codes.
Field to Finish recognizes several special codes suffixes. A special code comes after the regular code. A space separates the codes. Here is a listing of the default special codes.
This code begins a three point arc. 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. 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.
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.
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.
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.
This code is used to smooth the polyline.
This code is used to control multi-point symbols described later in this section.
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
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. For example, “BLDG
JOG R5 L12.2 L5 L12.2” or equivalently “BLDG JOG 5 –12.2 –5 –12.2”
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. Just as “cb pc” shown above uses the “pc” special code to
launch into a 3-point arc, by default, the “jog” special code,
following any normal user-defined code, enables the entry of left and
right “jogs” or segments of a polyline. This is useful for
drawing buildings based on tape measurements, as opposed to trying to
physically survey each building corner by total station or GPS.
The key is to take 2 measurements on a building, which establishes a
“line” or vector. Assuming you used bld for building, the second
bld would be followed by the reserved word “jog”, which in turn would
be followed by the left and right measurements in the form of bld jog
10 -20 10 40 20. The “-“ or negative sign indicates a left-hand
jog. All “jogs” are at right angles to the previous
segment. With Carlson TakeOff, the JOG option no longer creates
duplicate points for each jog segment. The additional segments
are drawn with no associated point numbers, minimizing point file size.
Straight JOG within
It is possible to add a straight “jog” instead of the conventional right and left jogs. This is done by using the S# option, as in S10, for 10 units, which must follow the “JOG” expression. You cannot use S10 as a reserved, “understood” command unless it follows JOG. This “straight jog” option makes the most sense when there is a need to extend the vector or line of the first 2 building points surveyed. If you can’t see or obtain a shot at the true, second building corner, you could take 2 shots where you can obtain them, then measure the additional distance to the true corner, recording it as a straight jog. Here is an example, displayed graphically.
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 3D polyline using one of two different methods. If a number follows “RECT” (e.g., “RECT10”), a 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”). 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 code creates a coal section for use in the Mining module.
You may substitute your own code for any of these special codes in the Code Definition Settings dialog shown on page 260.
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 SAVEAS command and change to Drawing Template (.DWT) under Save as Type. In Carlson TakeOff, the default drawing template that is used is named 15SCDRAW.DWT (or 14SCDRAW for AutoCAD R14 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 TakeOff 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.
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 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 Field to Finish will substitute this template code with the sequence codes (ie substitute RD with SHD).
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 Software's Tsunami data collection. See a three point symbol example below.
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 TakeOff 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). Shown below is a two point symbol example.
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 insertion points.
Using the Main Field to Finish Dialog
1 Select Code Table - This command opens the Code Definition Settings dialog shown below.
● Select: 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 Eagle Point Coding: When checked, this option allows the user to switch from interpreting coordinate files based on the Carlson Field-to-Finish method to interpreting coordinate files where the field coding was entered using the Eagle Point Data Collection method.
Currently the supported designators include, “Line”, “Curve”, “Close Line”, “Stop Line”, “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 library.
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.
● 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 uncheck this setting.
● Max Length for Linework:
Specify the maximum length that Field to finish should draw any section
● Max Elevation Difference for Linework: With Carlson TakeOff, within the option “Code Table Settings”, you can limit the elevation difference within which linework will connect. Thus, if you were taking fence line shots on a ridgeline fence, then took a series of fence line shots in the valley, the ridge linework would stop and not connect to the valley linework if the elevation exceeded an entered amount. If you wish to disable this “elevation detection” for linework, then keep the setting for the elevation high, as shown below in the upper right of the dialog.
● Special Codes: This section allows you to specify your own code for commands such as start curve, end curve, and offsets.
2 Sort Table - This sorts the code table by either code name or layer.
3 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.
4 Code Table by CRD - This command will create code table definitions based on the data file field descriptions. This is useful when creating a code table from scratch.
1 Edit - This command opens the Edit Field Code Definition dialog box. The currently highlighted code will be edited.
● 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.
● Sequence: This specifies a sequence type code. Sequences are described above in this section.
● Define Code Sequence: This sets the code names that make up the sequence.
● Processing ON: This toggle controls whether this code will be processed.
● Code Name: This is the key name that identities the code and is matched with the field data descriptions.
● Layer: The point and line work for the code will be created in this layer.
● Full Name: This is an optional field that describes the code for viewing.
● Description: This value is assigned to the point description field. An additional description can be added to a point by entering it after a forward slash in the data description field.
● Use Code: This option turns off the Description field described above. Instead the points will be drawn with their original unprocessed descriptions.
● 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 line types is
determined by the AutoCAD LTSCALE system variable and by the line type
settings from the Annotate Defaults command. The special line type
“hedge” is drawn with a user specified width. The special line type
“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 line type.
Carlson TakeOff also offers continuous linetypes to Field-to-Finish. When you select “Linetype” or “Set Linetype” in the Edit options, you can choose among the individual entity linetypes (first group of selections) and the true “continuous” linetypes (second part of the selections). The difference in these linetypes is illustrated by the “Copy” command. A fence line made up of individual entities, when copied by a single selection pick, will copy only the single entity picked (eg. the polyline but not the “X’s”). A continuous linetype will copy or offset as one entity, including the “X’s” in the fence. This is shown in the graphic below, where the lower fence line is made up of individual entities and upper fence line is a continuous linetype.
● Symbol: This is the point symbol for the code. To avoid drawing a symbol, use the Carlson TakeOff symbol named SPT0.
● Color: The line work will be drawn in this color. The default is BYLAYER.
● 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 Drawing Setup.
● Text Size: This is a scaler value that is multiplied by the horizontal scale to obtain the actual size.
● 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 in the template. The template file can be created in Carlson TakeOff.
● Entity Type: This defines the line type to be created. Points only does not create any line work. 3D Polyline can be used for breaklines.
● 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
● Precision: 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 TakeOff SUP directory with the file name of SRVPNO plus the ID number (i.e. 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. This option allows you to assign a different point display “style” (referred to as the attribute layout ID) with each particular code. This option is also available when multiple codes are selected. The option appears in the “Multiple Set” dialog. By selecting different attribute “ID’s”, you can set the location of the point number, elevation and description with respect to the node of the point, change the rotation or set the font and color of these attributes. New “ID Layouts” are made by loading the file for “Srvpno1.dwg” or “Srvpno2.dwg” or any of the “Srvpnox.dwg” files found in the “SUP” subdirectory. The attributes and their colors appear as shown below, and can be edited and re-saved as a new “Attribute Layout ID”. To save as ID 6, for example, use SaveAs and save the file as Srvpno6.dwg.
● 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 orientations.
● Line Width: This controls the width for the linework. Only applies to 2D polylines.
● 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 points.
● Entity Type (3D and 2D): This option allows polylines to be drawn as both 3D and 2D. When clicked on, the “Additional 2D Polyline Layer option, near the top of the standard Edit dialog, allows you to place the 2D polyline on a different layer than the 3D polyline. A curved polyline coded with the PC or equivalent “start curve” code, for example, would plot with a true arc for the 2D polyline and with a series of 3D interpolated vertices through the arc in the case of the 3D polyline.
2 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.
3 Copy - The “Copy” command requires that you first select and highlight a single code, and then it captures all the settings in the standard Edit dialog, but leaves the code name blank requiring entry of a new code name. It might be used to add a new IPF (iron pin found) by borrowing from IP, changing nothing but the symbol, as shown below:
4 Cut - This command will remove the highlighted code definitions from the list and puts them in a buffer for retrieval with Paste.
5 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.
6 Search - Allows you to search for a specific code in the list.
7 Save - Saves the Field to Finish code list (.FLD) file.
1 Set CRD File - This command allows you to specify a coordinate (.CRD) file to process.
2 Edit Points - This command opens the Edit Points spreadsheet editor. See Edit Points for more details.
3 Draw - The Draw Option leads to a dialog that controls the range of points to process. With Carlson TakeOff, this dialog also controls whether points only, lines only or lines and points are plotted. If you choose to plot lines only, that selection will be the default until changed. The Draw dialog, within Field-to-Finish, is shown below:
● Range of Points: Specify
the range of points to draw.
Point Groups: Point Groups are another way of defining a range of points to plot. Point Groups can be defined using the Point Group Manager under the Points pulldown menu, and include points sharing certain descriptions, elevation ranges, locations on the screen, etc. Here is an example of a Point Group selection set (points with zero elevation):
● Point Label Settings: Specify whether you want 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 place parenthesis around the elevation text.
● 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.
● Locate Linework on Real Z Axis: Choose between locating all the linework 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 Field to Finish.
● Erase Existing Field to Finish Entities: When checked, this option will erase from the drawing any old entities created by previous Field-To-Finish runs before drawing the new entities.
● Pause on Undefined Codes: When checked, Field to Finish will pause if it encounters a description that is not defined in the code table.
● Abort without drawing anything: This lets you stop to correct the code table.
● Use the default settings for this point: This default is to draw a point in the "MISC" layer with no linework. To set your own default, define a code called "SC_DFLT".
● Use the default settings for all undefined codes: Continue processing and use default code for all undefined codes.
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 Field to Finish is done.
● Draw Points Only: This command creates only the points.
● Draw Lines Only: This command creates only the line work.