Colorado

State: CO

Dates affected: 02/19/21

Describe the issue: On February 19, 2021, we had in error in Colorado's Total PCR tests (people). This also affected Negative PCR tests (people), which is calculated as Total PCR tests (people) minus Confirmed cases.

Screenshot with correct data: https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-quaternary-20210219-231911.png

State: CO

Dates affected: 02/19/21

Describe the issue: On February 19, 2021, we had in error in Colorado's Total PCR tests (people). This also affected Negative PCR tests (people), which is calculated as Total PCR tests (people) minus Confirmed cases.

Screenshot with correct data: https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-quaternary-20210219-231911.png

State: CO

Dates affected: 01/26/21

Describe the issue: On January 26, 2021, Colorado's Positive Cases PCR, Probable Cases, Negative Cases, Curr Hosp, Confirmed Deaths, and Probable Deaths did not update by our publication time.

State: CO

Dates affected: 01/26/21

Describe the issue: On January 26, 2021, Colorado's Positive Cases PCR, Probable Cases, Negative Cases, Curr Hosp, Confirmed Deaths, and Probable Deaths did not update by our publication time.

State or US: CO

Describe the problem Colorado's deaths due to COVID-19 metric is lagging its deaths among cases metric. On September 1, there was only 97 difference: 1946 deaths among cases, vs. 1849 deaths due to COVID. On December 11, there is a 759 difference—3759 deaths among cases, as opposed to 3005 deaths due to COVID. This means 20% of deaths among cases do not have death certificate data, vs. 5% in September, indicating a lag.

Link to data source https://covidtracking.com/data/state/colorado/screenshots CO's raw data files for confirmed/probable death breakdowns: https://www.arcgis.com/home/webmap/viewer.html?url=https://services3.arcgis.com/66aUo8zsujfVXRIT/ArcGIS/rest/services/colorado_covid19_daily_state_statistics_cumulative/FeatureServer&source=sd

State: CO

Dates affected: 12/2

Describe the issue: On December 2, 2020, Colorado did not update their Positive antibody tests (specimens) or Negative antibody tests (specimens) before the time of our daily update.

State or US: North Dakota

Describe the problem Over the past week, a gap has opened between the number of COVID-19 deaths North Dakota's health department reports and The COVID Tracking Project’s counts of deaths in the state. On November 30, North Dakota’s health department dashboard reported 927 cumulative COVID-19 deaths, but The COVID Tracking Project recorded 680. This is because we track deaths due to COVID, instead of deaths among cases in the state.

It’s clear that a reporting backlog is to blame for most of the widening discrepancy between figures: The share of COVID-19-positive individuals who died in North Dakota with death certificates still pending has doubled since the beginning of November. To better reflect the reality of rising deaths in North Dakota, we are changing our method for counting deaths in the state to the other main paradigm for tracking deaths: counting deaths among cases.

Link to data source https://covidtracking.com/data/state/north-dakota/screenshots

State: CO

Dates affected: 11/28

Describe the issue: On November 28, 2020, Colorado's Positive antibody tests (specimens) and Negative antibody tests (specimens) updated after we published our daily update.

State: CO

Dates affected: 11/18

Describe the issue: On 11/18, Colorado updated their Positive antibody tests (specimens) and Negative antibody tests (specimens) after our daily update.

State or US: Colorado

Describe the problem

1. Because of the timing of the data entry shift, we are regularly a day behind in our capture of Colorado's reporting. We are going to shift the entire timeseries in order to match up with what we would have captured on an evening shift each day from Colorado.
2. We are also going to patch up a few values to Total Tests PCR (People), Cumulative Hospitalizations, Deaths , and Cases (Confirmed and Probable) columns from a download from Colorado's website

Link to data source https://services3.arcgis.com/66aUo8zsujfVXRIT/ArcGIS/rest/services/colorado_covid19_daily_state_statistics_cumulative/FeatureServer/0

State: CO

Dates affected: 11/11

Describe the issue: The 11/11 timestamp for CO was entered as 11/10 23:59, but should have been 11/09 23:59.

State or US: Colorado

Describe the problem While doing probables backfill in https://github.com/COVID19Tracking/issues/issues/812, I discovered three main issues between CTP values and the state screenshots/archive:

1. We sourced a few of our total positive values from the respective day's PR. The issue with this is that, while those values were the most up to date values at the time of the PR, they were unaligned with the screenshots and the 1 day lag on the dashboard which throws off the proposed probable values' alignment. The days we used PR values are 4/29, 5/8, 5/10, and 5/11. These values should be changed to 14316, 18371, 19375, 19703, respectively.

2. Separate from these PRs, we had two values entered incorrectly on 4/25 (12256) and 8/27 (52229). These values should be changed to 12255 and 52228, respectively, to reflect the screen-shotted values from those days and the values from the archived files mentioned above. These revisions are also in blue in the proposed section.

