covidatlas / li

Next-generation serverless crawler for COVID-19 data
Apache License 2.0
57 stars 33 forks source link

Incorrect time series cases for Alameda County from July 7 to August 2+ #370

Closed 1ec5 closed 4 years ago

1ec5 commented 4 years ago

timeseries-byLocation.json is reporting incorrect cumulative case totals for Alameda County, California. The case total dropped from 6,887 on July 6 to just 6 on July 7, slowly rebounding to 11 by August 2. That’s far less than the number of deaths. In reality, Alameda County is reporting 11,524 cases total, including 402 in Berkeley, as of August 2.

{
      "2020-07-06": {
        "cases": 6887,
        "deaths": 140,
        "growthFactor": 1
      },
      "2020-07-07": {
        "cases": 6,
        "deaths": 140,
        "growthFactor": 0
      },
      "2020-07-08": {
        "cases": 7,
        "deaths": 142,
        "growthFactor": 1.17
      },
      "2020-07-09": {
        "cases": 7,
        "deaths": 146,
        "growthFactor": 1
      },
      "2020-07-10": {
        "cases": 7,
        "deaths": 147,
        "growthFactor": 1
      },
      "2020-07-11": {
        "cases": 7,
        "deaths": 148,
        "growthFactor": 1
      },
      "2020-07-12": {
        "cases": 7,
        "deaths": 148,
        "growthFactor": 1
      },
      "2020-07-13": {
        "cases": 7,
        "deaths": 148,
        "growthFactor": 1
      },
      "2020-07-14": {
        "cases": 8,
        "deaths": 152,
        "growthFactor": 1.14
      },
      "2020-07-15": {
        "cases": 8,
        "deaths": 154,
        "growthFactor": 1
      },
      "2020-07-16": {
        "cases": 8,
        "deaths": 154,
        "growthFactor": 1
      },
      "2020-07-17": {
        "cases": 8,
        "deaths": 161,
        "growthFactor": 1
      },
      "2020-07-18": {
        "cases": 9,
        "deaths": 162,
        "growthFactor": 1.13
      },
      "2020-07-19": {
        "cases": 9,
        "deaths": 162,
        "growthFactor": 1
      },
      "2020-07-20": {
        "cases": 9,
        "deaths": 162,
        "growthFactor": 1
      },
      "2020-07-21": {
        "cases": 9,
        "deaths": 167,
        "growthFactor": 1
      },
      "2020-07-22": {
        "cases": 9,
        "deaths": 171,
        "growthFactor": 1
      },
      "2020-07-23": {
        "cases": 9,
        "deaths": 173,
        "growthFactor": 1
      },
      "2020-07-24": {
        "cases": 10,
        "deaths": 178,
        "growthFactor": 1.11
      },
      "2020-07-25": {
        "cases": 10,
        "deaths": 178,
        "growthFactor": 1
      },
      "2020-07-26": {
        "cases": 10,
        "deaths": 178,
        "growthFactor": 1
      },
      "2020-07-27": {
        "cases": 10,
        "deaths": 178,
        "growthFactor": 1
      },
      "2020-07-28": {
        "cases": 10,
        "deaths": 181,
        "growthFactor": 1
      },
      "2020-07-29": {
        "cases": 10,
        "deaths": 181,
        "growthFactor": 1
      },
      "2020-07-30": {
        "cases": 11,
        "deaths": 182,
        "growthFactor": 1.1
      },
      "2020-07-31": {
        "cases": 11,
        "deaths": 182,
        "growthFactor": 1
      },
      "2020-08-01": {
        "cases": 11,
        "deaths": 189,
        "growthFactor": 1
      },
      "2020-08-02": {
        "cases": 11,
        "deaths": 189,
        "growthFactor": 1
      }
}
1ec5 commented 4 years ago

371 should fix this issue going forward, but I didn’t address the bad data that’s already in the cache.