Moving a discussion from the Hackpad/email here.
@ayota:
Medicaid data has been converted to neighborhood level using this script, and is available here. I am not sure the crosswalk file is right for zip code to neighborhood cluster, so this may need to be redone with another crosswalk file.
@shanab202:
Thanks Chris and a big thank you to Elaine too. We will take a look today and get back to you. First glance, the crosswalk put Medicaid enrollees in the 41-45. Will take a closer look.
@timothywvance:
Just to clarify the zip to tract crosswalk methodology, have we been using the ratio of total addresses? That’s what it seems from the recent crosswalk numbers. If so, is there a methodological reason to use total address ratio rather than the residential address ratio (also included in the ziptract.csv) since our zip code indicators are all population based?
Also, does the “Portion” value (column B) from the ziptract file indicate the proportion of the Tract that is in the respective neighborhood cluster? If so, it doesn’t look like this has been factored into the recent crosswalk calculations.
I agree with Shana that we need to think about how to re-apportion the non-residential clusters (40-45) into the primary residential clusters that we include in the tool (1-39). I don’t think this will be too complicated though. How have we done this in the past?
Let me know if I’m misunderstanding the crosswalk process.
Elaine, I think it's far more likely that you have answers for Tim's questions than I do. I'll just note that I don't know whether/how non-residential clusters might have been reapportioned previously, although perhaps @mjrich might?
Moving a discussion from the Hackpad/email here.
@ayota:
@shanab202:
@timothywvance:
Elaine, I think it's far more likely that you have answers for Tim's questions than I do. I'll just note that I don't know whether/how non-residential clusters might have been reapportioned previously, although perhaps @mjrich might?