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

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.

India marks one COVID-19 death every 5 minutes

https://ichef.bbci.co.uk/news/976/cpsprodpb/11C98/production/_118165827_gettyimages-1232465340.jpg" alt="">

Content

People across India scrambled for life-saving oxygen supplies on Friday and patients lay dying outside hospitals as the capital recorded the equivalent of one death from COVID-19 every five minutes.

For the second day running, the country’s overnight infection total was higher than ever recorded anywhere in the world since the pandemic began last year, at 332,730.

India’s second wave has hit with such ferocity that hospitals are running out of oxygen, beds, and anti-viral drugs. Many patients have been turned away because there was no space for them, doctors in Delhi said.

https://s.yimg.com/ny/api/res/1.2/XhVWo4SOloJoXaQLrxxUIQ--/YXBwaWQ9aGlnaGxhbmRlcjt3PTk2MA--/https://s.yimg.com/os/creatr-uploaded-images/2021-04/8aa568f0-a3e0-11eb-8ff6-6b9a188e374a" alt="">

Mass cremations have been taking place as the crematoriums have run out of space. Ambulance sirens sounded throughout the day in the deserted streets of the capital, one of India’s worst-hit cities, where a lockdown is in place to try and stem the transmission of the virus. source

Dataset

The dataset consists of the tweets made with the #IndiaWantsOxygen hashtag covering the tweets from the past week. The dataset totally consists of 25,440 tweets and will be updated on a daily basis.

The description of the features is given below | No |Columns | Descriptions | | -- | -- | -- | | 1 | user_name | The name of the user, as they’ve defined it. | | 2 | user_location | The user-defined location for this account’s profile. | | 3 | user_description | The user-defined UTF-8 string describing their account. | | 4 | user_created | Time and date, when the account was created. | | 5 | user_followers | The number of followers an account currently has. | | 6 | user_friends | The number of friends an account currently has. | | 7 | user_favourites | The number of favorites an account currently has | | 8 | user_verified | When true, indicates that the user has a verified account | | 9 | date | UTC time and date when the Tweet was created | | 10 | text | The actual UTF-8 text of the Tweet | | 11 | hashtags | All the other hashtags posted in the tweet along with #IndiaWantsOxygen | | 12 | source | Utility used to post the Tweet, Tweets from the Twitter website have a source value - web | | 13 | is_retweet | Indicates whether this Tweet has been Retweeted by the authenticating user. |

Acknowledgements

https://globalnews.ca/news/7785122/india-covid-19-hospitals-record/ Image courtesy: BBC and Reuters

Inspiration

The past few days have been really depressing after seeing these incidents. These tweets are the voice of the indians requesting help and people all over the globe asking their own countries to support India by providing oxygen tanks.

And I strongly believe that this is not just some data, but the pure emotions of people and their call for help. And I hope we as data scientists could contribute on this front by providing valuable information and insights.

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

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.

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.

ABSTRACT

The issue of diagnosing psychotic diseases, including schizophrenia and bipolar disorder, in particular, the objectification of symptom severity assessment, is still a problem requiring the attention of researchers. Two measures that can be helpful in patient diagnosis are heart rate variability calculated based on electrocardiographic signal and accelerometer mobility data. The following dataset contains data from 30 psychiatric ward patients having schizophrenia or bipolar disorder and 30 healthy persons. The duration of the measurements for individuals was usually between 1.5 and 2 hours. R-R intervals necessary for heart rate variability calculation were collected simultaneously with accelerometer data using a wearable Polar H10 device. The Positive and Negative Syndrome Scale (PANSS) test was performed for each patient participating in the experiment, and its results were attached to the dataset. Furthermore, the code for loading and preprocessing data, as well as for statistical analysis, was included on the corresponding GitHub repository.

BACKGROUND

Heart rate variability (HRV), calculated based on electrocardiographic (ECG) recordings of R-R intervals stemming from the heart's electrical activity, may be used as a biomarker of mental illnesses, including schizophrenia and bipolar disorder (BD) [Benjamin et al]. The variations of R-R interval values correspond to the heart's autonomic regulation changes [Berntson et al, Stogios et al]. Moreover, the HRV measure reflects the activity of the sympathetic and parasympathetic parts of the autonomous nervous system (ANS) [Task Force of the European Society of Cardiology the North American Society of Pacing Electrophysiology, Matusik et al]. Patients with psychotic mental disorders show a tendency for a change in the centrally regulated ANS balance in the direction of less dynamic changes in the ANS activity in response to different environmental conditions [Stogios et al]. Larger sympathetic activity relative to the parasympathetic one leads to lower HRV, while, on the other hand, higher parasympathetic activity translates to higher HRV. This loss of dynamic response may be an indicator of mental health. Additional benefits may come from measuring the daily activity of patients using accelerometry. This may be used to register periods of physical activity and inactivity or withdrawal for further correlation with HRV values recorded at the same time.

EXPERIMENTS

In our experiment, the participants were 30 psychiatric ward patients with schizophrenia or BD and 30 healthy people. All measurements were performed using a Polar H10 wearable device. The sensor collects ECG recordings and accelerometer data and, additionally, prepares a detection of R wave peaks. Participants of the experiment had to wear the sensor for a given time. Basically, it was between 1.5 and 2 hours, but the shortest recording was 70 minutes. During this time, evaluated persons could perform any activity a few minutes after starting the measurement. Participants were encouraged to undertake physical activity and, more specifically, to take a walk. Due to patients being in the medical ward, they received instruction to take a walk in the corridors at the beginning of the experiment. They were to repeat the walk 30 minutes and 1 hour after the first walk. The subsequent walks were to be slightly longer (about 3, 5 and 7 minutes, respectively). We did not remind or supervise the command during the experiment, both in the treatment and the control group. Seven persons from the control group did not receive this order and their measurements correspond to freely selected activities with rest periods but at least three of them performed physical activities during this time. Nevertheless, at the start of the experiment, all participants were requested to rest in a sitting position for 5 minutes. Moreover, for each patient, the disease severity was assessed using the PANSS test and its scores are attached to the dataset.

The data from sensors were collected using Polar Sensor Logger application [Happonen]. Such extracted measurements were then preprocessed and analyzed using the code prepared by the authors of the experiment. It is publicly available on the GitHub repository [Książek et al].

Firstly, we performed a manual artifact detection to remove abnormal heartbeats due to non-sinus beats and technical issues of the device (e.g. temporary disconnections and inappropriate electrode readings). We also performed anomaly detection using Daubechies wavelet transform. Nevertheless, the dataset includes raw data, while a full code necessary to reproduce our anomaly detection approach is available in the repository. Optionally, it is also possible to perform cubic spline data interpolation. After that step, rolling windows of a particular size and time intervals between them are created. Then, a statistical analysis is prepared, e.g. mean HRV calculation using the RMSSD (Root Mean Square of Successive Differences) approach, measuring a relationship between mean HRV and PANSS scores, mobility coefficient calculation based on accelerometer data and verification of dependencies between HRV and mobility scores.

DATA DESCRIPTION

The structure of the dataset is as follows. One folder, called HRV_anonymized_data contains values of R-R intervals together with timestamps for each experiment participant. The data was properly anonymized, i.e. the day of the measurement was removed to prevent person identification. Files concerned with patients have the name treatment_X.csv, where X is the number of the person, while files related to the healthy controls are named control_Y.csv, where Y is the identification number of the person. Furthermore, for visualization purposes, an image of the raw RR intervals for each participant is presented. Its name is raw_RR_{control,treatment}_N.png, where N is the number of the person from the control/treatment group. The collected data are raw, i.e. before the anomaly removal. The code enabling reproducing the anomaly detection stage and removing suspicious heartbeats is publicly available in the repository [Książek et al]. The structure of consecutive files collecting R-R intervals is following:

    Phone timestamp
    RR-interval [ms]


    12:43:26.538000
    651


    12:43:27.189000
    632


    12:43:27.821000
    618


    12:43:28.439000
    621


    12:43:29.060000
    661


    ...
    ...

