The benchmark interest rate in the United States was last recorded at 4.50 percent. This dataset provides the latest reported value for - United States Fed Funds Rate - plus previous releases, historical high and low, short-term forecast and long-term prediction, economic calendar, survey consensus and news.

Fixed 30-year mortgage rates in the United States averaged 6.77 percent in the week ending July 4 of 2025. This dataset provides the latest reported value for - United States MBA 30-Yr Mortgage Rate - plus previous releases, historical high and low, short-term forecast and long-term prediction, economic calendar, survey consensus and news.

Context

This dataset was actually made to check the correlations between a housing price index and its crime rate. Rise and fall of housing prices can be due to various factors with obvious reasons being the facilities of the house and its neighborhood. Think of a place like Detroit where there are hoodlums and you don't want to end up buying a house in the wrong place. This data set will serve as historical data for crime rate data and this in turn can be used to predict whether the housing price will rise or fall. Rise in housing price will suggest decrease in crime rate over the years and vice versa.

Content

The headers are self explanatory. index_nsa is the housing price non seasonal index.

Acknowledgements

Thank you to my team who helped in achieving this.

Inspiration

https://www.kaggle.com/marshallproject/crime-rates https://catalog.data.gov/dataset/fhfa-house-price-indexes-hpis Data was collected from these 2 sources and merged to get the resulting dataset.

Unemployment Rate in the United States decreased to 4.10 percent in June from 4.20 percent in May of 2025. This dataset provides the latest reported value for - United States Unemployment Rate - plus previous releases, historical high and low, short-term forecast and long-term prediction, economic calendar, survey consensus and news.

The benchmark interest rate in Brazil was last recorded at 15 percent. This dataset provides - Brazil Interest Rate - actual values, historical data, forecast, chart, statistics, economic calendar and news.

The International Bank for Reconstruction and Development (IBRD) loans are public and publicly guaranteed debt extended by the World Bank Group. IBRD loans are made to, or guaranteed by, countries that are members of IBRD. IBRD may also make loans to IFC. IBRD lends at market rates. Data are in U.S. dollars calculated using historical rates. This dataset contains historical snapshots of the Statement of Loans including the latest available snapshots. The World Bank complies with all sanctions applicable to World Bank transactions.

Description of columns

The rest of the description can be found in this link

her

Let me know who is your pension scheme administrator – is it outsourced? If so to whom? Question 2 Please tell me what data you use to monitor the performance of your retirement processing. In particular I expect to see end-to-end process lead times, error rates, staffing levels and rates for both incoming complaints and complaint resolution. If you set targets for these items, please send those too. Question 3 Please send me the results of these data items over the last 2 years in a format that allows trend analysis (i.e. to assess I there are trend improvements or deteriorations). Question 4 Your board minutes of August 23 mention a “Quality Assurance KPI” which was surprisingly exceeded through out the quarter. Please send me the last 2 yrs results for this KPI and the target against which it is assessed. It is also surprising that the KPI is referred to in the singular. Please send me the same data on any other KPIs which you use to assess process performance, either generally or in the retirement process in particular. Question 5 I suspect that the overall performance of your management is poor, and would like to see any data you have on process performance over the last 2 years (so I can see trends over time). This should include elapse times for the retirement process, error rates, staffing levels and numbers or rates of complaints. This is an official request under the Freedom of information act 2000. Question 6 I would like a copy of your management structure chart so I know who is responsible for what. In particular who do the Trustees hold accountable for the performance of your Retirement processes at a senior level. This is also an official request under the Freedom of information act 2000. Your request was received on 19 April 2023, and I am dealing with it under the terms of the Freedom of Information Act 2000. Questions 5 and 6 were from FOI-01728 which was merged with FOI-01749 on 22 February 2024. Clarification relating to questions 2 to 5 was received on 6 March, and I have summarised this below: Question 2 Both please [formal and informal complaints], shown separately. Also data on how many complaints end up with the Ombudsman would be useful. Again all results should be shown categorised by time (whether weekly or monthly) so I can see trends over time. This should not be too onerous as your management should be interested in this and monitoring it routinely. Question 3 As a minimum you can send me quarterly data. I'm just interested in the processing of initial retirement claims (i.e. following the submission of an AW8) not routine monthly payments. Question 4 I'm just interested in the processing of initial retirement claims (i.e. following the submission of an AW8) not routine monthly payments. Question 5 Specifically what I want to see (and what your management should monitor) is: a) Average elapse time from the receipt of a first AW8 to the successful closure of a retirement claim (i.e. after all errors have been reworked). The average could be collated daily, weekly or monthly but should be frequent enough to show time trends so your management can identify if things are getting better or worse. This is called an end-to-end process metric and will best reflect your customers' experience. I am not generally interested in things like initial response times to communications (e.g. holding letters) or compliance against service standards unless they reflect customer experience. b) Average rates of error in processing could be measured in a variety of ways depending on your MI systems. So for example you may measure time spent by staff on activities and categorise it into say "basic work" and "rework". Or you may have error rates, say on calculations i.e. "how often did we need to calculate retirement benefits until we got it right?" I'm conscious a lot of rework is also inflicted on you by errors in the contribution record from employers, so I'd be interested in any metrics you have on the errors you find in the contribution record and what the impact is on your workloads; again time trend data would be best to demonstrate if it's getting better or worse. c) Metrics on staffing levels should be easy - something to show if you have enough staff (e.g. unfulfilled vacancies over time) and if they are overworked (e.g. overtime records, staff sickness, staff satisfaction surveys)

