Field-to-Finish
A practical study guide for surveyors starting their first as-built project — from raw field data to a clean, plotted deliverable.
What Is Field-to-Finish?
Field-to-Finish (F2F) is Civil 3D’s automated system for translating raw survey field codes into finished CAD geometry — points, figures (linework), and blocks — in a single step. Instead of manually drawing lines between shot points after importing, you define rules up front so the software draws everything for you.
Think of it as a translation layer: your field crew shoots a point and types a code like EP (edge of pavement). F2F sees that code, drops the correct point symbol on the correct layer, and connects it to the next EP shot with the correct linestyle — automatically.
What F2F Automates
Drops the correct marker block (manhole, iron pin, tree, etc.) based on the field code.
Places each point and figure on the correct layer defined in your point style or figure prefix database.
Connects sequential shots of the same code into polylines, respecting begin/end codes.
Optionally converts figures into surface breaklines for TIN surface generation.
Key Concepts & Terminology
A folder-based repository that stores all networks, figures, and imported data for a project. One project = one SDB.
A text file containing raw traverse observations (directions, distances, angles) from a total station or field controller.
A named filter or collection of points in the drawing. Controls visibility, labeling, and surface inclusion.
A polyline entity in the survey database connecting sequential shots of the same code. Becomes CAD linework.
The F2F lookup table that maps field codes to layers, linetypes, colors, and figure styles.
Controls how point codes are rendered in the drawing — which marker block to use, label placement, etc.
A logical grouping of survey observations within a database — typically one network per day of fieldwork or per setup.
Known coordinates (benchmarks, monuments) used to orient the survey into the project coordinate system.
Common Field Codes to Know
| Code | Meaning | Figure Behavior |
|---|---|---|
| EP | Edge of Pavement | Begins/continues EP figure |
| CL | Centerline | Begins/continues CL figure |
| TC / BC | Top/Bottom of Curb | Parallel curb figures |
| MH | Manhole (center) | Single point, MH block inserted |
| CB | Catch Basin | Single point, CB block inserted |
| BLD | Building Corner | Connects corners into closed polygon |
| IP / MON | Iron Pin / Monument | Single point marker |
| TRE | Tree | Single point, tree block |
| EOP / BOP | End/Begin of figure | Stops or restarts a figure string |
The F2F Workflow Overview
Here is the high-level sequence you’ll follow every time. Each step is detailed in later sections.
Set up a new SDB folder linked to your project. Choose your coordinate zone and units here.
Assign your Figure Prefix Database and Code Set Style to the database before importing any data.
Bring in your .fbk, .raw, .csv, or total station file into a network inside the database.
Civil 3D reads codes, generates figures, inserts blocks, assigns layers. Output appears in the drawing.
Check linework for breaks, mismatches, or offset figures. Fix problem codes in the event editor.
Insert or xref into your template, verify styles are applied, check paperspace viewports, and publish.
Creating a New Survey Database
The Survey Database (SDB) is the backbone of everything. It lives on disk as a folder and is separate from your DWG. You link a DWG to an SDB, not the other way around.
Step-by-Step
Open your project DWG (your template-based file). Make sure it’s in your project folder.
Open the Toolspace palette. Click the Survey tab (the level icon). If the Survey tab isn’t visible, go to .
In the Survey tab, right-click Survey Databases → New local survey database…
Name the database (e.g., ProjectName_Survey). Choose a location inside your project folder structure.
Click OK. The new SDB appears in the tree.
Right-click the new SDB → Open survey database. This links it to your current drawing session.
After Creating — Set Database Properties
Right-click the SDB → Properties. Review these settings:
| Property | What to Set |
|---|---|
| Coordinate Zone | Your state plane or local projection (e.g., NAD83 Alaska 5001) |
| Angular Units | Degrees, minutes, seconds (DMS) or decimal degrees |
| Distance Units | US Survey Feet or Meters — match your fieldwork |
| Direction | North azimuth or bearing — match your traverse notes |
Configuring F2F Settings
This is the step most beginners skip — and then wonder why their import produces no linework. F2F settings must be assigned to the database before data comes in.
Access Survey Database Settings
In the Survey tab, right-click your SDB → Edit survey database settings…
The Survey Database Settings dialog opens. Navigate to the Field to Finish section in the tree on the left.
Figure Prefix Database
This is the core lookup table for F2F. It maps every field code to drawing behavior.
Under F2F settings, find Figure prefix database. Click the dropdown or browse button.
If your template came with a figure prefix database (common in firm templates), select it here.
If you need to build one: go to .
Building or Editing the Figure Prefix Database
Double-click a Figure Prefix Database to open the editor. Each row is one field code:
| Column | Purpose |
|---|---|
| Name | The exact field code (EP, MH, CL, etc.) — case sensitive |
| Figure Style | Controls how the figure looks (solid, dashed, etc.) |
| Site | Which Civil 3D site to place figure geometry in |
| Layer | The CAD layer for this figure’s linework |
| Breakline | Yes/No — adds figure to surface as a breakline |
| 3D Geometry | Whether to preserve elevation in the figure polyline |
Code Set Style
The Code Set Style controls point symbol appearance for each code. Think of it as the visual theme layer on top of F2F.
Still in Survey Database Settings, find Code set style.
Assign the code set style from your template. If your template has a Survey-Standard code set, select it.
This controls which block symbol gets dropped at each shot (circle for EP, manhole symbol for MH, etc.).
Other Important F2F Settings
# In Survey Database Settings → Field to Finish: Process linework during import = Yes # runs F2F automatically on import Insert figure objects = Yes # creates polylines in the drawing Insert survey points = Yes # drops point markers Current point group = All Points (or your group) Lot line closure tolerance = 0.05 ft # adjust to your accuracy standard
Importing Field Data
With the database configured, you’re ready to import. Civil 3D supports several input formats. The most common for total station as-builts are .fbk (field book), .raw, and plain .csv coordinate files.
Import via Survey Network
In the Survey tab, expand your SDB → right-click Networks → New network…. Name it by date or crew (e.g., Day1_MainSt).
Right-click the new network → Import field book… (for .fbk files) or use the appropriate import option for your file type.
Browse to your data file. Review the import settings dialog — confirm units and direction match your database settings.
Click OK. Civil 3D processes the traverse, adjusts, and if “Process linework during import” is on, runs F2F automatically.
Import CSV/TXT Coordinate File (No Traverse)
For GPS-collected as-builts or data already reduced to coordinates:
Go to or use IMPORTSURVEYDATA command.
Select your survey database and network.
Choose Point File as the data type.
Select your file format (PNEZD, PENZ, etc.) to match your CSV column order.
Confirm F2F is enabled in the options, then import.
Setting Control Points (if using raw traverse)
If importing a field book with a traverse, you need to set your control points first so the traverse closes to your project coordinate system:
Expand Networks → right-click Control Points → Add control point…
Enter the point number, Northing, Easting, Elevation, and description for each known monument.
These will be used automatically during import to orient and adjust the traverse.
Running F2F & Reviewing Output
If F2F ran automatically during import, you should already see linework and point markers in your drawing. If not, or if you need to re-run it after changes:
Manually Run F2F
In the Survey tab, right-click your Network → Process linework…
In the dialog, confirm the Figure Prefix Database is correct.
Click Process. Figures are generated and inserted into the drawing.
What You Should See in the Drawing
COGO point objects at each shot location, with the correct symbol and label style applied from your template.
3D polylines connecting sequential coded shots. These are Survey Figure objects — not plain polylines.
Each code’s linework should be on its own layer as defined in your Figure Prefix Database.
Symbol blocks for manholes, trees, monuments, etc., inserted at the correct rotation and scale.
Checking the Event Viewer
After import, always check the Event Viewer for warnings and errors:
Go to . Common issues to look for:
- Unrecognized codes (code exists in data but not in Figure Prefix DB)
- Figure not closed (begin code with no matching end)
- Point not found (control point reference that doesn’t exist)
- Closure errors exceeding tolerance
Editing & Fixing the Drawing
F2F gets you 80–90% of the way there. The remaining work is cleanup — fixing figure breaks, adding missing linework, and verifying topology.
Editing Survey Figures
Survey Figures are not plain polylines. Use survey-aware tools to edit them:
In the Survey tab, expand your network → Survey Figures. You’ll see a list of all figures by code.
Right-click a figure → Zoom to figure to locate it in the drawing.
To edit vertices: select the figure in the drawing → right-click → Edit survey figure vertices.
To add a point to an existing figure: right-click the figure in Toolspace → Insert point into figure.
Re-running F2F After Code Edits
If your field crew used inconsistent codes and you need to edit the raw data:
In the Survey tab → right-click your network → Edit field book (for .fbk imports).
Correct the code entries in the text editor.
Save and re-import, or right-click network → Re-process field book.
Common Fixes
| Problem | Cause | Fix |
|---|---|---|
| Line stops mid-run | Crew typed EOP (end) too early | Edit field book, remove EOP code |
| Linework on wrong layer | Code not in Figure Prefix DB | Add code to FPD, re-process |
| Building outline not closed | Last shot missing CLS code | Add CLS in field book or close manually |
| Lines cross each other | Crew shot out of sequence | Re-order points in figure editor |
| Points missing symbols | Code not in Code Set Style | Add code to Code Set Style |
Connecting to Your Template
Since your template is already built out with styles, paperspace frames, and a document structure, this step is about verification — making sure the survey output inherits the correct styles and appears correctly in your layout.
Working in the Same DWG
If you opened your template DWG and linked the survey database to it, your point and figure styles should already be applying from the template. Verify:
- Point label styles match your firm standard
- Figure layers match your template layer list
- Point groups are assigned to the right styles
Xref Approach (if survey is a separate DWG)
Some workflows keep the survey DWG separate and xref it into the final deliverable. In this case:
Complete all F2F processing and cleanup in the survey DWG.
Open your template/deliverable DWG.
Go to → browse to the survey DWG → attach as Overlay (not Attachment) to avoid chain references.
Set the xref to the correct insertion point and scale (usually 0,0,0 at 1:1 if coordinates match).
Paperspace Viewport Checklist
Double-click inside a viewport to activate it (model space through viewport).
Set the viewport scale using the scale dropdown in the status bar (1″=20′, 1:500, etc.).
Pan to center your survey area. Lock the viewport: right-click the viewport border → Display Locked → Yes.
Freeze unnecessary layers within the viewport using the layer manager (VP Freeze column) — this won’t affect other viewports.
Return to paperspace (double-click outside viewport) and verify your title block, north arrow, and scale bar are correct.
Real-World As-Built Checklist
Use this before submitting or plotting your first as-built. Work through each item top to bottom.
Database & Import
- Survey database created in project folder with correct name
- Coordinate zone and units set correctly before import
- Figure Prefix Database assigned with all expected codes
- Code Set Style assigned matching template styles
- Control points entered with correct coordinates
- Field data imported with no critical errors in Event Viewer
- Unrecognized code warnings resolved (codes added to FPD or field book corrected)
Linework & Drawing Cleanup
- All EP figures are continuous — no unexplained gaps
- Curb figures (TC/BC) run parallel without crossing
- Building outlines are closed polygons
- Utility features (MH, CB, valve) have correct symbols at correct locations
- All figure linework is on correct layers
- No rogue linework on layer 0 or wrong layers
- Survey points visible and labeled with correct style
Layout & Deliverable
- Paperspace viewport scale is correct and locked
- Annotation scale matches viewport scale
- Title block filled in (project name, date, drawn by, scale)
- North arrow pointing correctly
- Scale bar present and accurate
- Unused layers frozen or turned off in viewport
- Drawing plotted/published to PDF and visually reviewed
- PDF checked — no missing text, correct line weights, all symbols visible
Recent Comments