3. Lastly, we entered the total positive value in the confirmed case column on 6/13. The value should be changed from 28822 to 26215 to reflect the screenshotted value/archived value.

Links to data sources 4/25: https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-20200424-180528.png ; https://docs.google.com/spreadsheets/d/1QcI_QvssZpVxT5ib6yHoeHchLIuIIZkX45eKrn4ciCU/edit#gid=1892357304

4/29: https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-20200429-000541.png

5/8: https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-20200507-180530.png

5/10: https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-20200509-180520.png

5/11: https://docs.google.com/spreadsheets/d/1e2TLX1eJw9kueTZBssoA9eRWIwEtpgC3HZODao9mGGo/edit#gid=1282281468 ; https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-20200511-120513.png

6/13: https://drive.google.com/drive/folders/1bBAC7H-pdEDgPxRuU_eR36ghzc0HWNf1

8/27: https://docs.google.com/spreadsheets/d/1sU6w75m7SXuRR7gZxMiMhFksez6D9V2pGFjFZaLwRso/edit#gid=1728791480 (confirmed/probable breakdown not available in screenshots due to changed dashboard)

This issue solves https://github.com/COVID19Tracking/issues/issues/423

State or US: Colorado

Describe the problem On 7/28, CTP introduced an explicit probables column. Backfilling through 4/24 (when CO first separated out confirmed cases on their dashboard) by subtracting confirmed cases from total cases. Fixing issues with confirmed/probables in https://github.com/COVID19Tracking/issues/issues/848

Link to data source We have screenshots of probables through 4/24 to reference. We also have a state-provided archive with probable values: https://drive.google.com/drive/folders/1bBAC7H-pdEDgPxRuU_eR36ghzc0HWNf1

4/24 screenshot: https://covid-tracking-project-data.s3.us-east-1.amazonaws.com/state_screenshots/CO/CO-20200424-000533.png

The data is available in files here: https://drive.google.com/drive/folders/1bBAC7H-pdEDgPxRuU_eR36ghzc0HWNf1

Describe the problem The server does not appear to be returning Access-Control-Allow-Origin headers along with API requests.

This results in web browser errors such as: XMLHttpRequest at 'https://covidtracking.com/api/v1/us/daily.json' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I believe that the API server should be returning an Access-Control-Allow-Origin: * header, and that this would resolve the problem.

I don't have prior experience with these kinds of issues, so please forgive my ignorance if any of this is incorrect. I only began receiving these errors today for the first time, and I've been using this API for months now. I've temporarily mitigated the problem by routing all API requests through https://cors-anywhere.herokuapp.com/ but this doesn't seem like a great permanent solution.

Thanks for all your time and efforts!

CO publishes a "Test Encounters" value, and we recently added it to our worksheet, we need to backfill past data for this metric

We started collecting numbers on 7/27, when CO started publishing them on the dashboard.

To fill the values before 7/27, we used the "Testing Encounters" daily bar chart, to calculate cumulative sum by date. The values we used in this initial population of the time series were calculated from data as downloaded on 8/1.

We're using this calculated backfill only for dates before the 27th, and going forward (despite the bar chart with daily test encounters being continuously back-filled) we're only going to use the number posted on the dashboard. Since the numbers on the dashboard normally correspond to data as of two days previous, we are shifting the total test encounters to reflect what would have been displayed on the dashboard on the corresponding date.

On 12-July, CO reported 36,591 cases. Needs to be fixed from 36,951

State or US: Idaho

Describe the problem We did not capture these values before but they are available, so we should fill out the historical values

Link to data source https://public.tableau.com/profile/idaho.division.of.public.health#!/vizhome/DPHIdahoCOVID-19Dashboard_V2/Story1 Click Hospitalizations

Starting May 15, CO reports four different numbers about deaths: "deaths among cases," confirmed/probable breakdowns for "deaths among cases," and "deaths due to COVID-19." Deaths among cases captures information about all deaths in probable or confirmed COVID cases (e.g. determined by testing data for confirmed, syndromic or epidemiological evidence for probable), while "deaths due to COVID-19" tracks cases where COVID is listed on the death certificate.

Right now, we fill out our columns like this: Deaths (confirmed+probable): "deaths among cases" Deaths (confirmed): "deaths among cases (confirmed)" Deaths (probable): "deaths among cases (probable"

However, to maintain consistency with other states (e.g. ND) that provide data about whether COVID was the cause of death , we do not want to track "deaths among cases" but "deaths due to COVID-19," which tracks death certificate data. Hence for May 15 onward, we are going to switch to:

Deaths (confirmed+probable): "deaths due to COVID 19" Deaths (confirmed): no data (since "deaths due to COVID-19" is not broken down to confirmed/probable) Deaths (probable): "no data (since "deaths due to COVID-19" is not broken down to confirmed/probable)