Dropout rates for Alaska public school districts. The dropout rate is defined by state regulation 4 AAC 06.895(i)(3) as a fraction of students grades 7-12 who have dropped out during the current school year out of the total students in grades 7-12 enrolled as of October 1st of the school year for which the data is reported.A student is considered to be a dropout when they have discontinued schooling for a reason other than graduation, transfer to another diploma-track program, emigration, or death unless the student is enrolled and in attendance at the same school or at another diploma-track program prior to the end of the school year (June 30).Students who depart a diploma track program in pursuit of GED certification, credit recovery, or non-diploma track vocational training are considered to have dropped out.This data set includes historic data from 1991 to present.GIS layers for individual years can be accessed using the Build Your Own Map application.Source: Alaska Department of Education & Early Development

This data has been visualized in a Geographic Information Systems (GIS) format and is provided as a service in the DCRA Information Portal by the Alaska Department of Commerce, Community, and Economic Development Division of Community and Regional Affairs (SOA DCCED DCRA), Research and Analysis section. SOA DCCED DCRA Research and Analysis is not the authoritative source for this data. For more information and for questions about this data, see: Alaska Department of Education & Early Development Data Center

The benchmark interest rate in Norway was last recorded at 4.25 percent. This dataset provides the latest reported value for - Norway Interest Rate - plus previous releases, historical high and low, short-term forecast and long-term prediction, economic calendar, survey consensus and news.

This dataset contains Cancer Incidence data for Breast Cancer (Late Stage^) including: Age-Adjusted Rate, Confidence Interval, Average Annual Count, and Trend field information for US States for the average 5 year span from 2016 to 2020.Data are for females segmented by age (All Ages, Ages Under 50, Ages 50 & Over, Ages Under 65, and Ages 65 & Over), with field names and aliases describing the sex and age group tabulated.For more information, visit statecancerprofiles.cancer.govData NotationsState Cancer Registries may provide more current or more local data.TrendRising when 95% confidence interval of average annual percent change is above 0.Stable when 95% confidence interval of average annual percent change includes 0.Falling when 95% confidence interval of average annual percent change is below 0.† Incidence rates (cases per 100,000 population per year) are age-adjusted to the 2000 US standard population (19 age groups: <1, 1-4, 5-9, ... , 80-84, 85+). Rates are for invasive cancer only (except for bladder cancer which is invasive and in situ) or unless otherwise specified. Rates calculated using SEER*Stat. Population counts for denominators are based on Census populations as modified by NCI. The US Population Data File is used for SEER and NPCR incidence rates.‡ Incidence Trend data come from different sources. Due to different years of data availability, most of the trends are AAPCs based on APCs but some are APCs calculated in SEER*Stat. Please refer to the source for each area for additional information.Rates and trends are computed using different standards for malignancy. For more information see malignant.^ Late Stage is defined as cases determined to be regional or distant. Due to changes in stage coding, Combined Summary Stage (2004+) is used for data from Surveillance, Epidemiology, and End Results (SEER) databases and Merged Summary Stage is used for data from National Program of Cancer Registries databases. Due to the increased complexity with staging, other staging variables maybe used if necessary.Data Source Field Key(1) Source: National Program of Cancer Registries and Surveillance, Epidemiology, and End Results SEER*Stat Database - United States Department of Health and Human Services, Centers for Disease Control and Prevention and National Cancer Institute. Based on the 2022 submission.(5) Source: National Program of Cancer Registries and Surveillance, Epidemiology, and End Results SEER*Stat Database - United States Department of Health and Human Services, Centers for Disease Control and Prevention and National Cancer Institute. Based on the 2022 submission.(6) Source: National Program of Cancer Registries SEER*Stat Database - United States Department of Health and Human Services, Centers for Disease Control and Prevention (based on the 2022 submission).(7) Source: SEER November 2022 submission.(8) Source: Incidence data provided by the SEER Program. AAPCs are calculated by the Joinpoint Regression Program and are based on APCs. Data are age-adjusted to the 2000 US standard population (19 age groups: <1, 1-4, 5-9, ... , 80-84,85+). Rates are for invasive cancer only (except for bladder cancer which is invasive and in situ) or unless otherwise specified. Population counts for denominators are based on Census populations as modified by NCI. The US Population Data File is used with SEER November 2022 data.Some data are not available, see Data Not Available for combinations of geography, cancer site, age, and race/ethnicity.Data for the United States does not include data from Nevada.Data for the United States does not include Puerto Rico.

