-
Notifications
You must be signed in to change notification settings - Fork 16
Refactor claims_hosp to use new geomapper functions #322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original code is broken in main
due to the changes introduced in GeoMapper. I can run a comparison off commit 64eb227 (when the package was originally introduced, and before GeoMapper changes). The results line up for state
, hrr
, and county
, but msa
has an error.
I don't believe this indicator makes any use of the GeoMapper population functions. Is that correct? If we use population data here, I should block this merge until we fix #325. |
Yes, this indicator does not use population. So there shouldn't be any problem merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Late but lgtm (wanted to get that checkmark)
Part of #306
Summary of changes:
Couple things to note here:
The previous functions, e.g.
county_to_state()
, don't exist in the GeoMapper package.convert_fips_to_state_id()
in the GeoMapper package which contain the arguments called by this code, so maybe they used to be namedcounty_to_state()
but were renamed later. However, if you use these functions, the code doesn't work due to a non-unique multi-index.After switching to the new functions all tests pass, but I can't verify against previous behaviour since the original code didn't run.