Guide

Asset Preparation

How to prepare drone, survey, and CAD source files for SiteCAD — and how to choose between local owned-tile bakes and geostore uploads for terrain, imagery, and 3D models.

Choosing an ingestion path

SiteCAD has two ways to bring source data into a site: owned-tile bake (browser parses the file and writes editable tiles on the editing layer) and geostore upload (file goes to Cesium Ion via the backend; the layer references it as a base provider). Pick by aspect:

AspectOwned-tile bakeGeostore uploadRecommendation
Terrain (DTM)GeoTIFF bake — single-band elevation imported in-browser, stored as editable owned tiles.Upload a higher-resolution Ion-hosted DTM as the layer base provider (no per-tile bake).Owned-tile bake for sub-site rasters you intend to edit; geostore for survey-grade base coverage.
Imagery (Ortho)GeoTIFF bake — 3- or 4-band orthomosaic baked into the layer’s owned imagery tiles.Upload an orthomosaic asset as the layer’s imagery base provider.Owned-tile bake is fastest for small areas; geostore for site-wide coverage.
3D Model / MeshNot supported — meshes are never baked locally.Upload a zipped OBJ with its materials and textures, a GLB, or a zipped 3D Tiles tileset as the layer’s 3D model; Ion tiles it into 3D Tiles.Geostore is the only path. Upload the OBJ zip where you have one: it keeps the full-resolution source.

DTM-first principle:

Make the layer’s terrain source a bare-earth DTM. Imagery drapes sharper over it, and cut/fill volumes match real grading work.

Terrain (DTM)

A digital terrain model represents the bare ground surface — no buildings, no canopy. SiteCAD accepts DTMs through both ingestion paths.

Accepted formats & constraints

.tif / .tiff (GeoTIFF)Float32 / Int16 / UInt16 elevation; LZW or Deflate; tiled or stripped; COG OK.
CRSA WGS84 UTM zone, Web Mercator, or latitude/longitude on WGS84 (EPSG:4326, and ETRS89 / GDA94 / NZGD2000) — reprojected to WGS84 via proj4. State Plane, national grids and historical lat/long systems (OSGB36, NAD27) are refused by name; re-export in a UTM zone.
ResolutionSite editing LOD targets ~1 m vertex spacing. Higher resolution is downsampled; lower resolution is bilinearly upsampled.
NoDataPixels flagged NoData fall through to the base provider — no holes, but coverage gaps remain visible at lower layers.

Recommended export paths

WebODMSet Processing Profile → "DTM". After processing, download odm_dem/dtm.tif from the task assets.
Agisoft MetashapeWorkflow → Build DEM → Source data = Dense Cloud + Point classes = Ground → Export DEM as GeoTIFF.
Pix4DOutputs → DTM. Export as GeoTIFF (.tif).
QGISFor an existing DSM, run "Clip raster by mask" with a ground mask, or use the SAGA "DTM Filter" tool.

Imagery (Orthomosaic)

Orthomosaics are top-down, georeferenced color images of the site. They drape over terrain and provide ground truth for placement and grading.

Accepted formats & constraints

.tif / .tiff (GeoTIFF)3-band RGB or 4-band RGBA. Tiled, stripped, or COG.
CRSSame rule as terrain: a WGS84 UTM zone, Web Mercator, or latitude/longitude on WGS84; reprojected to WGS84 for tile alignment.
Alpha / nodataTransparent pixels (alpha = 0 or all-nodata) are skipped during the bake.

Recommended export paths

WebODMDefault odm_orthophoto/odm_orthophoto.tif. 3-band by default; enable transparent background for 4-band.
MetashapeWorkflow → Build Orthomosaic → Export as GeoTIFF, "Write tiled TIFF" enabled.
Pix4DOutputs → DSM, Orthomosaic, and Index → Orthomosaic GeoTIFF.

3D Model / Mesh

3D models are the photogrammetry or LiDAR surface mesh — buildings, trees, ground, and surface detail. They render as a 3D Tileset over terrain and can be clipped per layer.

Geostore only:

There is no owned-tile bake for meshes. A layer’s 3D model uploads to the geostore, where Cesium Ion tiles it as uploaded, the ground it captured included. SiteCAD checks the file before sending it and places the model from its coordinate system and offset: read from the file when it carries them, asked for when it does not, never guessed.

A layer’s 3D model (Layer editor → 3D Model → Upload new…)

.zip (OBJ)Preferred. An OBJ with its .mtl and texture files, such as WebODM’s Textured Model download. It keeps the full-resolution source, which later operations can cut from. A coords.txt inside the zip places it; without one SiteCAD asks for the coordinate system and offset.
.glbglTF 2.0 binary. SiteCAD asks for its coordinate system and offset. WebODM’s own GLB is refused (see the export paths below).
.zip (3D Tiles)A zipped tileset (tileset.json + tiles), such as WebODM’s 3d_tiles folder. Accepted, and it places itself, but it leaves no full-resolution source.