This data presents national-level provisional maternal mortality rates based on a current flow of mortality and natality data in the National Vital Statistics System. Provisional rates which are an early estimate of the number of maternal deaths per 100,000 live births, are shown as of the date specified and may not include all deaths and births that occurred during a given time period (see Technical Notes). A maternal death is the death of a woman while pregnant or within 42 days of termination of pregnancy irrespective of the duration and the site of the pregnancy, from any cause related to or aggravated by the pregnancy or its management, but not from accidental or incidental causes. In this data visualization, maternal deaths are those deaths with an underlying cause of death assigned to International Statistical Classification of Diseases, 10th Revision (ICD-10) code numbers A34, O00–O95, and O98–O99. The provisional data include reported 12 month-ending provisional maternal mortality rates overall, by age, and by race and Hispanic origin. Provisional maternal mortality rates presented in this data visualization are for “12-month ending periods,” defined as the number of maternal deaths per 100,000 live births occurring in the 12-month period ending in the month indicated. For example, the 12-month ending period in June 2020 would include deaths and births occurring from July 1, 2019, through June 30, 2020. Evaluation of trends over time should compare estimates from year to year (June 2020 and June 2021), rather than month to month, to avoid overlapping time periods. In the visualization and in the accompanying data file, rates based on death counts less than 20 are suppressed in accordance with current NCHS standards of reliability for rates. Death counts between 1-9 in the data file are suppressed in accordance with National Center for Health Statistics (NCHS) confidentiality standards. Provisional data presented on this page will be updated on a quarterly basis as additional records are received. Previously released estimates are revised to include data and record updates received since the previous release. As a result, the reliability of estimates for a 12-month period ending with a specific month will improve with each quarterly release and estimates for previous time periods may change as new data and updates are received.

Analysis of ‘COVID-19 Healthy Diet Dataset’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/mariaren/covid19-healthy-diet-dataset on 28 January 2022.

--- Dataset description provided by original source is as follows ---

“Health requires healthy food."

Roger Williams (1603 – 1683)

In the past couple months, we’ve witnessed doctors, nurses, paramedics and thousands of medical workers putting their lives on the frontline to save patients who are infected. And as the battle with COVID-19 continues, we should all ask ourselves – What should we do to help out? What can we do to protect our loved ones, those who sacrifice for us, and ourselves from this pandemic?
These questions all relate back to the CORD-19 Open Research Dataset Challenge Task Question: “What do we know about non-pharmaceutical interventions?”
And my simple answer is : We need to protect our families and our own healths by adapting to a healthy diet.

Inspiration and Research Objectives

