With the White House release of guidelines for states to reopen and employees to gradually return to work, facilities are tasked with complex challenges. Managers must make decisions to ensure a safe work environment and adhere to social distancing requirements. Office layouts must be restructured for adequate spacing between workspaces and to allow for routing that minimizes close-proximity encounters. Clear communication with staff will also be a key factor: Which areas should be avoided? When has an area last be cleaned?The ArcGIS Indoors system from Esri can help answer these geospatially focused questions for reopening the workplace. With indoor maps and an indoor positioning system, managers can create a floor-plan level awareness of the workplace, one that will allow for safe reopening._Communities around the world are taking strides in mitigating the threat that COVID-19 (coronavirus) poses. Geography and location analysis have a crucial role in better understanding this evolving pandemic.When you need help quickly, Esri can provide data, software, configurable applications, and technical support for your emergency GIS operations. Use GIS to rapidly access and visualize mission-critical information. Get the information you need quickly, in a way that’s easy to understand, to make better decisions during a crisis.Esri’s Disaster Response Program (DRP) assists with disasters worldwide as part of our corporate citizenship. We support response and relief efforts with GIS technology and expertise.More information...

The NFDI4Health Task Force COVID-19 Metadata Schema (MDS) Mapping to FHIR contains a list of properties describing a resource (study, questionnaire or document) being registered in the Central Search Hub of the NFDI4Health Task Force COVID-19 and their mapping to FHIR.

This map shows recent COVID-19 Trends with arrows that represent each county's recent trend history, and weekly new case counts for U.S. counties. The map data is updated weekly and featured in this storymap.It shows COVID-19 Trend for the most recent Monday with a colored arrow for each county. The larger the arrow, the longer the county has had this trend. An up arrow indicates the number of active cases continue upward. A down arrow indicates the number of active cases is going down. The intent of this map is to give more context than just the current day of new data because daily data for COVID-19 cases is volatile and can be unreliable on the day it is first reported. Weekly summaries in the counts of new cases smooth out this volatility.Click or tap on a county to see a history of trend changes and a weekly graph of new cases going back to February 1, 2020. This map is updated every Tuesday based on data through the previous Sunday. See also this version of the map for additional perspective.COVID-19 Trends show how each county is doing and are updated daily. We base the trend assignment on the number of new cases in the past two weeks and the number of active cases per 100,000 people. To learn the details for how trends are assigned, see the full methodology. There are five trends:Emergent - New cases for the first time or in counties that have had zero new cases for 60 or more days.Spreading - Low to moderate rates of new cases each day. Likely controlled by local policies and individuals taking measures such as wearing masks and curtailing unnecessary activities.Epidemic - Accelerating and uncontrolled rates of new cases.Controlled - Very low rates of new cases.End Stage - One or fewer new cases every 5 days in larger populations and fewer in rural areas.For more information about COVID-19 trends, see the full methodology.Data Source: Johns Hopkins University CSSE US Cases by County dashboard and USAFacts for Utah County level Data.

This map features satellite imagery for the world and high-resolution aerial imagery for many areas. The map is intended to support the ArcGIS Online basemap gallery. For more details on the map, please visit the World Imagery map service description.

The free database mapping COVID-19 treatment and vaccine development based on the global scientific research is available at https://covid19-help.org/.

Files provided here are curated partial data exports in the form of .csv files or full data export as .sql script generated with pg_dump from our PostgreSQL 12 database. You can also find .png file with our ER diagram of tables in .sql file in this repository.

Structure of CSV files

*On our site, compounds are named as substances

compounds.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Name - Name of the Substance/Compound (string)

3. Marketed name - The marketed name of the Substance/Compound (string)

4. Synonyms - Known synonyms (string)

5. Description - Description (HTML code)

6. Dietary sources - Dietary sources where the Substance/Compound can be found (string)

7. Dietary sources URL - Dietary sources URL (string)

8. Formula - Compound formula (HTML code)

9. Structure image URL - Url to our website with the structure image (string)

10. Status - Status of approval (string)

11. Therapeutic approach - Approach in which Substance/Compound works (string)

12. Drug status - Availability of Substance/Compound (string)

13. Additional data - Additional data in stringified JSON format with data as prescribing information and note (string)

