You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are running the Notebook on a Zip code, specifying State (cell 3) is not required. However, the "state" field is used in creating graph titles. This means that it's easy to accidentally create misleading graphics, showing mislabeled/invalid locations. For example:
(The Zip code specified is in Washington, but Alabama is selected by default in the State dropdown, so the graph title shows an invalid location.)
There are two possible solutions:
Infer the "state" field from the Zip code so that it is correct in the graphs
Don't display the state when analyzing by Zip code
Option 1 seems better to me even though it adds a bit more code complexity, since it produces a more usable end result. Any opinions on that preference @ericnost@shansen5 ?
The text was updated successfully, but these errors were encountered:
Hi, I would like to contribute and attempt to solve this issue. I am new to open source so I am not sure if you need to assign it to me or I can go ahead and fork. Can I work on it?
Yes @byvya1505, thank you for offering to help on this. Note that this notebook imports our ECHO_modules code, and you may need to look into that. https://github.com/edgi-govdata-archiving/ECHO_modules
I haven't yet looked to see if there is a resource for mapping from zip codes to states.
Notebook: https://colab.research.google.com/github/edgi-govdata-archiving/ECHO-Cross-Program/blob/main/ECHO-Cross-Programs.ipynb#scrollTo=LH-8VrSTaRLN
If you are running the Notebook on a Zip code, specifying State (cell 3) is not required. However, the "state" field is used in creating graph titles. This means that it's easy to accidentally create misleading graphics, showing mislabeled/invalid locations. For example:
(The Zip code specified is in Washington, but Alabama is selected by default in the State dropdown, so the graph title shows an invalid location.)
There are two possible solutions:
Option 1 seems better to me even though it adds a bit more code complexity, since it produces a more usable end result. Any opinions on that preference @ericnost @shansen5 ?
The text was updated successfully, but these errors were encountered: