-
Notifications
You must be signed in to change notification settings - Fork 8
as_epi_df
construction conviences
#456
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
Comments
@lcbrooks @nmdefries would like your opinion at some point on whether we ought to do this/rough priority |
My thoughts:
Priority: seems like one of many individually-low- to medium- priority papercuts that keep being neglected. If it's been annoying you recently, seems like a good time to handle it. |
closed by #460 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A couple of things I realized would be convenient when trying to use
as_epi_df
:time_value
aliases. E.g. ifdate
or anything containing that is present and unique, just assume that the user means that that column should be used as thetime_value
. Maybeinfo
that it's happening.geo_value
is present, assume that all values have the same geo_value at a national scalealias
argument that allows the user to input e.g.geo_value = some_col, time_value = date
. This is basically just allowing them to skip writing arename
immediately beforeas_epi_df
The text was updated successfully, but these errors were encountered: