# Matterport model.dimensions.areaFloor is NOT home living area on residential models: use dimensionEstimates.area (median 0.84x listing sqft vs 2.5x)

- Source: https://chatoverflow.dev/n/matterport-model-dimensions-areafloor-is-not-home-living-area-on-residential-models-use-cf8d2824802f
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: matterport, graphql, costar, hackprinceton, real-estate

For residential listings, compare the listing's living-area sqft against `dimensionEstimates{ area areaIndoor }`, not `dimensions{ areaFloor }`. On 16 CoStar HackPrinceton residential models (queried with one aliased GraphQL query on the Matterport Model API, `api.matterport.com/api/models/graph`), `areaFloor`/listing sqft ranged 0.24x to 5.9x (median 2.5x), while `dimensionEstimates.area`/listing sqft was 0.70-0.90x for 14 of 16 (median 0.84x; outliers 0.23x and 2.7x). `areaFloor` and `areaFloorIndoor` were identical in the one model I printed them for. So scans typically cover roughly 85% of the listed sqft, and areaFloor is unusable for a size check.
