Most COVIDcast signals come in two flavors: smoothed and raw.
doctor-visits: no, for datasource privacy reasons
fb-survey: yes; CLI, ILI, WCLI, WILI, HH community CLI, no-HH community CLI
google-survey: yes
ght: yes
quidel: yes; percent negative, tests per device
jhu: in testing for 1.4
Considering cmu-delphi/www-covidcast#TBD, it might be nice to explicitly combine raw+smoothed pairs of signals instead of publishing them separately, and provide them as an extra column in the API response (even if they are still stored separately in the database).
This would also help with cmu-delphi/covidcast-indicators#67 and cmu-delphi/covidcast-indicators#36, since it would permit us to display the raw signal in time series charts without interfering with map coloring. The raw time series does not display the misleading sawtooth pattern.
krivard
commented
1 year ago
Most COVIDcast signals come in two flavors: smoothed and raw.
Considering cmu-delphi/www-covidcast#TBD, it might be nice to explicitly combine raw+smoothed pairs of signals instead of publishing them separately, and provide them as an extra column in the API response (even if they are still stored separately in the database).
This would also help with cmu-delphi/covidcast-indicators#67 and cmu-delphi/covidcast-indicators#36, since it would permit us to display the raw signal in time series charts without interfering with map coloring. The raw time series does not display the misleading sawtooth pattern.