This dataset contains counts of deaths for California counties based on information entered on death certificates. Final counts are derived from static data and include out-of-state deaths to California residents, whereas provisional counts are derived from incomplete and dynamic data. Provisional counts are based on the records available when the data was retrieved and may not represent all deaths that occurred during the time period. Deaths involving injuries from external or environmental forces, such as accidents, homicide and suicide, often require additional investigation that tends to delay certification of the cause and manner of death. This can result in significant under-reporting of these deaths in provisional data.

The final data tables include both deaths that occurred in each California county regardless of the place of residence (by occurrence) and deaths to residents of each California county (by residence), whereas the provisional data table only includes deaths that occurred in each county regardless of the place of residence (by occurrence). The data are reported as totals, as well as stratified by age, gender, race-ethnicity, and death place type. Deaths due to all causes (ALL) and selected underlying cause of death categories are provided. See temporal coverage for more information on which combinations are available for which years.

The cause of death categories are based solely on the underlying cause of death as coded by the International Classification of Diseases. The underlying cause of death is defined by the World Health Organization (WHO) as "the disease or injury which initiated the train of events leading directly to death, or the circumstances of the accident or violence which produced the fatal injury." It is a single value assigned to each death based on the details as entered on the death certificate. When more than one cause is listed, the order in which they are listed can affect which cause is coded as the underlying cause. This means that similar events could be coded with different underlying causes of death depending on variations in how they were entered. Consequently, while underlying cause of death provides a convenient comparison between cause of death categories, it may not capture the full impact of each cause of death as it does not always take into account all conditions contributing to the death.

This dataset contains counts of deaths for California as a whole based on information entered on death certificates. Final counts are derived from static data and include out-of-state deaths to California residents, whereas provisional counts are derived from incomplete and dynamic data. Provisional counts are based on the records available when the data was retrieved and may not represent all deaths that occurred during the time period. Deaths involving injuries from external or environmental forces, such as accidents, homicide and suicide, often require additional investigation that tends to delay certification of the cause and manner of death. This can result in significant under-reporting of these deaths in provisional data.

The final data tables include both deaths that occurred in California regardless of the place of residence (by occurrence) and deaths to California residents (by residence), whereas the provisional data table only includes deaths that occurred in California regardless of the place of residence (by occurrence). The data are reported as totals, as well as stratified by age, gender, race-ethnicity, and death place type. Deaths due to all causes (ALL) and selected underlying cause of death categories are provided. See temporal coverage for more information on which combinations are available for which years.

The cause of death categories are based solely on the underlying cause of death as coded by the International Classification of Diseases. The underlying cause of death is defined by the World Health Organization (WHO) as "the disease or injury which initiated the train of events leading directly to death, or the circumstances of the accident or violence which produced the fatal injury." It is a single value assigned to each death based on the details as entered on the death certificate. When more than one cause is listed, the order in which they are listed can affect which cause is coded as the underlying cause. This means that similar events could be coded with different underlying causes of death depending on variations in how they were entered. Consequently, while underlying cause of death provides a convenient comparison between cause of death categories, it may not capture the full impact of each cause of death as it does not always take into account all conditions contributing to the death.

Provisional counts of the number of deaths registered in England and Wales, by age, sex, region and Index of Multiple Deprivation (IMD), in the latest weeks for which data are available.

Number and percentage of deaths, by month and place of residence, 1991 to most recent year.

Effect of suicide rates on life expectancy dataset

Abstract
In 2015, approximately 55 million people died worldwide, of which 8 million committed suicide. In the USA, one of the main causes of death is the aforementioned suicide, therefore, this experiment is dealing with the question of how much suicide rates affects the statistics of average life expectancy.
The experiment takes two datasets, one with the number of suicides and life expectancy in the second one and combine data into one dataset. Subsequently, I try to find any patterns and correlations among the variables and perform statistical test using simple regression to confirm my assumptions.

Data

The experiment uses two datasets - WHO Suicide Statistics[1] and WHO Life Expectancy[2], which were firstly appropriately preprocessed. The final merged dataset to the experiment has 13 variables, where country and year are used as index: Country, Year, Suicides number, Life expectancy, Adult Mortality, which is probability of dying between 15 and 60 years per 1000 population, Infant deaths, which is number of Infant Deaths per 1000 population, Alcohol, which is alcohol, recorded per capita (15+) consumption, Under-five deaths, which is number of under-five deaths per 1000 population, HIV/AIDS, which is deaths per 1 000 live births HIV/AIDS, GDP, which is Gross Domestic Product per capita, Population, Income composition of resources, which is Human Development Index in terms of income composition of resources, and Schooling, which is number of years of schooling.

LICENSE