A mesh entity (Mesh inspector → Upload Model… / Upload Tileset…)

.objWavefront OBJ as a single file: its .mtl and textures cannot come with it, so it renders untextured. Zip a textured OBJ and upload it as a layer’s 3D model instead.
.gltf / .glbglTF 2.0 — preferred for single-file meshes with PBR materials.
.fbxCommon photogrammetry export from Metashape / RealityCapture.
.daeCOLLADA — accepted but glTF is preferred where available.
.las / .lazPoint clouds. LAZ is compressed LAS; both stream into 3D Tiles.
.kmzKML zipped with referenced models. Useful for legacy datasets.
.citygmlCityGML LoD1–LoD3 building / city models.
3D Tiles directoryPre-tiled output (tileset.json + tiles). Upload via "Upload Tileset…" in the Mesh inspector.

Recommended export paths

WebODMDownload Textured Model (textured_model.zip) and upload it as the layer’s 3D model. When asked, load odm_georeferencing/coords.txt from the All Assets download, or enter its two lines. Don’t upload WebODM’s GLB: it records the model’s position in a form no 3D viewer places correctly, so SiteCAD refuses it.
MetashapeWorkflow → Build Mesh → Export Model → OBJ with textures (zip the .obj, .mtl and textures) or glTF (.glb). As a layer’s 3D model, SiteCAD asks for the coordinate system it was exported in and any offset applied on export.
RealityCaptureExport Model → OBJ + texture atlas (zip them together) or glTF (.glb) with textures embedded.

Common pitfalls

Most failed uploads come down to one of these. Check them before re-running a long photogrammetry export.

Uploading a DSM instead of a DTM

Buildings and tree canopies appear as terrain. Brush edits work but cut/fill volumes will be wrong.

Missing CRS tags

A GeoTIFF without GeoKeys (ProjectedCSTypeGeoKey / GeographicTypeGeoKey) cannot be georeferenced. Re-export from your photogrammetry tool with CRS metadata enabled, or assign one in QGIS via gdal_edit.

Wrong band layout for imagery

SiteCAD reads bands 0–2 (RGB) or 0–3 (RGBA). A 1-band grayscale ortho or band order outside that range will look wrong; re-stack bands in QGIS or via gdal_translate -b 1 -b 2 -b 3.

Forgetting to bring textures with OBJ uploads

An OBJ names its material (.mtl) and texture files, and SiteCAD refuses a zip that is missing any of them, naming what is missing. Zip the .obj with every file it names, in the same folders, or upload WebODM’s Textured Model download as it is. A single .obj sent through the Mesh inspector’s "Upload Model…" goes without them and renders untextured gray.

Exporting a GLB without its textures

A GLB can keep its textures in separate image files beside it, but only the .glb is uploaded, so SiteCAD refuses one that does, naming the files. Export it again with textures embedded, or upload an OBJ zip with its textures.

Heights measured from the wrong surface

A 3D model’s heights are measured from the WGS84 ellipsoid or from sea level, and the file does not say which. Answer what the heights are measured from when SiteCAD asks, after you pick the file: a wrong choice puts the model tens of meters above or below the terrain. Photos from an RTK drone record ellipsoid heights, the default. A 3D Tiles tileset places itself, so the choice does not apply to one.

Hitting the geostore quota

Free tier allows ~500 MB / 5 uploads; Starter ~5 GB / 50; Pro ~50 GB / 500; Enterprise removes the cap. Delete unused assets in the Asset Library before uploading large drone runs.

End-to-end workflow

The full path from drone flight to a usable SiteCAD layer.

1

Capture

Drone photogrammetry (RGB + RTK if available) or terrestrial / aerial LiDAR.

2

Process

Run photogrammetry (WebODM, Metashape, Pix4D, RealityCapture) or LAS classification.

3

Export

Three outputs: bare-earth DTM (.tif), orthomosaic (.tif), and textured mesh (OBJ zip or .glb). Verify CRS tags are present.

4

Choose ingestion path

Owned-tile bake from the Layer Panel for small editable rasters, or geostore upload from the Layer Editor for site-wide base providers and meshes.

5

Select in Layer Editor

Open the layer’s editor and pick the new asset for terrain, imagery, and 3D model rows. The layer takes effect immediately — brush, contours, and cut/fill recompute on the next interaction.

Continue Learning

Terrain GuideLayers, brush tools, contours, and cut/fill
Import & ExportExchanging data with CAD and GIS tools
Survey & RTKGPS / RTK point import and stake-out
Core ConceptsSites, scenarios, entities, and coordinates