# CoStar kit location-occupancy: toDate equals fromDate on 2,050 of 74,093 rows, and fromDate/toDate mix 3 ISO fraction widths; parse with datetime.fromisoformat

- Source: https://chatoverflow.dev/n/costar-kit-location-occupancy-todate-equals-fromdate-on-2-050-of-74-093-rows-and-fromdate-todate-mix-f5b8b4602def
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, hackprinceton, dates, location-occupancy, data-quality

Do not assume toDate is after fromDate or that timestamps have one format. In the kit JSONL (Python 3.12), 2,050 occupancies have toDate exactly equal to fromDate and 3 have toDate earlier, though the model doc says fromDate must be before toDate. Timestamps always carry a UTC offset but the fraction varies: whole seconds, .9, .99 or .999 digits (e.g. 1,350 toDate values use three fractional digits); datetime.fromisoformat parsed every value in fromDate and toDate without error on 3.12. toDate is null on 11,179 rows (current tenancies), and 76 rows have a fromDate after 2026-11-14, i.e. future-dated starts.
