Understanding Field to Finish

Don’t be intimidated!

DEFINITIONS

Field to Finish—A general term used to describe the process of automatically drawing survey field data based on point descriptions and other field codes.

Field Code (Description Key)—An alphanumeric code, corresponding to the point’s description, that defines how points are processed using Field to Finish. For points to be sorted onto a particular layer, be included in a point group, have a symbol inserted, or have linework that connects points be automatically generated, a Field Code having the point’s description must first be created.

Field Code File (Description Key File)—A file that contains all of the Field Codes.

Linework Codes
—Codes entered before or after a point description that, when processed using Field to Finish, indicate where linework starts and ends or how to create additional, associated linework. 
Somewhat like the seemingly Herculean task of developing CAD standards that I wrote about in the June issue, Field to Finish is one of those topics that almost everyone attending my workshops or training classes wants to learn more about. If they are not using Field to Finish, they think they should be—and, if they are already using it, they think they could be doing more or doing it better.

For those who are unfamiliar with it, Field to Finish is a general term used to describe the process of automatically drawing survey field data based on point descriptions and other field codes.

Depending on the survey software you use, Field to Finish may include some or all of these tasks:
  • insertion of survey points on to separate layers based on the point’s description,
  • sorting of points into point groups,
  • “tagging” of points, based on the point description, as “non-surface” points (this means that the points, even if selected, will be ignored when building a surface model),
  • insertion of a symbol onto a separate layer based on the point’s description or note,
  • rotation or scaling of a symbol based on the point’s description or note, and
  • drawing of 2D and/or 3D polylines connecting points based on the point’s description or note. 
Although most survey programs can perform these or other tasks that fall under the Field-to-Finish header, to my knowledge, Carlson Survey is the only one to have commands or files that are actually named “Field to Finish.” 

Land Desktop and AutoCAD Civil 3D use the term “Description Keys” for their feature that sorts points onto separate layers and inserts, rotates, and scales symbols. A separate feature called “Automatic Linework” or “Process Survey Linework” generates the polyline figures in these programs. For purposes of this article, Field to Finish refers to the generic term and, unless otherwise specified, applies to any survey program.

Benefits

For those who have never used Field to Finish, it can be summarized in one word: intimidating! But once you see what can be accomplished with a little extra coding, I believe you’ll be convinced it’s worth it. Because a picture is worth a thousand words, it’s easier to show you the benefits of Field to Finish. 

The generic command for importing points (rather than Field to Finish) was used to import the points in Figure 1. In addition to overlapping attributes that make it hard to read, the points are all on the same layer, making connecting the dots even more time consuming and difficult. 

However, if you use Field to Finish to import the points into the drawing, it looks like Figure 2. The points have been frozen in this view, but you can see the symbols and 2D and 3D linework that have been generated on their proper layers. 

Granted, these examples demonstrate the power of Field to Finish when used to its fullest capacity, and it does require additional time and attention in the field to generate these results. In my training classes I encounter a lot of skepticism from folks who don’t believe the extra time in the field is worth it. While it may look cool, they say, it’s just easier to sort to layers, insert symbols, and connect the dots manually back in the office.

Bite-size Pieces

I respectfully disagree—and I believe that tackling significant changes in procedure is best accomplished with bite-size pieces rather than one big bite. Do you remember how you’re supposed to eat an elephant? One bite at a time, of course! 
  • Nibble: Sort points onto separate layers and into point groups.
  • Snack: Tag points such as fire hydrants and inverts of manholes as “Non-Surface” points.
  • Bite: Specify symbols to be inserted on points where needed.
  • The whole enchilada—er—elephant: Also use special linework codes to connect points using lines or 2D polylines (for plan generation) and 3D polylines (for defining breaklines for surface models). 
Point Description Consistency

Regardless of the level of Field to Finish automation you strive for, the single biggest key to success with Field to Finish is consistency among the point descriptions. If you are attempting to implement Field to Finish for the first time and want to ensure buy-in from your field crews, allow them to help develop the list of descriptions. After all, they are the ones having to enter them in the field. If the folks in the field are not consistent with the descriptions they enter for each shot, Field to Finish is doomed to fail.

For instance, in the office, it doesn’t matter whether the description for a fire hydrant is “FH,” “HYD,” or “FIRE HYDRANT.” Once the Field Code File has been created, it’s simply a matter of processing the Field to Finish routine. So, rather than someone in the office dictating what descriptions the field crew should use, ask the crew what description makes most sense to them and what they are confident they can remember and enter every single time. 

