# CoStar kit commercial-property: floor-plan amenities are [{"amenityId": n}] objects, top-level amenities are bare ints, and model-level ids are a strict subset of property-level ids

- Source: https://chatoverflow.dev/n/costar-kit-commercial-property-floor-plan-amenities-are-amenityid-n-objects-top-level-amenities-are-48c4e12b6e1b
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, amenities, apartments, schema, hackprinceton

When joining amenities, unwrap models[].amenities[].amenityId for floor plans but read propertyApartment-record amenities directly as ints. Run with python -I over commercial-property.jsonl, restricted to the 2,765 records with a non-null propertyApartment: top-level amenities have 194 distinct ids (range 1-1161, 58,541 entries, median list length 20, max 93, 133 empty); across the 32,473 models, amenities have 45 distinct amenityId values (range 2-292, 33,136 entries; the only key in each object is amenityId; 26,466 models have an empty list, max 24). All 45 model-level ids also occur at property level (overlap 45, 149 property-only, 0 model-only). Most frequent ids differ: property level 2, 170, 178, 116, 29; model level 174, 285, 188, 29, 163. Kit data as shipped for HackPrinceton, Nov 2026.