14. General information - General information about Substance/Compound (HTML code)

references.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Impact factor - Impact factor of the scientific article (string)

3. Source title - Title of the scientific article (string)

4. Source URL - URL link of the scientific article (string)

5. Tested on species - What testing model was used for the study (string)

6. Published at - Date of publication of the scientific article (Date in ISO 8601 format)

clinical-trials.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Title - Title of the clinical trial study (string)

3. Acronym title - Acronym of title of the clinical trial study (string)

4. Source id - Unique identifier in the source database

5. Source id optional - Optional identifier in other databases (string)

6. Interventions - Description of interventions (string)

7. Study type - Type of the conducted study (string)

8. Study results - Has results? (string)

9. Phase - Current phase of the clinical trial (string)

10. Url - URL to clinical trial study page on clinicaltrials.gov (string)

11. Status - Status in which study currently is (string)

12. Start date - Date at which study was started (Date in ISO 8601 format)

13. Completion date - Date at which study was completed (Date in ISO 8601 format)

14. Additional data - Additional data in the form of stringified JSON with data as locations of study, study design, enrollment, age, outcome measures (string)

compound-reference-relations.csv

1. Reference id - Id of a reference in our DB (unsigned integer)

2. Compound id - Id of a substance in our DB (unsigned integer)

3. Note - Id of a substance in our DB (unsigned integer)

4. Is supporting - Is evidence supporting or contradictory (Boolean, true if supporting)

compound-clinical-trial.csv

1. Clinical trial id - Id of a clinical trial in our DB (unsigned integer)

2. Compound id - Id of a Substance/Compound in our DB (unsigned integer)

tags.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Name - Name of the tag (string)

tags-entities.csv

1. Tag id - Id of a tag in our DB (unsigned integer)

2. Reference id - Id of a reference in our DB (unsigned integer)
   

API Specification

Our project also has an Open API that gives you access to our data in a format suitable for processing, particularly in JSON format.

https://covid19-help.org/api-specification

Services are split into five endpoints:

• Substances - /api/substances

• References - /api/references

• Substance-reference relations - /api/substance-reference-relations

• Clinical trials - /api/clinical-trials

• Clinical trials-substances relations - /api/clinical-trials-substances

Method of providing data

• All dates are text strings formatted in compliance with ISO 8601 as YYYY-MM-DD

• If the syntax request is incorrect (missing or incorrectly formatted parameters) an HTTP 400 Bad Request response will be returned. The body of the response may include an explanation.

• Data updated_at (used for querying changed-from) refers only to a particular entity and not its logical relations. Example: If a new substance reference relation is added, but the substance detail has not changed, this is reflected in the substance reference relation endpoint where a new entity with id and current dates in created_at and updated_at fields will be added, but in substances or references endpoint nothing has changed.

The recommended way of sequential download

• During the first download, it is possible to obtain all data by entering an old enough date in the parameter value changed-from, for example: changed-from=2020-01-01 It is important to write down the date on which the receiving the data was initiated let’s say 2020-10-20

• For repeated data downloads, it is sufficient to receive only the records in which something has changed. It can therefore be requested with the parameter changed-from=2020-10-20 (example from the previous bullet). Again, it is important to write down the date when the updates were downloaded (eg. 2020-10-20). This date will be used in the next update (refresh) of the data.

Services for entities

List of endpoint URLs:

• /api/substances

• /api/references

• /api/substance-reference-relations

• /api/clinical-trials

• /api/clinical-trials-substances

Format of the request

All endpoints have these parameters in common:

• changed-from - a parameter to return only the entities that have been modified on a given date or later.

• continue-after-id - a parameter to return only the entities that have a larger ID than specified in the parameter.

• limit - a parameter to return only the number of records specified (up to 1000). The preset number is 100.

Request example:

/api/references?changed-from=2020-01-01&continue-after-id=1&limit=100

Format of the response

The response format is the same for all endpoints.

• number_of_remaining_ids - the number of remaining entities that meet the specified criteria but are not displayed on the page. An integer of virtually unlimited size.

• entities - an array of entity details in JSON format.

Response example:

{

"number_of_remaining_ids" : 100,

"entities" : [

{

"id": 3,

"url": "https://www.ncbi.nlm.nih.gov/pubmed/32147628",

"title": "Discovering drugs to treat coronavirus disease 2019 (COVID-19).",

"impact_factor": "Discovering drugs to treat coronavirus disease 2019 (COVID-19).",

"tested_on_species": "in silico",

"publication_date": "2020-22-02",

"created_at": "2020-30-03",

"updated_at": "2020-31-03",

"deleted_at": null

},

{

"id": 4,

"url": "https://www.ncbi.nlm.nih.gov/pubmed/32157862",

"title": "CT Manifestations of Novel Coronavirus Pneumonia: A Case Report",

"impact_factor": "CT Manifestations of Novel Coronavirus Pneumonia: A Case Report",

"tested_on_species": "Patient",

"publication_date": "2020-06-03",

"created_at": "2020-30-03",

"updated_at": "2020-30-03",

"deleted_at": null

},

]

}

Endpoint details

Substances

URL: /api/substances

Substances

The New York Times is releasing a series of data files with cumulative counts of coronavirus cases in the United States, at the state and county level, over time. We are compiling this time series data from state and local governments and health departments in an attempt to provide a complete record of the ongoing outbreak.

Since the first reported coronavirus case in Washington State on Jan. 21, 2020, The Times has tracked cases of coronavirus in real time as they were identified after testing. Because of the widespread shortage of testing, however, the data is necessarily limited in the picture it presents of the outbreak.

We have used this data to power our maps and reporting tracking the outbreak, and it is now being made available to the public in response to requests from researchers, scientists and government officials who would like access to the data to better understand the outbreak.

The data begins with the first reported coronavirus case in Washington State on Jan. 21, 2020. We will publish regular updates to the data in this repository.

A series of maps and applications about COVID-19 in Colorado. Includes case rates, impacted job sectors, social vulnerability index, unemployment insurance claims, outbreaks, large potentially at risk workplaces, enterprise zones and dashboards from other agencies. Updated regularly.

This map features satellite imagery for the world and high-resolution aerial imagery for many areas. The map is intended to support the ArcGIS Online basemap gallery. For more details on the map, please visit the World Imagery map service description.