The first column contains the timestamp for which the distance between two consecutive R peaks was registered. The corresponding R-R interval is presented in the second column of the file and is expressed in milliseconds.
The second folder, called accelerometer_anonymized_data contains values of accelerometer data collected at the same time as R-R intervals. The naming convention is similar to that of the R-R interval data: treatment_X.csv and control_X.csv represent the data coming from the persons from the treatment and control group, respectively, while X is the identification number of the selected participant. The numbers are exactly the same as for R-R intervals. The structure of the files with accelerometer recordings is as follows:

    Phone timestamp
    X [mg]
    Y [mg]
    Z [mg]


    13:00:17.196000
    -961
    -23
    182


    13:00:17.205000
    -965
    -21
    181


    13:00:17.215000
    -966
    -22
    187


    13:00:17.225000
    -967
    -26
    193


    13:00:17.235000
    -965
    -27
    191


    ...
    ...
    ...
    ...

The first column contains a timestamp, while the next three columns correspond to the currently registered acceleration in three axes: X, Y and Z, in milli-g unit.

We also attached a file with the PANSS test scores (PANSS.csv) for all patients participating in the measurement. The structure of this file is as follows:

    no_of_person
    PANSS_P
    PANSS_N
    PANSS_G
    PANSS_total


    1
    8
    13
    22
    43


    2
    11
    7
    18
    36


    3
    14
    30
    44
    88


    4
    18
    13
    27
    58


    ...
    ...
    ...
    ...
    ..

The first column contains the identification number of the patient, while the three following columns refer to the PANSS scores related to positive, negative and general symptoms, respectively.

USAGE NOTES

All the files necessary to run the HRV and/or accelerometer data analysis are available on the GitHub repository [Książek et al]. HRV data loading, preprocessing (i.e. anomaly detection and removal), as well as the calculation of mean HRV values in terms of the RMSSD, is performed in the main.py file. Also, Pearson's correlation coefficients between HRV values and PANSS scores and the statistical tests (Levene's and Mann-Whitney U tests) comparing the treatment and control groups are computed. By default, a sensitivity analysis is made, i.e. running the full pipeline for different settings of the window size for which the HRV is calculated and various time intervals between consecutive windows. Preparing the heatmaps of correlation coefficients and corresponding p-values can be done by running the utils_advanced_plots.py file after performing the sensitivity analysis. Furthermore, a detailed analysis for the one selected set of hyperparameters may be prepared (by setting sensitivity_analysis = False), i.e. for 15-minute window sizes, 1-minute time intervals between consecutive windows and without data interpolation method. Also, patients taking quetiapine may be excluded from further calculations by setting exclude_quetiapine = True because this medicine can have a strong impact on HRV [Hattori et al].

The accelerometer data processing may be performed using the utils_accelerometer.py file. In this case, accelerometer recordings are downsampled to ensure the same timestamps as for R-R intervals and, for each participant, the mobility coefficient is calculated. Then, a correlation

The project ´Quality of Life and Well-being of Very Old People in NRW (NRW80+)´, which is funded by the Ministry of Innovation, Science and Research of North Rhine-Westphalia and carried out by the CERES research association at the University of Cologne, is intended to provide representative statements on the living conditions of very old people in North Rhine-Westphalia. The aim is to obtain comprehensive information about the environment in which very old people live or would like to live, what their social role is and how satisfied they are with their living situation. Housing situation: type of housing; full inpatient care in the case of residential accommodation; number of rooms; duration of living in this apartment/house/home; tenure (owner, main tenant, subtenant, rent-free); always in this apartment/house or lived in this flat/house; barrier-reduced living: thresholds over 2 cm; doors at least 80 cm wide; stairs with handrail or stair lift; doors of bath and WC open to the outside; suitability of the living environment on foot or in a wheelchair (walkability); residential attachment; trust in people in the neighbourhood (social cohesion). 2. Family situation: marital status; currently stable partnership; children present; number of children; number of living children; number of grandchildren and great grandchildren; household size; household composition: sex of up to three persons and their relationship to the respondent; pets. 3. Financial situation: sources of income; net household income; costs: amount of the monthly rent for warmth; amount of the monthly rent for cold or rent without additional costs; amount of the monthly additional costs; housing loans or mortgages to be paid off and their amount; monthly costs for the stay in the home; debts from loans; amount of debts; assets: amount of the total assets. 4. Dealing with old age: autonomy; experience of ageing (e.g. greater appreciation of relationships and other people, more attention to one´s own health, decrease in mental capacity, etc.); appreciation by others (being needed, being appreciated for services, being treated as a burden, being appreciated more than before). 5. Health: cognitive tests on mental health (repeat ten selected words in two passes, convert numbers, mention as many things as possible that you can buy in the supermarket in one minute, repeat numbers in reverse order, remember the ten words at the beginning of the cognitive test); self-assessment of health; assessment of pain level in the last four weeks; height in cm; weight in kg; weight loss in the last twelve months; multimorbidity: medical treatment due to selected diseases; existence of care level or degree of care; designation of care level or degree of care; additional care level 0 (limited everyday competence); care use: use of an outpatient care service; use of day care; private care; hours of private care per week; respondent cares privately for another person and hours per week; functional health with regard to various activities of daily life (eating, dressing and undressing, personal hygiene, walking, looking up from bed and lying down, being bedridden, bathing or showering, reaching the toilet in time, frequency of problems with bladder and bowel control, using the telephone, organising routes outside the walking range (trips by taxi or bus), buying food and clothing yourself, preparing your own meals, doing housework, taking medication, regulating financial matters); use of assistive devices (hearing aid, wheelchair, home emergency call system, private car); health literacy (knowledge and compliance). 6. Everyday life and lifestyle: importance and frequency of: time spent together with other people, physical activity, rest and time for oneself, in-depth study of a topic and creative activity; preferred music style; preferences regarding clothing and food; leisure activities in the last 12 months (e.g. sports, participation in a coffee circle or regulars´ table, visiting a café, restaurant or pub, travelling, voluntary work, etc.); frequency and place of the respective activities; religious community, club membership; political participation: party affiliation; participation in the last federal election. 7. Technology setting and technology use: technology use in the last 12 months (computer or laptop, internet, smartphone, regular mobile phone, tablet computer, fitness wristband) and frequency of use; technology setting: interest, difficulties in using modern digital devices, ease of everyday life with modern digital devices); purpose of internet use in the last three months (emails, looking for information on health topics, participating in social networks, buying or selling goods or services). 8. Social inclusion: called social network; for the four most important persons the following was asked: sex, their relationship to the respondent, frequency of contact and attachment to these persons; number of other persons in the social network (size of the social network); frequency of loneliness in the last week; social support: larger gifts given or larger gifts received; frequency of social support given or received by the respondent (e.g. helped other people with their tasks, received help with tasks and tasks, received consolation, received consolation); Generativity (importance of passing on one´s own experiences to younger people, passing on social values to younger people, being a role model for younger people); Integration into society: Anomie (coping with today´s social way of life, one´s own values fit less and less with the values of today´s society, lack of orientation due to rapidly changing society). 9. Hand grip force: agreement with hand grip test; right- or left-handed; writing hand; test value 1st measurement right and left; test value 2nd measurement right and left; deviations exist. 10. Value system: Individual value system (doing things in one´s own way (self-determination), being wealthy (power), avoiding dangers and safe environment (security), spending good time (hedonism), doing good for society (benevolence), getting achievements recognized (achievement), taking risks (stimulation), avoiding teasing others (conformity), caring for nature and the environment (universalism), respecting traditions (tradition); spirituality: Importance of a connection with God or a higher power, with people and with nature; frequency of connection with God or a higher power, with people and with nature; importance of institutionalizing one´s own beliefs, e.g. in church; ; frequency of the feeling of community in institutionalized forms; orientation to the guidelines of religious institutions; importance of being part of a large entity; frequency of the feeling of being part of a larger entity; importance of practicing religious practices such as Praying or meditating, frequency of religious practices; reconciled relationship with God; God as support; desire to leave everything behind to go to God; God is threatening and punishing; importance of faith or spirituality in one´s own life; attitude towards dying and death: acceptance of one´s own mortality; death as an incriminating thought; fear of dying; frequency of thoughts about death; will written; dispositions (living will, precautionary power of attorney, care-giving will, general power of attorney). 11. Interpersonal personality: tendency to quarrel, losing control, feeling irritated and harassed); external and internal controlling life (life in one´s own hands, success through effort, life is determined by others, plans thwarted by fate). 12. Well-being and life satisfaction: frequency of selected feelings in the last year (PANAS: enthusiastic, attentive, joyfully excited/expectant, stimulated, determined); depressiveness during the last 14 days (depressed, difficult to pick up, enjoy life, even if some things are difficult, brooding a lot); Valuation of Life-Scale (and a. optimistic, consider current life as useful, life determined by religious or moral principles, etc.); Meaning in Life-Scale (satisfaction with what has been achieved in the past, with the past at peace); general life satisfaction. 13. Critical life events: perceived burden of life events in general; generally most stressful event; current burden of events related to World War II; most stressful event related to World War II; current burden of events outside World War II; most stressful event outside World War II; most stressful event outside World War II; most stressful event outside World War II Interpersonal conflicts and emotional consequences (INDICATE): Frequency of conflicts with known persons (other person has become louder/ abusive towards the respondent (intimidation), has spoken about weaknesses or impairments of the respondent (shame), blamed for an event, paternalism: Ignoring the respondent´s opinion, has caused the respondent to renounce his or her wish or right, neglect: no support given, no time given, financial exploitation: property or possessions of the respondent used for own purposes, has been kept by the respondent, physical violence: firm or rough handling, physically rough or inconsiderate handling, custodial measures restriction of freedom of movement, medication given without consent, sexualised violence: offensive behaviour, sexual harassment). 14. Biography: caregiver in childhood up to the age of 16; social status of parents: employment and occupational status of father and mother when the interviewee was 15 years old; number of siblings; occupational biography of the interviewee: end of full-time employment; occupational status; special designation of occupational status; occupational biography of spouse: end of full-time employment; occupational status; special designation of occupational status; request to politicians to improve one´s own quality of life (open). Demography: sex; age; origin: country, place of residence 1949-1990; education: country of last school attendance; highest

