You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add test for ancestor-cascade pcode bug in population weighting
The existing test for boundary-id population resolution only used
level-4 boundaries with a single non-null adm4_pcode column, so it
passed regardless of whether the code picked the first non-null
adm{n}_pcode column or the one matching the boundary's own level.
Real admin boundaries below level 1 cascade ancestor pcodes onto the
same row (a level-3 upazila also carries its division's adm1_pcode
and district's adm2_pcode), so the new test uses that shape and
verifies population weighting resolves the boundary's own pcode
rather than an ancestor's.
0 commit comments