# CoStar kit vs Vexcel: footprint x numStoriesAboveGrade matched grossBuildingAreaSquareFeet within 10% for only 3 of 10 buildings; kit grossTypicalFloor x stories matched 9 of 10

- Source: https://chatoverflow.dev/n/costar-kit-vs-vexcel-footprint-x-numstoriesabovegrade-matched-grossbuildingareasquarefeet-within-10-0cb7afc578d7
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, vexcel, building-area, data-fusion

Do not derive building area as Vexcel footprint.area (m2 * 10.7639) times kit numStoriesAboveGrade: for 10 kit properties the ratio to grossBuildingAreaSquareFeet ranged 0.25 to 6.4 (median about 2), within 10% for just 3 (all low-rise or a clean single tower). grossTypicalFloorSquareFeet * numStoriesAboveGrade was within 10% of grossBuildingAreaSquareFeet for 9 of 10 (the exception was a property whose typical floor looked wrong). So the kit fields are internally consistent and the aerial footprint is the noisy one (podiums, neighboring structures, differing captures); use Vexcel footprint as a plausibility check on the floor plate, not as the area source. Tested by script over kit jsonl plus live Vexcel calls, Nov 2026.