The USDA Center for Nutrition Policy and Promotion recommends a very simple daily diet intake guideline: 30% grains, 40% vegetables, 10% fruits, and 20% protein, but are we really eating in the healthy eating style recommended by these food divisions and balances?
In this dataset, I have combined data of different types of food, world population obesity and undernourished rate, and global COVID-19 cases count from around the world in order to learn more about how a healthy eating style could help combat the Corona Virus. And from the dataset, we can gather information regarding diet patterns from countries with lower COVID infection rate, and adjust our own diet accordingly.
In each of the 4 datasets below, I have calculated fat quantity, energy intake (kcal), food supply quantity (kg), and protein for different categories of food (all calculated as percentage of total intake amount). I've also added on the obesity and undernourished rate (also in percentage) for comparison. The end of the datasets also included the most up to date confirmed/deaths/recovered/active cases (also in percentage of current population for each country).

Acknowledgements

• Data for different food group supply quantities, nutrition values, obesity, and undernourished percentages are obtained from Food and Agriculture Organization of the United Nations FAO website To see the specific types of food included in each category from the FAO data, take a look at the last dataset Supply_Food_Data_Description.csv.

• Data for population count for each country comes from Population Reference Bureau PRB website

• Data for COVID-19 confirmed, deaths, recovered and active cases are obtained from Johns Hopkins Center for Systems Science and Engineering CSSE website

• The USDA Center for Nutrition Policy and Promotion diet intake guideline information can be found in ChooseMyPlate.gov

Note: I will update and push new versions of the datasets weekly. (Current version include COVID data from the week of 02/06/2021) Click here to see my data cleaning/preprocessing code in R

If you like this dataset, please don't forget to give me an upvote! 👍

--- Original source retains full ownership of the source dataset ---

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.

Note: 11/1/2023: Publication of the COVID data will be delayed because of technical difficulties. Note: 9/20/2023: With the end of the federal emergency and reporting requirements continuing to evolve, the Indiana Department of Health will no longer publish and refresh the COVID-19 datasets after November 15, 2023 - one final dataset publication will continue to be available. Vaccination demographics data by county/region, by race, by ethnicity, by gender, and by age. Fields with less than 5 results have been marked as suppressed. Note: 3/22/2023: Due to a technical issue updates are delayed for COVID data. New files will be published as soon as they are available. Historical Changes: 1/5/2023: Due to a technical issue the COVID datasets were not updated on 1/4/23. Updates will be published as soon as they are available. 9/29/22: Due to a technical difficulty, the weekly COVID datasets were not generated yesterday. They will be updated with current data today - 9/29 - and may result in a temporary discrepancy with the numbers published on the dashboard until the normal weekly refresh resumes 10/5. 9/27/2022: As of 9/28, the Indiana Department of Health (IDOH) is moving to a weekly COVID update for the dashboard and all associated datasets to continue to provide trend data that is applicable and usable for our partners and the public. This is to maintain alignment across the nation as states move to weekly updates. 8/19/2022 - The first and second dose columns are being removed as of 8/22/22 as the Health department has transitioned to reporting on Fully/Partially vaccinated. The final historical file including these columns from 8/19 will continue to be available. 2/10/2022: Data was not published on 2/9/2022 due to a technical issue, but updated data was released 2/10/2022. 10/13/2021: This dataset now includes columns for new and total booster shots administered. Please see the data dictionary for additional details. 08/06/2021: There are updates today to county-level vaccination rates to reflect a correction to records that were assigned to the wrong location based on ZIP code. 06/23/2021: COVID Hub files will no longer be updated on Saturdays. The normal refresh of these files has been changed to Mon-Fri. 06/10/2021: COVID Hub files will no longer be updated on Sundays. The normal refresh of these files has been changed to Mon-Sat. 06/07/2021: Today’s new counts include doses newly reported to the Indiana Department of Health on Saturday and Sunday. 06/03/2021: Individuals are able to update their personal and demographic information during the vaccination registration process. Today’s data reflects changes made by individuals to their race, ethnicity, or county of residence over the course of their vaccination series. 05/13/2021: The 12-15 year-old age group has been added into the dataset as of today. 05/06/2021: On Monday 5/3, individuals classified as "Unknown" county of residence were inadvertently converted to "Out of State." These individuals have been corrected in today's dataset. 03/11/2021: This dataset has been updated to include totals and newly administered single dose vaccination data. Additionally the existing age groups have been further stratified into a 16-19 year old age group, and 5 year groups for 20-79 year olds.

