Mazzap is a local-first digital twin viewer and processing workflow for terrain + vegetation + buildings + hydrology.

It provides:

• an upload-driven workflow for source data,
• automated processing pipelines,
• a Three.js web viewer with interactive layer controls.

From uploaded source data, Mazzap can generate and render:

• DEM terrain from LiDAR,
• shrubs + trees from LiDAR,
• building footprints from a FileGDB footprint source,
• soil polygons (SSURGO) clipped and themed over DEM,
• hydrology streams clipped to the DEM scene,
• building meshes (photogrammetry assets) matched to footprint names.

• Node.js (recommended: Node 18+)
• npm

• pdal
• gdalinfo, gdalsrsinfo, ogr2ogr, ogrinfo, projinfo
• blender (required only for per-building photogrammetry asset generation)

If these commands are missing, relevant pipeline steps fail with explicit errors.

From project root:

npm install
npm run start

Open:

http://127.0.0.1:3000

Use the in-app Upload Data Source modal. Each queued item has a type dropdown.

• Upload type: LiDAR
• Accepted source examples: .copc.laz, .laz, .las
• Normalized storage in app: Raw Data Inputs/lidar_input.*

• Upload type: Footprints
• Expected format: Esri FileGDB folder
• Normalized storage: Raw Data Inputs/Footprints.gdb/

• Upload type: Hydrology
• Expected format: shapefile set
• Minimum practical requirement: .shp
• Strongly recommended together: .shp + .shx + .dbf + .prj
• Normalized storage: Raw Data Inputs/Hydrology/

• Upload type: Soils (SSURGO)
• Recommended upload: full Web Soil Survey export folder (includes spatial/, tabular/, optional .mdb, metadata)
• Minimum for visible overlay: map unit polygon shapefile in spatial/
• Normalized storage: Raw Data Inputs/SSURGO/

• Upload type: Photogrammetry
• Typical files: .glb, .gltf, .obj, .ply
• Stored with original names in Raw Data Inputs/
• Meshes are matched to footprint names set in the Buildings editor

1. Click Upload Data Source.
2. Drag/drop files or use file/folder pickers.
3. Set each item’s type correctly.
4. Click Upload Selected.
5. A progress popup appears and runs required processing steps.

• LiDAR upload triggers: DEM -> Soils/Hydrology (if present) -> Shrubs -> Trees
• Footprints upload with LiDAR available triggers: Generate Footprints
• Hydrology upload triggers hydrology processing if DEM exists (or can be generated from LiDAR)
• SSURGO upload triggers soils processing if DEM exists (or can be generated from LiDAR)

The viewer refreshes layers after processing.

• Show/hide shrubs, trees, building assets, building footprints, soil data, hydrology.

• Vertical exaggeration slider.
• Reset view.

• Independent shrub and tree density controls.

• Stream width
• Stream depth (0.0m is centered in slider range)
• Flow speed animation
• Snap Hydrology To Terrain to re-fit streams onto current DEM terrain

• Soil polygons are draped over DEM with thematic colors.
• A right-side Soil Legend is shown when Soil Data layer is visible.

• Click footprint outlines to select.
• Name footprints.
• Process and load matched building assets.
• Move/rotate loaded assets and save transforms.

Use Manage Data Sources in sidebar footer to:

• list currently staged raw sources,
• delete individual sources,
• Clear Data (wipe raw + processed data contents and restart from scratch).

If you prefer CLI/manual runs:

npm run dem
npm run vegetation
npm run trees
npm run buildings
npm run hydrology

Per-building mesh generation:

npm run building-asset

Or full batch (without hydrology):

npm run all

Generated outputs are under Processed Data/, including:

• dem.tif
• vegetation/*
• trees/*
• buildings/*
• soils/*
• hydrology/*

• Verify hydrology output exists and is non-empty:
  • Processed Data/hydrology/hydrology_clipped_local.geojson
• Ensure source includes geometry (.shp) and preferably sidecars (.shx, .dbf, .prj).
• Ensure hydrology and DEM extents actually overlap.
• Ensure Show Hydrology is enabled.

• Verify soils output exists and is non-empty:
  • Processed Data/soils/soils_clipped_local.geojson
• Ensure SSURGO upload included the map-unit polygon data in spatial/.
• Ensure DEM exists (soils processing clips/reprojects to DEM extent).
• Ensure Show Soil Data is enabled.

• Footprint pipeline likely did not run or failed.
• Verify Raw Data Inputs/Footprints.gdb is present and valid.

• Prefer the current per-file upload flow (default in UI).
• Retry with smaller batches if system resources are constrained.

• Restart server after pulling/updating code:
  • npm run start

• Assets/ is used for vegetation model templates.
• Building photogrammetry source meshes come from Raw Data Inputs/.
• For best reproducibility, upload through the UI so naming contracts are normalized automatically.