THE EXPERIMENT USES TWO DATASET - WHO SUICIDE STATISTICS AND WHO LIFE EXPECTANCY, WHICH WERE COLLEECTED FROM WHO AND UNITED NATIONS WEBSITE. THEREFORE, ALL DATASETS ARE UNDER THE LICENSE ATTRIBUTION-NONCOMMERCIAL-SHAREALIKE 3.0 IGO (https://creativecommons.org/licenses/by-nc-sa/3.0/igo/).

[1] https://www.kaggle.com/szamil/who-suicide-statistics

[2] https://www.kaggle.com/kumarajarshi/life-expectancy-who

Rank, number of deaths, percentage of deaths, and age-specific mortality rates for the leading causes of death, by age group and sex, 2000 to most recent year.

Do you know?

Do you know how much time you spend on an app? Do you know the total use time of a day or average use time of an app?

What it consists of?

This data set consists of - how many times a person unlocks his phone. - how much time he spends on every app on every day. - how much time he spends on his phone.

It lists the usage time of apps for each day.

What we can do?

Use the test data to find the Total Minutes that we can use the given app in a day. we can get a clear stats of apps usage. This data set will show you about the persons sleeping behavior as well as what app he spends most of his time. with this we can improve the productivity of the person.

The dataset was collected from the app usage app.

Updates

• Notice of data discontinuation: Since the start of the pandemic, AP has reported case and death counts from data provided by Johns Hopkins University. Johns Hopkins University has announced that they will stop their daily data collection efforts after March 10. As Johns Hopkins stops providing data, the AP will also stop collecting daily numbers for COVID cases and deaths. The HHS and CDC now collect and visualize key metrics for the pandemic. AP advises using those resources when reporting on the pandemic going forward.

  • CDC Weekly case and death counts (national and state level)
  • CDC County level cases and deaths
  • HHS New hospital admissions
  • CDC NowCast COVID variant proportions (national and regional level)

• April 9, 2020

  • The population estimate data for New York County, NY has been updated to include all five New York City counties (Kings County, Queens County, Bronx County, Richmond County and New York County). This has been done to match the Johns Hopkins COVID-19 data, which aggregates counts for the five New York City counties to New York County.

• April 20, 2020

  • Johns Hopkins death totals in the US now include confirmed and probable deaths in accordance with CDC guidelines as of April 14. One significant result of this change was an increase of more than 3,700 deaths in the New York City count. This change will likely result in increases for death counts elsewhere as well. The AP does not alter the Johns Hopkins source data, so probable deaths are included in this dataset as well.

• April 29, 2020

  • The AP is now providing timeseries data for counts of COVID-19 cases and deaths. The raw counts are provided here unaltered, along with a population column with Census ACS-5 estimates and calculated daily case and death rates per 100,000 people. Please read the updated caveats section for more information.

• September 1st, 2020

  • Johns Hopkins is now providing counts for the five New York City counties individually.

• February 12, 2021

  • The Ohio Department of Health recently announced that as many as 4,000 COVID-19 deaths may have been underreported through the state’s reporting system, and that the "daily reported death counts will be high for a two to three-day period."
  • Because deaths data will be anomalous for consecutive days, we have chosen to freeze Ohio's rolling average for daily deaths at the last valid measure until Johns Hopkins is able to back-distribute the data. The raw daily death counts, as reported by Johns Hopkins and including the backlogged death data, will still be present in the new_deaths column.

• February 16, 2021

  - Johns Hopkins has reconciled Ohio's historical deaths data with the state.

  Overview

The AP is using data collected by the Johns Hopkins University Center for Systems Science and Engineering as our source for outbreak caseloads and death counts for the United States and globally.

The Hopkins data is available at the county level in the United States. The AP has paired this data with population figures and county rural/urban designations, and has calculated caseload and death rates per 100,000 people. Be aware that caseloads may reflect the availability of tests -- and the ability to turn around test results quickly -- rather than actual disease spread or true infection rates.

This data is from the Hopkins dashboard that is updated regularly throughout the day. Like all organizations dealing with data, Hopkins is constantly refining and cleaning up their feed, so there may be brief moments where data does not appear correctly. At this link, you’ll find the Hopkins daily data reports, and a clean version of their feed.

The AP is updating this dataset hourly at 45 minutes past the hour.

To learn more about AP's data journalism capabilities for publishers, corporations and financial institutions, go here or email kromano@ap.org.

Queries

Use AP's queries to filter the data or to join to other datasets we've made available to help cover the coronavirus pandemic

• Filter cases by state here

• Rank states by their status as current hotspots. Calculates the 7-day rolling average of new cases per capita in each state: https://data.world/associatedpress/johns-hopkins-coronavirus-case-tracker/workspace/query?queryid=481e82a4-1b2f-41c2-9ea1-d91aa4b3b1ac

• Find recent hotspots within your state by running a query to calculate the 7-day rolling average of new cases by capita in each county: https://data.world/associatedpress/johns-hopkins-coronavirus-case-tracker/workspace/query?queryid=b566f1db-3231-40fe-8099-311909b7b687&showTemplatePreview=true

• Join county-level case data to an earlier dataset released by AP on local hospital capacity here. To find out more about the hospital capacity dataset, see the full details.

• Pull the 100 counties with the highest per-capita confirmed cases here

• Rank all the counties by the highest per-capita rate of new cases in the past 7 days here. Be aware that because this ranks per-capita caseloads, very small counties may rise to the very top, so take into account raw caseload figures as well.

Interactive

The AP has designed an interactive map to track COVID-19 cases reported by Johns Hopkins.

@(https://datawrapper.dwcdn.net/nRyaf/15/)

Interactive Embed Code

<iframe title="USA counties (2018) choropleth map Mapping COVID-19 cases by county" aria-describedby="" id="datawrapper-chart-nRyaf" src="https://datawrapper.dwcdn.net/nRyaf/10/" scrolling="no" frameborder="0" style="width: 0; min-width: 100% !important;" height="400"></iframe><script type="text/javascript">(function() {'use strict';window.addEventListener('message', function(event) {if (typeof event.data['datawrapper-height'] !== 'undefined') {for (var chartId in event.data['datawrapper-height']) {var iframe = document.getElementById('datawrapper-chart-' + chartId) || document.querySelector("iframe[src*='" + chartId + "']");if (!iframe) {continue;}iframe.style.height = event.data['datawrapper-height'][chartId] + 'px';}}});})();</script>

Caveats

• This data represents the number of cases and deaths reported by each state and has been collected by Johns Hopkins from a number of sources cited on their website.
• In some cases, deaths or cases of people who've crossed state lines -- either to receive treatment or because they became sick and couldn't return home while traveling -- are reported in a state they aren't currently in, because of state reporting rules.
• In some states, there are a number of cases not assigned to a specific county -- for those cases, the county name is "unassigned to a single county"
• This data should be credited to Johns Hopkins University's COVID-19 tracking project. The AP is simply making it available here for ease of use for reporters and members.
• Caseloads may reflect the availability of tests -- and the ability to turn around test results quickly -- rather than actual disease spread or true infection rates.
• Population estimates at the county level are drawn from 2014-18 5-year estimates from the American Community Survey.
• The Urban/Rural classification scheme is from the Center for Disease Control and Preventions's National Center for Health Statistics. It puts each county into one of six categories -- from Large Central Metro to Non-Core -- according to population and other characteristics. More details about the classifications can be found here.

Johns Hopkins timeseries data - Johns Hopkins pulls data regularly to update their dashboard. Once a day, around 8pm EDT, Johns Hopkins adds the counts for all areas they cover to the timeseries file. These counts are snapshots of the latest cumulative counts provided by the source on that day. This can lead to inconsistencies if a source updates their historical data for accuracy, either increasing or decreasing the latest cumulative count. - Johns Hopkins periodically edits their historical timeseries data for accuracy. They provide a file documenting all errors in their timeseries files that they have identified and fixed here

Attribution

This data should be credited to Johns Hopkins University COVID-19 tracking project

This dataset provides values for CORONAVIRUS DEATHS reported in several countries. The data includes current values, previous releases, historical highs and record lows, release frequency, reported unit and currency.

One in every 100 children dies before completing one year of life. Around 68 percent of infant mortality is attributed to deaths of children before completing 1 month. 15,000 children die every day – Child mortality is an everyday tragedy of enormous scale that rarely makes the headlines Child mortality rates have declined in all world regions, but the world is not on track to reach the Sustainable Development Goal for child mortality Before the Modern Revolution child mortality was very high in all societies that we have knowledge of – a quarter of all children died in the first year of life, almost half died before reaching the end of puberty Over the last two centuries all countries in the world have made very rapid progress against child mortality. From 1800 to 1950 global mortality has halved from around 43% to 22.5%. Since 1950 the mortality rate has declined five-fold to 4.5% in 2015. All countries in the world have benefitted from this progress In the past it was very common for parents to see children die, because both, child mortality rates and fertility rates were very high. In Europe in the mid 18th century parents lost on average between 3 and 4 of their children Based on this overview we are asking where the world is today – where are children dying and what are they dying from?

5.4 million children died in 2017 – Where did these children die? Pneumonia is the most common cause of death, preterm births and neonatal disorders is second, and diarrheal diseases are third – What are children today dying from? This is the basis for answering the question what can we do to make further progress against child mortality? We will extend this entry over the course of 2020.

@article{owidchildmortality, author = {Max Roser, Hannah Ritchie and Bernadeta Dadonaite}, title = {Child and Infant Mortality}, journal = {Our World in Data}, year = {2013}, note = {https://ourworldindata.org/child-mortality} }

Demographic Trends and Health Outcomes in the U.S

Inequalities,Risk Factors and Access to Care

By Data Society [source]

About this dataset

This dataset contains key demographic, health status indicators and leading cause of death data to help us understand the current trends and health outcomes in communities across the United States. By looking at this data, it can be seen how different states, counties and populations have changed over time. With this data we can analyze levels of national health services use such as vaccination rates or mammography rates; review leading causes of death to create public policy initiatives; as well as identify risk factors for specific conditions that may be associated with certain populations or regions. The information from these files includes State FIPS Code, County FIPS Code, CHSI County Name, CHSI State Name, CHSI State Abbreviation, Influenza B (FluB) report count & expected cases rate per 100K population , Hepatitis A (HepA) Report Count & expected cases rate per 100K population , Hepatitis B (HepB) Report Count & expected cases rate per 100K population , Measles (Meas) Report Count & expected cases rate per 100K population , Pertussis(Pert) Report Count & expected case rate per 100K population , CRS report count & expected case rate per 100K population , Syphilis report count and expected case rate per 100k popuation. We also look at measures related to preventive care services such as Pap smear screen among women aged 18-64 years old check lower/upper confidence intervals seperately ; Mammogram checks among women aged 40-64 years old specified lower/upper conifence intervals separetly ; Colonosopy/ Proctoscpushy among men aged 50+ measured in lower/upper limits ; Pneumonia Vaccination amongst 65+ with loewr/upper confidence level detail Additionally we have some interesting trend indicating variables like measures of birth adn death which includes general fertility ratye ; Teen Birth Rate by Mother's age group etc Summary Measures covers mortality trend following life expectancy by sex&age categories Vressionable populations access info gives us insight into disablilty ratio + access to envtiromental issues due to poor quality housing facilities Finally Risk Factors cover speicfic hoslitic condtiions suchs asthma diagnosis prevelance cancer diabetes alcholic abuse smoking trends All these information give a good understanding on Healthy People 2020 target setings demograpihcally speaking hence will aid is generating more evience backed policies

More Datasets

For more datasets, click here.

Featured Notebooks

• 🚨 Your notebook can be here! 🚨!

How to use the dataset

What the Dataset Contains

This dataset contains valuable information about public health relevant to each county in the United States, broken down into 9 indicator domains: Demographics, Leading Causes of Death, Summary Measures of Health, Measures of Birth and Death Rates, Relative Health Importance, Vulnerable Populations and Environmental Health Conditions, Preventive Services Use Data from BRFSS Survey System Data , Risk Factors and Access to Care/Health Insurance Coverage & State Developed Types of Measurements such as CRS with Multiple Categories Identified for Each Type . The data includes indicators such as percentages or rates for influenza (FLU), hepatitis (HepA/B), measles(MEAS) pertussis(PERT), syphilis(Syphilis) , cervical cancer (CI_Min_Pap_Smear - CI_Max\Pap \Smear), breast cancer (CI\Min Mammogram - CI \Max \Mammogram ) proctoscopy (CI Min Proctoscopy - CI Max Proctoscopy ), pneumococcal vaccinations (Ci min Pneumo Vax - Ci max Pneumo Vax )and flu vaccinations (Ci min Flu Vac - Ci Max Flu Vac). Additionally , it provides information on leading causes of death at both county levels & national level including age-adjusted mortality rates due to suicide among teens aged between 15-19 yrs per 100000 population etc.. Furthermore , summary measures such as age adjusted percentage who consider their physical health fair or poor are provided; vulnerable populations related indicators like relative importance score for disabled adults ; preventive service use related ones ranging from self reported vaccination coverage among men40-64 yrs old against hepatitis B virus etc...

Getting Started With The Dataset

To get started with exploring this dataset first your need to understand what each column in the table represents: State FIPS Code identifies a unique identifier used by various US government agencies which denote states . County FIPS code denotes counties wi...

Abstract

In 1985 the population and health observatory was established at Mlomp, in the region of Ziguinchor, in southern Senegal (see map). The objective was to complement the two rural population observatories then existing in the country, Bandafassi, in the south-east, and Niakhar, in the centre-west, with a third observatory in a region - the south-west of the country (Casamance) - whose history, ethnic composition and economic situation were quite different from those of the regions where the first two observatories were located. It was expected that measuring the demographic levels and trends on those three sites would provide better coverage of the demographic and epidemiological diversity of the country.

Following a population census in 1984-1985, demographic events and causes of death have been monitored yearly. During the initial census, all women were interviewed concerning the birth and survival of their children. Since 1985, yearly censuses, usually conducted in January-February, have been recording demographic data, including all births, deaths, and migrations. The completeness and accuracy of dates of birth and death are cross-checked against those of registers of the local maternity ward (_95% of all births) and dispensary (all deaths are recorded, including those occurring outside the area), respectively. The study area comprises 11 villages with approximately 8000 inhabitants, mostly Diola. Mlomp is located in the Department of Oussouye, Region of Ziguinchor (Casamance), 500 km south of Dakar.

On 1 January 2000 the Mlomp area included a population of 7,591 residents living in 11 villages. The population density was 108 people per square kilometre. The population belongs to the Diola ethnic group, and the religion is predominantly animist, with a large minority of Christians and a few Muslims. Though low, the educational level - in 2000, 55% of women aged 15-49 had been to school (for at least one year) - is definitely higher than at Bandafassi. The population also benefits from much better health infrastructure and programmes. Since 1961, the area under study has been equipped with a private health centre run by French Catholic nurses and, since 1968, a village maternity centre where most women give birth. The vast majority of the children are totally immunized and involved in a growth-monitoring programme (Pison et al.,1993; Pison et al., 2001).

Geographic coverage

The Mlomp DSS site, about 500 km from the capital, Dakar, in Senegal, lies between latitudes 12°36' and 12°32'N and longitudes 16°33' and 16°37'E, at an altitude ranging from 0 to 20 m above sea level. It is in the region of Ziguinchor, Département of Oussouye (Casamance), in southwest Senegal. It is locates 50 km west of the city of Ziguinchor and 25 kms north of the border with Guinea Bissau. It covers about half the Arrondissement of Loudia-Ouolof. The Mlomp DSS site is about 11 km × 7 km and has an area of 70 km2. Villages are households grouped in a circle with a 3-km diameter and surrounded by lands that are flooded during the rainy season and cultivated for rice. There is still no electricity.

Analysis unit

Individual

Universe

At the census, a person was considered a member of the compound if the head of the compound declared it to be so. This definition was broad and resulted in a de jure population under study. Thereafter, a criterion was used to decide whether and when a person was to be excluded or included in the population.

A person was considered to exit from the study population through either death or emigration. Part of the population of Mlomp engages in seasonal migration, with seasonal migrants sometimes remaining 1 or 2 years outside the area before returning. A person who is absent for two successive yearly rounds, without returning in between, is regarded as having emigrated and no longer resident in the study population at the date of the second round. This definition results in the inclusion of some vital events that occur outside the study area. Some births, for example, occur to women classified in the study population but physically absent at the time of delivery, and these births are registered and included in the calculation of rates, although information on them is less accurate. Special exit criteria apply to babies born outside the study area: they are considered emigrants on the same date as their mother.

A new person enters the study population either through birth to a woman of the study population or through immigration. Information on immigrants is collected when the list of compounds of a village is checked ("Are there new compounds or new families who settled since the last visit?") or when the list of members of a compound is checked ("Are there new persons in the compound since the last visit?"). Some immigrants are villagers who left the area several years before and were excluded from the study population. Information is collected to determine in which compound they were previously registered, to match the new and old information.

Information is routinely collected on movements from one compound to another within the study area. Some categories of the population, such as older widows or orphans, frequently move for short periods of time and live in between several compounds, and they may be considered members of these compounds or of none. As a consequence, their movements are not always declared.

Kind of data

Event history data

Frequency of data collection

One round of data collection took place annually, except in 1987 and 2008.

Sampling procedure

No samplaing is done

Sampling deviation

None

Mode of data collection

Proxy Respondent [proxy]

Research instrument

List of questionnaires: - Household book (used to register informations needed to define outmigrations) - Delivery questionnaire (used to register information of dispensaire ol mlomp) - New household questionnaire - New member questionnaire - Marriage and divorce questionnaire - Birth and marital histories questionnaire (for a new member) - Death questionnaire (used to register the date of death)

Cleaning operations

On data entry data consistency and plausibility were checked by 455 data validation rules at database level. If data validaton failure was due to a data collection error, the questionnaire was referred back to the field for revisit and correction. If the error was due to data inconsistencies that could not be directly traced to a data collection error, the record was referred to the data quality team under the supervision of the senior database scientist. This could request further field level investigation by a team of trackers or could correct the inconsistency directly at database level.

No imputations were done on the resulting micro data set, except for:

a. If an out-migration (OMG) event is followed by a homestead entry event (ENT) and the gap between OMG event and ENT event is greater than 180 days, the ENT event was changed to an in-migration event (IMG). b. If an out-migration (OMG) event is followed by a homestead entry event (ENT) and the gap between OMG event and ENT event is less than 180 days, the OMG event was changed to an homestead exit event (EXT) and the ENT event date changed to the day following the original OMG event. c. If a homestead exit event (EXT) is followed by an in-migration event (IMG) and the gap between the EXT event and the IMG event is greater than 180 days, the EXT event was changed to an out-migration event (OMG). d. If a homestead exit event (EXT) is followed by an in-migration event (IMG) and the gap between the EXT event and the IMG event is less than 180 days, the IMG event was changed to an homestead entry event (ENT) with a date equal to the day following the EXT event. e. If the last recorded event for an individual is homestead exit (EXT) and this event is more than 180 days prior to the end of the surveillance period, then the EXT event is changed to an out-migration event (OMG)

In the case of the village that was added (enumerated) in 2006, some individuals may have outmigrated from the original surveillance area and setlled in the the new village prior to the first enumeration. Where the records of such individuals have been linked, and indivdiual can legitmately have and outmigration event (OMG) forllowed by and enumeration event (ENU). In a few cases a homestead exit event (EXT) was followed by an enumeration event in these cases. In these instances the EXT events were changed to an out-migration event (OMG).

Response rate

On an average the response rate is about 99% over the years for each round.

Sampling error estimates

Not applicable

Data appraisal

CenterId Metric Table QMetric Illegal Legal Total Metric Rundate
SN012 MicroDataCleaned Starts 18756 2017-05-19 00:00
SN012 MicroDataCleaned Transitions 0 45136 45136 0 2017-05-19 00:00
SN012 MicroDataCleaned Ends 18756 2017-05-19 00:00
SN012 MicroDataCleaned SexValues 38 45098 45136 0 2017-05-19 00:00
SN012 MicroDataCleaned DoBValues 204 44932 45136 0 2017-05-19 00:00

Data for CDC’s COVID Data Tracker site on Rates of COVID-19 Cases and Deaths by Vaccination Status. Click 'More' for important dataset description and footnotes

Dataset and data visualization details: These data were posted on October 21, 2022, archived on November 18, 2022, and revised on February 22, 2023. These data reflect cases among persons with a positive specimen collection date through September 24, 2022, and deaths among persons with a positive specimen collection date through September 3, 2022.

Vaccination status: A person vaccinated with a primary series had SARS-CoV-2 RNA or antigen detected on a respiratory specimen collected ≥14 days after verifiably completing the primary series of an FDA-authorized or approved COVID-19 vaccine. An unvaccinated person had SARS-CoV-2 RNA or antigen detected on a respiratory specimen and has not been verified to have received COVID-19 vaccine. Excluded were partially vaccinated people who received at least one FDA-authorized vaccine dose but did not complete a primary series ≥14 days before collection of a specimen where SARS-CoV-2 RNA or antigen was detected. Additional or booster dose: A person vaccinated with a primary series and an additional or booster dose had SARS-CoV-2 RNA or antigen detected on a respiratory specimen collected ≥14 days after receipt of an additional or booster dose of any COVID-19 vaccine on or after August 13, 2021. For people ages 18 years and older, data are graphed starting the week including September 24, 2021, when a COVID-19 booster dose was first recommended by CDC for adults 65+ years old and people in certain populations and high risk occupational and institutional settings. For people ages 12-17 years, data are graphed starting the week of December 26, 2021, 2 weeks after the first recommendation for a booster dose for adolescents ages 16-17 years. For people ages 5-11 years, data are included starting the week of June 5, 2022, 2 weeks after the first recommendation for a booster dose for children aged 5-11 years. For people ages 50 years and older, data on second booster doses are graphed starting the week including March 29, 2022, when the recommendation was made for second boosters. Vertical lines represent dates when changes occurred in U.S. policy for COVID-19 vaccination (details provided above). Reporting is by primary series vaccine type rather than additional or booster dose vaccine type. The booster dose vaccine type may be different than the primary series vaccine type. ** Because data on the immune status of cases and associated deaths are unavailable, an additional dose in an immunocompromised person cannot be distinguished from a booster dose. This is a relevant consideration because vaccines can be less effective in this group. Deaths: A COVID-19–associated death occurred in a person with a documented COVID-19 diagnosis who died; health department staff reviewed to make a determination using vital records, public health investigation, or other data sources. Rates of COVID-19 deaths by vaccination status are reported based on when the patient was tested for COVID-19, not the date they died. Deaths usually occur up to 30 days after COVID-19 diagnosis. Participating jurisdictions: Currently, these 31 health departments that regularly link their case surveillance to immunization information system data are included in these incidence rate estimates: Alabama, Arizona, Arkansas, California, Colorado, Connecticut, District of Columbia, Florida, Georgia, Idaho, Indiana, Kansas, Kentucky, Louisiana, Massachusetts, Michigan, Minnesota, Nebraska, New Jersey, New Mexico, New York, New York City (New York), North Carolina, Philadelphia (Pennsylvania), Rhode Island, South Dakota, Tennessee, Texas, Utah, Washington, and West Virginia; 30 jurisdictions also report deaths among vaccinated and unvaccinated people. These jurisdictions represent 72% of the total U.S. population and all ten of the Health and Human Services Regions. Data on cases among people who received additional or booster doses were reported from 31 jurisdictions; 30 jurisdictions also reported data on deaths among people who received one or more additional or booster dose; 28 jurisdictions reported cases among people who received two or more additional or booster doses; and 26 jurisdictions reported deaths among people who received two or more additional or booster doses. This list will be updated as more jurisdictions participate. Incidence rate estimates: Weekly age-specific incidence rates by vaccination status were calculated as the number of cases or deaths divided by the number of people vaccinated with a primary series, overall or with/without a booster dose (cumulative) or unvaccinated (obtained by subtracting the cumulative number of people vaccinated with a primary series and partially vaccinated people from the 2019 U.S. intercensal population estimates) and multiplied by 100,000. Overall incidence rates were age-standardized using the 2000 U.S. Census standard population. To estimate population counts for ages 6 months through 1 year, half of the single-year population counts for ages 0 through 1 year were used. All rates are plotted by positive specimen collection date to reflect when incident infections occurred. For the primary series analysis, age-standardized rates include ages 12 years and older from April 4, 2021 through December 4, 2021, ages 5 years and older from December 5, 2021 through July 30, 2022 and ages 6 months and older from July 31, 2022 onwards. For the booster dose analysis, age-standardized rates include ages 18 years and older from September 19, 2021 through December 25, 2021, ages 12 years and older from December 26, 2021, and ages 5 years and older from June 5, 2022 onwards. Small numbers could contribute to less precision when calculating death rates among some groups. Continuity correction: A continuity correction has been applied to the denominators by capping the percent population coverage at 95%. To do this, we assumed that at least 5% of each age group would always be unvaccinated in each jurisdiction. Adding this correction ensures that there is always a reasonable denominator for the unvaccinated population that would prevent incidence and death rates from growing unrealistically large due to potential overestimates of vaccination coverage. Incidence rate ratios (IRRs): IRRs for the past one month were calculated by dividing the average weekly incidence rates among unvaccinated people by that among people vaccinated with a primary series either overall or with a booster dose. Publications: Scobie HM, Johnson AG, Suthar AB, et al. Monitoring Incidence of COVID-19 Cases, Hospitalizations, and Deaths, by Vaccination Status — 13 U.S. Jurisdictions, April 4–July 17, 2021. MMWR Morb Mortal Wkly Rep 2021;70:1284–1290. Johnson AG, Amin AB, Ali AR, et al. COVID-19 Incidence and Death Rates Among Unvaccinated and Fully Vaccinated Adults with and Without Booster Doses During Periods of Delta and Omicron Variant Emergence — 25 U.S. Jurisdictions, April 4–December 25, 2021. MMWR Morb Mortal Wkly Rep 2022;71:132–138

Interaction matrices and metadata used in "Social networks predict the life and death of honey bees"

Preprint: Social networks predict the life and death of honey bees

See the README file in bb_network_decomposition for example code.

The following files are included:

interaction_networks_20160729to20160827.h5

The social interaction networks as a dense tensor and metadata.

Keys:

interactions: Tensor of shape (29, 2010, 2010, 9) (days x individuals x individuals x interaction_types). I_{d,i,j,t} = log(1 + x), where x is the number of interactions of type t between individuals i and j at recording day d. See the methods section of paper of the interaction types.

labels: Names of the 9 interaction types in the order they are stored in the interactions tensor.

bee_ids: List of length 2010, mapping from sequential index used in the interaction tensor to the original BeesBook tag ID of the individual

alive_bees_bayesian.csv

This file contains the results of the bayesian lifetime model with one row for each bee.

Columns:

bee_id: Numerical unique identifier for each individual.

days_alive: Number of bees the bees was determined to be alive. If the individual was still alive at the end of the recording, the number of days from the day she hatched until the end of the recording.

death_observed: Boolean indicator whether the death occurred during the recording period.

annotated_tagged_date: Hatch date of the individual, i.e. the date she was tagged.

inferred_death_date: The death date as determined by the model.

bee_daily_data.csv

This file contains one row per bee per day that she was alive for the focal period.

Columns:

bee_id: Numerical unique identifier for each individual.

date: Date in year-month-day format.

age: Age in days. Can be NaN if the bee has no associated death_date.

network_age, network_age_1, network_age_2: The first three dimensions of network age.

dance_floor, honey_storage, near_exit, brood_area_total: Normalized (sum to 1). Can be NaN if a bee had no high confidence detections (>0.9) for a given day. Can be 0 if a bee was only seen outside of the annotated areas.

location_descriptor_count: The number of minutes the bee was seen in one of the location labels during that day. I.e., dance_floor * location_descriptor_count calculates the number of minutes, the bee was seen on the dance floor on the given day.

death_date: Date the bee was last seen in the colony in year-month-day format. Can be NaN for individuals that did not die until the end of the recording period.

circadian_rhythm: R² value of a sine with a period of one day fitted to the velocity data of the individual over three days. Can be NaN if the fit did not converge due to a lack of data points.

velocity_peak_time: Phase of the circadian sine fit in hours as an offset to 12:00 UTC. Can be NaN if circadian_rhythm is NaN.

velocity_day, velocity_night: Mean velocity of the individual between 09:00-18:00 UTC and 21:00-06:00 UTC, respectively. Can be NaN if no velocity data was available for that interval.

days_left: Difference in days between date and death_date. Can be NaN if death_date is NaN.

location_data.csv

This file contains subsampled position information for all bees during the focal period. The data contains one row for every individual for every minute of the recording if that individual was seen at least once during that minute with a tag confidence of at least 0.9. The first matching detection for each individual is used.

Columns:

In addition to the bee_id and date columns as in the bee_daily_data.csv, the file contains these additional columns:

cam_id, cams: The cam_id is a numerical identifier from {0, 1, 2, 3}. Each side of the hive is filmed by two cameras where {0, 1} and {2, 3} record the same side respectively. The cams column contains values either “(0, 1)” or “(2, 3)” and indicates to which sides of the hive this detection belongs.

x_pos_hive, y_pos_hive: The spatial positions in millimeters on the hive. The two cameras from one side share a common coordinate system.

location: The label that was assigned to the comb at (x_pos_hive, y_pos_hive) on the given date. The label “other” indicates detections that were outside of any annotated region. The label “not_comb” indicates the wooden frame or empty space around the comb.

timestamp, date: The timestamp indicates the beginning of each one-minute sampling interval and is given in UTC, as indicated (example: “2016-08-13 00:00:00+00:00”). The date part of the timestamp is repeated in the “date” column. Both are given in year-month-day format.

Software used to acquire and analyze the data:

bb_network_decomposition: Network age calculation and regression analyses

bb_pipeline: Tag localization and decoding pipeline

bb_pipeline_models: Pretrained localizer and decoder models for bb_pipeline

bb_binary: Raw detection data storage format

bb_irflash: IR flash system schematics and arduino code

bb_imgacquisition: Recording and network storage

bb_behavior: Database interaction and data (pre)processing, velocity calculation

bb_circadian: Circadian rhythm calculations

bb_tracking: Tracking of bee detections over time

bb_wdd: Automatic detection and decoding of honey bee waggle dances

bb_interval_determination: Homography calculation

bb_stitcher: Image stitching

Data for CDC’s COVID Data Tracker site on Rates of COVID-19 Cases and Deaths by Vaccination Status. Click 'More' for important dataset description and footnotes

Dataset and data visualization details: These data were posted on October 21, 2022, archived on November 18, 2022, and revised on February 22, 2023. These data reflect cases among persons with a positive specimen collection date through September 24, 2022, and deaths among persons with a positive specimen collection date through September 3, 2022.

Vaccination status: A person vaccinated with a primary series had SARS-CoV-2 RNA or antigen detected on a respiratory specimen collected ≥14 days after verifiably completing the primary series of an FDA-authorized or approved COVID-19 vaccine. An unvaccinated person had SARS-CoV-2 RNA or antigen detected on a respiratory specimen and has not been verified to have received COVID-19 vaccine. Excluded were partially vaccinated people who received at least one FDA-authorized vaccine dose but did not complete a primary series ≥14 days before collection of a specimen where SARS-CoV-2 RNA or antigen was detected. Additional or booster dose: A person vaccinated with a primary series and an additional or booster dose had SARS-CoV-2 RNA or antigen detected on a respiratory specimen collected ≥14 days after receipt of an additional or booster dose of any COVID-19 vaccine on or after August 13, 2021. For people ages 18 years and older, data are graphed starting the week including September 24, 2021, when a COVID-19 booster dose was first recommended by CDC for adults 65+ years old and people in certain populations and high risk occupational and institutional settings. For people ages 12-17 years, data are graphed starting the week of December 26, 2021, 2 weeks after the first recommendation for a booster dose for adolescents ages 16-17 years. For people ages 5-11 years, data are included starting the week of June 5, 2022, 2 weeks after the first recommendation for a booster dose for children aged 5-11 years. For people ages 50 years and older, data on second booster doses are graphed starting the week including March 29, 2022, when the recommendation was made for second boosters. Vertical lines represent dates when changes occurred in U.S. policy for COVID-19 vaccination (details provided above). Reporting is by primary series vaccine type rather than additional or booster dose vaccine type. The booster dose vaccine type may be different than the primary series vaccine type. ** Because data on the immune status of cases and associated deaths are unavailable, an additional dose in an immunocompromised person cannot be distinguished from a booster dose. This is a relevant consideration because vaccines can be less effective in this group. Deaths: A COVID-19–associated death occurred in a person with a documented COVID-19 diagnosis who died; health department staff reviewed to make a determination using vital records, public health investigation, or other data sources. Rates of COVID-19 deaths by vaccination status are reported based on when the patient was tested for COVID-19, not the date they died. Deaths usually occur up to 30 days after COVID-19 diagnosis. Participating jurisdictions: Currently, these 31 health departments that regularly link their case surveillance to immunization information system data are included in these incidence rate estimates: Alabama, Arizona, Arkansas, California, Colorado, Connecticut, District of Columbia, Florida, Georgia, Idaho, Indiana, Kansas, Kentucky, Louisiana, Massachusetts, Michigan, Minnesota, Nebraska, New Jersey, New Mexico, New York, New York City (New York), North Carolina, Philadelphia (Pennsylvania), Rhode Island, South Dakota, Tennessee, Texas, Utah, Washington, and West Virginia; 30 jurisdictions also report deaths among vaccinated and unvaccinated people. These jurisdictions represent 72% of the total U.S. population and all ten of the Health and Human Services Regions. Data on cases

Second-Hand Fashion Dataset

Overview

The dataset originates from projects focused on the sorting of used clothes within a sorting facility. The primary objective is to classify each garment into one of several categories to determine its ultimate destination: reuse, reuse outside Sweden (export), recycling, repair, remake, or thermal waste.

The dataset has 31,997 clothing items, a massive update from the 3,000 items in version 1. The dataset collection started under the Vinnova funded project "AI for resource-efficient circular fashion" in Spring, 2022 and involves collaboration among three institutions: RISE Research Institutes of Sweden AB, Wargön Innovation AB, and Myrorna AB. The dataset has received further support through the EU project, CISUTAC (cisutac.eu).

Project page

- Webpage: https://fnauman.github.io/second-hand-fashion/">second-hand-fashion
- Contact: farrukh.nauman@ri.se

Dataset Details

- The dataset contains 31,997 clothing items, each with a unique item ID in a datetime format. The items are divided into three stations: `station1`, `station2`, and `station3`. The `station1` and `station2` folders contain images and annotations from Wargön Innovation AB, while the `station3` folder contains data from Myrorna AB. Each clothing item has three images and a JSON file containing annotations.

- Three images are provided for each clothing item:
1. Front view.
2. Back view.
3. Brand label close-up. About 4000-5000 brand images are missing because of privacy concerns: people's hands, faces, etc. Some clothing items did not have a brand label to begin with.

- Image resolutions are primarily in two sizes: `1280x720` and `1920x1080`. The background of the images is a table that used a measuring tape prior to January 2023, but later images have a square grid pattern with each square measuring `10x10` cm.

- Each JSON file contains a list of annotations, some of which require nuanced interpretation (see `labels.py` for the options):
- `usage`: Arguably the most critical label, usage indicates the garment's intended pathway. Options include 'Reuse,' 'Repair,' 'Remake,' 'Recycle,' 'Export' (reuse outside Sweden), and 'Energy recovery' (thermal waste). About 99% of the garments fall into the 'Reuse,' 'Export,' or 'Recycle' categories.
- `price`: The price field should be viewed as suggestive rather than definitive. Pricing models in the second-hand industry vary widely, including pricing by weight, brand, demand, or fixed value. Wargön Innovation AB does not determine actual pricing.
- `trend`: This field refers to the general style of the garment, not a time-dependent trend as in some other datasets (e.g., Visuelle 2.0). It might be more accurately labeled as 'style.'
- `material`: Material annotations are mostly based on the readings from a Near Infrared (NIR) scanner and in some cases from the garment's brand label.
- Damage-related attributes include:
- `condition` (1-5 scale, 5 being the best)
- `pilling` (1-5 scale, 5 meaning no pilling)
- `stains`, `holes`, `smell` (each with options 'None,' 'Minor,' 'Major').

Note: 'holes' and 'smell' were introduced after November 17th, 2022, and stains previously only had 'Yes'/'No' options. For `station1` and `station2`, we introduced additional damage location labels to assist in damage detection:

      "damageimage": "back",
      "damageloc": "bottom left",
      "damage": "stain ",
      "damage2image": "front",
      "damage2loc": "None",
      "damage2": "",
      "damage3image": "back",
      "damage3loc": "bottom right",
      "damage3": "stain"

Taken from `labels_2024_04_05_08_47_35.json` file. Additionally, we annotated a few hundred images with bounding box annotations that we aim to release at a later date.
- `comments`: The comments field is mostly empty, but sometimes contains important information about the garment, such as a detailed text description of the damage.

- Whenever possible, ISO standards have been followed to define these attributes on a 1-5 scale (e.g., `pilling`).

- Gold dataset: `Test` inside the comments field is meant for garments that were annotated multiple times by different annotators for annotator agreement comparisons. These 100 garments were annotated twice at Wargön Innovation AB (search within `station1/[dec2022,feb2023]`)and once at Myrorna AB (see `station3/test100` folder for JSON files containing their annotations).

- The data has been annotated by a group of expert second-hand sorters at Wargön Innovation AB and Myrorna AB.

- Some attributes, such as `price`, should be considered with caution. Many distinct pricing models exist in the second-hand industry:
- Price by weight
- Price by brand and demand (similar to first-hand fashion)
- Generic pricing at a fixed value (e.g., 1 Euro or 10 SEK)

Wargön Innovation AB does not set the prices in practice and their prices are suggestive only (`station1` and `station2`). Myrorna AB (`station3`), in contrast, does resale and sets the prices.

Comments

- We received feedback on our version 1 that some images were too blurry or had poor lighting. The image quality has slightly improved, but largely remains similar to release 1.
- We further learned that a handful of data items were duplicates. Several duplicate images were removed, but about 400 still remain.
- Some users did not prefer a `tar.gz` format that we uploaded in version 1 of the dataset. We have now switched to `.zip` for convenience.
- Most JSON files parse fine using any standard JSON reader, but a handful that are problematic have been set aside in the `json_errors` folder.
- Extra care was taken not to leak personal information. This is why you will not see any entries for `annotator` attribute in the JSON files in station1/sep2023 since people used their real names. Since then, we used internally assigned IDs.
- Many brand images contained people's hands, faces, or other personal information. We have removed about 4000-5000 brand images for privacy reasons.
- Please inform us immediately if you find any personal information revelations in the dataset:
- Farrukh Nauman (RISE AB): `farrukh.nauman@ri.se`,
- Susanne Eriksson (Wargön Innovation AB): `susanne.eriksson@wargoninnovation.se`,
- Gabriella Engstrom (Wargön Innovation AB): `gabriella.engstrom@wargoninnovation.se`.

We went through 100k images three times to ensure no personal information is leaked, but we are human and can make mistakes.

Partners

The data collection for this dataset has been carried out in collaboration with the following partners:

1. RISE Research Institutes of Sweden AB: RISE is a leading research institute dedicated to advancing innovation and sustainability across various sectors, including fashion and textiles.

2. Wargön Innovation AB: Wargön Innovation is an expert in sustainable and circular fashion solutions, contributing valuable insights and expertise to the dataset creation.

3. Myrorna AB: Myrorna is Sweden's oldest chain of stores for collecting clothes and furnishings that can be reused.

License

CC-BY 4.0. Please refer to the LICENSE file for more details.

Acknowledgments

This dataset was made possible through the collaborative efforts of RISE Research Institutes of Sweden AB, Wargön Innovation AB, and Myrorna AB, with funding from Vinnova and support from the EU project CISUTAC. We extend our gratitude to all the expert second-hand sorters and annotators who contributed their expertise to this project.

1. Database contents The Russian Short-Term Mortality Fluctuations database (RusSTMF) contains a series of standardized and crude death rates for men, women and both sexes for Russia as a whole and its regions for the period from 2000 to 2021. All the output indicators presented in the database are calculated based on data of deaths registered by the Vital Registry Office. The weekly death counts are calculated based on depersonalized individual data provided by the Russian Federal State Statistics Service (Rosstat) at the request of the HSE. Time coverage: 03.01.2000 (Week 1) – 31.12.2021 (Week 1148)
2. A brief description of the input data on deaths Date of death: date of occurrence Unit of time: week First and last days of the week: Monday – Sunday First and last week of the year: The weeks are organized according to ISO 8601:2004 guidelines. Each week of the year, including the first and last, contains 7 days. In order to get 7-day weeks, the days of previous years are included in this first week (if January 1 fell on Tuesday, Wednesday or Thursday) or in the last calendar week (if December 31 fell on Thursday, Friday or Saturday). Age groups: the entire population Sex: men, women, both sexes (men and women combined) Restrictions and data changes: data on deaths in the Pskov region were excluded for weeks 9-13 of 2012 Note: Deaths with an unknown date of occurrence (unknown year, month, or day) account for about 0.3% of all deaths and are excluded from the calculation of week-age-specific and standardized death rates.
3. Description of the week-specific mortality rates data file Week-specific standardized death rates for Russia as a whole and its regions are contained in a single data file presented in .csv format. The format of data allows its uploading into any system for statistical analysis. Each record (row) in the data file contains data for one calendar year, one week, one territory, one sex. The decimal point is dot (.) The first element of the row is the territory code ("PopCode" column), the second element is the year ("Year" column), the third element ("Week" column) is the week of the year, the fourth element ("Sex" column) is sex (F – female, M – male, B – both sexes combined). This is followed by a column "CDR" with the value of the crude death rate and "SDR" with the value of the standardized death rate. If the indicator cannot be calculated for some combination of year, sex, and territory, then the corresponding meaningful data elements in the data file are replaced with ".".

DM-FS enables the bidirectional exploration of fatal encounters. In other words, it allows others to investigate how deaths in one group, officers, modulate deaths in another, fatally shot civilians and vice-versa Recommended Instructions First, click on the "Tree" button near the bold "Change View" text, underneath the "Files" tab. This will make the repository legible. Second, there are three folders listed below. Click on the folder whose contents you wish to access and download the corresponding database. Civilians. This folder contains DM-FS Civilians, a database that can enable the exploration of how a civilian’s death affects the number of officers that other civilians kill each year, and under which circumstances. Officers.This folder contains DM-FS Officers, a database that enables the exploration of how an officer’s death affects the number of civilians other officers fatally shoot each year, and under which circumstances. Technical Validation Tables. This folder contains the various technical validation tables that appear in the DM-FS data descriptor. For most users, we recommend (i) reading the codebook and (ii) downloading the cleaned version of DM-FS. For more advanced users who wish to customize the database and apply their own filtering, we recommend downloading the full database. Changelog DM-FS will be updated with additional information, such as additional years or databases. Any additions or changes to the database will appear in the text below. ************************* Version 1.0 January 16, 2025 ************************* This post represents the launch of the first full version of DM-FS. The version of DM-FS that appears below is therefore an exact copy of the one described in the Scientific Data dataset descriptor.

Current issue 23/09/2020

Please note: Sensors 67, 68 and 69 are showing duplicate records. We are currently working on a fix to resolve this.



This dataset contains minute by minute directional pedestrian counts for the last hour from pedestrian sensor devices located across the city. The data is updated every 15 minutes and can be used to determine variations in pedestrian activity throughout the day.

The sensor_id column can be used to merge the data with the Sensor Locations dataset which details the location, status and directional readings of sensors. Any changes to sensor locations are important to consider when analysing and interpreting historical pedestrian counting data.

Note this dataset may not contain a reading for every sensor for every minute as sensor devices only create a record when one or more pedestrians have passed underneath the sensor.

The Pedestrian Counting System helps us to understand how people use different city locations at different times of day to better inform decision-making and plan for the future. A representation of pedestrian volume which compares each location on any given day and time can be found in our Online Visualisation.

Related datasets:
Pedestrian Counting System – 2009 to Present (counts per hour).
Pedestrian Counting System - Sensor Locations