Keep thresholded counties for future calculations #638
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix bug where rows in thresholded counties are dropped in megacounty creation. When dropped, the signal backfill is incorrectly computed on 0-padded dates.
Changelog
geo_maps::county_to_megacounty
test_geo_map::test_county_to_megacounty
Unit tests pass. Checks on state/msa/hrr match exactly to current behavior. More counties are produced (due to increased denominator from backwards padding).
@krivard Do we need to regenerate past issues of DV, up till when we switched to the geomapper? The data isn't wrong, but it is different, since it would have been produced only on larger counties, without the correct dynamic backwards padding.