The map that processes
your own data.
Upload an aerial scan and it comes back as buildings with real roof shapes, terrain and trees. Upload a Rhino, SketchUp, IFC or Revit model and it stands in its real street with every layer, name and colour kept. All of it on the Cityweft map, next to the buildings we reconstructed for whole countries, and in every export.
- Your aerial scan28 million points
- Rebuilt from it430 buildings, LoD 2.2, real roof shapes
- Your uploaded modela Rhino block, 305 parts, its own colours
- Cityweft Globalthe city around it, on your terrain
Two kinds of upload
Processed by the same pipeline, exported with the same city
Every dataset, geolocated, next to the city model.
A drone flight over an old town, a Rhino model on a harbour front, a SketchUp house in a suburb: each one is placed where it belongs and shown on the same map as the buildings, terrain and trees Cityweft reconstructed for whole countries. Any project drawn over it picks it up.
Alfama rooftops, drone flight
0.42 km² · 318 buildings · 140 trees · 0.25 m terrain
Open dataset
Everything on one map. The point cloud in one tool, the city model in another, the architect's model in a third, the survey report in a shared folder, the context fetched by hand. My Data puts your scan, your model and our city model in one place, in the same coordinates, with the same terrain under all of it.
Processed, not just stored. A point cloud is a billion dots until someone classifies it and reconstructs the buildings. That used to be days of specialist work per survey. Drop the file and the roofs appear as real building models, with terrain and trees, and a fit rating for every building.
Context comes along on the way out. You don't export your model. You export your project with the city around it, in the format your tool reads. Your own file travels through untouched, and your organisation's models stay organised on one map.
The same upload button, four different reasons to press it.
Architects and urban designers
Getting a model into real context takes a day of fetching, converting and aligning.
Drop your model in. It stands in its real street in minutes, and exports with the city around it.
Surveyors and drone operators
The deliverable is a point cloud the client cannot use.
Deliver buildings, terrain and trees, not dots. Upload the scan; Cityweft classifies and reconstructs it.
Developers and planners
Context data for a site is scattered across tools and folders.
One map for the site: your survey, your design, our city.
Engineers on Revit and IFC
Exports lose the native model on the way.
Your Revit or SketchUp file travels through untouched and comes back inside a city model.
The same pipeline that built the country models.
The classifier and the roof reconstruction behind the upload button are the ones we run at national scale: more than 200 trillion LiDAR points turned into whole-country 3D maps. A drone survey of a city block is a few hundred million points; the map it lands in is a million times larger. Your scan gets the same treatment, in minutes.
Stages, in order
- 1Inspect
- 2Normalize
- 3Footprints
- 4Classify
- 5Scan footprints
- 6Roofs
- 7Terrain
- 8Canopy
- 9Trees
- 10Publish
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.
Before you upload
Which files can I upload?+
Aerial LiDAR as LAS, LAZ or COPC, classified or not, up to 10 GB per dataset. 3D models as 3DM, SKP, IFC, DXF, glTF or GLB, OBJ, STL, PLY, DAE, FBX, 3MF and Revit, with their textures, .bin or .mtl files. Anything else, photos, PDFs, drawings, is stored and pinned to its place on the map.
How long does processing take?+
Minutes for a typical drone survey of a few hundred buildings; a city-scale scan runs longer. You see every stage's progress, and the result loads into the map the moment it is done. Placing a model usually takes under a minute.
How good are the buildings?+
Every roof is reconstructed as an LoD 2.2 model from the scan's own points, and every building gets a fit rating, good, check or poor, against the scan's roof heights. Typically 99 % of roofs are within 1 m; the exact figure depends on the dataset and is in the report.
What about coordinate systems?+
Any projected system. We read it from the file and ask only when it carries none. A model is placed by its own georeference, a Rhino Earth Anchor Point, an IFC map conversion or DXF geodata, by a coordinate system you name, or by a point you pick on the map and turn into place.
Who can see my uploads?+
Nobody outside your workspace. Uploads made with an organisation active belong to the organisation: every member can view them, use them in projects and export; the uploader and the organisation's admins can change or delete them. Personal uploads stay personal.
What does a free account get?+
Five uploads, 5 GB kept and 1 GB of scans processed a month, with previews of everything. Exporting a project that uses your data is part of Professional, Small Business and Business, which also keep 50 GB to 1 TB and process 15 GB to 60 GB of scans a month.
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.