The U.S. COVID-19 Atlas provides county-level visualizations and analytics to reveal a more detailed pandemic landscape with local hotspots of surging COVID cases that are missed by state-level data.
The current Atlas is available here: https://USCovidAtlas.org. The Atlas is being updated everyday before 12pm, CT. We are working on releasing regular updates with more data, functions, and analysis.
For more information about additional datasets used in the Atlas, see our Data page.
Because there is no one single validated source for county-level COVID cases and deaths for real-time analysis, we incorporate multiple datasets from multiple projects to allow for comparisons. For now, two datasets are available. More will be incorporated later.
- USAFacts:this dataset is provided by a non-profit organization. The data are aggregated from CDC, state- and local-level public health agencies. County-level data is confirmed by referencing state and local agencies directly.
- 1P3A: This was the initial, crowdsourced data project that served as a volunteer project led by Dr. Yu Gao, Head of Machine Learning Platform at Uber. We access this data stream using a token provided by the group.
- CDC: the US Center for Disease Control and Prevention is the nation's health protection agency. The data provided includes vaccination and county level testing data.
- New York Times: the New York Times newspaper releases time-series data compiled from state and local governments and health departments. The data is available via their github repository and is updated several times each day.
We also include information from the following datasets:
- American Community Survey. We incorporate population data used to generate rates, and will add more information as needed in future iterations.
- COVIDCareMap. Healthcare System Capacity includes Staffed beds, Staffed ICU beds, Licensed Beds by County. This data aggregates information about the healthcare system capacity with additions/edits allowed in real-time.. It sources data from the Healthcare Cost Report Information System (HCRIS) and an open hospital facilities dataset by Definitive Healthcare.
- County Health Rankings & Roadmaps: social, economic, and health indicators by County.
- Bin Yu Group: Predicted death counts and Severity index by County
- Native American Reservations: boundary for Native American Reservations.
- Hypersegregated Cities: boundary for historical and current hypersegregated cities.
We have multiple datasets planned for future inclusion in the atlas, including:
- DesCartes Lab: Mobility index by County
- PlaceIQ, Couture et al: Limited Exposure Index by County
To access raw 1P3A data, you must contact the 1P3A for a token directly.
Not all cases from 1P3A data can be assigned to a particular county, see following (the list is being updated as new data comes in everyday)
- 1P3A does NOT assign cases in New York to specific counties, which includes New York City, Kings, Bronx, and Richmond.
- Cases reported for US Virgin Islands, Guam are NOT included.
- Cases in the following areas can NOT be assigned and hence are NOT included: Southwest Utah; Southeast Utah; Central Utah; Tri County, Utah; Kansas City, MO; Benton and Franklin, WA.
- Other unassigned cases (or “cases to be assigned”) are NOT included.
- Cases reported in the Military and some Correctional Centers are NOT included.
For a complete breakdown about the methods used in the Atlas, see our Methods page.
The hotspot detection ( a Local Indicator of Spatial Autocorrelation) is powered by Geoda. We also use many other features from GeoDa including natural breaks classification and cartogram techniques. See below for how one can apply these methods to reproduce the results using above datasets.
- Natural breaks choropleth map
- Cartogram
- Queen contiguity spatial weights creation
- Local Moran statistics
- Univariate Local Indicator of Spatial Autocorrelation (LISA)
More information about the Geoda project can be found here.
We are growing a coalition of research partners that have been integral to developing and expanding the Covid Atlas to meet the needs of health practitioners, planners, researchers, and the public. This is an open-source collaborative project.
- Center for Spatial Data Science (CSDS) at the University of Chicago. The Atlas was originally developed as a project co-led by Marynia Kolak, Xun Li, and Qinyun Lin at the Center for Spatial Data Science, where it remains as its home institution. CSDS leads the development and management of the atlas with developers Robert Martin and Arianna Israel.
- The Yu Group at UC Berkeley’s Department of Statistics is working with Response4Life to develop a severity index for each hospital to help distribute supplies when they become available. The Yu Group generates daily updates of COVID data and contributes both hospital and county-level severity index data for the Atlas.
- County Health Rankings & Roadmaps (CHR&R) led by Lawrence Brown. CHR’s goal is to improve health outcomes for all and to close the health gaps between those with the most and least opportunities for good health. CHR leads efforts to connect socioeconomic and health vulnerability indicators to the Atlas to better contextualize and inform findings.
- CSI Solutions led by Roger L. Chaufournier and Kathy Reims are critical to connecting the Atlas with rural health partners across the country to define and prioritize needs for care management during the pandemic. CSI leads efforts in developing and refining this “Communities of Practice” forum.
- AFI DSI COVID-19 Research Group at UW-Madison. This group led by Brian Yandell was an early institutional partner to amplify regional efforts to respond to the pandemic. Kevin Little of Informing Ecological Design was critical in connecting the Atlas team with a nationwide network and leading user-group sessions to review the atlas, align priorities, and ensure it was effective for a wide audience. Steve Goldstein continues to work with our team in data validation efforts.
We highly appreciate our many contributors and volunteers, including:
- Erin Abbott (CSDS)
- Sihan Mao (CSDS Alumni, City of Pittsburgh)
- Karina Acoste (CSDS)
- Julia Koschinsky (CSDS)
- Luc Anselin (CSDS)
- Bibind Vasu (CSDS)
- John Steill (UW-Madison)
- Sean Kent (UW-Madison)
- Steven Wangen (UW-Madison)
- Yuetian Luo (UW-Madison)
- Fletcher Barryman (CSDS)
If you have a question regarding a specific dataset, please contact the dataset author(s) directly. If you have any questions regarding the Atlas, feel free to pose an issue here or contact us by: mkolak@uchicago.edu or qinyunlin@uchicago.edu.
Please cite us using: Xun Li, Qinyun Lin, Marynia Kolak, Robert Martin, Stephanie Yang, Moksha Menghaney, Ari Israel, Ryan Wang, Vidal Anguiano Jr., Erin Abbott, Dylan Halpern, Sihan-Mao. (2020, October 12). GeoDaCenter/covid: beta (Version beta). Zenodo. http://doi.org/10.5281/zenodo.4081869
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.