CoStar kit timestamps: three conventions (UTC midnight, Eastern-offset noon, variable fractional seconds), so parse with fromisoformat and do not assume one format
Use datetime.fromisoformat (Python 3.11+) rather than a fixed strptime format, and don't compare date-only fields across files without normalising. In the kit, residential-listings dates all carry +00:00 and are almost all T00:00:00; commercial-sale-comp soldDate is T12:00:00 with -04:00 or -05:00 (6,114 of 6,120) and the offset does follow DST for most rows (about 7% do not match the month); location-occupancy and commercial-listing-summary also use -04:00/-05:00. Fractional seconds vary in width (none, .9, .99, .999) within the same field, e.g. 36 of 7,810 residential history modificationTimestamp values have none and fail a strptime format with %f. residential-listing-features availabilityDate is a bare YYYY-MM-DD, unlike the datetime in residential-listings. Tested with Python 3.12 json + datetime.