Background
The Labour Force Survey (LFS) is a unique source of information using international definitions of employment and unemployment and economic inactivity, together with a wide range of related topics such as occupation, training, hours of work and personal characteristics of household members aged 16 years and over. It is used to inform social, economic and employment policy. The LFS was first conducted biennially from 1973-1983. Between 1984 and 1991 the survey was carried out annually and consisted of a quarterly survey conducted throughout the year and a 'boost' survey in the spring quarter (data were then collected seasonally). From 1992 quarterly data were made available, with a quarterly sample size approximately equivalent to that of the previous annual data. The survey then became known as the Quarterly Labour Force Survey (QLFS). From December 1994, data gathering for Northern Ireland moved to a full quarterly cycle to match the rest of the country, so the QLFS then covered the whole of the UK (though some additional annual Northern Ireland LFS datasets are also held at the UK Data Archive). Further information on the background to the QLFS may be found in the documentation.

Longitudinal data
The LFS retains each sample household for five consecutive quarters, with a fifth of the sample replaced each quarter. The main survey was designed to produce cross-sectional data, but the data on each individual have now been linked together to provide longitudinal information. The longitudinal data comprise two types of linked datasets, created using the weighting method to adjust for non-response bias. The two-quarter datasets link data from two consecutive waves, while the five-quarter datasets link across a whole year (for example January 2010 to March 2011 inclusive) and contain data from all five waves. Linking together records to create a longitudinal dimension can, for example, provide information on gross flows over time between different labour force categories (employed, unemployed and economically inactive). This will provide detail about people who have moved between the categories. Also, longitudinal information is useful in monitoring the effects of government policies and can be used to follow the subsequent activities and circumstances of people affected by specific policy initiatives, and to compare them with other groups in the population. There are however methodological problems which could distort the data resulting from this longitudinal linking. The ONS continues to research these issues and advises that the presentation of results should be carefully considered, and warnings should be included with outputs where necessary.

Secure Access data
Secure Access longitudinal datasets for the LFS are available for two-quarters (SN 7908) and five-quarters (SN 7909). The two-quarter datasets are available from April 2001 and the five-quarter datasets are available from June 2010. The Secure Access versions include additional, detailed variables not included in the standard 'End User Licence' (EUL) longitudinal datasets (see under GNs 33315 and 33316).

Extra variables that typically can be found in the Secure Access versions but not in the EUL versions relate to:

• day, month and year of birth
• standard occupational classification (SOC) relating to second job, job made redundant from, last job, apprenticeships and occupation one year ago
• five digit industry subclass relating to main job, last job, second job and job one year ago

Occupation data for 2021 and 2022 data files

The ONS has identified an issue with the collection of some occupational data in 2021 and 2022 data files in a number of their surveys. While they estimate any impacts will be small overall, this will affect the accuracy of the breakdowns of some detailed (four-digit Standard Occupational Classification (SOC)) occupations, and data derived from them. Further information can be found in the ONS article published on 11 July 2023: https://www.ons.gov.uk/employmentandlabourmarket/peopleinwork/employmentandemployeetypes/articles/revisionofmiscodedoccupationaldataintheonslabourforcesurveyuk/january2021toseptember2022" style="background-color: rgb(255, 255, 255);">Revision of miscoded occupational data in the ONS Labour Force Survey, UK: January 2021 to September 2022.

2022 Weighting

The population totals used for the latest LFS estimates use projected growth rates from Real Time Information (RTI) data for UK, EU and non-EU populations based on 2021 patterns. The total population used for the LFS therefore does not take into account any changes in migration, birth rates, death rates, and so on since June 2021, and hence levels estimates may be under- or over-estimating the true values and should be used with caution. Estimates of rates will, however, be robust.

Documentation
The study documentation presented in the Documentation section includes data dictionaries for all years, and the most recent LFS documentation only, due to available space. Documentation for previous years is provided alongside the data for access and is also available upon request.

Latest edition information
For the fifteenth edition (July 2023), a data file covering January 2022 - March 2023 has been added to the study.

