fix(site-finder): robust is_residential_zone detection for NSPD zone codes (#1353) #1681

Merged
lekss361 merged 1 commit from fix/residential-zone-detect-1353 into main 2026-06-17 17:55:03 +00:00

1 commit

Author SHA1 Message Date
3fd06228ff fix(site-finder): robust is_residential_zone detection for NSPD zone codes (#1353)
Some checks failed
CI / changes (push) Successful in 11s
CI / changes (pull_request) Successful in 6s
CI / backend-tests (push) Has been skipped
CI / frontend-tests (push) Has been skipped
CI / openapi-codegen-check (push) Has been skipped
CI / frontend-tests (pull_request) Has been skipped
CI / openapi-codegen-check (pull_request) Successful in 1m47s
CI / backend-tests (pull_request) Failing after 9m15s
NSPD quarter-dump territorial_zones (layer 875838) does NOT store ПЗЗ letter
codes in properties — zone_code receives the cadastral reg number ("66:41-7.14")
or None, never a "Ж-1" style code. The old prefix check (startswith "Ж-"/"Ж1" …)
therefore never matched real NSPD data, silently marking every dump-sourced parcel
as non-residential (PZZ_NOT_RESIDENTIAL blocker).

Fix: three-tier detection in is_residential_zone:
1. Regex ^Ж on zone_code — handles PKK6/pzz_zones_ekb sources ("Ж-1", "Жс")
2. NSPD subcategory from raw_props — subcategory=2 (Жилые зоны, 221 ЕКБ objects)
   and subcategory=3 (Смешанное использование, 126 objects) → residential;
   subcategory=1 (ИЖС) excluded — МКД not permitted there
3. zone_name substring "жил" — fallback for non-standard sources

compute_gate_verdict now passes nspd_zoning["raw_props"] to is_residential_zone.
2026-06-17 20:33:48 +03:00