# \[CALL\] Making COVID-19 Data Computable

**URL:** <https://community.wolfram.com/t/call-making-covid-19-data-computable/15583>\
**Category:** Staff Picks\
**Tags:** biological-sciences, data-science, medical-sciences, curated-data, staff-pick, events-and-media, living-systems\
**Created:** [March 25, 2020, 10:08pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583 "2020-03-25T22:08:29Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![alanj](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/alanj/32/12575_2.png) [@alanj](https://community.wolfram.com/u/alanj)\
**Post date:** [March 25, 2020, 10:08pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/1 "2020-03-25T22:08:29Z")

</div>

_MODERATOR NOTE: coronavirus resources & updates:_ [https://wolfr.am/coronavirus](https://wolfr.am/coronavirus)

* * *

It’s inspiring to see so many people in the community devoting time and expertise to tracking and understanding this pandemic. Here at Wolfram, we’ve been trying to keep on top of a few critical datasets related to COVID-19 (see the “Curated Computable Data” section in the main hub post linked above) and present them through the Wolfram Data Repository so they’re ready for immediate analysis in the Wolfram Language. But there are obviously tons of other data resources available, either directly relating to the pandemic or providing helpful historical, medical, or other context. We’ve had a lot of different suggestions inside the company for further additions to WDR or Wolfram|Alpha, but we can’t possibly tackle everything — so we’d like to invite people in the community to contribute to making more data surrounding this topic computable.

First: there are a few suggestions below, but we’d welcome others; I’d hope that part of this hub could just be a growing list of links to useful and relevant external data sources. Even if you don’t have the time or ability to scrape and transform a particular dataset yourself, someone else might be able to tackle it. A few initial ideas:

- [Spanish Flu data (R code applied to data from mortality.org)](https://kieranhealy.org/blog/archives/2020/03/05/spanish-flu/)
- [Spanish Flu in NYC](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4082668/)
- [Past Pandemics](https://www.cdc.gov/flu/pandemic-resources/basics/past-pandemics.html)
- [Italian COVID-19 data](https://github.com/pcm-dpc/COVID-19)
- [National Notifiable Diseases Surveillance System](https://data.cdc.gov/browse?category=NNDSS&sortBy=last_modified)
- [FAO Food Price Monitoring and Analysis Tool](https://fpma.apps.fao.org/giews/food-prices/tool/public/#/home)
- [US Health Weather Map](https://healthweather.us)
- [State actions to address coronavirus](https://www.kff.org/health-costs/issue-brief/state-data-and-policy-actions-to-address-coronavirus)

Second: if you have the time and inclination to scrape data from one of these sources and try to put it in a more computable form, please jump in and do so! We’ve already seen what people can do with the “curated computable data” we’re providing, and having more neatly-packaged data resources available to the community would benefit everyone.

If you’re not completely confident in your Wolfram Language data curation skills, we do have a lot of resources to help you improve, like a helpful screencast series at

[GitHub - WolframResearch/Data-Curation-Training · GitHub](https://github.com/WolframResearch/Data-Curation-Training).

And if you’ve got a dataset or collection of data around this topic that you’d like to make available to the community — I strongly recommend preparing it using the Data Resource Definition Notebook (available from the File menu in Mathematica, as below):

 ![PastedGraphic-29.jpg](https://global.discourse-cdn.com/wolfram/original/2X/9/90a9a71dfae476fab2cca731b7eb2cc066a86e96.jpeg)

Particularly for work being done around the topic of COVID-19, where time is of the essence and many data resources are changing rapidly, I’d also strongly encourage you to deploy finished resources directly to the cloud, instead of submitting to the Wolfram Data Repository for formal review and publication:

 ![PastedGraphic-28.jpg](https://global.discourse-cdn.com/wolfram/original/2X/6/60b2765c19d3d6a320f61d2072453d55706b0743.jpeg)

Deploying resources in this way will make them easily and immediately accessible to other users, and also automatically create a “shingle” for your data resource where anyone can view your data and analysis, while Wolfram Language users can directly access the underlying data as easily as any object published in the WDR:

```
DateListPlot[
 ResourceData[
   "https://www.wolframcloud.com/obj/alanj/DeployedResources/Data/Hospital-Beds-by-Country"][All, #TotalBedsPer1000Inhabitants &]]

```

 ![PastedGraphic-30.png](https://global.discourse-cdn.com/wolfram/original/3X/2/9/29e4a6e5bc1e9f7cffb6683a837d7da771498d4f.png)

In the interest of making data available to people as quickly as possible, this is probably the best route to follow right now — but I would definitely hope to see lots of user creations become formal Wolfram Data Repository submissions eventually, after “peer review” and revision by the community.

---

<div class="post-metadata">

**Author:** ![bobs](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/bobs/32/24995_2.png) [@bobs](https://community.wolfram.com/u/bobs)\
**Post date:** [March 27, 2020, 9:37pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/2 "2020-03-27T21:37:40Z")

</div>

For United States data two nice sources are [https://covidtracking.com/](https://covidtracking.com/) and the NY Times git hub repo here: [GitHub - nytimes/covid-19-data: A repository of data on coronavirus cases and deaths in the U.S. · GitHub](https://github.com/nytimes/covid-19-data).  
With some help I created resource functions for importing the latest data from each of them.  
They were both published in the Wolfram Function Repository today.

[https://resources.wolframcloud.com/FunctionRepository/resources/COVIDTrackingData](https://resources.wolframcloud.com/FunctionRepository/resources/COVIDTrackingData)  
[https://resources.wolframcloud.com/FunctionRepository/resources/NYTimesCOVID19Data](https://resources.wolframcloud.com/FunctionRepository/resources/NYTimesCOVID19Data)

See the documentation pages above for examples on how to use them.

Unlike data repository entries where data is periodically updated but always good, these function repository entries are dependent on evolving third party services, so they could break. But they always grab the latest data from those services.

---

<div class="post-metadata">

**Author:** ![rhrimmer](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/rhrimmer/32/16480_2.png) [@rhrimmer](https://community.wolfram.com/u/rhrimmer)\
**Post date:** [March 27, 2020, 9:47pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/3 "2020-03-27T21:47:37Z")

</div>

[Open in Wolfram Cloud ↗](https://www.wolframcloud.com/obj/0c0c4f3c-8b5e-4d0c-807d-e02cd90aa9ab)

---

<div class="post-metadata">

**Author:** ![alanj](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/alanj/32/12575_2.png) [@alanj](https://community.wolfram.com/u/alanj)\
**Post date:** [April 10, 2020, 7:20pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/4 "2020-04-10T19:20:31Z")

</div>

We’ve had a few other WDR additions in the past week or so — not all directly related to COVID-19, but possibly of use for historical or other kinds of context:

- [https://datarepository.wolframcloud.com/resources/OECD-Data-Hospital-Beds-Per-Country](https://datarepository.wolframcloud.com/resources/OECD-Data-Hospital-Beds-Per-Country)
- [https://datarepository.wolframcloud.com/resources/Hospital-Beds-Per-US-State](https://datarepository.wolframcloud.com/resources/Hospital-Beds-Per-US-State)
- [https://datarepository.wolframcloud.com/resources/COVID-19-Hospital-Resource-Use-Projections](https://datarepository.wolframcloud.com/resources/COVID-19-Hospital-Resource-Use-Projections)

---

<div class="post-metadata">

**Author:** ![betwys1](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/betwys1/32/29856_2.png) [@betwys1](https://community.wolfram.com/u/betwys1)\
**Post date:** [April 13, 2020, 11:31pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/5 "2020-04-13T23:31:05Z")

</div>

I have tracked accumulated Case and Death data for Oklahoma from Worldometers.info.

Because these data are somewhat noisy, I used an exponential low pass on the input with time constant ~ 3 days and fit the series to a sigmoid function of this kind: cases = k / (1 + exp( A - b\*days)) like this:

 ![4-11-Elogistic.jpg](https://global.discourse-cdn.com/wolfram/original/3X/b/f/bf44578308edfe67e29a2c4aa1c6172efeab9fb2.jpeg)

I continue by presenting the logistic function (with best-fit parameters) to Wolfram Alpha to plot the differential : which is cases per day like this:

 ![4-11-CasePerDayDistribution.jpg](https://global.discourse-cdn.com/wolfram/original/3X/c/3/c386190f0c974f8929785ad8528b55a3e3b93af5.jpeg)

In the same way I fit deaths to a logistic like this:

 ![4-11N-deaths.jpg](https://global.discourse-cdn.com/wolfram/original/1X/291f042717206fb1d224c75e0785b7682a29c7c8.jpeg)

and the resulting Alpha plot of death rate like this:

 ![4-11N-DeathRateOK.jpg](https://global.discourse-cdn.com/wolfram/original/3X/3/5/35261ace9d9d0169d757851f9e2176455f401b75.jpeg)

Here is a plot of residual errors in the case fitting function:

 ![OKCV-19-CaseFitResiduals.jpg](https://global.discourse-cdn.com/wolfram/original/2X/8/81fc2ab90cd4172900e75ba7fee2d93a232f320f.jpeg)

I noticed a growing 7 day oscillation in reported cases. This may be a clerical artifact - or some intyernal dynamic.

DISCUSSION.  
The logistic function is just two model steps away from the initial exponential function, and for later days the intermediate Straight Line fit. It provides high R^2 values for the largely pre-peak data. The logistic function has a short-coming to balance its simplicity: it uses the same exponential parameters before AND after the peak. This may become less realistic if the post-peak data decays on a LONGER time constant as it may well do. I hope that this approach may dissuade modelers starting from case/day data which is inevitably more noisy than the sigmoid case progression.  
It is perfectly possible to require the non-linear regression application to refit the exponential rate after an established peak rate day, but I do not yet have sufficient data to make this practical.

---

<div class="post-metadata">

**Author:** ![rhrimmer](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/rhrimmer/32/16480_2.png) [@rhrimmer](https://community.wolfram.com/u/rhrimmer)\
**Post date:** [April 14, 2020, 1:14am UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/6 "2020-04-14T01:14:28Z")

</div>

You might want to look at these posts:

[Logistic Model for Quarantine Controlled Epidemics](https://wolfram.discourse.group/t/15516/1)

[Predicting Coronavirus Epidemic in United States](https://wolfram.discourse.group/t/15573/1)

---

<div class="post-metadata">

**Author:** ![mohammadb](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/mohammadb/32/14729_2.png) [@mohammadb](https://community.wolfram.com/u/mohammadb)\
**Post date:** [April 19, 2020, 11:18pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/7 "2020-04-19T23:18:16Z")

</div>

I’ve wrangled the [Google mobility data of USA and Canada](https://www.wolframcloud.com/obj/outreach/Published/USACanadaGoogleMobilityData.nb)

---

<div class="post-metadata">

**Author:** ![betwys1](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/betwys1/32/29856_2.png) [@betwys1](https://community.wolfram.com/u/betwys1)\
**Post date:** [April 20, 2020, 2:31pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/8 "2020-04-20T14:31:19Z")

</div>

This note gave me a warm fuzzy for sure! I don’t have an immediate need, but it speaks to practical purposes for useful ends. Thank you! Brian W

---

<div class="post-metadata">

**Author:** ![mohammadb](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/mohammadb/32/14729_2.png) [@mohammadb](https://community.wolfram.com/u/mohammadb)\
**Post date:** [April 21, 2020, 6:26pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/9 "2020-04-21T18:26:08Z")

</div>

I’ve wrangled the US county data of Cases and Deaths from JHU dataset.

```
CloudGet[CloudObject[
  "https://www.wolframcloud.com/obj/47230f9f-9bc0-4682-9aff-bdde93e98544"]]

```

The dataset has this structure:

 ![ScreenShot2020-04-21at11.15.40AM.png](https://global.discourse-cdn.com/wolfram/original/3X/4/a/4a957e5850252d034b9699e439075ef30e34beb1.png)

Example:

```
CloudGet[CloudObject[
    "https://www.wolframcloud.com/obj/47230f9f-9bc0-4682-9aff-bdde93e98544"]][
  SelectFirst[#USCounty == 
     Entity["AdministrativeDivision", {"LosAngelesCounty", 
       "California", "UnitedStates"}] &]][
 DateListPlot[
   Through[{Differences, 
      MovingAverage[Differences[#], Quantity[1, "Weeks"]] &}[#Cases]],
    PlotRange -> All, 
   PlotLegends -> {"Daily new cases", "Filtered over 1 week"}] &]

```

 ![ScreenShot2020-04-21at11.25.35AM.png](https://global.discourse-cdn.com/wolfram/original/3X/c/3/c31768e999ad617856de987737b730c06a5a04ba.png)

---

<div class="post-metadata">

**Author:** ![mohammadb](https://yyz1.discourse-cdn.com/wolfram/user_avatar/community.wolfram.com/mohammadb/32/14729_2.png) [@mohammadb](https://community.wolfram.com/u/mohammadb)\
**Post date:** [April 26, 2020, 11:43pm UTC](https://community.wolfram.com/t/call-making-covid-19-data-computable/15583/10 "2020-04-26T23:43:20Z")

</div>

Please check out [my post](https://community.wolfram.com/groups/-/m/t/1955760) where I processed Facebook population density map and make them computable datasets in Wolfram Language. It can be very useful for epidemic models using population densities.
