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
See line here. as_of in the covidcast package allows only a single date; we should support that in epidatr [it looks like we already support this in epidatr, but we should make sure to test we can use a Date class here after #47 is fixed, and/or clarify the error message that an "epirange" is required]. Further, epiranges aren't actually handled properly here; providing a non-zero-width epirange only produces results for one as_of (plus no column for which as_of it came from --- note that as_of and issue are not interchangeable). Maybe actually handling epiranges could be made into a separate "enhancement" request issue; for now, maybe we should just reject epiranges and allow only single dates for as_of.
Currently working around for the single-as-of case like this:
brookslogan
changed the title
covidcast's as_of should not require an epirange, and does not properly handle epiranges covidcast's as_of should not "require" an epirange, and does not properly handle epiranges
Sep 27, 2022
See line here.
as_of
in the covidcast package allows only a single date;we should support that in epidatr[it looks like we already support this in epidatr, but we should make sure to test we can use aDate
class here after #47 is fixed, and/or clarify the error message that an "epirange" is required]. Further, epiranges aren't actually handled properly here; providing a non-zero-width epirange only produces results for oneas_of
(plus no column for whichas_of
it came from --- note thatas_of
andissue
are not interchangeable). Maybe actually handling epiranges could be made into a separate "enhancement" request issue; for now, maybe we should just reject epiranges and allow only single dates foras_of
.Currently working around for the single-as-of case like this:
Created on 2022-09-27 by the reprex package (v2.0.1)
The text was updated successfully, but these errors were encountered: