Guide

Import & Export

Move data between SiteCAD and the tools you already use. This guide covers supported formats, the import workflow, export options, AI-assisted file handling, converting files with SQL, and common integration scenarios.

Export Formats

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

FormatExtensionWhat It ExportsBest For
GeoJSON.geojsonBoundaries, traces, control pointsGIS analysts, surveyors
Shapefile.shp/.zipBoundaries, traces, control points; NRCS practice columnsArcGIS, QGIS
CSV.csvControl points, boundaries, traces, entity metadataSpreadsheets, databases
DXF.dxfBoundaries, traces, control pointsAutoCAD, CAD workflows
LandXML.xmlControl points, boundaries as parcels, traces as alignments, terrain layers as TIN surfacesCivil engineering, surveying
KML / KMZ.kml/.kmzBoundaries (with their fill and outline colors), traces, control pointsGoogle Earth, mapping
glTF / GLB.gltf/.glbSolids as meshes with materials; binary .glb or text .gltf3D visualization, presentations
STEP.stepParametric solid geometryCAD/CAM, manufacturing
OBJ.objSolids as meshes3D modeling, rendering
STL.stlSolids as triangle meshes3D printing, prototyping
PLY.plySolids with vertex colorsPoint clouds, visualization
IFC.ifcSolid geometry (IFC4)BIM workflows, Revit
SVG.svg2D sheet drawings (plan, section, elevation)Presentations, print

Boundaries With Holes

A boundary's holes travel with it through GeoJSON, Shapefile and KML/KMZ, in both directions. Exporting a holed boundary to GeoJSON and importing that file gives back the same outline and the same holes, corner for corner. DXF has no way to mark a ring as a hole, so a DXF export writes each hole as its own closed polyline, and a DXF reader (SiteCAD's own DXF import included) sees separate rings. LandXML export carries the outline only.

NRCS Practice Maps

A Shapefile export writes NRCS conservation-practice columns for every shape that carries a practice code, so the file reads as an NRCS practice map. A shape carries a code in one of three ways: a - NRCS-{code} segment in its name, as in Pond - NRCS-378; for a boundary, a role whose key is nrcs-{code}; or a PRAC_CODE attribute holding the code. The columns are PRAC_CODE and PRAC_NAME, then PROGRAM, BUFR_WD_FT, FARM_NO, TRACT_NO and FIELD_NO, filled from the attributes program, buffer_width_ft, farm_number, tract_number and field_number set in the Inspector. Each column is written only when its value is there, and shapes without a code get none of them. Renaming a shape so its name loses the NRCS- segment drops that code, so give a path or a point that should keep its code through renames a PRAC_CODE attribute: Inspector → Attributes → +, key PRAC_CODE, value the code (382). A shapefile import keeps a file's PRAC_CODE column that way already. A name segment or a role, when present, wins over the attribute.

CSV Separators, Quotes and Header Rows

A CSV export separates values with commas, puts " around a value that needs it, and always writes a header row. A CSV import works out whether the file is separated by commas, tabs, semicolons or pipes, and reads its first row as the header. A number written with a decimal comma, such as 12,5, is not read as a number: an import into a table rejects that cell, and a control point import leaves it empty and warns you.

For another separator or quote character, or a file with no header row, ask the AI assistant, attaching the file for an import: “Export the Readings table as a semicolon-separated CSV” or “Import this CSV into the Readings table — it has no header row”. Separators and quote characters are one character each. For a text encoding other than UTF-8, lines to skip before the header, or an escape character other than the quote character, read and write the file with SQL instead (Converting Files With SQL).

Path Heights

A path stores each point's height as an offset above the ground under it, so the path stays at the same height above the terrain when the terrain changes. GeoJSON and KML/KMZ write those offsets as they are and mark them as heights above the ground (GeoJSON with an elevation_mode property of relative, KML with the relativeToGround altitude mode), so importing the file back into SiteCAD gives the same offsets. DXF cannot mark a height as above the ground, so a DXF export writes each point's real elevation, the ground under it plus its offset. That is what CAD software expects, and SiteCAD's DXF import converts it back into the same offsets. If the ground under any point of a path is unknown when you export to DXF, for example because no terrain is loaded, that path is written flat at height 0 and imports back following the ground. LandXML and Shapefile exports carry a path's line without its heights.

Which format should I use?

For CAD users: DXF or STEP. For GIS: GeoJSON or Shapefile. For Google Earth, with boundary colors: KML/KMZ. 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 that carry the wrong extension, and tells two formats apart when an extension is shared.
  • 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.

Path Heights

When a file gives heights for a path's points, SiteCAD stores each one as an offset above the ground at that point. A height the file marks as above the ground (a GeoJSON elevation_mode property of relative, or KML's relativeToGround altitude mode) is kept as it is. KML's default clampToGround mode ignores heights, so those points follow the ground. Any other height is treated as an absolute elevation (above the WGS 84 ellipsoid in GeoJSON, KML, Shapefile and LandXML, and in the site's local coordinates in DXF) and the ground height under the point is subtracted, so the path sits where the file put it. Where the ground under a point is not known, for example because no terrain is loaded, that height is dropped, the point follows the ground, and the import warns how many heights it could not keep. Points with no height follow the ground; in DXF a height of exactly 0 counts as no height.

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

FormatExtensionWhat It Imports
GeoJSON.geojsonBoundaries (Polygon, with holes), traces (LineString), control points (Point)
Shapefile.shp/.zipBoundaries (with holes), traces, control points; a ZIP holding several shapefiles imports all of them, each with its own projection and text encoding
KML / KMZ.kml/.kmzBoundaries (with their colors and holes), traces, control points
CSV.csvControl points, entity metadata, custom tabular data
DXF.dxfClosed polylines as boundaries, open polylines as traces, points as control points
DWG.dwgThe same as DXF: SiteCAD converts the drawing to DXF in your browser and imports that. AutoCAD R14 through 2018 drawings are supported. The first DWG you open after the page loads downloads a converter of about 25 MB from SiteCAD, so it needs a connection. Import only — export DXF, which AutoCAD opens and can save as DWG. If a conversion fails, save the drawing as DXF in your CAD software and import that.
LandXML.xmlSurvey control points, alignments, parcels, and TIN surfaces (each as a new terrain layer)
GeoTIFF.tifElevation rasters and orthophotos, baked onto a terrain layer
Scenario Bundle.scenario.yamlA whole scenario as readable YAML, binary content as base64 text, with fresh IDs unless the file names a library
Scenario Snapshot.scenario.snapA whole scenario, including binary content and sync history, from a SiteCAD version that stores data the same way

How To Export & Import

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

Exporting

1

Select the entities you want to export (or export all)

2

Open the menu and choose Export

3

Pick a format and configure options

4

Click Export to save the file

To save a whole scenario instead, open the Sites & Scenarios panel, press Export Scenario on the open scenario, then choose the YAML bundle, the snapshot or the archive.

Importing

1

Open the menu and choose Import, or drag a file into the editor

2

SiteCAD auto-detects the format

3

Review the preview — check entity counts and coordinates

4

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.

Converting Files With SQL

A file can be read into rows, changed with SQL and written back out as a file, and the output format does not have to match the input. Filter rows with where, join them to your scenario's tables, or compute new columns on the way through.

csv_rows reads a CSV, with every cell as text in col_0, col_1, and so on; csv_parse_cell turns a text cell into a number. geojson_features reads a GeoJSON file, one row per feature. csv_file and geojson_file write rows out. Each function's columns and options are listed in the SQL console's completions and its Functions tab in SQL mode. If you only need a CSV with a different separator, quote character or header row, see CSV Separators, Quotes and Header Rows.

Example: Wells From a Survey CSV

This script takes a CSV with the columns name, lat, lon, kind and saves the rows whose kind is well as GeoJSON points. Rows without both coordinates are left out. Open the Command console (the S key), paste it in JS mode and press Execute; it asks for the CSV, then downloads wells.geojson.

const file = await kit.openFilePicker({ accept: ['.csv'] });
const src = await kit.createImportHandle(file);
const out = await kit.createExportHandle('wells.geojson', 'application/geo+json');
await runSQL(`
  select geojson_file(?, col_0, 'Point',
    '{"type":"Point","coordinates":[' || csv_parse_cell(col_2, 'REAL') || ',' || csv_parse_cell(col_1, 'REAL') || ']}',
    null)
  from csv_rows(?, '{"max_columns": 4, "header": true}')
  where col_3 = 'well'
    and csv_parse_cell(col_1, 'REAL') is not null
    and csv_parse_cell(col_2, 'REAL') is not null
`, [out.id, src.id]);
await kit.downloadHandle(out.id);

You can also attach the file in the Agent panel and ask for the same thing: “Keep only the wells from the attached CSV and give them back to me as a GeoJSON file”. A file you pick or attach can be read until the page reloads, or until it has gone 30 minutes unused.

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 Layers tab. 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

To move a whole scenario between SiteCAD instances or share it with a colleague, open the Sites & Scenarios panel, press Export Scenario on the open scenario and choose a bundle or a snapshot.

Scenario Bundle (.scenario.yaml): Every row of the scenario — entities, parts, properties, bindings, triggers, drawings, templates, user tables, terrain and imported imagery — as readable YAML. It does not depend on how SiteCAD stores data, so it still imports after an update changes the storage format; it can be read, edited and diffed in source control, and imported rows get fresh IDs. Leaves out the viewer-captured base imagery the destination rebuilds, and sync history.

Scenario Snapshot (.scenario.snap): Everything in the scenario, including binary content and its full sync history, in one compact file whose integrity is checked on import. Imports only into a SiteCAD version that stores data the same way as the one that wrote it. After an update that changes the storage format, an older snapshot will not import.

Keeping a Record: Archives

To keep a record of the scenario rather than a copy to work on — to close a period, say — choose the third format, Archive (.scenario.archive): A read-only record of the scenario to keep, optionally signed: every row of the scenario and its recordings, and its state at the end of a period you choose, with a checksum that shows the file is undamaged. Any later version of SiteCAD can check and read it, whatever storage format it uses, and so can any tool that reads gzipped JSON. Can't be imported as a scenario to edit. Leaves out imagery captured from a commercial provider, which may not be passed on. Next… asks for its name, the end of the period it records, the earlier archive it amends if any, and the signing keys to sign it with. The history browser’s newest point offers the same export.

Archive file… in the Sites & Scenarios panel, or Import Scenario given an archive, checks a file’s checksum and signatures without opening it. From there you can add your signature to a copy, add the signatures of another copy of the same archive, or copy the archive into a new site to work on; its machine readings stay in the archive.

Open read-only in the same panel shows the archive in place of the open site as a temporary copy, readings included, with the clock at its period end; move the clock to see changes dated after it. Nothing in it can be edited, nothing is saved, and no account or connection is needed. A banner across the editor names the archive; its Close returns to the site you had open.

Continue Learning

Core ConceptsSites, scenarios, entities, and coordinates
TerrainElevation data, contours, and grading
Export & Import FeaturesFormat details and use cases
Getting StartedCreate your first site in 10 minutes