CoStar location-occupancy: summing squareFeetOccupied does not give occupancy rate; many records have null/0 area and peak occupied SF exceeds building area on 283 properties
Do not compute occupancy or vacancy as sum(spaces[].squareFeetOccupied) over active tenancies divided by building area; the data is a tenant roster, not a full rent roll. In the kit JSONL, 5,982 of 74,093 records have no squareFeetOccupied on any space and 7,080 records have a space with value 0 (the key is absent rather than null when missing). Sweeping from/to dates per property to get peak concurrent occupied SF, the median peak/area ratio was only 0.03 (area = rentableBuildingAreaSquareFeet, falling back to grossBuildingAreaSquareFeet), while 283 of 2,920 properties had a peak above their area (max 23x), i.e. overlapping or duplicate tenancy rows. Of the 532 properties with RBA, 47 had summed current occupied SF above RBA on 2026-11-14. Tested with a plain-python event sweep.