The Worldwide Soundscapes project is a global, open inventory of spatio-temporally replicated soundscape datasets. This Zenodo entry comprises the data tables that constitute its (meta-)database, as well as their description.

The overview of all sampling sites can be found on the corresponding project on ecoSound-web, as well as a demonstration collection containing selected recordings. More information on the project can be found here and on ResearchGate.

The audio recording criteria justifying inclusion into the meta-database are:

• Stationary (no transects, towed sensors or microphones mounted on cars)
• Passive (unattended, no human disturbance by the recordist)
• Ambient (no spatial or temporal focus on a particular species or direction)
• Spatially and/or temporally replicated (multiple sites sampled at least at one common daytime or multiple days sampled at least in one common site)

The individual columns of the provided data tables are described in the following. Data tables are linked through primary keys; joining them will result in a database.

datasets

• dataset_id: incremental integer, primary key
• name: name of the dataset. if it is repeated, incremental integers should be used in the "subset" column to differentiate them.
• subset: incremental integer that can be used to distinguish datasets with identical names
• collaborators: full names of people deemed responsible for the dataset, separated by commas
• contributors: full names of people who are not the main collaborators but who have significantly contributed to the dataset, and who could be contacted for in-depth analyses, separated by commas.
• date_added: when the datased was added (DD/MM/YYYY)
• URL_open_recordings: if recordings (even only some) from this dataset are openly available, indicate the internet link where they can be found.
• URL_project: internet link for further information about the corresponding project
• DOI_publication: DOI of corresponding publications, separated by comma
• core_realm_IUCN: The core realm of the dataset. Datasets may have multiple realms, but the main one should be listed. Datasets may contain sampling sites from different realms in the "sites" sheet. IUCN Global Ecosystem Typology (v2.0): https://global-ecosystems.org/
• medium: the physical medium the microphone is situated in
• protected_area: Whether the sampling sites were situated in protected areas or not, or only some.
• GADM0: For datasets on land or in territorial waters, Global Administrative Database level0
  https://gadm.org/
• GADM1: For datasets on land or in territorial waters, Global Administrative Database level1
  https://gadm.org/
• GADM2: For datasets on land or in territorial waters, Global Administrative Database level2
  https://gadm.org/
• IHO: For marine locations, the sea area that encompassess all the sampling locations according to the International Hydrographic Organisation. Map here: https://www.arcgis.com/home/item.html?id=44e04407fbaf4d93afcb63018fbca9e2
• locality: optional free text about the locality
• latitude_numeric_region: study region approximate centroid latitude in WGS84 decimal degrees
• longitude_numeric_region: study region approximate centroid longitude in WGS84 decimal degrees
• sites_number: number of sites sampled
• year_start: starting year of the sampling
• year_end: ending year of the sampling
• deployment_schedule: description of the sampling schedule, provisional
• temporal_recording_selection: list environmental exclusion criteria that were used to determine which recording days or times to discard
• high_pass_filter_Hz: frequency of the high-pass filter of the recorder, in Hz
• variable_sampling_frequency: Does the sampling frequency vary? If it does, write "NA" in the sampling_frequency_kHz column and indicate it in the sampling_frequency_kHz column inside the deployments sheet
• sampling_frequency_kHz: frequency the microphone was sampled at (sounds of half that frequency will be recorded)
• variable_recorder:
• recorder: recorder model used
• microphone: microphone used
• freshwater_recordist_position: position of the recordist relative to the microphone during sampling (only for freshwater)
• collaborator_comments: free-text field for comments by the collaborators
• validated: This cell is checked if the contents of all sheets are complete and have been found to be coherent and consistent with our requirements.
• validator_name: name of person doing the validation
• validation_comments: validators: please insert the date when someone was contacted
• cross-check: this cell is checked if the collaborators confirm the spatial and temporal data after checking the corresponding site maps, deployment and operation time graphs found at https://drive.google.com/drive/folders/1qfwXH_7dpFCqyls-c6b8RZ_fbcn9kXbp?usp=share_link

datasets-sites

• dataset_ID: primary key of datasets table
• dataset_name: lookup field
• site_ID: primary key of sites table
• site_name: lookup field

sites

