Fabio
1beeaab2db
The first edges in the repo. Every US county now links to the districts it sits in, weighted by area overlap, and every legislator links to the district they represent — county → district → representative, traversable. Data (PostGIS, no Atlas dependency — computed directly from geometry): - data/county_district_edges.jsonl — 16,328 weighted edges. area_weight = ST_Area(ST_Intersection(county, district))/ST_Area(county) over ST_MakeValid Census TIGER 2024 geometries, overlaps <0.5% dropped. Uses area-intersection, NOT centroid-in-polygon, so urban districts that carve through counties (e.g. GA CD-5 / Atlanta across Clayton+DeKalb+Fulton) are captured, not silently dropped. Per-county weights sum to ~1.0 per district type. build.py: - ~6,896 new district nodes: 435 CD (ACS demographics where available; sparse for the 8 states missing from acs_cd) + 4,927 state-house + 1,897 state-senate (geometry-only). GEOID/number-keyed, stable. - county index.md gains a `districts:` block (frontmatter) + a ## Districts section (body links, so link-integrity checks them). - legislators + US House members gain `represents:` pointing at their district node; edge stored once on the person, inverse left to the view. - schemas/jurisdiction: classification enum + chamber/districts fields. Honest gaps (logged, not hidden): ID + NH have no state-house geometry, so their house districts get nodes (represents resolves) but no county edges; CD nodes for acs_cd-missing states are demographically sparse. Deterministic (byte-identical rebuild); validate.py passes 26,617 records, link-integrity clean (every district/represents link resolves). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.4 KiB
2.4 KiB
type, title, classification, fips, state, demographics, districts, sources, confidence, tags, timestamp
| type | title | classification | fips | state | demographics | districts | sources | confidence | tags | timestamp | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Jurisdiction | Chisago County, MN | county | 27025 | MN |
|
|
|
official |
|
2026-07-03 |
Chisago County, MN
County jurisdiction.
Demographics (ACS 2023)
| Measure | Value |
|---|---|
| Population | 57991 |
| Under 18 | 12958 |
| 18–64 | 35123 |
| 65+ | 9910 |
| Median household income | 99400 |
| Poverty rate | 5.95 |
| Homeownership rate | 85.92 |
| Unemployment rate | 4.09 |
| Median home value | 351900 |
| Gini index | 0.3884 |
| Vacancy rate | 7.1 |
| White | 52595 |
| Black | 728 |
| Asian | 1157 |
| Native | 235 |
| Hispanic/Latino | 1644 |
| Bachelor's or higher | 12971 |
Districts
- MN-08 — 100% (congressional)
- MN Senate District 28 — 82% (state senate)
- MN Senate District 11 — 18% (state senate)
- MN House District 28B — 67% (state house)
- MN House District 11B — 18% (state house)
- MN House District 28A — 15% (state house)
Source
- demographics: Census ACS 2023
- districts: PostGIS area-intersection over Census TIGER 2024 boundaries