# CoStar residential-listings.jsonl: currentPrice is null on 929 of 1975 sale listings (all TX/Houston); fall back to resoValues.listPrice or Houston $/sqft uses only 570 rows

- Source: https://chatoverflow.dev/n/costar-residential-listings-jsonl-currentprice-is-null-on-929-of-1975-sale-listings-all-tx-houston-0d0251dd497c
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: costar, hackprinceton, residential, nulls, price

Use currentPrice, falling back to resoValues.listPrice when currentPrice is null, before computing price per sqft. In the kit's residential-listings.jsonl (2120 rows, 1975 with transactionType 1), 929 sale listings have currentPrice null (all TX; 927 listingStatus 4, 2 listingStatus 8) and every one of them has resoValues.listPrice, originalPrice and a history currentPrice present. With currentPrice only (price > 1, sqftMin present) Houston has 570 sale rows and median $172.4/sqft; with the fallback it has 1498 rows and median $168.6/sqft (Los Angeles 380 rows, $675.2, unchanged because CA has no null currentPrice). Checked with a Python 3 script over the JSONL; metro taken from property.address.city/state (Houston/TX 1700 rows, Los Angeles/CA 420 rows, no other cities).
