How to Export Site Analysis Data to AutoCAD and Revit
A guide to choosing and verifying site-analysis exchange files, including units, coordinate references, geometry, source coverage and receiving-application checks.
Quick answer
To reuse site-analysis data in AutoCAD or Revit, agree a supported exchange format, verify the files returned, then check units, coordinates, geometry and source coverage in the receiving application. A usable context drawing can reduce rework, but it does not automatically become a measured survey or a coordinated project model.
Site evidence is more useful when the next person can understand and test the handover. This guide separates three tasks: choosing an exchange format, coordinating placement, and deciding which geometry is reliable enough for the next design decision.
Choose an exchange format for a specific purpose
List what the receiving team needs: two-dimensional context, contours, a terrain surface, building massing or tabular evidence. Confirm the formats currently available and test a representative file. DXF is an exchange drawing, not proof of native DWG delivery. Likewise, an importable geometry file is not a native Revit or SketchUp project. Preserve a file manifest and note missing layers.
Agree units and reference systems
State whether geometry uses local project coordinates or a geographic/projected reference system. Degrees and metres are not interchangeable. The reviewed Atlasly context DXF exporter defaults to local metres and exposes other settings; do not infer British National Grid or an agreed project origin from a filename. In UK work, use the appropriate Ordnance Survey transformation where required and record any vertical datum separately.
Coordinate import or link placement
Autodesk documents distinct positioning and scale choices for CAD imports and links. Select the appropriate units and placement for the project, then measure a known distance and compare known points. Shared coordinates need an agreed relationship between files; they are not created merely by naming a layer or choosing a CAD format. Keep an untouched copy of the received file for comparison.
Inspect geometry and layer meaning
Check that boundaries close where intended, contours use the expected elevations and intervals, and building outlines and terrain occupy plausible positions. Look for duplicates, isolated distant objects and missing elevations. A layer name is not evidence of legal status or completeness: confirm the underlying source, date and coverage. Record conversion and cleanup work rather than promising none.
Issue a concise handover record
Include the source site boundary, file names, version/date, units, origin, horizontal reference, vertical datum if known, verified check points and unresolved issues. Identify which elements are desktop context and which come from a measured survey. Coordinate critical geometry against the project survey before detailed design; do not overwrite trusted survey data with approximate context.
Illustrative example
Illustrative scenario: A team reopens an exported context file in its intended design application and checks units, two known distances, location and layer contents. Missing or altered elements are recorded before the file is used as a design reference.
Frequently asked
Can site exports reduce redraw work?
They can where the delivered geometry is suitable and passes checks. Measure the review and cleanup effort as well as export time before claiming a saving.
Does export guarantee correct shared coordinates?
No. Agree and test the coordinate relationship in the receiving application.
Can exported context replace a measured survey?
It should not be treated as a substitute for the measured information needed for precise design and setting-out.
What if a requested layer is absent?
Record the omission and obtain the needed evidence separately. An empty or missing layer does not prove that no constraint exists.
Conclusion
A successful export is one the receiving team has checked and can trace to its sources. Keep the site-feasibility review alongside the drawing so geometry and unresolved evidence travel together.
About the author
Shatakshi Patil
Architect writing about pre-construction due diligence, planning context, and site intelligence workflows for design teams using Atlasly.
Sources and references
Authoritative references for the planning policies, regulations, and standards referenced in this article. Always check the publisher for the latest version.
Related articles
Auto-suggested
pre-construction site analysis
Pre-Construction Site Analysis: The Complete Guide for Architects and Engineers
A comprehensive guide to zoning, flood risk, solar, topography, transport, demographics, reports, and CAD-ready outputs in pre-construction workflows.
Read
site feasibility study checklist
Site Feasibility Study Checklist: 12 Things to Assess Before Your Design Brief
A practical 12-point checklist covering planning, physical, environmental, access, and viability factors that should be tested before briefing design work.
Read
pre-construction due diligence for architects
Pre-Construction Due Diligence for Architects: An Early Review Checklist
An early due-diligence checklist for architects covering site evidence, planning questions, physical conditions, specialist investigations and unresolved project assumptions.
Read
export site analysis to AutoCAD and Revit
Export Site Analysis to AutoCAD and Revit with Less Rework
A practical handover method for reusing site-analysis context in AutoCAD and Revit, with checks for file formats, coordinates, units and geometry.
Read