DirtMate Centimeter-level machine guidance and fleet telematics for earthmoving
AeroPoints High-accuracy ground points for faster, reliable surveys
Propeller CAD AI-powered earthworks design built directly on your real survey terrain
Drone & hardware integrations Connect Propeller with your existing tools seamlessly
A technical walk through why design overlays shift and heatmaps turn one color, covering the four conditions every comparison must share, what each civil file format can and cannot tell you, and how to validate alignment before it becomes field instructions or closeout evidence.
You upload a design file, place it over the current survey, and the entire site appears above or below grade. The problem may not be the work on the ground. It may be the relationship between the design file, survey coordinates, vertical datum, and target surface.
A design overlay is only useful when the survey and design describe the same location, elevation reference, units, and intended surface. This guide explains why civil construction overlays shift, what each file format can tell you, and how to align the data before you trust the result.
A CAD file can appear visually aligned with an orthomosaic while still being vertically offset from the survey surface. That error may remain hidden until the team runs a cut and fill comparison and sees widespread false variance.
There are several kinds of alignment:
An image or line overlay helps with orientation. A terrain surface provides elevations. A surface comparison calculates the difference between those elevations. The underlying coordinate and vertical references determine whether that difference is meaningful.
Every reliable design comparison depends on four shared conditions: horizontal position, vertical reference, units and scale, and design intent. If one is wrong, the output can look precise while pointing the team toward the wrong decision.
1. Horizontal position
Both datasets must use a compatible horizontal coordinate reference or local calibration. If they do not, the design may shift across the survey and make the comparison look wrong before elevation is even considered.
2. Vertical reference
Both datasets must use the same elevation datum or site benchmark. A vertical mismatch can make the entire site appear above or below target grade.
3. Units and scale
Feet versus meters, or survey feet versus international feet, can create material errors. Teams should confirm file units before trusting measurements, elevations, or volumes.
4. Design intent
The team must know what the file represents:
Technical alignment alone does not prove that the correct target has been selected. A perfectly aligned comparison against the wrong surface is still the wrong comparison.
A heatmap that turns almost entirely one color often points to setup or alignment, not a site-wide construction issue. Before assuming the work is wrong, check the vertical reference, calibration, coordinate system, units, design revision, and intended target surface.
Common causes include:
| Pattern | Likely issue | First check |
|---|---|---|
| Nearly uniform red or blue across the site | Vertical offset | Datum, benchmark, calibration |
| Overlay shifted consistently in one direction | Horizontal grid mismatch | Coordinate system and local grid |
| Variance increases across the site | Scale, rotation, or calibration problem | Units and transformation |
| Localized variance around active work | Potential field deviation | Cross-section and field review |
| Unexpected results only in one zone | Incorrect comparison extent or surface | Design limits and revision |
The key is pattern recognition. A localized issue may point to field variance. A site-wide offset often points to the relationship between datasets.
Civil file formats do not all carry the same information. The extension tells you the container, not whether the file includes the geometry, elevation, alignment, or surface data required for the comparison you want to run.
DXF
A DXF can contain 2D lines, 3D polylines, contours, points, triangulated data, or other design information depending on the export. A DXF extension alone does not confirm that the file contains a usable design surface.
Check:
DXF can be useful for visual overlays and, in some cases, elevation comparison. The workflow depends on what the file actually contains.
LandXML
LandXML is commonly used to exchange civil design information such as surfaces, alignments, profiles, corridors, and parcels, depending on the export. It can be valuable for earthworks and corridor comparison when it includes a valid design surface and is correctly positioned to the project reference.
Check the design revision, coordinate reference, and whether the exported data includes the surface needed for the intended comparison.
TTM
TTM represents a terrain model commonly associated with Trimble civil workflows. It can describe an existing or design terrain using triangulated surface information. TTM can be useful for civil construction comparisons, but the team still needs to confirm site grid positioning, units, and design intent.
IFC
IFC is commonly used for BIM and built-asset model exchange. It can provide strong model-based visual and structural context. It is not necessarily the primary earthworks terrain format, and whether it supports the intended comparison depends on the model geometry and the workflow being performed.
A PDF can provide a drawing, plan image, or visual reference. It may support a plan overlay, but it does not ordinarily provide a true terrain surface for elevation comparison. Check scale, georeferencing, and whether the PDF is being used for context rather than analytical comparison.
KML and KMZ
KML and KMZ files can provide geospatial boundaries, locations, and contextual layers. They are useful for showing features or areas in space, but they are not typically a substitute for a civil design surface. Confirm datum, elevation content, and intended use before relying on these files for design comparison.
| Format | Common content | Useful for visual overlay | Useful for elevation comparison | Important check |
|---|---|---|---|---|
| DXF | Lines, contours, points, surfaces | Yes | Sometimes | Confirm elevations and export structure |
| LandXML | Civil surfaces, alignments, profiles | Yes | Yes, when a valid surface is included | Confirm design revision and coordinate reference |
| TTM | Triangulated terrain model | Yes | Yes | Confirm site grid and units |
| IFC | BIM model elements | Yes | Depends on workflow | Confirm model geometry and intended use |
| Drawing or plan image | Yes | No | Confirm scale and georeferencing | |
| KML/KMZ | Geospatial features and boundaries | Yes | Generally no | Confirm datum and elevation content |
Local site grids make construction workflows practical, but they can also break simple overlay workflows when the survey and design are not transformed consistently. A reliable workflow applies the project’s coordinate and calibration information so new surveys remain aligned with the design reference.
Projects use local grids because they can be more practical for:
A platform or process needs to handle:
The goal is consistency: a reliable workflow applies the project’s coordinate and calibration information the same way every time, so new surveys stay aligned with the design reference. A dependable drone mapping and survey processing pipeline makes that repeatability practical.
A design line shows where work belongs. A design surface helps quantify whether the ground is above, below, or within tolerance of the target elevation.
Design line or drawing
A line, drawing, or plan can show:
This is valuable for orientation and communication, but it may not provide the elevation data required for surface comparison.
Design surface
A design surface can show:
A line overlay helps a team see where work belongs. A surface comparison helps quantify whether the ground is above, below, or within tolerance of the target elevation, which feeds directly into volume calculations.
Before trusting a heatmap, validate that the survey and design are aligned to the same project reality. The goal is to catch setup problems before they become field instructions, payment discussions, or closeout evidence.
Use this checklist:
This checklist can also become a LinkedIn carousel, campaign email section, downloadable one-page asset, or field leave-behind.
Heatmaps, cross-sections, and grade-check points serve different purposes. A heatmap is useful for finding the pattern, while a cross-section or point check can help explain whether that pattern is caused by alignment, design intent, or field variance.
Heatmaps
Heatmaps are best for:
Cross-sections
Cross-sections are best for:
Grade-check points
Grade-check points are best for:
The strongest workflow uses the right analysis method for the question being asked, rather than stopping at the first visual output.
Closeout evidence is strongest when reviewers can trace the result back to the survey, design, and comparison conditions that produced it. The final report is more useful when it carries the context behind the output.
A defensible chain looks like this:
Survey source, coordinate alignment, approved design revision, comparison method, variance output, field review, exported report.
Keep these details attached to the result:
Comparing the same site across captures with progress tracking keeps the record current, and shared reporting makes it easy to hand the evidence to a reviewer.
When evaluating design conformance software, teams should ask whether the platform supports the full civil workflow, not just whether it can display design files. The right questions separate visual overlay from reliable surface analysis, alignment, inspection, and reporting.
Ask:
Basic design overlays and surface comparisons are common category claims now, so the useful question is how complete and usable the civil workflow really is. The design conformance solution page covers how Propeller answers each of these.
A design comparison displays a nearly uniform elevation difference across the site. At first glance, the heatmap suggests the entire area is above or below target grade.
Before directing field rework, the team checks a known benchmark and finds a vertical reference mismatch. Correcting the alignment removes the false site-wide variance and exposes the smaller localized areas that require field review.
The lesson is simple: when the whole map turns one color, validate the relationship between the survey and design before assuming the entire site is wrong.
Bring supported design surfaces and survey data into one cloud workflow to inspect grade, volume, and alignment variance before closeout.
A CAD overlay may be offset because the design and survey use different coordinate systems, local grids, calibrations, units, or control references. The issue can also come from export settings or an incorrectly positioned file. Check horizontal reference, site calibration, units, and known control points before trusting the overlay.
A cut and fill map that is almost entirely one color often points to a vertical offset, datum mismatch, calibration issue, wrong design revision, or incorrect target surface. Before assuming the whole site is wrong, check known elevations and confirm the survey and design share the same vertical reference.
A DXF file can contain elevation data, but it does not always. It may include 2D lines, 3D polylines, contours, points, or surface-related information depending on how it was exported. Teams should check Z-values, layers, contours, breaklines, units, and export settings before using a DXF for elevation comparison.
LandXML is commonly used to exchange civil design information such as surfaces, alignments, and profiles. DXF is a broader CAD exchange format that may contain lines, contours, points, or 3D information depending on export. Either can be useful, and the right file depends on the comparison being performed.
A PDF is usually useful as visual reference or a plan overlay, not as a true terrain surface for elevation comparison. It can help teams understand design context, scale, or layout, while surface-to-design comparison typically requires a file that contains usable elevation surface data.
A local site grid is a project-specific coordinate system used to make survey, design, and machine-control work practical on a construction site. It helps teams work in coordinates that match the project, and it requires consistent calibration and transformation so survey and design data align correctly.
Check a known benchmark, control point, or location with a trusted elevation. Confirm the vertical datum, calibration, units, and design surface before running a full comparison. A small test area, cross-section, or grade-check point can reveal whether the survey and design elevations are aligned.
The best file depends on the source design and workflow, though formats such as LandXML or TTM often carry civil terrain surface information when exported correctly. A DXF may also work if it contains usable elevation data. The important check is whether the file includes the target surface needed for comparison.
We’re happy to show you how Propeller can power your worksite, and boost productivity.