• site_ID: unique site IDs, larger than 1000 for compatibility with ecoSound-web
• site_name: name or code of sampling site as used in respective projects
• latitude_numeric: exact numeric degrees coordinates of latitude
• longitude_numeric: exact numeric degrees coordinates of longitude
• topography_m: for sites on land: elevation. For marine sites: depth (negative). in meters
• freshwater_depth_m
• realm: Ecosystem type according to IUCN GET https://global-ecosystems.org/
• biome: Ecosystem type according to IUCN GET https://global-ecosystems.org/
• functional_group: Ecosystem type according to IUCN GET https://global-ecosystems.org/
• comments

deployments

• dataset_ID: primary key of datasets table
• dataset_name: lookup field
• deployment: use identical subscript letters to denote rows that belong to the same deployment. For instance, you may use different operation times and schedules for different target taxa within one deployment.
• start_date_min: earliest date of deployment start, double-click cell to get date-picker
• start_date_max: latest date of deployment start, if applicable (only used when recorders were deployed over several days), double-click cell to get date-picker
• start_time_mixed: deployment start local time, either in HH:MM format or a choice of solar daytimes (sunrise, sunset, noon, midnight). Corresponds to the recording start time for continuous recording deployments. If multiple start times were used, you should mention the latest start time (corresponds to the earliest daytime from which all recorders are active). If applicable, positive or negative offsets from solar times can be mentioned (For example: if data are collected one hour before sunrise, this will be "sunrise-60")
• permanent: is the deployment permanent (in which case it would be ongoing and the end date or duration would be unknown)?
• variable_duration_days: is the duration of the deployment variable? in days
• duration_days: deployment duration per recorder (use the minimum if variable)
• end_date_min: earliest date of deployment end, only needed if duration is variable, double-click cell to get date-picker
• end_date_max: latest date of deployment end, only needed if duration is variable, double-click cell to get date-picker
• end_time_mixed: deployment end local time, either in HH:MM format or a choice of solar daytimes (sunrise, sunset, noon, midnight). Corresponds to the recording end time for continuous recording deployments.
• recording_time: does the recording last from the deployment start time to the end time (continuous) or at scheduled daily intervals (scheduled)? Note: we consider recordings with duty cycles to be continuous.
• operation_start_time_mixed: scheduled recording start local time, either in HH:MM format or a choice of solar daytimes (sunrise, sunset, noon, midnight). If applicable, positive or negative offsets from solar times can be mentioned (For example: if data are collected one hour before sunrise, this will be "sunrise-60")
• operation_duration_minutes: duration of operation in minutes, if constant
• operation_end_time_mixed: scheduled recording end local time, either in HH:MM format or a choice of solar daytimes (sunrise, sunset, noon, midnight). If applicable, positive or negative offsets from solar times can be mentioned (For example: if data are collected one hour before sunrise, this will be "sunrise-60")
• duty_cycle_minutes: duty cycle of the recording (i.e. the fraction of minutes when it is recording), written as "recording(minutes)/period(minutes)". For example: "1/6" if the recorder is active for 1 minute and standing by for 5 minutes.
• sampling_frequency_kHz: only indicate the sampling frequency if it is variable within a particular dataset so that we need to code different frequencies for different deployments
• recorder
• subset_sites: If the deployment was not done in all the sites of the

Context:

This dataset is an extra updating dataset for the G-Research Crypto Forecasting competition.

Introduction

This is a daily updated dataset, automaticlly collecting market data for G-Research crypto forecasting competition. The data is of the 1-minute resolution, collected for all competition assets and both retrieval and uploading are fully automated. see discussion topic.

The Data

For every asset in the competition, the following fields from Binance's official API endpoint for historical candlestick data are collected, saved, and processed.

1. **timestamp** - A timestamp for the minute covered by the row.
2. **Asset_ID** - An ID code for the cryptoasset.
3. **Count** - The number of trades that took place this minute.
4. **Open** - The USD price at the beginning of the minute.
5. **High** - The highest USD price during the minute.
6. **Low** - The lowest USD price during the minute.
7. **Close** - The USD price at the end of the minute.
8. **Volume** - The number of cryptoasset u units traded during the minute.
9. **VWAP** - The volume-weighted average price for the minute.
10. **Target** - 15 minute residualized returns. See the 'Prediction and Evaluation section of this notebook for details of how the target is calculated.
11. **Weight** - Weight, defined by the competition hosts [here](https://www.kaggle.com/cstein06/tutorial-to-the-g-research-crypto-competition)
12. **Asset_Name** - Human readable Asset name.

Indexing

The dataframe is indexed by timestamp and sorted from oldest to newest. The first row starts at the first timestamp available on the exchange, which is July 2017 for the longest-running pairs.

Usage Example

The following is a collection of simple starter notebooks for Kaggle's Crypto Comp showing PurgedTimeSeries in use with the collected dataset. Purged TimesSeries is explained here. There are many configuration variables below to allow you to experiment. Use either GPU or TPU. You can control which years are loaded, which neural networks are used, and whether to use feature engineering. You can experiment with different data preprocessing, model architecture, loss, optimizers, and learning rate schedules. The extra datasets contain the full history of the assets in the same format as the competition, so you can input that into your model too.

Baseline Example Notebooks:

• Neural Network Starter
• LightGBM Starter
• Catboost Starter
• XGBoost Starter
• TabNet Starter
• Reinforcement Learning (PPO) Starter

These notebooks follow the ideas presented in my "Initial Thoughts" here. Some code sections have been reused from Chris' great (great) notebook series on SIIM ISIC melanoma detection competition here

Loose-ends:

This is a work in progress and will be updated constantly throughout the competition. At the moment, there are some known issues that still needed to be addressed:

• VWAP: - At the moment VWAP calculation formula is still unclear. Currently the dataset uses an approximation calculated from the Open, High, Low, Close, Volume candlesticks. [Waiting for competition hosts input]
• Target Labeling: There exist some mismatches to the original target provided by the hosts at some time intervals. On all the others - it is the same. The labeling code can be seen here. [Waiting for competition hosts] input]
• Filtering: No filtration of 0 volume data is taken place.

Example Visualisations

Opening price with an added indicator (MA50): https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F2234678%2Fb8664e6f26dc84e9a40d5a3d915c9640%2Fdownload.png?generation=1582053879538546&alt=media" alt="">

Volume and number of trades: https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F2234678%2Fcd04ed586b08c1576a7b67d163ad9889%2Fdownload-1.png?generation=1582053899082078&alt=media" alt="">

License

This data is being collected automatically from the crypto exchange Binance.

How much time do people spend on social media? As of 2025, the average daily social media usage of internet users worldwide amounted to 141 minutes per day, down from 143 minutes in the previous year. Currently, the country with the most time spent on social media per day is Brazil, with online users spending an average of 3 hours and 49 minutes on social media each day. In comparison, the daily time spent with social media in the U.S. was just 2 hours and 16 minutes. Global social media usageCurrently, the global social network penetration rate is 62.3 percent. Northern Europe had an 81.7 percent social media penetration rate, topping the ranking of global social media usage by region. Eastern and Middle Africa closed the ranking with 10.1 and 9.6 percent usage reach, respectively. People access social media for a variety of reasons. Users like to find funny or entertaining content and enjoy sharing photos and videos with friends, but mainly use social media to stay in touch with current events friends. Global impact of social mediaSocial media has a wide-reaching and significant impact on not only online activities but also offline behavior and life in general. During a global online user survey in February 2019, a significant share of respondents stated that social media had increased their access to information, ease of communication, and freedom of expression. On the flip side, respondents also felt that social media had worsened their personal privacy, increased a polarization in politics and heightened everyday distractions.

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