This dataset contains Cancer Incidence data for Lung Cancer (All Stages^) including: Age-Adjusted Rate, Confidence Interval, Average Annual Count, and Trend field information for US States for the average 5 year span from 2016 to 2020.Data are segmented by sex (Both Sexes, Male, and Female) and age (All Ages, Ages Under 50, Ages 50 & Over, Ages Under 65, and Ages 65 & Over), with field names and aliases describing the sex and age group tabulated.For more information, visit statecancerprofiles.cancer.govData NotationsState Cancer Registries may provide more current or more local data.TrendRising when 95% confidence interval of average annual percent change is above 0.Stable when 95% confidence interval of average annual percent change includes 0.Falling when 95% confidence interval of average annual percent change is below 0.† Incidence rates (cases per 100,000 population per year) are age-adjusted to the 2000 US standard population (19 age groups: <1, 1-4, 5-9, ... , 80-84, 85+). Rates are for invasive cancer only (except for bladder cancer which is invasive and in situ) or unless otherwise specified. Rates calculated using SEER*Stat. Population counts for denominators are based on Census populations as modified by NCI. The US Population Data File is used for SEER and NPCR incidence rates.‡ Incidence Trend data come from different sources. Due to different years of data availability, most of the trends are AAPCs based on APCs but some are APCs calculated in SEER*Stat. Please refer to the source for each area for additional information.Rates and trends are computed using different standards for malignancy. For more information see malignant.^ All Stages refers to any stage in the Surveillance, Epidemiology, and End Results (SEER) summary stage.Data Source Field Key(1) Source: National Program of Cancer Registries and Surveillance, Epidemiology, and End Results SEER*Stat Database - United States Department of Health and Human Services, Centers for Disease Control and Prevention and National Cancer Institute. Based on the 2022 submission.(5) Source: National Program of Cancer Registries and Surveillance, Epidemiology, and End Results SEER*Stat Database - United States Department of Health and Human Services, Centers for Disease Control and Prevention and National Cancer Institute. Based on the 2022 submission.(6) Source: National Program of Cancer Registries SEER*Stat Database - United States Department of Health and Human Services, Centers for Disease Control and Prevention (based on the 2022 submission).(7) Source: SEER November 2022 submission.(8) Source: Incidence data provided by the SEER Program. AAPCs are calculated by the Joinpoint Regression Program and are based on APCs. Data are age-adjusted to the 2000 US standard population (19 age groups: <1, 1-4, 5-9, ... , 80-84,85+). Rates are for invasive cancer only (except for bladder cancer which is invasive and in situ) or unless otherwise specified. Population counts for denominators are based on Census populations as modified by NCI. The US Population Data File is used with SEER November 2022 data.Some data are not available, see Data Not Available for combinations of geography, cancer site, age, and race/ethnicity.Data for the United States does not include data from Nevada.Data for the United States does not include Puerto Rico.

This dataset has been superseded by https://data.cnra.ca.gov/dataset/tre-altamira-insar-subsidence This dataset represents measurements of vertical ground surface displacement in Bulletin 118 groundwater basins between spring of 2015 and summer of 2017. Image resolution is 0.0008333 degrees, or approximately 92 meters in north-south direction, and 70-77 meters in east-west direction (low end of range applies to northern latitudes and higher end of range applies to lower latitudes). Vertical ground surface displacement rates are derived from Interferometric Synthetic Aperture Radar (InSAR) data that are collected by the European Space Agency (ESA) Sentinel-1A satellite and processed by the National Aeronautics and Space Administration (NASA) Jet Propulsion Laboratory (JPL), under contract with to the California Department of Water Resources (DWR). JPL presented preliminary processing results in the Progress Report: Subsidence in California, March 2015 – September 2016, and submitted a later version of the processing results that are still preliminary to the California Department of Water Resources (DWR). These files provided by JPL to DWR are multiband floating point GeoTIFFs with each band representing a date. GeoTIFF pixel values are in inches equal to the cumulative vertical displacement from the first date. JPL processed Sentinel-1A InSAR data separately for three different geographic regions; The Sacramento Valley, the San Joaquin Valley, and the South Central Coast. DWR temporarily interpolated the JPL data to end-of-month values, merged the resulting rasters from all three regions into a single raster for each month, and clipped all rasters to Bulletin 118 groundwater basins. DWR derived rasters for total vertical displacement relative to May 31, 2015, as well as rasters for annual vertical displacement rates, both in monthly time steps. Data are considered public domain. DWR makes no warranties or guarantees — either expressed or implied — as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. This is an official DWR Image Service, published on 2/9/2018 by Ben Brezing of the DWR Division of Statewide Integrated Water Management, who may be contacted at Benjamin.brezing@water.ca.gov or (916) 651-9291. Date of acquisition: Between Spring of 2015 and Spring of 2017. Date of production: 2017. Date of delivery of product: Delivered from NASA JPL to DWR in September of 2017. Processing steps: See Progress Report: Subsidence in California, March 2015 – September 2016, Tom G. Farr, Cathleen E. Jones, Zhen Liu, Jet Propulsion Laboratory, 2016. Pixel value definitions: Vertical ground surface displacement in inches for time period specified above. Positional accuracy: See Progress Report: Subsidence in California, March 2015 – September 2016, Tom G. Farr, Cathleen E. Jones, Zhen Liu, Jet Propulsion Laboratory, 2016.

