Creating a Figure Prefix Database for Survey Import in Civil 3D

In this comprehensive tutorial, we'll establish a Figure Prefix Database for survey import functionality within your Civil 3D drawing. This foundational step is crucial for maintaining organized survey data and ensuring seamless integration with your project workflow. Begin by navigating to the Toolspace and selecting the Survey tab, where you'll locate the Figure Prefix Database option at the top of the interface.

Right-click on Figure Prefix Database and select "New" to create your custom database. For this example, we'll name it "Civ 201" and click OK to confirm. This action generates a new Figure Prefix Database file, which you can verify by checking your working folder—you'll find a newly created "Civ 201.fdb" file containing your database structure. This file serves as the repository for all figure prefix definitions and remains accessible across multiple drawing sessions within your project directory.

To configure your newly created database, return to the drawing interface and right-click on "Civ 201" in the Survey tab. Select "Manage Figure Prefix Database" to launch the comprehensive Figure Prefix Database Manager window. This powerful tool allows you to define how survey codes translate into specific Civil 3D objects and their associated properties.

The Database Manager operates through Code Sets—organized collections of survey codes that correspond to specific figure types within your drawing environment. Unlike Description Key Sets, which apply to individual survey points, Figure Prefix Databases focus on linear features and continuous elements that form the backbone of your site design. Click the plus icon to add a new Code Set, then begin defining the survey codes that your field crews and data collectors will use during surveying operations.

Let's start with "TC" (Top of Curve), a fundamental survey element. Configure this code as a Break Line—a critical Civil 3D object type that carries elevation data and directly influences surface generation algorithms. Break Lines serve as the skeletal framework for accurate terrain modeling, ensuring that significant elevation changes and geometric features are properly captured in your digital surface models. Assign the TC code to layer "V-Road TC" and maintain the Standard Style settings within the Survey Site container.

Leverage the efficiency of the Copy function to rapidly create additional code definitions. Create an "FL*" (Flow Line) code by copying the TC configuration, then modify the layer assignment to "V-Road FL." Flow lines represent critical drainage elements and typically require separate layer organization for visibility control and plotting purposes.

Continue building your code library by establishing an "EP*" (Edge of Pavement) code set. Edge of pavement codes are essential for roadway design and construction layout, providing precise boundaries for paving operations and maintenance activities. Assign this code to the "V-Road EP" layer to maintain consistency with your project's CAD standards.

Add a "SW*" (Sidewalk) code to capture pedestrian infrastructure elements. Sidewalk codes become increasingly important in urban design projects where accessibility compliance and pedestrian safety are paramount considerations. Route this code to the "V-Road SW" layer for appropriate categorization within your drawing's layer architecture.

Expand your slope management capabilities by creating "Top" and "Toe" codes for embankment and cut slope documentation. These codes transition from the roadway-focused "V-Road" layer family to the "V-Slope" layer series, reflecting the different design disciplines involved. The "Top" code should be assigned to "V-Slp-Top" layer, while "Toe" codes belong on the "V-Slope-Toe" layer. This systematic approach ensures that slope stability analysis and grading operations have properly organized data sources.

Upon clicking OK, Civil 3D automatically saves your Figure Prefix Database configuration to your designated working folder. Unlike drawing-specific elements, Figure Prefix Databases operate at the project level, making them available across multiple drawings within your current working directory. This project-level storage approach promotes consistency across large, multi-drawing projects and facilitates team collaboration. While saving the current drawing isn't mandatory for preserving your database work, maintaining regular save intervals remains a best practice for comprehensive project protection.

With your Figure Prefix Database properly configured, you're now prepared to move forward with survey database creation—a process that will integrate your field-collected data with the organizational structure you've just established. This systematic approach ensures that survey imports will automatically organize incoming data according to your project's specific requirements and CAD standards.