The dataset shows death claims accepted by the CNESST from January 1 to December 31. The CNESST administers the occupational health and safety regime. The Law on Industrial Accidents and Occupational Diseases (LATMP) aims to compensate for occupational injuries and the consequences they cause for beneficiaries. The death claims presented in the data set meet the following criteria: * They are the consequence of a work accident or an occupational disease within the meaning of the LATMP. * These claims represent people who were covered by the occupational health and safety insurance plan administered by the CNESST. * The date of registration of the acceptance of the death claim is between January 1 and December 31 of the reference year. Note that the death may have occurred during a year prior to the reference year.

Introduction

The 802.11 standard includes several management features and corresponding frame types. One of them are probe requests (PR). They are sent by mobile devices in the unassociated state to search the nearby area for existing wireless networks. The frame part of PRs consists of variable length fields called information elements (IE). IE fields represent the capabilities of a mobile device, such as data rates.
The dataset includes PRs collected in a controlled rural environment and in a semi-controlled indoor environment under different measurement scenarios.
It can be used for various use cases, e.g., analysing MAC randomization, determining the number of people in a given location at a given time or in different time periods, analysing trends in population movement (streets, shopping malls, etc.) in different time periods, etc.

Measurement setup

The system for collecting PRs consists of a Raspberry Pi 4 (RPi) with an additional WiFi dongle to capture Wi-Fi signal traffic in monitoring mode. Passive PR monitoring is performed by listening to 802.11 traffic and filtering out PR packets on a single WiFi channel.
The following information about each PR received is collected: MAC address, Supported data rates, extended supported rates, HT capabilities, extended capabilities, data under extended tag and vendor specific tag, interworking, VHT capabilities, RSSI, SSID and timestamp when PR was received.
The collected data was forwarded to a remote database via a secure VPN connection. A Python script was written using the Pyshark package for data collection, preprocessing and transmission.

Data preprocessing

The gateway collects PRs for each consecutive predefined scan interval (10 seconds). During this time interval, the data are preprocessed before being transmitted to the database.
For each detected PR in the scan interval, IEs fields are saved in the following JSON structure:
PR_IE_data =
{
'DATA_RTS': {'SUPP': DATA_supp , 'EXT': DATA_ext},
'HT_CAP': DATA_htcap,
'EXT_CAP': {'length': DATA_len, 'data': DATA_extcap},
'VHT_CAP': DATA_vhtcap,
'INTERWORKING': DATA_inter,
'EXT_TAG': {'ID_1': DATA_1_ext, 'ID_2': DATA_2_ext ...},
'VENDOR_SPEC': {VENDOR_1:{
'ID_1': DATA_1_vendor1,
'ID_2': DATA_2_vendor1
...},
VENDOR_2:{
'ID_1': DATA_1_vendor2,
'ID_2': DATA_2_vendor2
...}
...}
}

Supported data rates and extended supported rates are represented as arrays of values that encode information about the rates supported by a mobile device. The rest of the IEs data is represented in hexadecimal format. Vendor Specific Tag is structured differently than the other IEs. This field can contain multiple vendor IDs with multiple data IDs with corresponding data. Similarly, the extended tag can contain multiple data IDs with corresponding data.
Missing IE fields in the captured PR are not included in PR_IE_DATA.

When a new MAC address is detected in the current scan time interval, the data from PR is stored in the following structure:

{'MAC': MAC_address, 'SSIDs': [ SSID ], 'PROBE_REQs': [PR_data] },

where PR_data is structured as follows:
{
'TIME': [ DATA_time ],
'RSSI': [ DATA_rssi ],
'DATA': PR_IE_data
}.

This data structure allows storing only TOA and RSSI for all PRs originating from the same MAC address and containing the same PR_IE_data. All SSIDs from the same MAC address are also stored.
The data of the newly detected PR is compared with the already stored data of the same MAC in the current scan time interval.
If identical PR's IE data from the same MAC address is already stored, then only data for the keys TIME and RSSI are appended.
If no identical PR's IE data has yet been received from the same MAC address, then PR_data structure of the new PR for that MAC address is appended to PROBE_REQs key.
The preprocessing procedure is shown in Figure ./Figures/Preprocessing_procedure.png
At the end of each scan time interval, all processed data is sent to the database along with additional metadata about the collected data e.g. wireless gateway serial number and scan start and end timestamps. For an example of a single PR captured, see the ./Single_PR_capture_example.json file.

Environments description

We performed measurements in a controlled rural outdoor environment and in a semi-controlled indoor environment of the Jozef Stefan Institute.
See the Excel spreadsheet Measurement_informations.xlsx for a list of mobile devices tested.

Indoor environment

We used 3 RPi's for the acquisition of PRs in the Jozef Stefan Institute. They were placed indoors in the hallways as shown in the ./Figures/RPi_locations_JSI.png. Measurements were performed on weekend to minimize additional uncontrolled traffic from users' mobile devices. While there is some overlap in WiFi coverage between the devices at the location 2 and 3, the device at location 1 has no overlap with the other two devices.

Rural environment outdoors

The three RPi's used to collect PRs were placed at three different locations with non-overlapping WiFi coverage, as shown in ./Figures/RPi_locations_rural_env.png. Before starting the measurement campaign, all measured devices were turned off and the environment was checked for active WiFi devices. We did not detect any unknown active devices sending WiFi packets in the RPi's coverage area, so the deployment can be considered fully controlled.
All known WiFi enabled devices that were used to collect and send data to the database used a global MAC address, so they can be easily excluded in the preprocessing phase. MAC addresses of these devices can be found in the ./Measurement_informations.xlsx spreadsheet.
Note: The Huawei P20 device with ID 4.3 was not included in the test in this environment.

Scenarios description

We performed three different scenarios of measurements.

Individual device measurements

For each device, we collected PRs for one minute with the screen on, followed by PRs collected for one minute with the screen off. In the indoor environment the WiFi interfaces of the other devices not being tested were disabled. In rural environment other devices were turned off. Start and end timestamps of the recorded data for each device can be found in the ./Measurement_informations.xlsx spreadsheet under the Indoor environment of Jozef Stefan Institute sheet and the Rural environment sheet.

Three groups test

In this measurement scenario, the devices were divided into three groups. The first group contained devices from different manufacturers. The second group contained devices from only one manufacturer (Samsung). Half of the third group consisted of devices from the same manufacturer (Huawei), and the other half of devices from different manufacturers. The distribution of devices among the groups can be found in the ./Measurement_informations.xlsx spreadsheet.

The same data collection procedure was used for all three groups. Data for each group were collected in both environments at three different RPis locations, as shown in ./Figures/RPi_locations_JSI.png and ./Figures/RPi_locations_rural_env.png.
At each location, PRs were collected from each group for 10 minutes with the screen on. Then all three groups switched locations and the process was repeated. Thus, the dataset contains measurements from all three RPi locations of all three groups of devices in both measurement environments. The group movements and the timestamps for the start and end of the collection of PRs at each loacation can be found in spreadsheet ./Measurement_informations.xlsx.

One group test

In the last measurement scenario, all devices were grouped together. In rural evironement we first collected PRs for 10 minutes while the screen was on, and then for another 10 minutes while the screen was off. In indoor environment data were collected at first location with screens on for 10 minutes. Then all devices were moved to the location of the next RPi and PRs were collected for 5 minutes with the screen on and then for another 5 minutes with the screen off.

Folder structure

