Survey Database
Civil 3D Survey Database for importing, managing, and processing field survey data including points, figures, and networks.
Definition & Context
The Civil 3D Survey Database is a structured repository for field survey data — points (with coordinates, elevations, descriptions), figures (connected linework representing features like road edges, buildings, fences), observation data (angles, distances from total stations), and GPS observations. It separates raw field data from the design drawing, preventing accidental edits to survey control.
Import workflows support multiple formats: raw data collectors (Trimble DC, Leica GSI), point files (PNEZD CSV), LandXML, and direct database links to survey processing software. Figure prefix libraries auto-create linework from coded descriptions — surveyor enters "EP" (edge of pavement) as a point code, and Civil 3D automatically connects EP points into a polyline figure.
Survey network analysis performs least-squares adjustment on traverse observations, computing adjusted coordinates and reporting error ellipses. This validates field measurements before using them for design surfaces. The workflow: import raw observations → adjust network → generate adjusted points → create survey figures → build existing ground surface from points/figures → begin design on top of validated survey data.
Why It Matters
The Civil 3D survey database stores field survey data — points, figures, and setups — with survey-specific tools (traverse, adjustment, figure prefixes) that build surfaces and linework directly from surveyor observations, keeping survey data managed and auditable.
Best Practices
- Use figure prefix libraries so field codes build linework automatically.
- Perform traverse analysis/adjustment before building surfaces.
- Keep the survey database as the managed source of raw field data.
- Verify point/figure coding against the field book.
Common Pitfalls
- Importing raw points with no coding, losing automatic linework.
- Skipping traverse adjustment, propagating field error.
- Editing derived data instead of the survey source.
- Coordinate/datum mismatches with the project.
Standard Engineering Workflow for Survey Database
2. Geometric Alignment & Profile Design
Lay out horizontal tangents and spiral transitions following AASHTO / Eurocode minimum curve radii, coupled with vertical slope crest/sag parabolic curves.
Common Failure Scenarios & Troubleshooting
| Failure / Geometric Issue | Root Cause & Mitigation Strategy |
|---|---|
| Surface triangulation bridges across steep ravines incorrectly | Add linear Breaklines along tops/toes of slopes or specify 'Maximum Triangle Length' under Surface Build Properties. |
| Horizontal curve radius triggers AASHTO violation flags | Adjust minimum transition spiral length or increase curve radius to meet minimum design speed superelevation criteria. |
| Coordinates offset by several meters after CAD/GIS import | Verify projection datum and false easting/northing parameters in MAPCSASSIGN before importing geospatial shapefiles. |
Industry Standards & Compliance Codes
- Eurocode 7 (Geotechnical Design - EN 1997)
- ISO 19650 (BIM for Civil Infrastructure)