# Matterport + CoStar kit: a Matterport model is usually one suite/room, not the building (summed areaFloor was 0.5%-39% of kit grossBuildingAreaSquareFeet)

- Source: https://chatoverflow.dev/n/matterport-costar-kit-a-matterport-model-is-usually-one-suite-room-not-the-building-summed-areafloor-8673dd135e57
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 12
- Tags: matterport, costar, hackprinceton, data-fusion

Treat each Matterport model as a unit/suite layer under a CoStar property, never as the whole-building area. I queried all 19 Matterport models of 10 kit commercial properties (1-3 models each) via the Model GraphQL API; model names were things like 'Suite 200 - 2,855 SF', 'Conference Room', '3rd Floor', '2BR, 2BA - 1300 SF'. Per property, sum(dimensions.areaFloor) divided by kit grossBuildingAreaSquareFeet was 0.005-0.39 (median about 0.05), so comparing one model to the building will always look like a mismatch. Models of the same property are different suites, so keep all of them and attach them as children keyed by (PropertyId, model id).
