Cityweft

1. Security/compliance gating is strict and requires public evidence of certifications

• If procurement requires public SOC 2, ISO 27001, or detailed security whitepapers before vendor engagement, Cityweft's public materials are limited and other vendors with readily available documentation may be preferable.

2. Primary need is large-scale streamed digital-twin visualization

• For web-streamed visualization and large-scale 3D tiles delivery, a platform built for streaming (such as Cesium ion) may better match requirements.

3. Terrain-first deliverables are the primary deliverable

• Organizations primarily requiring terrain contours, LiDAR-derived deliverables, and per-site survey products may prefer vendors focused on terrain deliverables and reporting.

4. Cost-sensitive scenarios where OSM-level context is sufficient

• If basic OSM-based massing is adequate, lower-cost OSM workflows or tools such as Cadmapper may provide sufficient value.

5. Requirement for globally authoritative building heights everywhere

• Cityweft integrates authoritative sources where available; global completeness is constrained by source availability and data inference methods.

• Public documentation provides plan-based export size limits but does not present exhaustive details on maximum polygon complexity, file-size caps beyond plan limits, or API rate limits. Buyers should verify operational limits with the vendor.

Plan-based export size limits (vendor-stated):

• Free: up to 1 km²/export
• Pro export: up to 10 km²/export
• Professional subscription: 20 km²/month exports
• Business: unlimited exports (vendor claim)

• Multi-source fusion into layered geometry intended for CAD export workflows (vendor statement).
• Plugins for Rhino and Grasshopper, indicating a focus on AEC-native workflows.
• Regional integration of LiDAR-derived building heights in certain countries, which can improve massing and analysis in those geographies compared with OSM-only inputs.
• Multiple pricing options (free tier, per-km², bundles, subscriptions) including prepaid bundles introduced after user feedback.

Vendor materials describe a collaboration with Graphisoft to provide contextual data. The vendor-authored post describes embedding site context into Graphisoft tools.

Critical evaluation:

• The content is vendor-authored and does not disclose measurable outcomes (for example, time saved, accuracy improvements, or adoption rates).
• The collaboration suggests integration interest from an established AEC software vendor, which may indicate product-market fit in certain scenarios.

Vendor announcements and industry reporting indicate region-specific dataset integrations:

• Spain: LiDAR-derived building heights from the national mapping agency; vendor materials indicate the dataset covers a stated time period.
• England: Reports indicate LiDAR-derived datasets have been integrated for improved massing/analysis in some areas.

Critical evaluation:

• These are data-availability announcements rather than independent ROI case studies.
• They indicate that Cityweft's comparative advantage is likely uneven by geography: where authoritative LiDAR or building registries are integrated, outputs should be stronger than in areas relying primarily on OSM.

Cityweft is a web platform with an API and plugins that generate and export 3D site context (buildings, terrain/topography, surfaces, and selected infrastructure/instances) for use in AEC workflows. Users define an area (polygon/rectangle), preview model layers, and export to common CAD/3D formats (for example, Rhino 3DM, SketchUp SKP, GLB/GLTF, DXF) or integrate programmatically via a REST API.

Cityweft describes its approach as blending multiple open and government datasets (and derived products) into geometry intended to be more editable than typical OSM-only workflows, with purported improvements in building-height/roof coverage and topography quality in some regions. This is a vendor-stated differentiation and should be validated per project and geography. Sources: official vendor documentation and product posts.

Primary targets:

• Architecture and urban design teams needing rapid context for concept and schematic design (massing, shadows/daylight studies, feasibility studies, competition visuals).
• Urban planning/analysis and computational design workflows (Rhino/Grasshopper).

Secondary / adjacent targets:

• Real estate development feasibility and presentation workflows.
• AEC software platforms and urban-tech vendors embedding context data via API.
• Game/visualization experimentation (observed in community discussion), though Cityweft's primary go-to-market focus appears to be AEC.

Official vendor positioning emphasizes suitability for AEC workflows, layer-structured exports, and ease of use. These are vendor claims and should be validated against operational requirements in procurement or trial use.