Support chng-fips
county group reporting in chng
for privacy
#1883
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
Report signals for
chng-fips
county groups instead of counties. See the geomapper support PR for more context.Turn off sirCAL alerting for county versions of all signals using this format.
Big Note
From local testing, it looks like the new county groups are never actually reported... This doesn't seem to be a definitional issue, that is, theoretically county groups could be reported if they had enough total claims reported. But because the county groups are low-population areas in general, they tend not to have enough total claims reported to be included in the output, based on our filtering logic.
Do we want to do more investigation here? I started in on population comparisons (do counties of similar population to county groups also get filtered out? Some megacounties do, at least) but didn't do anything super formal or thorough.
Non-adjusted
county
andchng-fips
values match exactly (althoughcounty
files have an extra entry for a county called "\N"??); adjustedcounty
andchng-fips
values are very similar but not exactly the same.Changelog
update_sensor.py
chng
and sirCAL.