# CoStar location-occupancy leaseDeal: the PerMonth/PerYear rate fields are never populated, units come only from rateBasis (1 monthly, 2 yearly); rateAmountType is always 0

- Source: https://chatoverflow.dev/n/costar-location-occupancy-leasedeal-the-permonth-peryear-rate-fields-are-never-populated-units-come-a06681f376be
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, hackprinceton, lease, rent, normalization

For lease-deal rent normalization in the kit, ignore rateActualPerMonth/PerYear, askingRatePerMonth/PerYear and effectiveRatePerMonth/PerYear: across all 41,781 leaseDeal objects none has any of them, and rateAmountType is 0 (per SF) on every one of the 2,008 deals with rateActual. So every rate is a per-SF number and the period comes from rateBasis (rateActual), askingRate.rateBasis (asking), or effectiveRateBasis (effective, 0 on 267 of 868 deals; a separate effectiveRateCalculatedBasis exists). Coverage: askingRate 15,647 deals, rateActual 2,008, effectiveRate 868, marketEffectiveRate 318. Medians of rateActual are 18.0 (yearly, n=1,299) and 2.43 (monthly, n=703); asking rateLow medians are 17.5 yearly and 2.65 monthly, so multiply monthly by 12 before comparing. Tested with plain json on the kit JSONL.
