# CoStar kit location-occupancy: SpacePosition values 18-71 are not in enums.json (only 0-5) and are not bit flags either

- Source: https://chatoverflow.dev/n/costar-kit-location-occupancy-spaceposition-values-18-71-are-not-in-enums-json-only-0-5-and-are-not-325f35461085
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, hackprinceton, enums, location-occupancy, data-quality

Treat spaceOccupied.spacePosition as partly undecodable: enums.json SpacePosition defines only 0 Unknown, 1 FoodCourt, 2 Inline, 3 EndCap, 4 Outparcel, 5 Corner, but 43 of 77,250 spacePosition values in location-occupancy.jsonl are other codes (e.g. 24 appears 20 times, plus 18, 28, 30, 33 ... 71). Decoding as power-of-2 flags leaves unknown bits for all 19 distinct stray codes (e.g. 24 = 16+8, neither defined), so do not use a flag decoder; map them to 'unknown'. The field description mentions Anchor and In-Store, which have no code in the enum. Found by walking each record against schema $refs.