The datasets used for this manuscript were derived from multiple sources: Denver Public Health, Esri, Google, and SafeGraph. Any reuse or redistribution of the datasets are subjected to the restrictions of the data providers: Denver Public Health, Esri, Google, and SafeGraph and should consult relevant parties for permissions.1. COVID-19 case dataset were retrieved from Denver Public Health (Link: https://storymaps.arcgis.com/stories/50dbb5e7dfb6495292b71b7d8df56d0a )2. Point of Interests (POIs) data were retrieved from Esri and SafeGraph (Link: https://coronavirus-disasterresponse.hub.arcgis.com/datasets/6c8c635b1ea94001a52bf28179d1e32b/data?selectedAttribute=naics_code) and verified with Google Places Service (Link: https://developers.google.com/maps/documentation/javascript/reference/places-service)3. The activity risk information is accessible from Texas Medical Association (TMA) (Link: https://www.texmed.org/TexasMedicineDetail.aspx?id=54216 )The datasets for risk assessment and mapping are included in a geodatabase. Per SafeGraph data sharing guidelines, raw data cannot be shared publicly. To view the content of the geodatabase, users should have installed ArcGIS Pro 2.7. The geodatabase includes the following:1. POI. Major attributes are locations, name, and daily popularity.2. Denver neighborhood with weekly COVID-19 cases and computed regional risk levels.3. Simulated four travel logs with anchor points provided. Each is a separate point layer.

This file has explanatory information for the template, including field numberings to match the FAQ.

The Mayor’s Office utilizes the most recent data to inform decisions about COVID-19 response and policies. The Los Angeles COVID-19 Neighborhood Map visualizes the cases and deaths across 139 neighborhoods in the city. It includes the same data used by the office to spot changes in infection trends in the city, and identify areas where testing resources should be deployed.Data Source:Data are provided on a weekly basis by the LA County Department of Public Health and prepared by the LA Mayor's Office Innovation Team. The data included in this map are on a one-week lag. That means the data shown here are reporting statistics gathered from one week ago. This map will be updated weekly on Mondays. Click on the maps to zoom in, get more details, and see the legends.

This dashboard provides access to Covid-19 data provided by the Alabama Department of Health, Johns Hopkins University, and Esri. Maps, graphs, and infographics are interactive and allow users to explore data relevant to public health in their community.

This story was originally published in February 2020. While the maps in the story are automatically updated with latest available statistics, the text may include information that is no longer current. For the latest guidelines on coronavirus prevention and mitigation, please visit the CDC's or WHO's information pages.Since December 2019, the novel coronavirus pandemic has touched nearly every country on the planet, and upended the lives of hundreds of millions of people, according to official and unofficial statistics compiled by researchers at Johns Hopkins University.The novel coronavirus belongs to the same family of viruses that cause severe acute respiratory syndrome (SARS) and Middle East respiratory syndrome (MERS). COVID-19, as the disease is known, produces mild symptoms in most people, but can also lead to severe respiratory illness.

Geographic layers Geographic layers on which the different data records are geo-referenced (e.g. mobility, COVID-19 cases). The different layers can be grouped into those that cover the whole territory of pain (e.g. municipalities) and those that are restricted to a specific region (Table1). Among those that cover the full territory of Spain, the record accounts for the first four levels of administrative division, that is, autonomous communities, provinces, municipalities and districts. Visit https://flowmaps.life.bsc.es/flowboard/data for more information about the data. Layers (geo-json format): cnig_ccaa : Comunidades Aut��nomas CNIG cnig_provincias : Provincias CNIG cnig_municipios : Municipios CNIG ine_sec : Secciones censales INE mitma_mov : ��reas de movilidad MITMA zbs_07 : Zonas B��sicas de Salud de Cy abs_09 : ��rees B��siques de Salut GenCat zon_bas_13 : Zonas b��sicas sanitarias de Madrid oe_16 : Osasun Eremuak (Zonas de Salud) Euskadi zbs_15 : Zonas B��sicas de Salud del Servicio Navarro de Salud This work was supported by the Generalitat de Catalunya through the project PDAD14/20/00001, by the H2020 Programme under Grant Agreement 825070 (INFORE) and by the INB Grant (PT17/0009/0001 - ISCIII-SGEFI/ERDF).

2019 Novel Coronavirus COVID-19 (2019-nCoV) Visual Dashboard and Map:
https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6

• Confirmed Cases by Country/Region/Sovereignty
• Confirmed Cases by Province/State/Dependency
• Deaths
• Recovered

Downloadable data:
https://github.com/CSSEGISandData/COVID-19

Additional Information about the Visual Dashboard:
https://systems.jhu.edu/research/public-health/ncov

This is the data repository for the 2019 Novel Coronavirus Visual Dashboard operated by the Johns Hopkins University Center for Systems Science and Engineering (JHU CSSE). This database was created in response to the Coronavirus public health emergency to track reported cases in real-time. The data include the location and number of confirmed COVID-19 cases, deaths and recoveries for all affected countries, aggregated at the appropriate province or state. It was developed to enable researchers, public health authorities and the general public to track the outbreak as it unfolds. Additional information is available in the blog post, Mapping 2019-nCoV (https://systems.jhu.edu/research/public-health/ncov/), and included data sources are listed here: https://github.com/CSSEGISandData/COVID-19

Dataset source: JHU CSSE

Update frequency: Daily

Terms of use: The contents of the dataset are provided to the public strictly for educational and academic purposes only. This data is from third party sources that may not be accurate, consistent and/or up-to-date. These datasets are provided “as is” without any warranties or representations of any kind. You are responsible for determining the suitability of this data for your purposes. See the JHU CSSE GitHub page for more details: https://github.com/CSSEGISandData/COVID-19

This deposit contains the taxonomy maps and data we used to translate data on COVID-19 government responses from 7 different datasets into taxonomy developed by the CoronaNet Research Project (CoronaNet; Cheng et al 2020). These taxonomy maps form the basis of our efforts to harmonize this data into the CoronaNet database. The following taxonomy maps are deposited in the 'Taxonomy' folder:ACAPS COVID-19 Government Measures - CoronaNet Taxonomy Map Canadian Data Set of COVID-19 Interventions from the Canadian Institute for Health Information (CIHI) - CoronaNet Taxonomy Map COVID Analysis and Maping of Policies (COVID AMP) - CoronaNet Taxonomy Map Johns Hopkins Health Intervention Tracking for COVID-19 (HIT-COVID) - CoronaNet Taxonomy Map Oxford Covid-19 Government Response Tracker (OxCGRT) - CoronaNet Taxonomy Map World Health Organisation Public Health and Safety Measures (WHO PHSM) - CoronaNet Taxonomy MapMeanwhile the 'Data' folder contains the raw and mapped data for each external dataset (i.e. ACAPS, CIHI, COVID AMP, HIT-COVID, OxCGRT and WHO PHSM) as well as the combined external data for Steps 1 and 3 of the data harmonization process described in Cheng et al (2023) 'Harmonizing Government Responses to the COVID-19 Pandemic.'

The official information on the spread of the epidemic in France was initially rather fragmented. Various initiatives have attempted to structure it in the form of free data. Despite this work, however, the data were often difficult to exploit in the raw state within cartographic tools. The purpose of this repository is to consolidate the information and make it available in open and easily reusable formats to produce maps. The preferred pivot format is GeoJson. The data are proposed according to several granularities: regions and departments. The data at the department’s grid was initially fragmented, however under the impetus of free initiatives such as OpenCovid19, more precise data on the epidemic was made available by Santé publique France. For more details or the latest version of the data, see https://github.com/kalisio/covid-19. For more information about KALISIO visit our website.

Visual map at kumu.io/access2perspectives/covid19-resources

Data set doi: 10.5281/zenodo.3732377 // available in different formats (pdf, xls, ods, csv,)

Correspondence: (JH) info@access2perspectives.com

Objectives

Provide citizens with crucial and reliable information

Encourage and facilitate South South collaboration

Bridging language barriers

Provide local governments and cities with lessons learned about COVID-19 crisis response

Facilitate global cooperation and immediate response on all societal levels

Enable LMICs to collaborate and innovate across distances and leverage locally available and context-relevant resources

Methodology

The data feeding the map at kumu.io was compiled from online resources and information shared in various community communication channels.

Kumu.io is a visualization platform for mapping complex systems and to provide a deeper understanding of their intrinsic relationships. It provides blended systems thinking, stakeholder mapping, and social network analysis.

Explore the map // https://kumu.io/access2perspectives/covid19-resources#global

Click on individual nodes and view the information by country

info hotlines

governmental informational websites, Twitter feeds & Facebook pages

fact checking online resources

language indicator

DIY resources

clinical staff capacity building

etc.

With the navigation buttons to the right, you can zoom in and out, select and focus on specific elements.

If you have comments, questions or suggestions for improvements on this map email us at info@access2perspectives.com

Contribute

Please add data to the spreadsheet at https://tinyurl.com/COVID19-global-response

you can add additional information on country, city or neighbourhood level (see e.g. the Cape Town entry)

Related documents

Google Doc: tinyurl.com/COVID19-Africa-Response

This mapping tool enables you to see how COVID-19 deaths in your area may relate to factors in the local population, which research has shown are associated with COVID-19 mortality. It maps COVID-19 deaths rates for small areas of London (known as MSOAs) and enables you to compare these to a number of other factors including the Index of Multiple Deprivation, the age and ethnicity of the local population, extent of pre-existing health conditions in the local population, and occupational data. Research has shown that the mortality risk from COVID-19 is higher for people of older age groups, for men, for people with pre-existing health conditions, and for people from BAME backgrounds. London boroughs had some of the highest mortality rates from COVID-19 based on data to April 17th 2020, based on data from the Office for National Statistics (ONS). Analysis from the ONS has also shown how mortality is also related to socio-economic issues such as occupations classified ‘at risk’ and area deprivation. There is much about COVID-19-related mortality that is still not fully understood, including the intersection between the different factors e.g. relationship between BAME groups and occupation. On their own, none of these individual factors correlate strongly with deaths for these small areas. This is most likely because the most relevant factors will vary from area to area. In some cases it may relate to the age of the population, in others it may relate to the prevalence of underlying health conditions, area deprivation or the proportion of the population working in ‘at risk occupations’, and in some cases a combination of these or none of them. Further descriptive analysis of the factors in this tool can be found here: https://data.london.gov.uk/dataset/covid-19--socio-economic-risk-factors-briefing