Even though the “nibble” part seems simple enough, it still requires a considerable amount of thought and consideration. So, how do you start? First, determine what descriptions will be used for shots taken in the field. In order to use Field to Finish, you will need to create a field code for each description that may be processed now or in the future.

Start by going back to one or two of the largest point files you’ve worked on recently and sort it out based on the point descriptions in it. Use this list as a guide to determine what descriptions to keep and what to throw out and also to trigger your memory for other descriptions that may be used in the future.  

Once you’ve completed your list of descriptions, each description must be defined as a Field Code (Description Key) in the software. It’s during this step that layers can be assigned for the points, symbols can be specified for insertion, point groups can be defined, and non-surface points can be tagged. Depending on the software you use, the dialog boxes and interface will be different, but the data and settings entered are generally the same. 

For Carlson Software users, there is a routine in the “Draw Field to Finish” dialog box that automatically creates a Field Code Table (populated with Field Codes) from a Coordinate File. If you’re not using Carlson Survey, I recommend opening your point file in Microsoft Excel to sift through and sort the list of descriptions.

The Field Code that processes points with an FH description, as defined in Carlson Survey 2012, is shown in Figure 3. On the “General” tab of the dialog box, note the highlighted areas that show the layers, point group, and the checkbox to tag points as non-surface. Importing points with an FH description and using the “FH” Field Code definition results in the symbol named SPT16 being inserted on the layer V-WATR-STRC, the point being inserted on layer V-NODE-WATR-STRC, and the point included in a point group named EX-WATER. 

The “Symbol” tab of the dialog box (Figure 4) is where you specify the symbol name and various other rotation, scale, and insertion settings.

Connecting All Your Points

As I stated previously, it’s a reasonable goal to get to the point where Field to Finish is used to sort points and/or symbols onto their proper layers and into point groups and to tag some points as non-surface to keep them from being included in a surface model. These are office-only tasks, because using Field to Finish to complete them does not require anything from the field crew other than consistency when entering point descriptions.However, the ultimate goal is having Field to Finish connect all of your points with 2D and/or 3D linework. Compared to the previous tasks, this requires more buy-in from the field crew because of the additional coding and noting. 

In Figure 5 you can see the linework coding that has been added to the “BOC” (Back of Curb) point descriptions in the sample of the point file. The “+7” linework code instructs the program to begin drawing linework, and the “-7” instructs it to stop drawing that piece of linework. The “PC” and “PT” identify the starting and ending points of a curve that fit all points in between the PC and PT. 

The Field Code that processes points with a BOC description is shown in Figure 6. If you use the linework codes from the point file along with the BOC Field Code definition, it results in a 2D polyline on layer V-ROAD-CURB-BACK that starts at point 119 and goes to point 120. Then it goes into a curve that best fits between points 120 and 124 and ends with another tangent line from point 124 to point 125. A 3D polyline connecting the same points will also be drawn on layer 3D-EXISTING. In addition, the points will be inserted on layer V-NODE-CURB-BACK and included in a Point Group named EX-ROAD.

And this is just a sample of what can be done using Field to Finish. Depending on your software and data collector firmware, there are many other linework codes that can be used to automate the creation of linework based on your point descriptions and notes. In some cases there are specific linework codes that must be used, such as “B” for Begin linework (instead of the +7 used above) or “E” for End linework (instead of -7). Other programs, like Carlson, allow you to customize these codes. The “Special Codes” dialog box in Figure 7 shows the default linework codes used in Carlson Survey 2012. 

I have one last piece of advice for those who are considering jumping into the world of Field to Finish for the first time. Cheat! Well, kinda. Every survey program with a Field to Finish feature has sample files that you can use as-is or modify to meet your needs. Rather than starting from scratch, it’s sometimes easier to work with one of those prepared files. 

As always, I encourage you to send your feedback or contact me with questions at ContactUs@ThatCADGirl.com.

About the Author

  • Jennifer DiBona
    Jennifer DiBona is an independent consultant doing business as That CAD Girl. She is a Carlson Software reseller and provides CAD training, technical support, and other CAD-related services. Visit her website at www.thatcadgirl.com to find out more.

» Back to our September 2011 Issue

Website design and hosting provided by 270net Technologies in Frederick, Maryland.