Skip to content

Consider supplying both smoothed + raw values in each COVIDcast signal #131

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

Closed
krivard opened this issue Jun 15, 2020 · 1 comment
Closed
Labels
Engineering Used to filter issues when synching with Asana

Comments

@krivard
Copy link
Contributor

krivard commented Jun 15, 2020

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
Copy link
Contributor Author

krivard commented Feb 2, 2023

wontfix

@krivard krivard closed this as completed Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Used to filter issues when synching with Asana
Projects
None yet
Development

No branches or pull requests

2 participants