Import & Export Guide

Export Formats

SiteCAD supports 13 export formats across geographic, CAD, 3D, and presentation categories. Each format targets specific downstream tools and use cases.

Format	Extension	What It Exports	Best For
GeoJSON	`.geojson`	Boundaries, traces, control points	GIS analysts, surveyors
Shapefile	`.shp/.zip`	Boundaries, traces, control points	ArcGIS, QGIS
CSV	`.csv`	Control points, boundaries, traces, entity metadata	Spreadsheets, databases
DXF	`.dxf`	Boundaries, traces, control points	AutoCAD, CAD workflows
LandXML	`.xml`	Control points, boundaries as parcels, traces as alignments, terrain layers as TIN surfaces	Civil engineering, surveying
KML / KMZ	`.kml/.kmz`	Boundaries, traces, control points	Google Earth, mapping
glTF / GLB	`.gltf/.glb`	Solids as textured meshes	3D visualization, presentations
STEP	`.step`	Parametric solid geometry	CAD/CAM, manufacturing
OBJ	`.obj`	Solids as meshes	3D modeling, rendering
STL	`.stl`	Solids as triangle meshes	3D printing, prototyping
PLY	`.ply`	Solids with vertex colors	Point clouds, visualization
IFC	`.ifc`	Solid geometry (IFC4)	BIM workflows, Revit
SVG	`.svg`	2D sheet drawings (plan, section, elevation)	Presentations, print

Which format should I use?

For CAD users: DXF or STEP. For GIS: GeoJSON or Shapefile. For 3D visualization: glTF (recommended). For civil engineering: LandXML. For printing: SVG drawings. When in doubt, ask the AI assistant — it can recommend a format based on who you're sending the file to.

Importing Data

SiteCAD can import survey data, GIS features, CAD geometry, and full scenario bundles. The import system auto-detects file formats and previews data before committing changes.

Automatic Format Detection

Drop a file into SiteCAD and it identifies the format automatically using a three-phase detection pipeline:

Extension matching — Recognizes common file extensions (e.g. .geojson, .dxf, .csv).
Content sniffing — Reads the first bytes to verify the format. Catches mislabeled files and ambiguous extensions like .json (GeoJSON vs. scenario bundle).
Validation fallback — If the top candidate fails validation, the next-ranked format is tried automatically.

Preview Before Committing

After detection, SiteCAD shows a preview of what will be imported — entity counts, coordinate details, and any warnings. Nothing changes in your scenario until you confirm. If something looks wrong, cancel and adjust your file.

Coordinate Conversion

SiteCAD handles coordinate transformations automatically. DXF files use local ENU (East-North-Up) coordinates — SiteCAD converts them to geodetic using the site anchor. GeoJSON and KML use WGS84 natively. LandXML coordinates are projected as needed.

Undo Support

Every import is a single undo step. If you import a file with 50 control points and realize it's the wrong dataset, press Ctrl+Z (or ⌘+Z) once to undo the entire import.

Supported Import Formats

GeoJSON .geojson

Boundaries (Polygon), traces (LineString), control points (Point)

CSV .csv

Control points, entity metadata, custom tabular data

DXF .dxf

Closed polylines as boundaries, open polylines as traces, points as control points

LandXML .xml

Survey control points, alignments, parcels, and TIN surfaces (each as a new terrain layer)

GeoTIFF .tif

Elevation rasters and orthophotos, baked onto a terrain layer

Scenario Bundle .json

Full scenario round-trip with all entities, blueprints, and relationships

Scenario Snapshot .scenario.snap

CRDT snapshot for lossless environment migration

How To Export & Import

Both export and import are accessible from the menu or through the AI assistant.

Exporting

Select the entities you want to export (or export all)
Open the menu and choose Export
Pick a format and configure options
Click Download to save the file

Importing

Open the menu and choose Import, or drag a file into the editor
SiteCAD auto-detects the format
Review the preview — check entity counts and coordinates
Click Confirm to add the data to your scenario

AI-Assisted File Handling

The AI assistant can handle export and import through natural language. Describe what you need and it will choose the right format and options.

Example Prompts

Export

“Export my boundaries as a DXF file for the contractor”

Export

“Create a GeoJSON of all control points with their elevations”

Import

“Import the survey points from this CSV file”

Import

“Bring in the parcels and alignments from this LandXML”

Tip

You can also ask the AI which format to use: “My surveyor sent me a file, what format should I use to get it into SiteCAD?” The assistant will inspect the file and recommend the best import path.

Common Workflows

Here's how import and export fit into typical site engineering and design workflows.

Contractor Handoff

Export DXF for AutoCAD or LandXML for civil engineering software. Include boundaries, alignments, and control points so contractors work from accurate site data, and export a graded terrain layer as a LandXML surface from the layer panel. The whole layer stack still travels only in a scenario bundle or a published link.

Survey Data Import

Bring in CSV control points from total stations or GNSS, LandXML from survey software, or GeoJSON from GIS tools. SiteCAD auto-detects the format and converts coordinates.

BIM / CAD Integration

Export solids as STEP for direct CAD editing, IFC for BIM coordination, or glTF for visualization in tools like Blender or web viewers.

Client Presentations

Share glTF models for interactive 3D viewing, SVG drawings for printed plans, or KML files for Google Earth flyovers.

Round-Trip: Scenario Bundles

Need to move a full project between SiteCAD instances or share it with a colleague? Export as a Scenario Bundle (.json). This captures every entity, blueprint, tag, property, and relationship. On import, IDs are remapped to avoid conflicts with existing data.

For environment migration (e.g., dev to staging) where sync history must be preserved, use a Scenario Snapshot (.scenario.snap) instead. This preserves the full CRDT history for lossless migration.

Import & Export