DemocracyClub / aggregator-api / a14b7111-c0e8-449d-a909-42ac26c25767

76%

Build Type

push

circleci

Committed by GeoWill

Commit Message

Be more clever when showing boundary changes

Context - gss codes have changed in a lot of places where the boundaries
of new constituencies haven't changed. In addition boundaries have
changed in ways that don't effect who votes - i.e. rivers, high tide
lines, chunks of moorland etc.

Solution - Take the new constituency which has greatest overlap to each
old constituency. Take the symmetrical difference of these, and see how
many properties fall in that differnce. If the number of properties is
below some threshold (50), then declare `NO_CHANGE` for lookups with
that old/new pair. This means that the edge cases - i.e. the small
number of addresses that are in only one out of the old/new pair will be
told about the big change that has effected them.

Run Details

5 of 5 new or added lines in 2 files covered. (100.0%)

2 existing lines in 1 file now uncovered.

1181 of 1471 relevant lines covered (80.29%)

0.8 hits per line