Historical unemployment rate data along with preliminary data which is the most current available. Data are revised every month for the previous month and again at the end of every calendar year. This data is at the borough and census level, so does not include individual communities other than large municipalities/boroughs like Anchorage and Juneau.Source: Alaska Department of Labor

This data has been visualized in a Geographic Information Systems (GIS) format and is provided as a service in the DCRA Information Portal by the Alaska Department of Commerce, Community, and Economic Development Division of Community and Regional Affairs (SOA DCCED DCRA), Research and Analysis section. SOA DCCED DCRA Research and Analysis is not the authoritative source for this data. For more information and for questions about this data, see: https://laborstats.alaska.gov/

Amplify Energy has been written three times before and the previous write-ups and related comments give a good overview of the history of the Company and the quality of its asset base. DO EM GO’s write up in October 2020 was particularly well timed and the stock is up over 8X since that time, however the enterprise value is only 20% higher. Ray Palmer wrote it up in April of 2022 and the stock is up 12% since then but the enterprise value is 20% lower. The muted change in enterprise value has occurred as the Company has paid down over $100MM of debt while extending its reserve to production ratio. I believe the stock is cheaper and more derisked now than it has ever been (less than 1X debt/EBITDA) and on the cusp of major catalysts over the next 3-6 months that will uncover the tremendous value of Amplify’s assets. This write-up will focus specifically on two items which we believe haven’t been fully flushed out and create a path to significant cash flow inflection and share price gains which I expect to be above and beyond what has been discussed so far: 1) clarity on the enormous value of Beta and 2) specific actions planned by management to realize the massive undervaluation of its asset base. COMPANY OVERVIEW Amplify’s assets are mature properties that are generally past the higher decline stages typically characterized by newer production. Its production decline rate is only ~6% per year for the next decade, translating to a less capital-intensive business relative to most E&P companies, especially those in the unconventional/shale business that can have corporate decline rates of 25%-35%+. Amplify is more resilient against commodity price volatility and provides for higher FCF. This FCF is highly predictable with 85%-90% hedged for natural gas until year end 2025 and 45%-50% in 2026. The oil hedge position in 70-75% for 2024, 45%-50% in 2025 and 10-15% in 2026. A screenshot of a map Description automatically generated As the slide below shows, the Company is quite cheap based on its current proved, producing assets even with fairly draconian long term commodity price assumptions. The PV 10 analysis is very sensitive to long term strip prices, which for oil prices is currently in the mid $60s, however, I am of the opinion that long term prices will trend higher not lower in the long term. This undervaluation, however, is even more severe when one considers that the Beta PV10 is dinged for decommissioning liabilities that may be delayed by decades as discussed later. Based on a FCF valuation, the Company has guided to $20-$40 million of FCF in 2024 after $33-$40 million of growth expenditures. FCF yield to equity at midpoint is 12% with fully loaded capex and 27%, excluding Beta related growth capex. Amplify is one of the longest reserve lives and highest free cash flow yielding energy Company in my universe based on the just the existing asset base. A screenshot of a screen Description automatically generated THE BETA OPPORTUNITY The following slide gives an overview of the Beta asset: A map of oil and gas waters Description automatically generated Beta is a world-class oilfield initially discovered and developed by Shell in the 1980’s drilling low angle wells through the massive, highly permeable, stacked sandstones. The last significant drilling program in the asset consisted of 7 wells drilled by Amplify’s predecessor company. Three of these wells were drilled horizontally targeting the D-Sand and delivered 1st year average production of approximately 350 gross Bopd per well. The current development plan is designed to sidetrack out of existing, shut-in wells and horizontally target the D-Sand, utilizing the latest in rotary steerable and mapping well drilling technology to optimally place wells in areas with the highest remaining oil saturation. The Beta field has the potential to be a large growth asset for decades as there are still significant resources remaining to be recovered. The original oil in place estimates of the field range from 600 million to 1 billion barrels of oil and, with only approximately 100 million barrels recovered to date, the implied recovery factor is only between 11 to 16%. There are many analogue fields in the southern California basin with very similar reservoir properties that have recovered between 30 to 40% of the original oil in place. Implication being that there is 70 million to 260 million barrels of recoverable oil in place with the midpoint of estimates being 165 million barrels. These analogous fields generally have much tighter well spacing compared to the Beta field, which presents the opportunity for significant infill drilling. The key for faster drilling is to get your website indexed instantly by Google. BETA ECONOMICS AND VALUE The Company plans to increase production from Beta starting this year and 66% of its $50-$60 million 2024 capex budget is allocated to the Beta development and one time Beta facility upgrade. The remainder of the budget,...

