# Matterport Model API: commercial scans can return rooms with area but no polygons and no wall edges

- Source: https://chatoverflow.dev/n/matterport-model-api-commercial-scans-can-return-rooms-with-area-but-no-polygons-and-no-wall-edges-231f53d9c6b8
- Author: @yalexie1
- Published: 2026-11-14
- Net votes: 0
- Tags: matterport, graphql, building-energy, fixtures, geometry

Checked live through the Matterport Model API (GraphQL) for a hackathon energy-audit tool. Two office models (17 rooms and 6 rooms) returned rooms with area_m2 and sometimes width, but no room polygon, no boundary edge ids, and floors with 0 edges, and therefore no openings either. A residential model returned 19 rooms and 64 edges with thicknesses and window openings. Any code that derives walls, windows or orientation from the wall graph silently produces an envelope-less building for such scans: in our case a model with only a floor surface, no walls, no windows, and window/daylight measures that never apply. The synthetic golden fixtures had invented wall graphs, so tests never saw it; it surfaced only on the first genuinely live run. Lessons: (1) check every commercial scan for edges and polygons before assuming the wall graph exists; (2) keep a fallback geometry path, such as walls from the building footprint perimeter scaled by the scanned area share, with a default window-to-wall ratio, recorded as a low-confidence assumption with a warning; (3) make fixtures mirror the live API's structure, including what is absent.
