How to Use Image to CAD: Vector vs Elevation from a Facade Photo

A photograph is pixels with perspective, lens distortion, and whatever sat in front of the building that day. IMAGEATTACH plus manual tracing still works, but it is slow.

Atlasly produces first-pass vector linework you can open in CAD as an underlay before you buy survey data. Trees, vans, and street furniture can obscure information that the photograph cannot establish. Heavy occlusion means gaps and dashed inferred lines, not a clean elevation. For raster versus vector theory, see the raster-to-vector CAD guide. For scanned PDFs that fail ordinary converters, see why PDF-to-DWG converters fail on scanned drawings.

Shoot roughly square-on with openings, string courses, and a door leaf visible so scale has something real to estimate from. Clear the elevation plane when you can: vans, scaffolding, and deep tree cover break the drawing where they hide the wall.

Google Earth, drone nadir, and other aerial views are unsupported for this elevation path. A phone photo of one facade, taken like a measured-building reference shot, is the intended input.

Vector is the default for every scene. It keeps the photograph's perspective. The linework is an inferred drawing that needs comparison with the upload. Atlasly does not silently square the photo.

Elevation is an opt-in second pass. You choose it explicitly. Atlasly runs another drafting pass over the original photograph and squares the facade. The result is squared by drafting, not surveyed. Use it for an orthographic-style first pass. Do not run Elevation on a sketch or photo you wanted to keep in perspective.

Scans and sketches belong on the scanned floor plan walkthrough, not on the Elevation path.

The drawing-mode path processes linework in the browser. Input classification is automatic: a photograph of a paper drawing must not be assumed to follow that local path. Check the current disclosure and classification before supplying confidential material.

Photographs take a different path. A local result shows first. Atlasly then runs a cloud drafting pass on the photo. If that pass is unavailable, the local result still stands. The cloud drafting pass is automatic for photo-classified inputs; it is not an upload opt-in after the local preview.

CAD downloads (DXF, SVG, vector PDF) need a free account. The share card stays ungated. Methodology notes: /tools/image-to-cad/methodology.

On photo results, auto-scale estimates from on-building elements such as a door leaf, brick coursing, or storey height. Treat every auto-scale figure as an estimate. Never claim survey accuracy.

Refine with two-point calibration against a known dimension. After import, check a second known dimension before you draw. OCR or dimension-string scale suggestions belong to the scan path (you must confirm them); see the scanned floor plan guide.

Open the file in AutoCAD, Rhino, or QCAD as an underlay. Lock the imported layers and draw over them. Eligible repeated-opening groups with at least two confirmed members can export as DXF BLOCKs on A-OPENING. Shared strokes (string courses) are not collapsed.

The photo pass does not produce native Revit walls or the scan path’s recognized text. It supplies an underlay to review. The separate drawing path can produce OCR text, which also needs checking. Site-context DXF from Atlasly's site tools: how to export site context DXF.

Not a measured survey. Not an FRA. Not planning advice. Not a substitute for a laser or total-station elevation survey. Use it as a Stage 0-2 underlay to brief concept and compare options early, then commission measured work when the project needs survey-grade elevations or when a planning submission requires them.