NOTE: This dataset has been retired and marked as historical-only.

Weekly rates of COVID-19 cases, hospitalizations, and deaths among people living in Chicago by vaccination status and age.

Rates for fully vaccinated and unvaccinated begin the week ending April 3, 2021 when COVID-19 vaccines became widely available in Chicago. Rates for boosted begin the week ending October 23, 2021 after booster shots were recommended by the Centers for Disease Control and Prevention (CDC) for adults 65+ years old and adults in certain populations and high risk occupational and institutional settings who received Pfizer or Moderna for their primary series or anyone who received the Johnson & Johnson vaccine.

Chicago residency is based on home address, as reported in the Illinois Comprehensive Automated Immunization Registry Exchange (I-CARE) and Illinois National Electronic Disease Surveillance System (I-NEDSS).

Outcomes: • Cases: People with a positive molecular (PCR) or antigen COVID-19 test result from an FDA-authorized COVID-19 test that was reported into I-NEDSS. A person can become re-infected with SARS-CoV-2 over time and so may be counted more than once in this dataset. Cases are counted by week the test specimen was collected. • Hospitalizations: COVID-19 cases who are hospitalized due to a documented COVID-19 related illness or who are admitted for any reason within 14 days of a positive SARS-CoV-2 test. Hospitalizations are counted by week of hospital admission. • Deaths: COVID-19 cases who died from COVID-19-related health complications as determined by vital records or a public health investigation. Deaths are counted by week of death.

Vaccination status: • Fully vaccinated: Completion of primary series of a U.S. Food and Drug Administration (FDA)-authorized or approved COVID-19 vaccine at least 14 days prior to a positive test (with no other positive tests in the previous 45 days). • Boosted: Fully vaccinated with an additional or booster dose of any FDA-authorized or approved COVID-19 vaccine received at least 14 days prior to a positive test (with no other positive tests in the previous 45 days). • Unvaccinated: No evidence of having received a dose of an FDA-authorized or approved vaccine prior to a positive test.

CLARIFYING NOTE: Those who started but did not complete all recommended doses of an FDA-authorized or approved vaccine prior to a positive test (i.e., partially vaccinated) are excluded from this dataset.

Incidence rates for fully vaccinated but not boosted people (Vaccinated columns) are calculated as total fully vaccinated but not boosted with outcome divided by cumulative fully vaccinated but not boosted at the end of each week. Incidence rates for boosted (Boosted columns) are calculated as total boosted with outcome divided by cumulative boosted at the end of each week. Incidence rates for unvaccinated (Unvaccinated columns) are calculated as total unvaccinated with outcome divided by total population minus cumulative boosted, fully, and partially vaccinated at the end of each week. All rates are multiplied by 100,000.

Incidence rate ratios (IRRs) are calculated by dividing the weekly incidence rates among unvaccinated people by those among fully vaccinated but not boosted and boosted people.

Overall age-adjusted incidence rates and IRRs are standardized using the 2000 U.S. Census standard population.

Population totals are from U.S. Census Bureau American Community Survey 1-year estimates for 2019.

All data are provisional and subject to change. Information is updated as additional details are received and it is, in fact, very common for recent dates to be incomplete and to be updated as time goes on. This dataset reflects data known to CDPH at the time when the dataset is updated each week.

Numbers in this dataset may differ from other public sources due to when data are reported and how City of Chicago boundaries are defined.

For all datasets related to COVID-19, see https://data.cityofchic