gendesign/site-finder/cache/parcel_polygons/README.md
Light1YT 97b19a0b85 Import Site Finder app from analysis/ vibe-coding session
Adds site-finder/ subfolder with:
  - server.py — FastAPI scoring service v2 (35 endpoints, ~85KB)
  - 01_load_sites.py … 12_more_pois.py — data ingest pipeline
  - db_init.py — SQLite schema bootstrap
  - static/ — Leaflet UI (index.html ~3500 lines + sw.js)
  - cache/ — small persistent caches (admin districts, jk polygons,
    geocode warm cache, parcel polygons drop-zone with README)
  - reports/ — sample generated parcel report (HTML+JSON)

Excluded via .gitignore (regeneratable, too big for git):
  - analysis.db (336MB SQLite — rebuild via 01_*..12_*.py)
  - cache/objective_raw/ (1.2GB Объектив raw dumps)
  - cache/overpass_raw.json, cache/osm_buildings_all.geojson
    (regen from Overpass API)

Production deploy: /opt/gendesign/site-finder/ on gendsgn.ru
(container gendesign-site-finder-1, served at /sf/).
2026-05-10 22:42:25 +05:00

11 lines
487 B
Markdown

# Parcel polygons cache
Drop `<cad_number>.geojson` here when you have NSPD polygon for a parcel
(e.g., manually exported from nspd.gov.ru after trusting the Минцифры cert).
Format: standard GeoJSON Feature or FeatureCollection in EPSG:4326 (WGS84).
The pipeline (`01_load_sites.py`) will pick it up next run, store the
geometry, and use polygon centroid as the parcel point.
If a polygon is loaded, the JSON report adds a `geometry` field with
the polygon for map rendering.