This command turns data collector field notes into a final 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.
Example drawing results using the example points and example code definitions
Two files are used in Draw Field to Finish - a coordinate file and a field code definition file. The coordinate file consists of point#, x,y,z points with text description fields. The description fields contain codes for the Draw Field to Finish processing. 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.
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
Carlson12.DWT. This template name will correspond to the version of
AutoCAD that is being used. 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.
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 first method.
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 draws 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.
Draw
Within: These
options are methods to filter the points to draw. The Polyline
method prompts for a closed polyline and only draws points inside
this polyline. The Distance method uses a specified center point
and distance to only draw points within this circle. The
Window/Coordinate Range prompts for lower left and upper right
points to define the rectangular area to draw
points.
Layer Prefix: Optional layer prefix added to all entities drawn with Draw Field to Finish.
Erase Existing Draw 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.
Erase In Range: This option only erases and redraws those Draw Field to Finish entities that are within the specified range of points to process.
Preview
Only: When
checked, this option will temporarily draw the points and linework
and allow you to review it with zoom and pan.
Fix
Overlaps: This option checks the points drawn by
Field-to-Finish for any point labels that overlap with other points
or linework. For any overlaps, the point labels can be
automatically moved or you can step through each overlap to decide
how to handle it. See the command called Fix Point Attribute
Overlaps in the Points chapter for more information on this
feature.
Code
Table: Sets the FLD file to process which contains the code
definitions.
Coordinate
File: Sets the CRD file to process which contains the point
numbers, coordinates and descriptions.
GIS
Table: Sets the GIS file which defines the GIS feature and
attribute names. This file is optional and is used in GIS
processing.
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.
Elevation Label Settings: Specify the elevation labeling options. The Elevations toggle controls whether to draw the elevation attribute label for the points. The Label Zeros option will label the elevations of points with z=0. The Prefix and Suffix By Code sets whether to use the general Prefix and Suffix for all point elevation labels from this dialog or use the Prefix and Suffix defined in each code definition. 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.
Locate Linework on Real Z Axis: Choose between drawing all the linework at real Z elevation, all at zero elevation or to use the 2D/3D polyline 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
Sequential Arcs method draws multiple arcs with arc end points at
each of the curve points. These arcs are tangent to the preceding
line segment. The Best Fit method creates a single best-fit curve
for all the curve points between the PC and PT.
Adjust PC/PT
for Arcs to be Tangential: This option
will adjust the PC and PT polyline vertices to make the curve
tangential. The program will only adjust these points is the
adjustment distance is less than the specified tolerance. This
option applies to cases where the tangents are well defined and the
PC/PT are harder to survey exactly.
Creating Point Notes:
These options append point notes to the coordinate file data for
some of the data fields processed by Field-to-Finish. These notes
can then be used by other commands like List Points to report these
fields. For example, this enables List Points to report both the
point coordinate file description as well as the point drawing
description as generated by Field-to-Finish.
Keep Layers Frozen: This option will not thaw layers that
Field-to-Finish uses for drawing entities. So when you have this
option on and some layers are frozen, then you won't see the
entities that Field-to-Finish creates until you thaw those
layers.
Output Caice TSS File: This option creates a TSS file
from the processing results.
Flip Text for Twist
Screen: This option will rotate the point labels and symbol
by 180 degrees when needed to make them right-side up readable
relative to the current twist screen drawing view. This option
applies to the Rotate To Line and Rotate special code
(ROT).
Set
Levels By Codes: This option assigns the optional Level Names
for use by selection filters.
Auto Zoom Extents: When checked, this will force a zoom extents after Draw Field to Finish is done.
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.
Report Codes/PointsThis 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.
The Field to
Finish dialog box allows you to load the coordinate and field code
definition files, view and edit the code definitions, view and edit
the coordinate file, view reports, and then return to the Draw
Field to Finish dialog box to process the files. The top section
displays the code definitions. The bottom section has three columns
of functions each pertaining to controls for different elements of
the command. The Code Table section provides controls for
settings, sorting and reporting of codes. The Code
Definitions section provides tools for the creation and editing
of codes. The Feature Settings section provides controls for
the special tree and pipe feature types.
Code Table
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.
Coding
Method
Carlson Coding: When
checked, this option interprets and processes coordinate files
based upon the Carlson Coding method and data collection
method.
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 special designators.
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 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.
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.
SDMS
Coding: This option
processes coordinate files based upon SDMS coding method. When
active, the program will prompt for an SDMS .PRJ file to
process.
LandXML
Coding: This method prompts for a LandXML or Leica/Hexagon
HeXML file to use with the processing. This method applies when the
point descriptions do not have linework coding and the LandXML file
has PlanFeatures that define how points are connected to create
linework. This method reads the LandXML file to find the points
that begin and end lines and curves.
Split Multiple Codes: 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 Land 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 COGO/DescKey directory.
Import TDS
Codes: This option
imports TDS codes into the Carlson Field to Finish (fld) code
definition file.
Import
Topcon Codes: This function imports Topcon codes and layers
from an XML file.
Import Trimble Codes: This option imports Trimble .FXL file codes into the Carlson Field to Finish (fld) code definition file.
Import Civil 3D Codes: This option imports Civil 3D .fdb_xdef file codes into the Carlson Field to Finish (fld) code definition file.
Import Eagle Point Codes: This option imports Eagle Point codes into the Carlson Field to Finish (fld) code definition file.
Import C&G Description Table: This option imports C&G code tables (tbl) into the Carlson Field to Finish (fld) code definition file.
Import Text/ASCII Codes: This option imports code definitions from a user-defined format. Each row in the text file should represent one code. The program will prompt for the delimiter (ie. comma separated) that is used in the text file and then for the field type for each of the columns (ie. "Layer" or "Description").
Import GIS Feature Codes: This option imports features in a .GIS file from Define GIS Features into F2F codes.
Import SurvCE Codes: This option imports a SurvCE Feature Code List (fcl) into a Carlson Field to Finish (fld) code definition file.
Export
SurvCE Codes: This option
creates a SurvCE Feature Code List (fcl) from the current a Carlson
Field to Finish (fld) code definition file.
Merge Code
File: This
function adds code definitions from another (fld) code definition
file into the current code table. The program shows a list of the
codes from the other file that are different than the current code
table. You can choose which codes to import. Any codes that
conflict with an existing code definition are defaulted to not
import.
Spreadsheet
Editor: This
function lets you edit all the codes with all their settings in a
single large spreadsheet. This method can be a handy way to use
copy and paste to edit the codes. This method can also be quicker
to make many changes than navigating the Edit Code dialog. This
method is for expert users and you need to take care make valid
inputs.
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.
Skip
Multiple Z Labels For Linework At Same Z: This option labels
only the first point elevation for points on polyline or rectangle
from the RECT code when the elevation difference between the points
is less than the specified Z Tolerance and the horizontal
distance is less than the Distance Tolerance. For example,
for points on the corners of a level utility pad, this option will
label the pad elevation just once.
Stop
Linework At Gap In Point Numbers: This option is a method for
controlling the start and stop of drawing linework. This method
will automatically stop linework where there is a gap in the point
numbers for the linework code. For example, if there are points
with code EP then points with code CL then more points with code
EP, the EP linework for the first set of EP points will stop at the
last EP before the CL points and then new EP linework will start
after the CL points.
Stop
Linework For Different Point Groups: This option applies to
when you have points for the same job collected at different times
or with different crews and you want to prevent linework connecting
points between them. For example, this applies when you survey a
job with two crews and combine their points into a single CRD and
both crews used "EP1". In this case, to keep each set of "EP1"
separate, you can put each set of points into a separate point
group with Point Group Manager and use this Field-to-Finish option.
The Point Group Filter is optional and is used to make the
program only check groups that match the filter. A point can be in
multiple groups such as “CONTROL” and “DAY1”. Some groups could be
used for different days such as “CONTROL”. So the Point Group
Filter could be set to “DAY” to filter out the common groups and
only process the time related groups.
Default
Distinct Point Layer: These settings control the default layer
for when the Distinct Point Layer option is turned on for each code
definition.
Use
Preceding Special Codes: This setting tells the program to
expect the special codes before the main code. For example, if
"BEG" is the special code for begin linework and "EP" is a main
code, then the program looks for "BEG EP". The default sequence is
for the special code to come after the main code as in "EP
BEG".
Interpolate
No Elevation Points for 3D Polyline: For points tagged as "No
Elevation" that are part of a 3D polyline, this option will
interpolate an elevation for this point from the other points in
the 3D polyline. Otherwise, this point will be skipped in the 3D
polyline.
GIS Special
Codes: This option
allows you to use GIS attribute for Field-to-Finish special coding.
For a select group of special codes, a GIS attribute can be
assigned. When processing the points, if a point has GIS data for
the specified attribute, then that attribute value is used for the
special coding. For example, you can have a GIS attribute of
COMMENT set to the Append Description special code. Then if a point
has a GIS attribute for COMMENT, the value of that COMMENT will be
added to the description label for that point.
The Append
Code option adds the GIS code to the description code to make the
code for processing. For example, for a point with description
"ROAD" and a GIS attribute named "TYPE" with a value of "DIRT",
then set the GIS Special Code for Append Code to "TYPE" and the
program will process this point using the combined code of
"ROADDIRT".
Substitution
Codes: This option
defines a lookup table for translations of the raw point
descriptions. This translation is done as a pre-processing step
before the regular Field-to-Finish processing. For example, if you
had a substitution setup for "25" = "EOP", then a point
description of "25" would get translated to "EOP" and then this
"EOP" would be processed with Field-to-Finish. Use the Import and
Export functions to load and save substitution codes to a comma
separated text file.
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. The Append
Desc Auto Space option applies to the special codes that control
the point description label. This option sets whether to insert a
space in the description label when appending to the
description.
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 the 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.
Special Codes
"/": Append Description
Carlson points in the drawing have point attributes including a
description. When 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
150".
"///":
Replace Description
This special code takes the part of the description after the "///"
and uses it as the point description label.
"\": Prefix
Description
This special code takes the part of the
description after the "\" and puts it as the prefix before the
point description. For example, a data point with the description
"TR \ 24ft" and a "TR" code definition with a description of "Tree"
would be drawn with a description of "24ft Tree".
"//": Append Field Code Description
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 become "&&".
"\\": Prefix Field Code Description
This special code is the same as "//" except that field code's
description is then prefixed instead of appended to the first field
code's description.
"|": End Coding
The bar separator indicates the end of coding. Everything after the bar is ignored for Field-to-Finish processing.
MULT: Multiple Field Code
This code applies when the Split Multiple Codes under Code Table Settings is set to None and you want to override this setting and explicitly spilt selected codes. Multiple codes apply to points with dual code definitions for drawing two different style points or for connecting different linework to the same point. For example, if a point is both a sidewalk and driveway corner, then the point description could be "SW MULTDR".
PC: Start Curve
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
PT: End Curve
This code 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.
AFIT: Fit
Arc
This special code adjusts the PC/PT points for the current arc
to make the arc tangential. This special code is a way to
individually control this tangential arc adjustment. To adjust all
arcs within a specified adjustment tolerance, use the Adjust PC/PT
setting under the Additional Draw Options from the first
Field-To-Finish dialog.
BFIT: Best-Fit Line
This code creates a best-fit line using the points for the
linework. This feature can be used when you have multiple points on
a feature that you know is a straight line such as a sidewalk and
you want a single line to be drawn.
CTOG: Curve Toggle
This special code toggles curve mode on and off. Instead of using PC to start a curve, you can use CTOG. Likewise, instead of using PT to end a curve, you can use CTOG.
CLO: Close
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.
GAP
This special code makes a single segment break in the current linework. For example, if you have a curb polyline that you want to break to skip over a driveway, then you could add the GAP code at the start of the driveway and continue the curb as normal on the other side.
NE: No Elevation
This code represents no elevation. A point with this special code is located at zero elevation.
YZ: Yes Elevation
This special code locates at the point entities at the coordinate elevation and overrides any other setting for locating the point at zero elevation.
NOS: Non-Surface
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.
ZO:
Elevation Only
This code represents elevation only (Z-Only). A point with this special code is used at part of a 3D polyline for elevating the 3D polyline without effecting the horizontal position of the polyline. For example, this code could be used on a grade break point along a cube where only the elevation should change and not the horizontal alignment.
PHOTO
This code attaches a photo file to the point. The name of the
photo file should be right after the PHOTO code. The PHOTO Link
setting controls whether the photo is attached using a
Carlson-format link or a CAD Hyperlink. Use the Image Inspector
command to view photos attached to points by either link method. To
use the Hyperlink, you can Ctrl-click or right-click on the point
entity.
In addition to the PHOTO code, Field-to-Finish will also
automatically create the photo links for SurvCE photos. The program
looks for the photo database from SurvCE which should have the same
name as the coordinate file with an extension of .phdb. This photo
database file should be in a sub-folder of the coordinate file
folder and called Pictures_X where X is the name of the coordinate
file. For example, if your coordinate file is
C:\Projects\Job1\Job1.crd, then the program looks for
C:\Projects\Job1\Pictures_Job1\Job1.phdb.
When SurvCE stores photos, it creates this photo database using
this naming. So to process with Field-to-Finish, copy the
coordinate file and photo files from the data collector to your
computer.
LABEL
This code controls the point attribute format using a
number after the code. This number uses 0=attribute block, 1=text,
2=both, 3=none. For example, LABEL1 means draw that point using
text attributes.
Offsets: OH, OV, OFL, OFB
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.
When there are multiple "OH" codes for the same point, the polyline is offset multiple times.
FACE3D
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.
HOLE3D
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.
Example
1:
2500 HOUSE1 FACE3D /front of
house
2501 HOUSE1
2502 HOUSE1
2503 HOUSE1
2504 HOUSE1
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.
2506 VENT1
2507 VENT1
2508 VENT1
Example 2:
2500 HOUSE1 FACE3D /front of
house
2501 HOUSE1
2502 HOUSE1
2503 HOUSE1
2504 HOUSE1
2505 HOUSE1 HOLE3D /stops the
above mesh and applies 2505-2508 as a hole
2506 HOUSE1
2507 HOUSE1
2508 HOUSE1
Example 3:
2500 HOUSE1 FACE3D /front of
house
2501 HOUSE1
2502 HOUSE1
2503 HOUSE1
2504 HOUSE1
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.
2506 WINDOW1
2507 WINDOW1
2508 WINDOW1
Example 4 (same result as Example 3):
2500 HOUSE1 FACE3D /front of
house
2501 HOUSE1
2502 HOUSE1
2503 HOUSE1
2504 HOUSE1
2505 WINDOW1 FACE3D /starts a
new mesh using the WINDOW field code.
2506 WINDOW1
2507 WINDOW1
2508 WINDOW1 HOLE3D2504 /makes the
mesh 2505-2508 also be a hole in the mesh
2500-2504.
BLOCK3D
WALL3D
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). This height is a signed value so you can shoot either the top of the wall or the bottom of the wall. The height can be negative if the points on the top of the wall have been shot. If no height parameter exists, then the height is determined by the distance from the current point to the next point.Example -- 6' high wall shot along the bottom:
2000 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' high and 1.5' wide wall shot along the bottom:
2000 1000.000
1060.000 100.000 WALL1 WALL3D6.0 1.5 /wall 6'
high and 1.5' thick
2001 1100.000
1060.000 100.000 WALL1
2002 1100.000
1160.000 100.000 WALL1
Example -- 6' high wall, height specified by 1st to 2nd point, shot along the bottom:
2020 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
Load Default
This button sets the special codes to Carlson, Eagle Point, Geopak,
InRoads or TMOSS defaults.
Code Table (continued)
Sort Table - This sorts the code table by either code name or layer.
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.
Code Definitions
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.
Resulting points and linework showing Zorro style template
Define Code Sequence: This sets the code names that make up the sequence.The Values for the attributes can be fixed strings that you enter in the dialog shown here. They can also be dynamic parameters including point number, northing, easting, elevation or description for the current point as well as a point note, GIS attribute or equation. The Equation type sets the value by the specified equation of attribute names and numbers. Besides the attribute names, there are keywords of "X", "Y" and "Z" for the values of the current point coordinates. For example, if there is an attribute named DEPTH, then you could define a value for the invert as an equation of "Z - DEPTH". To setup a parameter value, pick the Set button and then select the attribute. The Decimals setting applies to fields that are real values. The Prefix and Suffix fields are added to the Value for the attribute string.
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
insertion points.
Multi Point Symbol Drawing
The Point Layer Suffix for 2nd/3rd Points option allows for having different layers for the 2nd and 3rd points used with the multi-point symbol.Coordinate File
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 box.
Coding Examples
Under the Carlson Projects folder, there is an example that shows the different ways for linework coding along with examples for many of the special codes. The examples are in f2f_example.crd and f2f_example.fld. Here is a breakdown of the features that the points illustrate.
Point 1: Point Entity by itself
Points 2-3: Using Begin code to start a line; end line using Begin
code for next line
Points 4-5: Using Begin and End to start and stop linework
Point 6: Point Entity by itself after End code
Points 7-11: Linework by code defined as Polyline entity type;
using End as break between linework
Points 12-15: Linework by code defined as Polyline entity type;
using Begin as break between linework
Points 16-19: Linework by code defined as Polyline entity type;
using # after code instead of Begin/End to separate linework
Points 20-22: Linework by code defined as Polyline entity type
without using Begin/End to start/stop linework
Points 24-26: 3 point curve using on PC code
Points 27-30: 3+ point curve using PC/Point codes
Points 32-33: 2 point tangent curve using PC/Point codes
Points 35-39: reverse curve using PC/Point codes
Point 40: Regular point without extra descriPointion
Point 41: Using // to use a code descriPointion as a suffix
Point 42: Using \\ to use a code descriPointion as a prefix
Point 43: Using / to append a descriPointion
Point 44: Using \ to add a descriPointion as a prefix
Point 45: Using ROT and a Point# to rotate to that Point#
Point 46: Using ROT and a value to set the rotation
Point 47: Using ROT by itself to rotate to the next Point#
Point 48: Regular point without rotation
Point 49: Using AZI and DIST codes to offset the point
Point 50: Using SZ with value to set size of symbol
Points 51-52: Using SZ by itself to size symbol by the distance to
the next point
Point 53: Using SZ with 2 values to draw multiple symbols at those
sizes
Points 54-55: Using 2ND code to size the symbol
Points 56-58: Using 2ND and 3RD codes to size the symbol in 2
dimensions
Points 59-62: Using CLO to close the linework
Points 63-64: Using RECT with two points and a value to create a
rectangle
Points 65-67: Using RECT with three points to create a
rectangle
Points 68-69: Using OH to offset right a fixed amount
Points 70-73: Using OH on multiple points to offset various
amounts
Points 74-75: Using multiple OH on the same point to offset
polyline multiple times
Points 76-77: Using OH with negative value for offset to left
Points 78-79: Using OFL with value for offset left a fixed
amount
Points 80-81: Using OFB with value to offset both left and right a
fixed amount
Point 82: Using CIR to draw circle at specified radius
Points 83-84: Using CIR to draw circle using two points for center
and perimeter
Points 85-89: Using CIR to draw best-fit circle through points on
perimeter
Points 90-91: Using JPN to join linework to another Point#
Points 92-95: Using SMO to create smoothed linework
Points 96-97: Using JOG to create additional linework segment
extensions
Points 98-102: Using GAP to create a break in the linework
Points 103-106: Using LFT to switch linetype to left side
Points 107-109: Using WALL3D with specified height value
Points 110-112: Using WALL3D with height from 2nd point
Points 113-115: Using BLOCK3D with height and three points to
define parallelogram
Points 116-123: Using BLOCK3D with height and multiple points to
define perimeter
Points 124-128: Using FACE3D with multiple points to make a
surface
Points 129-132: Using HOLE3D with multiple points to define the
perimeter of a hole in the FACE3D surface
Point 133: Using code definition with Attribute Format set to Text
and only Elevation turned on with Label Decimal On PointPointCAD
Coding
Field-to-Finish supports an early Carlson style of linework coding
called PointCAD. The PointCAD codes use numbers with +,-,* symbols
as follows:
+0 Starts a regular 2D line (not a polyline)
that is open.
*0 Starts a regular 2D line that is closed.
+4 Starts a curved 2D polyline that is open.
*4 Starts a curved 2D polyline that is
closed.
+1 Begins a 3-point arc.
-0 or -1 or -3 or -4 or -5 or -6 or -7
Ends a line.
+5 Starts a 3D polyline that is open.
*5 Starts a 3D polyline that is closed.
+6 Starts a 2D polyline that is open.
*6 Starts a 2D polyline that is closed.
+7 starts line whose type (2D line, 2D polyline,
3D polyline) is specified by the point's field code
definition. If the field code definition is to use points,
then a 2D line is started.
+2 Middle point of 3 point arc
-05 starts a curved 3D polyline section.
-50 ends a curved 3D polyline section.
+8 starts a 2D and 3D polyline combination that
is open.
*8 starts a 2D and 3D polyline combination that
is closed.
-8 ends a 2D and 3D polyline combination.
-08 starts a 2D and 3D polyline combination
curve that is open.
-80 reverts back to a straight 2D and 3D
polyline combination.
PointCAD linework coding examples
Pulldown Menu Location: Survey
Keyboard Command: fld2fin
Prerequisite: A data file of points with
descriptions