Free tools Windows power users keep installed
One-click scans. No signup required.
You can build a repeatable 3D context workflow with these tools, but they are not a documented, integrated product chain. Treat Cityweft or Shapezo as potential sources of map-derived site context, Tripo3D as a model-conversion stage, CityEngine as a procedural city-authoring and export tool, and Site3D as civil road-and-site design software. Test each file handoff in the application that will use it.
What each tool does in this workflow
The five names describe different production jobs, not interchangeable ways to make the same model. Keeping those jobs separate helps prevent a common pipeline mistake: assuming that because two products mention 3D or BIM, they share data directly or preserve the same information.
| Tool | Documented role | What the available product information establishes |
|---|---|---|
| Cityweft | Site-context generation | Describes a web platform and API for generating 3D site context, with integrations and exports spanning architecture, CAD, BIM, GIS, and visualization tools. It claims geolocation and coordinate-system support; verify those details in an actual export. |
| Shapezo | Map-derived context generation and editing | Describes editable buildings, terrain, water, and vegetation generated from map data, followed by review or editing and export for 3D, BIM, GIS, and game-engine workflows. A direct connection to every other named tool is not established. |
| Tripo3D | Model conversion and related model handling | Its API documents conversion targets including GLTF, FBX, USDZ, OBJ, STL, and 3MF. This does not establish Tripo3D as a source of geographically authoritative site data. |
| Esri CityEngine | Procedural city authoring and export | Documents exports for CGA models, manually drawn and static models, and terrain meshes, with routes to other 3D authoring tools, ArcGIS Online, web, or VR. Available formats and interface depend in part on version. |
| Site3D at site3d.co.uk | Civil road and site design | The UK product is presented as civil-engineering software and describes IFC export for BIM collaboration. The cited product information does not establish a direct integration with the other tools here. |
“Site3D” is ambiguous: another unrelated product uses the same name. The Site3D described in this workflow is the UK civil-engineering product at site3d.co.uk. Confirm the intended vendor before assigning any feature to a product called Site3D.
How to build a reproducible pipeline
Start with a small test area and a clear definition of what the model is for. A visualization backdrop, a GIS dataset, design context, and engineering work do not have the same authority requirements. A map-derived context model should not be treated as surveyed or engineering-validated geometry unless separate evidence establishes that status.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11#1 Best Overall
- Define the project and its spatial reference. Record the area of interest, intended use, required level of authority, units, and coordinate reference system (CRS). Decide which terrain, buildings, water, vegetation, or other layers the task requires. Do this before choosing an export format.
- Select a context source. Evaluate Cityweft and Shapezo against the geographic coverage, source data, editable layers, metadata, georeferencing, available exports, and update controls your project needs. Their descriptions overlap at a high level, but they do not establish identical output quality or an independent comparative winner.
- Run a representative pilot export. Use a small area that includes the features and terrain you expect in the full project. Record the export date, area, selected layers, CRS, units, format, and settings. Import it into the intended destination application and check the coordinates and layer organization before scaling up.
- Convert only when conversion is needed. If the target application requires a different model format, use Tripo3D as a conversion stage. Record the input and output formats and conversion options. After conversion, inspect scale, orientation, topology, and materials or textures in the receiving application.
- Use CityEngine for the task it addresses. Bring data into CityEngine when procedural city authoring or one of its export routes is needed. Record the CityEngine version and chosen route, then check whether the resulting file retains the scene data required downstream.
- Keep civil design distinct. If the intended Site3D is the UK road-and-site design application, use it for that civil-engineering role rather than assuming it is a generic context generator. Before BIM collaboration, check units and coordinate alignment in the target BIM application.
- Save the handoff record. Keep source and intermediate files with the settings and validation notes. A colleague should be able to identify the source, reproduce the export, and see what was checked without relying on undocumented memory.
How to choose between Cityweft and Shapezo
Cityweft and Shapezo are the two tools in this group described as sources of site context. The information available for them supports a requirements-based evaluation, not a claim that one is more accurate or better in general.
| Evaluation question | Cityweft | Shapezo |
|---|---|---|
| What does it describe generating? | 3D site context, according to Cityweft’s product information. | Map-derived, editable buildings, terrain, water, and vegetation, according to Shapezo’s product information. |
| Which exports or integrations are documented? | Integrations and exports across architecture, CAD, BIM, GIS, and visualization tools; the product information summarized here does not establish a specific format for every handoff. | Exports for 3D, BIM, GIS, and game-engine workflows; the product information summarized here does not establish a specific format for every handoff. |
| What should you verify for your project? | Geographic coverage, chosen layers, coordinate behavior, output format, and whether the downloaded data works as needed in the target application. | Geographic coverage, editable layers, output format, and whether the downloaded data works as needed in the target application. |
| What cost is stated? | Cityweft’s page, accessed in 2026, states a starting price of €30 for a single export. This is a vendor pricing claim, not a verified quote; check the live price and terms before budgeting. | Not stated in the Shapezo product information described here. |
| Is comparative accuracy established? | No independent comparison is established. | No independent comparison is established. |
Choose based on a pilot export against your actual area and destination software. Compare what arrives—not just the feature list—including coordinate placement, layer separation, editable structure, and any metadata your next stage depends on.
Rank #2
What file formats do—and do not—tell you
Format compatibility is not the same as a reliable handoff. A file may open while losing or changing geolocation, coordinate reference details, metadata, materials, or editable structure. The format names alone do not prove that a particular pair of applications preserves those properties.
- Tripo3D: the documented API lists GLTF, FBX, USDZ, OBJ, STL, and 3MF as target formats, with conversion options. That list does not establish which format is best for a given project or what every conversion preserves.
- CityEngine: its documentation describes export routes for several kinds of CityEngine content and destinations. Check the documentation for your installed version and the specific route you intend to use.
- Site3D: the UK vendor describes IFC export for BIM collaboration. Confirm the resulting file in the target BIM application and check alignment and units.
- Cityweft and Shapezo: their product descriptions cover broad workflow categories, but do not establish a specific compatible format for every named handoff in this pipeline.
For each transition, validate a representative file in the receiving application. Check the properties that matter to the next task: spatial placement and units for site context; geometry, orientation, and material appearance after conversion; and the required scene content after an authoring-tool export. Record the outcome rather than assuming that a successful import proves full fidelity.
What to record so another person can repeat the work
Keep a short manifest beside the project files. The following fields are workflow guidance for reproducibility, not a claim that any one product automatically records them.
- Project purpose and intended authority level.
- Source product and, where available, source-data date.
- Area of interest and selected layers.
- Coordinate reference system, units, and any alignment steps.
- Software versions, export route, output format, and conversion settings.
- Names or locations of source, intermediate, and final files.
- Validation checks performed in each receiving application, including any failures or known changes.
Keep the original export as well as converted files. If a later stage changes geometry, materials, or coordinate behavior, preserving the earlier file makes it possible to locate where the change entered the pipeline.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
