Skip to content
Cityweft
Open
My Data · 3D models

Your model, in its street.
Every layer still there.

Upload a Rhino, SketchUp, IFC, DXF, glTF or Revit model. It is placed in the real city with its names, layers, colours and materials, it replaces the building that stood on its plot, and when you export the same format you get your original file back, inside the city model. Your organisation's models, organised on one map, never lost.

Real upload · Rhino · .3dm
Loading the model
One environment

Your upload, your scan and the city, in one model. Ready to export.

Everything on this page lives in the same Cityweft environment: the model you uploaded, the buildings reconstructed from your scan, and Cityweft Global around them. One project, one export, in the format your tool reads.

Export model
Loading the map

Exported together as

RhinoRevitSketchUpIFCDXFand more
Formats in

Thirteen formats, read for what they carry.

  1. Rhino 3DM

    Meshes, Breps and extrusions as render meshes, nested blocks, the layer tree with colours, materials and transparency, object names, user text, and the Earth Anchor Point.

  2. SketchUp SKP

    Groups, components, materials and tags, read as they are, and the geolocation when the file has one.

  3. IFC 2x3, 4 and 4x3

    Elements with their classes, surface styles and storeys, placed by the map conversion or the site's coordinates and true north.

  4. DXF

    Meshes, 3D faces, polyfaces and block inserts, layer and true colours, the drawing's units and geodata.

  5. glTF, GLB, OBJ, STL, PLY, DAE, FBX, 3MF

    Node names and colours, units from the file where it declares them, Cityweft's own extras when the file was exported from Cityweft.

  6. Revit RVT

    Converted to IFC by Autodesk Platform Services first, then read like an IFC: elements, categories and colours. A Revit export of a project that includes the model is built into your own file.

Up to 2 million triangles per model. Textures and companion files travel with the upload and are kept with it.

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

Coming

Drop a 3D model or any file here or click to choose

Models — 3DM, SKP, IFC, DXF, glTF, OBJ, STL, FBX or 3MF with their textures, .bin or .mtl (up to 2 M triangles) — are processed and placed. Anything else — photos, PDFs, drawings — is pinned on the map.

Name

e.g. Competition entry, option B

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.

Position and units

Placement

From the file, or on the map after processing

Model unit

From the file

Up axis

From the file

A 3dm EarthAnchorPoint, an IFC map conversion or DXF geodata places the model by itself; you can move or turn it on the map afterwards.

CancelUpload & process
A model upload: placed from the file, by a coordinate system or on the map, with unit and up axis read from the file.
Placed where it belongs

Three ways to the right spot. Seconds to move it.

My Data

harbour_pavilion_v3.3dm

Model · 3DMReadyView only1 file · 9 MB · EPSG:25832
Start a project here

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 (components)

1

3DM file · 46,210 triangles

Parts

412

412 with their own colour · unit m · Z up

Footprint area

2,860 m²

EPSG:25832

Native export

3DM

the original file is embedded in these formats

+−
Coverage Model footprint (1)
A Rhino upload on its dataset page: 412 coloured parts, the footprint traced on the map, native export as 3DM.

3D model

The model as it was read from your file, with its parts and colours — the same geometry that goes into projects and exports.

Show model

Position

Placed from the file's own georeference (earthAnchor). Rotation 0.4° from north · 55.71024, 12.59612 · sits on the terrain

Notes

  • No base elevation given — the model is placed on the terrain at its centroid in each project.
  • Placed from the file's own georeference (earthAnchor).
Placed from the file's own Earth Anchor Point, 0.4° from north, standing on the terrain.

My Data

ReplaceOverlayOff

Inside your scans, your buildings, terrain and trees replace Cityweft's.

harbour_pavilion_v3.3dm

covers ~9% · 1 building

Keep models whole
Keep models whole: your model is placed complete, even where it reaches past the drawn area.
  1. From the file

    A Rhino Earth Anchor Point, an IFC map conversion, DXF geodata or Cityweft's glTF extras place the model by themselves.

  2. By a coordinate system

    Name the projected system the file's coordinates are in, a national grid or a UTM zone, and the x and y are used as they are. No rotation, nothing to drag.

  3. On the map

    The model's real plan outline on the imagery: click where it belongs, drag it, turn it with a ring, snap to 90°. Exact values if you have them.

Heights are decided per project, not at upload: keep the file's own heights, set the model on the terrain, or give the ground level above sea level, the ±0.00 of the plans. Moving or turning a placed model re-runs only its placement, in seconds.

In replace mode the model takes the place of the Cityweft buildings under its footprint. It is never cut at the project boundary: your models are placed whole.

Three files, one project

A SketchUp tower, an IFC condo and a Rhino block. One export.

Three uploads from three tools, each placed where it belongs and kept whole, exported together with the city around them.

A city model with a SketchUp tower, an IFC condominium and a Rhino block of buildings standing among the reconstructed city
  • SketchUp Art Deco tower
  • IFC 12-storey condo
  • Rhino 34-building block
A project export with three uploaded models standing in the Cityweft city model, each with its own geometry and colours.
Kept native

Export the same format, get your file back.

Your upload is stored byte for byte. When a project that includes it is exported in the same format family, the original file is embedded as itself, through the library the exporter writes with. Every other format receives a structured copy: the geometry with its part names, layers and flat colours.

Export Model

Configure your export and download.

All formats

Rhino

Native .3dm — a layered model with NURBS terrain and georeferencing.

Features

GeoreferencedBlock instancesBuildings & structuresRoads, land use & topographyTrees & vegetationLayered model, with metadataMaterials & coloursNURBS Terrain
Your model “harbour_pavilion_v3” · original 3DM embedded

Settings

Version
Rhino 8Rhino 7
Surface
GeometricRaster & Satellite
Trees
BasicPrecise
Coordinate systemLocal coordinates

Centered on the site, no map grid. Choose one to line the file up with surveys, GIS data and your other exports.

Units
mmmftin
Exporting as Rhino: the original 3DM is embedded as itself, next to NURBS terrain, block instances and a layered model with metadata.

Export Model

Configure your export and download.

All formats

SketchUp

Native .skp — tag-organised model with georeferencing.

Features

GeoreferencedComponentsBuildings & structuresRoads, land use & topographyTrees & vegetationOrganised into tags
Your model “harbour_pavilion_v3” · included as a mesh with its names, tags and colours

Settings

Surface
GeometricRaster & Satellite
Trees
BasicPrecise
GeolocationAutomatic

Set automatically — the model carries its real geographic location, so SketchUp's location-based features line up.

Units
mmmftin
Exporting the same project as SketchUp: the model travels as a mesh copy with its names, tags and colours.
  • Rhino 3DM

    Exported as the same format

    Your objects as they are: Breps, NURBS, extrusions, meshes and curves, the layer tree with its colours, materials and user text, under a layer named after your dataset.

    Exported as any other format

    Mesh copy with names, layers and colours

  • SketchUp SKP

    Exported as the same format

    Your file as a component: groups, components, materials, textures and tags intact.

    Exported as any other format

    Mesh copy with names, tags and colours

  • IFC

    Exported as the same format

    Your elements appended under a building named after your dataset, with their classes, styles and property sets.

    Exported as any other format

    Mesh copy with names, storeys and colours

  • DXF

    Exported as the same format

    Your drawing as a block, entities, layers and nested blocks included.

    Exported as any other format

    Mesh copy with names, layers and colours

  • glTF, GLB, OBJ, STL, PLY, DAE

    Exported as the same format

    Your nodes added to the exported scene, hierarchy and materials kept across the family.

    Exported as any other format

    Mesh copy with names and colours

  • Revit RVT

    Exported as the same format

    The Cityweft context is built into your own Revit file: every element, family, view and sheet stays as it is.

    Exported as any other format

    Mesh copy with names, categories and colours

  • FBX, 3MF

    Exported as the same format

    Mesh copy with names and colours

    Exported as any other format

    Mesh copy with names and colours

In the organisation

Not lost in a folder. On the map, for everyone.

Uploads made with an organisation active belong to the organisation. Every member sees them on the map, uses them in projects, exports with them and downloads the originals. The uploader and the organisation's admins change, re-run or delete them. Exports made by teammates embed the organisation's original files natively, and a note on each dataset tells everyone where the file comes from and what to watch out for.

  • Every model of the firm, on one map, searchable
  • Private to the workspace; nobody outside can see or use it
  • Pooled storage on Small Business and Business

My Data

16 datasets · 2.1 GB · ready for any project that touches them

Add data
All · 16 Point clouds · 6 Models · 9 Pins · 1 From teammates · 7
Point cloudView only

Harbour district survey

2.71 km² · 34 pts/m² · 512 MB · added 2 Nov

1,184 buildings6,412 trees0.5 m terrain
Model · 3DMView only

harbour_pavilion_v3.3dm

2,860 m² · 46k triangles · 9 MB · added 2 Nov

1 building
Point cloud

Alfama rooftops, drone flight

0.42 km² · 61 pts/m² · 198 MB · added 30 Oct

318 buildings140 trees0.25 m terrain
Model · SKP

waterfront_tower_option_b.skp

1,514 m² · 41k triangles · 1 MB · added 30 Oct

1 building
Model · IFCView only

Campus library, IFC4

4,120 m² · 96k triangles · 18 MB · added 28 Oct

2 buildings
Point cloud

Marina competition site

1.1 km² · 46 pts/m² · 640 MB · added 29 Oct

512 buildings1,930 trees0.5 m terrain
Model · FBXView only

stadium_roof_study.fbx

24,600 m² · 310k triangles · 21 MB · added 27 Oct

1 building
Pin · PDF

Site survey report, May 2026

3 files · 14 MB · added 27 Oct

The organisation's library: who uploaded what, view-only for teammates, each dataset on its own map tile.
In your software

What arrives on the other side.

  1. Rhino

    Your 3DM comes back under a layer named after your dataset, with its own layer tree, colours, materials and user text, inside the Cityweft layers of the city around it.

  2. Revit

    Upload the RVT, and the export is built into that very file by Revit running in the cloud: the city arrives as masses, a Toposolid and site elements next to your own work.

  3. SketchUp

    Your SKP is loaded as a component with its groups, materials and tags, placed on its own tag next to the Cityweft groups.

  4. IFC

    Your elements are appended under a building named after your dataset, with their property sets, next to the city's proxies, slabs and geographic elements.

Use cases

What people upload, and why.

  1. A design in its real context

    The Rhino or SketchUp model on its plot, the neighbourhood around it at country-model quality, exported together for the next review.

  2. Rhino to Revit, without rebuilding

    The concept lives in Rhino, the documentation in Revit. Upload the 3DM once, export the project as RVT or IFC, and the context comes with it.

  3. The firm's model library

    Every project model, placed where it was built, visible to the whole organisation, re-exportable in a format the next tool reads.

  4. A survey DXF in the national grid

    A surveyor's drawing in the local coordinate system is placed exactly by naming that system, no dragging and no rotation.

  5. Options side by side

    Massing variants uploaded as separate models, each replacing the building on the plot, compared on the same map.

Plans

Included on every plan. Sized by the plan.

Pay-as-you-goProfessionalSmall BusinessBusiness
Storage for your uploads5 GB50 GB250 GB1 TB
Point cloud processed per month1 GB15 GB40 GB60 GB, then €3 per GB
Uploads5 in totalUnlimitedUnlimitedUnlimited
Largest file1 GB10 GB10 GB10 GB
Export projects that use your dataPreview onlyUnlimitedUnlimitedUnlimited
AllowancesPer userPer userPooled across the organisationPooled 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.