We will add back the data for "deaths among cases (confirmed)" at a later date when we add a column for deaths w/ positive lab tests but not necessarily COVID as a cause of death on a death certificate.

State or US: CO

Describe the problem Updating historical values for "Total PCR Tests (People)" for CO prior to implementation of this column. Historicals updated from 3/17 to 5/14, using the screenshot captured at 6 - 7 pm the previous day. Unfortunately due to lack of screenshots, gaps will exist on 3/27, 4/9 and 5/18.

Link to data source https://covidtracking.com/data/state/colorado#historical

"I think there's an issue with Colorado 5-12-20 info. It indicated that there was "-133" new tests, which makes no sense."

Based on the screenshots form 5/11 it appears that Positive Cases should have be 19,703 instead of 19,899, causing the there to be negative new test and cases on 5/12

Front conversations

I suggest publishing both sets of numbers. I have used this site to track the numbers, but they need to be accurate.

https://www.cdc.gov/nchs/nvss/vsrr/covid19/index.htm

Hello. I have been tracking COVID-19 on worldometers.info/coronavirus since mid-March.

You report U.S. deaths at 52,525 as of yesterday.

Yesterday, worldometers.info/coronavirus reported 57,862.

Which number is correct?

Thank you!

for example, this data set has the following info for positive tests by date: 4/23 10,878 4/24 11,262 4/25, 12,256 4/26, 12968

The CO state website (listed as the best source of data on the covid tracking website) lists this data 4/23 12,256 4/24 12,947 4/25, 13,441 4/26, not listed yet

Similarly, on new deaths, the covid tracking project shows 44 new deaths on 4/24, whereas the CO state website shows 2.

These are not the only issues, just illustrations to show the data doesn't match.

I would like to ask you if it is possible to obtain the following dataset as time-series dataset:

https://docs.google.com/spreadsheets/d/e/2PACX-1vTfUQPxkhP_CRcGmnnpUBihnTNZ9Z8pcizII4_sc2o2n3opOoAJdAM4CRTJBI339tou8LWnQrqbTMgH/pubhtml?gid=1129119811&single=true

Best, Riccardo

RE: https://covidtracking.com/data/state/wisconsin#historical

How can the new tests for March 30 be negative??

https://covidtracking.com/data/state/washington#historical positives dropped from 4/19 to 4/20

At https://covidtracking.com/data/state/california#historical it appears that the data around April 10-12 seems odd. Flat, then big jump?

https://covid19.colorado.gov/hospital-data

Hi, a great initiative you have for consolidating US COVID-19 data. I'm the author of the CovidJSON initiative, a standards based GeoJSON data model for infection data. Our goal is to harmonize national and international data interchange of COVID-19 data as geospatial datasets, and to make it easier to collect, publish, analyze and visualize infection data across different data providers and uses.

Would you be interested in testing out the CovidJSON format as an output format for the COVIDTracking API, providing input for improving it, and, in case you like it, promoting it's use for the different COVID-19 stakeholders within US?

I have some live data samples from Finland at https://data.covidjson.org/ and some static examples at https://github.com/spatineo/covidjson/tree/master/examples

Both are very influential sources -- I'd like to propose we focus more on improving hospitalization counts.

Statnews is using cumulative hospitalizations. JHU unfortunately appears to be mixing current and cumulative hospitalizations in their 'hospitalization rate' tab.

JHU dashboard: https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6 "the COVID Tracking Project (testing and hospitalizations)"

STAT Tracker:
https://www.statnews.com/2020/03/26/covid-19-tracker/ "The datasets are drawn from the Johns Hopkins University Center for Systems Science and Engineering, from the COVID Tracking Project, and from USAFacts. In some cases, data on hospitalizations were not available."

If they are on weekly updates, we should note that. Otherwise they may not be tracking the tests. Worrisome for one of the top hot-spots.

These can't both be right unless CO reported no data for 3/31:

The one you probably want to post in the States-info.csv file is the "Daily updated status report". Providing others in case you need to track data down to county level.

Daily updated status report - https://dph.georgia.gov/georgia-department-public-health-covid-19-daily-status-report

Links to JSON data behind the above report Total cases: https://sendss.state.ga.us/sendss/!ncovstatus.ajax?ptarget=obsummary Breakdown by Sex: https://sendss.state.ga.us/sendss/!ncovstatus.ajax?ptarget=gender Breakdown by Age Bucket: https://sendss.state.ga.us/sendss/!ncovstatus.ajax?ptarget=age Cases by County - https://sendss.state.ga.us/sendss/!ncovstatus.ajax_ncovmap

This is the data from the Colorado website

Colorado's data seems to come out first at https://covid19.colorado.gov/case-data today's was posted: Colorado Case Summary (Updated 3/31/20 at 4:00 p.m.)

I am going to extract a spreadsheet that contains the currently implemented logic for y'all to review.

It will in Excel and checked into the repo as a living document.