Open ryantibs opened 3 years ago
The Epidata API actually doesn't support fetching all issues, so this will have to be supported on the server side before clients can add it. cc @krivard to add this to the Epidata wishlist
Why couldn't this just be interpreted within the covidcast_signal()
function as issues = c(start_day, Sys.Date())
?
When the Epidata API itself allows for issues = "*"
, we can use that instead.
We probably need to use max(start_day, min_issue)
since we have a bunch of signals whose first issue included data from multiple months beforehand. min_issue
is not supported yet in metadata. There's a PR for it (cmu-delphi/delphi-epidata#236) but the logic is tricky and we don't want to inadvertently double the running time of the meta cache updates.
We use this kind of query to build epi_archive
s in epiprocess
. In case this is relevant for v4 or implementing issues="*"
in the API:
max(start_day, min_issue)
would be buggy. We might favor min_issue
instead, but that might break covidcast_days. On the API server side, issues="*" could take the simpler approach of just not filtering by issue at all.]epidatr
by using covidcast(......., issues = epirange(12340101, 34560101))
, but this approach looks a little ugly (and will be buggy in a short ~1400 years), and could not be simply applied to the covidcast
library because covidcast_days
works off of an issue sequence built from the requested range.using
covidcast(......., issues = epirange(12340101, 34560101))
@melange396 was this the usage you thought was causing performance problems?
Currently as I understand it, there's not a super convenient way in the
covidcast_signal()
function (in the covidcast R package) to specify that I want all issues of a single data point. To get all issues of the JHU deaths in PA on Sept 1, I could use, for example:It would be convenient if I could set
issues = "*"
to return the same thing. Similar for Python.Tagging @sarah-colq @chinandrew to draw their attention. This is pretty low priority, but should be an easy fix.