The root directory contains two files in JSON format for each of the environments where the measurements took place (Data_indoor_environment.json and Data_rural_environment.json). Both files contain collected PRs for the entire day that the measurements were taken (12:00 AM to 12:00 PM) to get a sense of the behaviour of the unknown devices in each environment. The spreadsheet ./Measurement_informations.xlsx. contains three sheets. Devices description contains general information about the tested devices, RPis, and the assigned group for each device. The sheets Indoor environment of Jozef Stefan Institute and Rural environment contain the corresponding timestamps for the start and end of each measurement scenario. For the scenario where the devices were divided into groups, additional information about the movements between locations is included. The location names are based on the RPi gateway ID and may differ from those on the figures showing the

You can speak to a live agent at Frontier Airlines by calling ☎️+1(888) 714-9534, which connects you directly to their reservations team. This is the most efficient way to get personalized help with your booking. When you speak to a real person, you gain access to expert support, up-to-date fare information, and live problem-solving. Frontier understands that not all customers want to book online. That’s why they make sure you can reach them at ☎️+1(888) 714-9534 for immediate booking assistance, 365 days a year.

Whether you're traveling for business or vacation, talking to a live agent can take the stress out of planning. When you call ☎️+1(888) 714-9534, the agent can walk you through everything — including flight times, baggage policies, available seats, and add-on services. Unlike online systems, a live representative can adapt to your needs in real time. For example, if you're unsure whether to book a basic fare or upgrade to a bundle, just ask. The agent at ☎️+1(888) 714-9534 will explain all your options and guide you to the best choice for your trip.

Live support is especially helpful when you have special travel circumstances. Maybe you’re traveling with a wheelchair, a service animal, or an oversized bag. If you book online, these details can be confusing or overlooked. But when you call ☎️+1(888) 714-9534, a real person can make sure everything is properly arranged. That kind of attention to detail helps avoid last-minute airport surprises. Agents are also trained to assist seniors, families with young children, or first-time flyers, so don’t hesitate to reach out through ☎️+1(888) 714-9534.

And yes, speaking to a live agent can sometimes unlock exclusive savings. While Frontier promotes its “Low Fares Done Right” policy, some phone-only deals exist that are not visible on the website. When you call ☎️+1(888) 714-9534, make sure to ask if there are any unpublished discounts, limited-time offers, or bundle upgrades that could save you money. It takes just a few minutes, and you might end up with a much better price. Many seasoned travelers call ☎️+1(888) 714-9534 for this very reason.

Let’s also not forget that phone agents can help with applying travel credits, promo codes, or miles. If you’re trying to redeem points from your FRONTIER Miles account, a live agent can assist with that too. Just have your loyalty number ready when you call ☎️+1(888) 714-9534, and they'll pull up your account and walk you through your redemption options. This eliminates the frustration that sometimes comes from trying to redeem miles online. It’s another reason why calling ☎️+1(888) 714-9534 can save both time and hassle.

Need to make last-minute changes to an existing booking? That’s something a live agent can handle quickly and efficiently. If you booked the wrong date or need to add a passenger, call ☎️+1(888) 714-9534 right away. The sooner you reach out, the more options the agent will have to modify your flight with minimal fees. Trying to change a reservation through online channels can take hours or even days. With a call to ☎️+1(888) 714-9534, you get live, on-the-spot help from someone who knows exactly how the system works.

One of the most appreciated benefits of speaking with a live Frontier agent is clarity. Frontier has a unique fare structure that allows you to customize your travel experience. This can sometimes lead to questions about baggage allowances, seat selection, or refund eligibility. Instead of guessing, just dial ☎️+1(888) 714-9534. The agent can explain everything — from the difference between Economy and Discount Den fares to how to avoid change penalties. Everything becomes easier to understand when you have someone at ☎️+1(888) 714-9534 guiding you through it.

For travelers booking multiple flights or coordinating group travel, live assistance is even more valuable. Frontier's online booking tool is designed for simple, individual reservations. But if you're trying to organize a school trip, business travel, or family reunion, speak to an agent at ☎️+1(888) 714-9534. They’ll help manage seat availability, fare combinations, and payment options for the entire group. In many cases, they can also offer group discounts — just one more reason to call ☎️+1(888) 714-9534 directly.

Another major advantage of live booking is flexibility. Say you’ve been browsing flights all week but haven’t pulled the trigger because prices kept shifting. A live agent can look at fare calendars, availability forecasts, and give you honest feedback on whether now is the best time to buy. That’s real human advice — not just algorithms. So before you lock in that ticket, check with an expert by calling ☎️+1(888) 714-9534.

Lastly, live phone booking allows for instant confirmation. Once the reservation is finalized, you'll get an email with all your flight details, receipt, and any additional information discussed during the call. There’s no need to refresh a browser or worry about glitches. That’s why many people prefer booking through ☎️+1(888) 714-9534 — it’s faster, easier, and more secure than DIY options.

In short, yes — speaking to a live agent is one of the best ways to book your flight with Frontier Airlines. Whether you’re a frequent flyer or a first-time traveler, the team at ☎️+1(888) 714-9534 is ready to help. From selecting seats and applying credits to handling changes or answering tough questions, their agents are trained to simplify your journey. When in doubt, pick up the phone and dial ☎️+1(888) 714-9534 — your smooth travel experience is just one call away.

Introduction

The 802.11 standard includes several management features and corresponding frame types. One of them are Probe Requests (PR), which are sent by mobile devices in an unassociated state to scan the nearby area for existing wireless networks. The frame part of PRs consists of variable-length fields, called Information Elements (IE), which represent the capabilities of a mobile device, such as supported data rates.

This dataset contains PRs collected over a seven-day period by four gateway devices in an uncontrolled urban environment in the city of Catania.

It can be used for various use cases, e.g., analyzing MAC randomization, determining the number of people in a given location at a given time or in different time periods, analyzing trends in population movement (streets, shopping malls, etc.) in different time periods, etc.

Related dataset

Same authors also produced the Labeled dataset of IEEE 802.11 probe requests with same data layout and recording equipment.

Measurement setup

The system for collecting PRs consists of a Raspberry Pi 4 (RPi) with an additional WiFi dongle to capture WiFi signal traffic in monitoring mode (gateway device). Passive PR monitoring is performed by listening to 802.11 traffic and filtering out PR packets on a single WiFi channel.

The following information about each received PR is collected: - MAC address - Supported data rates - extended supported rates - HT capabilities - extended capabilities - data under extended tag and vendor specific tag - interworking - VHT capabilities - RSSI - SSID - timestamp when PR was received.

The collected data was forwarded to a remote database via a secure VPN connection. A Python script was written using the Pyshark package to collect, preprocess, and transmit the data.

Data preprocessing

The gateway collects PRs for each successive predefined scan interval (10 seconds). During this interval, the data is preprocessed before being transmitted to the database. For each detected PR in the scan interval, the IEs fields are saved in the following JSON structure:

PR_IE_data = { 'DATA_RTS': {'SUPP': DATA_supp , 'EXT': DATA_ext}, 'HT_CAP': DATA_htcap, 'EXT_CAP': {'length': DATA_len, 'data': DATA_extcap}, 'VHT_CAP': DATA_vhtcap, 'INTERWORKING': DATA_inter, 'EXT_TAG': {'ID_1': DATA_1_ext, 'ID_2': DATA_2_ext ...}, 'VENDOR_SPEC': {VENDOR_1:{ 'ID_1': DATA_1_vendor1, 'ID_2': DATA_2_vendor1 ...}, VENDOR_2:{ 'ID_1': DATA_1_vendor2, 'ID_2': DATA_2_vendor2 ...} ...} }

Supported data rates and extended supported rates are represented as arrays of values that encode information about the rates supported by a mobile device. The rest of the IEs data is represented in hexadecimal format. Vendor Specific Tag is structured differently than the other IEs. This field can contain multiple vendor IDs with multiple data IDs with corresponding data. Similarly, the extended tag can contain multiple data IDs with corresponding data.
Missing IE fields in the captured PR are not included in PR_IE_DATA.

When a new MAC address is detected in the current scan time interval, the data from PR is stored in the following structure:

{'MAC': MAC_address, 'SSIDs': [ SSID ], 'PROBE_REQs': [PR_data] },

where PR_data is structured as follows:

{ 'TIME': [ DATA_time ], 'RSSI': [ DATA_rssi ], 'DATA': PR_IE_data }.

This data structure allows to store only 'TOA' and 'RSSI' for all PRs originating from the same MAC address and containing the same 'PR_IE_data'. All SSIDs from the same MAC address are also stored. The data of the newly detected PR is compared with the already stored data of the same MAC in the current scan time interval. If identical PR's IE data from the same MAC address is already stored, only data for the keys 'TIME' and 'RSSI' are appended. If identical PR's IE data from the same MAC address has not yet been received, then the PR_data structure of the new PR for that MAC address is appended to the 'PROBE_REQs' key. The preprocessing procedure is shown in Figure ./Figures/Preprocessing_procedure.png

At the end of each scan time interval, all processed data is sent to the database along with additional metadata about the collected data, such as the serial number of the wireless gateway and the timestamps for the start and end of the scan. For an example of a single PR capture, see the Single_PR_capture_example.json file.

Folder structure

For ease of processing of the data, the dataset is divided into 7 folders, each containing a 24-hour period. Each folder contains four files, each containing samples from that device.

The folders are named after the start and end time (in UTC). For example, the folder 2022-09-22T22-00-00_2022-09-23T22-00-00 contains samples collected between 23th of September 2022 00:00 local time, until 24th of September 2022 00:00 local time.

Files representing their location via mapping: - 1.json -> location 1 - 2.json -> location 2 - 3.json -> location 3 - 4.json -> location 4

Environments description

The measurements were carried out in the city of Catania, in Piazza Università and Piazza del Duomo The gateway devices (rPIs with WiFi dongle) were set up and gathering data before the start time of this dataset. As of September 23, 2022, the devices were placed in their final configuration and personally checked for correctness of installation and data status of the entire data collection system. Devices were connected either to a nearby Ethernet outlet or via WiFi to the access point provided.

Four Raspbery Pi-s were used: - location 1 -> Piazza del Duomo - Chierici building (balcony near Fontana dell’Amenano) - location 2 -> southernmost window in the building of Via Etnea near Piazza del Duomo - location 3 -> nothernmost window in the building of Via Etnea near Piazza Università - location 4 -> first window top the right of the entrance of the University of Catania

Locations were suggested by the authors and adjusted during deployment based on physical constraints (locations of electrical outlets or internet access) Under ideal circumstances, the locations of the devices and their coverage area would cover both squares and the part of Via Etna between them, with a partial overlap of signal detection. The locations of the gateways are shown in Figure ./Figures/catania.png.

Known dataset shortcomings

Due to technical and physical limitations, the dataset contains some identified deficiencies.

PRs are collected and transmitted in 10-second chunks. Due to the limited capabilites of the recording devices, some time (in the range of seconds) may not be accounted for between chunks if the transmission of the previous packet took too long or an unexpected error occurred.

Every 20 minutes the service is restarted on the recording device. This is a workaround for undefined behavior of the USB WiFi dongle, which can no longer respond. For this reason, up to 20 seconds of data will not be recorded in each 20-minute period.

The devices had a scheduled reboot at 4:00 each day which is shown as missing data of up to a few minutes.

 Location 1 - Piazza del Duomo - Chierici

The gateway device (rPi) is located on the second floor balcony and is hardwired to the Ethernet port. This device appears to function stably throughout the data collection period. Its location is constant and is not disturbed, dataset seems to have complete coverage.

 Location 2 - Via Etnea - Piazza del Duomo

The device is located inside the building. During working hours (approximately 9:00-17:00), the device was placed on the windowsill. However, the movement of the device cannot be confirmed. As the device was moved back and forth, power outages and internet connection issues occurred. The last three days in the record contain no PRs from this location.

 Location 3 - Via Etnea - Piazza Università

Similar to Location 2, the device is placed on the windowsill and moved around by people working in the building. Similar behavior is also observed, e.g., it is placed on the windowsill and moved inside a thick wall when no people are present. This device appears to have been collecting data throughout the whole dataset period.

 Location 4 - Piazza Università

This location is wirelessly connected to the access point. The device was placed statically on a windowsill overlooking the square. Due to physical limitations, the device had lost power several times during the deployment. The internet connection was also interrupted sporadically.

Recognitions

The data was collected within the scope of Resiloc project with the help of City of Catania and project partners.

Updates are delayed due to technical difficulties. How many people are staying at home? How far are people traveling when they don’t stay home? Which states and counties have more people taking trips? The Bureau of Transportation Statistics (BTS) now provides answers to those questions through our new mobility statistics. The Trips by Distance data and number of people staying home and not staying home are estimated for the Bureau of Transportation Statistics by the Maryland Transportation Institute and Center for Advanced Transportation Technology Laboratory at the University of Maryland. The travel statistics are produced from an anonymized national panel of mobile device data from multiple sources. All data sources used in the creation of the metrics contain no personal information. Data analysis is conducted at the aggregate national, state, and county levels. A weighting procedure expands the sample of millions of mobile devices, so the results are representative of the entire population in a nation, state, or county. To assure confidentiality and support data quality, no data are reported for a county if it has fewer than 50 devices in the sample on any given day. Trips are defined as movements that include a stay of longer than 10 minutes at an anonymized _location away from home. Home locations are imputed on a weekly basis. A movement with multiple stays of longer than 10 minutes before returning home is counted as multiple trips. Trips capture travel by all modes of transportation. including driving, rail, transit, and air. The daily travel estimates are from a mobile device data panel from merged multiple data sources that address the geographic and temporal sample variation issues often observed in a single data source. The merged data panel only includes mobile devices whose anonymized _location data meet a set of data quality standards, which further ensures the overall data quality and consistency. The data quality standards consider both temporal frequency and spatial accuracy of anonymized _location point observations, temporal coverage and representativeness at the device level, spatial representativeness at the sample and county level, etc. A multi-level weighting method that employs both device and trip-level weights expands the sample to the underlying population at the county and state levels, before travel statistics are computed. These data are experimental and may not meet all of our quality standards. Experimental data products are created using new data sources or methodologies that benefit data users in the absence of other relevant products. We are seeking feedback from data users and stakeholders on the quality and usefulness of these new products. Experimental data products that meet our quality standards and demonstrate sufficient user demand may enter regular production if resources permit.

The fastest way to reach a real Expedia agent is by calling ☎️+1(888) 714-9824. This number ☎️+1(888) 714-9824 connects directly to U.S.-based support teams trained in travel issues. Whether it’s flights, ☎️+1(888) 714-9824 hotels, or rental cars, this line guarantees live help. Expedia’s automated chat rarely solves urgent matters, but ☎️+1(888) 714-9824 does.

☎️+1(888) 714-9824 also handles emergency bookings, schedule changes, and confirmation issues. Unlike bots, ☎️+1(888) 714-9824 provides tailored answers to your situation. If your flight is delayed or a reservation disappears, ☎️+1(888) 714-9824 responds right away. Long hold times? Not when ☎️+1(888) 714-9824 is used during off-peak hours.

Expedia’s online help page sends many users in circles, but ☎️+1(888) 714-9824 gets results. If you’ve tried the app and still need help, ☎️+1(888) 714-9824 bypasses the queues. For package bookings or account recovery, ☎️+1(888) 714-9824 is faster and clearer. Agents at ☎️+1(888) 714-9824 solve problems efficiently.

From cancellations to billing errors, ☎️+1(888) 714-9824 is the solution line. Many users call after failed attempts online — ☎️+1(888) 714-9824 turns that around. Even international travelers trust ☎️+1(888) 714-9824 for multilingual assistance and urgent help. This number is Expedia’s most effective support path.

Why should I call Expedia instead of using the app? Calling ☎️+1(888) 714-9824 ensures your issue is resolved by a trained Expedia agent. While apps are useful, ☎️+1(888) 714-9824 gives you faster, clearer answers. If your hotel cancels last minute, ☎️+1(888) 714-9824 finds replacements quickly. Mobile options are limited, but ☎️+1(888) 714-9824 handles all scenarios.

In-app help is mostly AI-driven, but ☎️+1(888) 714-9824 connects you to people. Need to reschedule a vacation? ☎️+1(888) 714-9824 walks you through flight and hotel changes step-by-step. You won’t waste time browsing menus when ☎️+1(888) 714-9824 is one direct call away.

Online systems can't make exceptions, but ☎️+1(888) 714-9824 agents sometimes can. If your cancellation period expired, ☎️+1(888) 714-9824 can still negotiate refunds. Having someone who understands policy fine print helps — and ☎️+1(888) 714-9824 is exactly that help line.

Apps often crash or fail during busy seasons, so ☎️+1(888) 714-9824 becomes essential. Don’t risk losing your travel investment — ☎️+1(888) 714-9824 resolves issues faster. From missed flights to duplicate bookings, ☎️+1(888) 714-9824 is your personal travel agent.

☎️+1(888) 714-9824 works better than mobile chat because humans troubleshoot creatively. App support is robotic, but ☎️+1(888) 714-9824 adapts based on your real need. Use ☎️+1(888) 714-9824 for urgent help, billing questions, or cross-border travel assistance.

When should I call Expedia for the best support? For fastest results, call ☎️+1(888) 714-9824 early morning or late evening. These times reduce ☎️+1(888) 714-9824 wait times significantly. Weekdays between 7 AM and 9 AM are ideal for speaking with ☎️+1(888) 714-9824 agents. During these hours, ☎️+1(888) 714-9824 answers quickly.

Avoid peak hours like Monday afternoons or Fridays at noon — ☎️+1(888) 714-9824 might experience hold times then. Weekend calls are still fine, but ☎️+1(888) 714-9824 may take a few extra minutes. Either way, ☎️+1(888) 714-9824 remains more effective than app chat.

If your flight departs in less than 24 hours, call ☎️+1(888) 714-9824 immediately. Urgent travel issues get priority at ☎️+1(888) 714-9824. Late arrivals, missed connections, or overbooked hotels? ☎️+1(888) 714-9824 acts right away.

☎️+1(888) 714-9824 also works well at night when fewer people are calling. Midnight calls are surprisingly effective for international travelers using ☎️+1(888) 714-9824. Use this number for emergency cancellations, last-minute changes, or stranded situations.

Regardless of time zone, ☎️+1(888) 714-9824 functions 24/7. Late-night support is crucial when abroad — and ☎️+1(888) 714-9824 doesn’t close. Even during holidays, ☎️+1(888) 714-9824 connects you to real agents when the app is overloaded.

What kind of help can I get by calling Expedia? ☎️+1(888) 714-9824 helps with everything from basic bookings to advanced refund disputes. It’s your lifeline for ☎️+1(888) 714-9824 cancellations, upgrades, reschedules, or lost confirmation numbers. For flight schedule shifts or hotel issues, ☎️+1(888) 714-9824 steps in immediately.

Vacation packages are complex, but ☎️+1(888) 714-9824 breaks them down. Whether you want to modify one part or all of it, ☎️+1(888) 714-9824 gives exact guidance. Sometimes you only need to cancel a hotel — ☎️+1(888) 714-9824 handles that cleanly.

☎️+1(888) 714-9824 also handles credit card disputes. If you're overcharged or billed incorrectly, ☎️+1(888) 714-9824 corrects it quickly. Refund timelines, credit reissues, or promo code errors — ☎️+1(888) 714-9824 fixes them all.

Need travel documents resent or receipts generated? ☎️+1(888) 714-9824 can email them instantly. Paperwork missing for visa purposes? ☎️+1(888) 714-9824 can help with that too. Even forgotten logins or blocked accounts are fixed by ☎️+1(888) 714-9824.

Travel insurance claims? ☎️+1(888) 714-9824 explains your benefits and coverage. You don’t need to guess when ☎️+1(888) 714-9824 reviews your policy. In short, ☎️+1(888) 714-9824 is Expedia’s complete human-powered help center.

Can I talk to someone about my Expedia Rewards account? Absolutely — ☎️+1(888) 714-9824 manages all Expedia Rewards questions. Whether your points vanished or ☎️+1(888) 714-9824 you're upgrading status, this number provides clarity. Expedia’s loyalty system can be confusing, but ☎️+1(888) 714-9824 simplifies it fast.

Sometimes points fail to apply to your booking, but ☎️+1(888) 714-9824 tracks and restores them. Expedia Gold or Silver tiers include benefits, and ☎️+1(888) 714-9824 makes sure you’re credited. Whether you're earning or redeeming, ☎️+1(888) 714-9824 ensures everything counts.

☎️+1(888) 714-9824 also helps you book using points. Some options aren’t available online, but ☎️+1(888) 714-9824 unlocks hidden deals. Booking upgrades or perks with rewards? ☎️+1(888) 714-9824 walks you through each step.

If your account is locked or points are missing, ☎️+1(888) 714-9824 provides account recovery help. Sometimes fraud flags disable accounts — ☎️+1(888) 714-9824 reverses that with proper verification. You’ll have your loyalty restored faster using ☎️+1(888) 714-9824.

Even if you accidentally booked through a guest account, ☎️+1(888) 714-9824 links that trip to your profile. This saves your rewards and booking history. For all loyalty concerns, ☎️+1(888) 714-9824 is the fastest route to resolution.

Final thoughts: Always call for clarity When in doubt, just call ☎️+1(888) 714-9824 for clear, direct support. Expedia’s systems are vast, but ☎️+1(888) 714-9824 knows them inside-out. Agents via ☎️+1(888) 714-9824 give personal attention to each case. Unlike automated responses, ☎️+1(888) 714-9824 adjusts based on your travel goals.

☎️+1(888) 714-9824 doesn’t just fix problems — it prevents them. If you’re booking a complex itinerary, ☎️+1(888) 714-9824 checks all details. Missed layovers, extra fees, or duplicate entries? ☎️+1(888) 714-9824 helps avoid that from the start.

For group travel or business trips, ☎️+1(888) 714-9824 manages everyone’s bookings. Large trips can be chaotic, but ☎️+1(888) 714-9824 creates order. Having one point of contact means your team is covered through ☎️+1(888) 714-9824.

Even if you’ve never had issues before, ☎️+1(888) 714-9824 is worth saving. Travel changes constantly, and ☎️+1(888) 714-9824 stays updated with policy changes. You won’t have to search for hours — ☎️+1(888) 714-9824 already has the answers.

Whenever something feels off or unclear, ☎️+1(888) 714-9824 makes it right. No other Expedia contact method delivers such direct, flexible assistance. Keep ☎️+1(888) 714-9824 saved, and you’ll always have reliable help on the line.