Upload a point cloud,
get a city.
An aerial scan from an aircraft or a drone, classified or not, in any coordinate system. The pipeline that built our country models tells ground, buildings, vegetation and water apart, rebuilds every roof, models your terrain and measures every tree. Minutes later it is on the map, with the city around it, ready for Rhino, Revit, SketchUp or IFC.
Billions of dots in. Clean geometry out.
On the left, a real aerial scan of 28 million points. On the right, what our pipeline built from it: every roof an LoD 2.2 building with its real shape, every tree a sized instance, the ground a surface at scan resolution. Drag to compare, then export it as native geometry for the tool you work in.
Exported as native geometry for
Rhino
Revit
SketchUp
IFC
DXFand moreA scan, straight from the flight.
Aerial LiDAR
LAS, LAZ or COPC tiles from an aircraft or a drone, classified or not, colour optional, in any projected coordinate system. We read the coordinate system from the file and ask only when it carries none. Up to 10 GB per dataset.
Drone photogrammetry
Point clouds exported from photogrammetry as LAS or LAZ work too. Without return numbers, trees and roof edges come out a little less precise than from LiDAR, so the fit rating per building matters more.
Your own footprints
Optional: a GeoJSON, GeoPackage or FlatGeobuf of building outlines. Your outlines win over Cityweft Global, and the scan fills in the buildings they miss.
Add to My Data
An aerial LiDAR scan, a 3D model, or any file to pin on the map. We read what the files carry and ask only for what is missing.
Aerial scan
LiDAR from aircraft or drones
3D model or file
Models processed, other files pinned
Street scan
Vehicle or tripod
ComingDrop a LiDAR scan or a 3D model here or click to choose
Scans: aerial or drone LiDAR as LAS, LAZ or COPC tiles, classified or not, up to 10 GB. Models: 3DM, SKP, IFC, DXF, glTF, OBJ, STL, FBX or 3MF with their textures. Anything else is pinned on the map.
Name
Uploading to Studio North — visible to everyone in the organisation.
Private to you and Studio North — no one else can access your data. Files are deleted together with the dataset.
More options
CRS, survey date, classification, building outlines, elevation offset
Stage by stage, the way the pipeline runs.
Every stage is versioned. When the pipeline improves, your dataset offers a re-run from the first stage that changed; everything before it is reused, so it is usually minutes, not a full run.
- 1
Inspect
Point count, density over the area the scan actually covers, the coordinate system from the file, and a check whether the file's own classes can be trusted.
- 2
Normalize
Reprojected to one metric frame, outliers flagged, noise below the water floor removed. Dense drone clouds are thinned for reconstruction; the full cloud stays for terrain and trees.
- 3
Footprints
Your own outlines if you uploaded them, else Cityweft Global. Where the scan shows a roof and no outline exists, the outline is derived from the scan itself, so new construction gets a building too.
- 4
Classify
Ground, buildings, vegetation and water. Our own rules, or Cityweft's own classifier trained on national LiDAR.
- 5
Roofs
Every footprint becomes an LoD 2.2 building with its measured roof planes. Each one gets a fit rating, good, check or poor, against the scan's own roof heights.
- 6
Terrain
A bare-earth model from your ground points at 0.5 m, down to 0.25 m when the scan supports it, water flattened, blended into Cityweft's terrain at the edge.
- 7
Trees
Every tree located and measured: height and crown width, placed as a sized tree in the map and in every export.
On the map the moment it is done.
My Data
Harbour district survey
Uploaded by a teammate — you can view it, use it in projects and download its files. The uploader and organisation admins can change or delete it.
Results
Buildings
1,184
of 1,242 footprints · 34 not reconstructed · 24 at the scan edge
Trees
6,412
median 9.8 m · 23.7/ha
Terrain
0.5 m cells
IDW · 14.2 ground pts/m² · levels 0.25 / 0.5 / 1 / 2 m
Covered area
2.71 km²
EPSG:25832 · 91.6 M points
Roof quality
Roof heights
99% within 1 m
typical error 0.24 m against the scan's roof tops · 1,150 buildings scored
Roof fit
0.21 m
typical gap between the roof and the points · 9 in 10 roofs within 0.46 m
Buildings to check
24
9 poor fit · 15 worth a look · coloured on the map under Roof fit
Roof shapes
91% pitched
1,047 pitched · 103 flat · 34 without roof points
Processing
Point density
34 pts/m²
91.6 M points · RGB colour · DVR90
Classes
From the file
ground from the file
Water
3 bodies
48.2 ha flattened
Roof repairs
26
4 ramps left · 78 roofs without footprint
Replace or overlay
Inside your scan, your buildings, terrain and trees replace Cityweft's, or sit on top as their own layer. Your choice, per project.
Your terrain under everything
Roads, trees and the surrounding buildings stand on the ground your scan measured, at 0.5 m instead of the 1 m and coarser of global terrain.
A report you can read
Buildings reconstructed, outlines derived from the scan, trees with their heights, terrain resolution, and the buildings worth a second look, coloured on the map.
A project in one click
Start a project here draws the area of your scan on the project map. From there it exports like any other Cityweft project.
Draw an area over it. It is in the model.
Start a project from the dataset page or draw any area over the scan on the project map. The My Data card shows what covers it and lets you choose Replace or Overlay. Generate, and the scan's buildings and trees stand on the scan's own terrain, with Cityweft's roads and surfaces around them.
Model settings
Set your details, then generate a free preview.
Area
Terrain
Building data
My Data
Inside your scans, your buildings, terrain and trees replace Cityweft's.
Harbour district survey
covers the whole area · 1,184 buildings · 6,412 trees · 0.5 m terrain
Notes
- 3 water body polygon(s) (48.2 ha): 1,204,118 points over water ignored, terrain flattened at the shoreline level.
- 6,412 trees detected from the scan (position, height and crown diameter; placed as sized tree instances); 1,290 treetops inside building footprints were suppressed.
- 78 building outline(s) (31,420 m²) were derived from the scan where the outline sources had none; the other 1,184 come from Cityweft Global.
- 24 footprints at the edge of the scan were skipped (partial coverage).
- 99 %
- of roofs within 1 m of the scan's own heights
- typical, depends on the dataset
- 1,723
- building outlines derived from one downtown scan in under a minute
- 82 million points, one run
- 0.25 m
- terrain resolution when the scan supports it
- every dataset
- 20 min
- for a 33-million-point city scan, from upload to buildings
- a typical run
Native where the format allows it.
Rhino
Layers per type with sub-layers, every attribute as user text, trees as block instances, the terrain as a NURBS surface, the Earth Anchor Point set.
Revit
A native .rvt built by Revit in the cloud: the terrain as a Toposolid with sub-divisions for roads and surfaces, each building a selectable mass, three schedules, the survey point set.
SketchUp
Groups per type, trees as components, tags you can switch, the model geolocated so it lines up with Add Location imagery.
IFC
IFC4 or IFC 2x3 with a site, a building and a storey, buildings as proxies and terrain as geographic elements, property sets on every element, the map conversion set.
DXF, glTF, FBX, 3MF
Layers and blocks in DXF with a smooth terrain mesh, node names and extras in glTF, instancing and an embedded terrain texture in FBX for Twinmotion, Lumion and game engines.
What people upload, and why.
A survey the client can use
A surveyor delivers the scan and the processed model together: buildings with their roofs, the terrain, the trees, exportable to whatever the client designs in.
A drone flight over the site
An afternoon's flight becomes the site's own context: outlines derived from the scan where the map has none, the ground exactly as it was flown.
New construction the maps don't know yet
A district still under construction, a campus just finished. The scan outlines every building itself, so the model is current.
Context for a competition entry
The real neighbourhood, at scan resolution, under the design. Replace mode takes out the buildings on the plot and keeps everything around it.
A municipality's own flight
Public LiDAR of a town, processed once, available to every project in the organisation, kept up to date with a re-run when the pipeline improves.
Included on every plan. Sized by the plan.
| Pay-as-you-go | Professional | Small Business | Business | |
|---|---|---|---|---|
| Storage for your uploads | 5 GB | 50 GB | 250 GB | 1 TB |
| Point cloud processed per month | 1 GB | 15 GB | 40 GB | 60 GB, then €3 per GB |
| Uploads | 5 in total | Unlimited | Unlimited | Unlimited |
| Largest file | 1 GB | 10 GB | 10 GB | 10 GB |
| Export projects that use your data | Preview only | Unlimited | Unlimited | Unlimited |
| Allowances | Per user | Per user | Pooled across the organisation | Pooled across the organisation |
- A scan counts its file size when a run starts. Models and pinned files never count as processing.
- In replace mode, the part of a project your own scan covers is not counted against the km² allowance. A project entirely inside your scan exports free.
- Free accounts upload and preview. Every subscription exports without limit.
Bring your first scan or model.
Upload once. It is on the map with every project that touches it, and in every export you make from there.