Export Site Analysis to DXF: A CAD Handover Checklist
How to request and verify a site-analysis CAD export, including actual file formats, units, coordinates, layer coverage and checks before AutoCAD or Revit coordination.
Quick answer
Use a site-analysis export as a starting point for CAD coordination: request the available format, wait for confirmed completion, inspect the files actually returned, then check units, origin, coordinate reference system and geometry in the receiving application. Do not assume that a DXF package contains native DWG, SKP or every requested evidence layer.
A connected site-review workflow can help carry available context into design. The useful question is whether the delivered files preserve the information your team needs. A successful chat response or an export request alone does not establish a usable, complete CAD handover.
Define the handover before requesting a package
Record the site boundary, required layers, receiving application and intended use. A concept-context drawing has different requirements from measured design geometry. Agree the horizontal reference, units, vertical datum where relevant, and a known check distance or control point. Ask for formats currently offered by the product or documented API; format availability and account access can change.
Check the returned package rather than the requested list
Wait for the operation to finish and inspect its status, file list and any warnings. A partial package may omit unavailable evidence. Keep the source dates and limitations with the drawing. Native DWG or SketchUp SKP should only be promised when that exact file is delivered and tested; a DXF that an application can import is a different deliverable.
Understand what the coordinate setting means
The context DXF exporter in the reviewed code defaults to local coordinates in metres and also contains WGS84 and UTM options. These settings are not a blanket promise of British National Grid output or automatic shared coordinates in Revit. Ordnance Survey publishes transformations for its reference systems; use the appropriate transformation when those systems are required, rather than relabelling coordinates.
Validate the drawing in the receiving application
Open a copy, confirm units and measure a known distance. Inspect the origin and placement against trusted project geometry. In Revit, choose an import or link placement deliberately and coordinate shared positioning with the project team. Inspect boundaries, contours, elevations and layer names; identify open polylines, duplicates and missing objects. Record any conversion or cleanup needed.
Keep evidence separate from drawing appearance
A visible flood polygon, building outline or tree symbol does not certify its currency, survey accuracy or statutory status. Check the source and coverage for each layer. Treat desktop context as an early design aid until verified against the project survey and appropriate authority records. Share a short handover note listing received files, checks performed and unresolved issues.
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
Does a DXF export include native DWG or SKP?
No. Confirm the actual returned formats. Importing DXF into another application is not the same as receiving its native file format.
Will coordinates align automatically in AutoCAD or Revit?
Do not assume so. Check the export setting, units, origin, reference system and receiving application placement against known project information.
How long will an export take?
It depends on the requested work and service conditions. Use the reported completion status; this article does not establish a fixed duration or step count.
Which subscription or API quota is required?
Check current pricing and the documented account entitlement. This guide does not assert a fixed price or quota.
Conclusion
A reliable handover is a tested set of files with a clear coordinate and evidence note. Use the export review checklist and the current developer documentation for the applicable workflow.
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
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
how to use Atlasly in Claude ChatGPT
How To Use Atlasly Inside Claude, ChatGPT, and Other AI Assistants
Connect Atlasly’s hosted MCP endpoint in a supported Claude or ChatGPT client, verify discovered tools and distinguish public checks from account-linked operations.
Read
free AI site analysis tool for architects
Free Site Analysis for Architects: How Atlasly's Starter Plan Works
What Atlasly Starter includes, where its limits sit, and how to evaluate site evidence before choosing a paid plan.
Read
Atlasly MCP tools reference
Atlasly MCP Tools: Public Discovery and Site-Research Limits
A dated reference to Atlasly MCP public tool discovery, practical tool groups, input schemas, source coverage and account-linked actions.
Read