The dataset includes customer id,Martial Status,Gender,Income,Children,Education,Occupation,Home Owner,Cars,Commute Distance,Region,Age,Purchased Bike. Blog

This dataset contains a structured HR Analytics report for the year 2024–2025, prepared entirely in Microsoft Excel. It has been designed to help students, analysts, HR professionals, and data enthusiasts practice real-world HR analytics using clean and well-organized data.

The dataset covers key HR areas such as employee demographics, salary structure, performance scores, promotions, attendance, and attrition indicators. All data is synthetic and manually curated for educational and analytical purposes.

The main purpose of this dataset is to provide users with a practical Excel-based resource to:

Explore and analyze employee trends

Build HR dashboards in Excel

Practice pivot tables, formulas, and HR KPIs

Learn workforce analytics without Power BI or coding

Work on beginner-friendly and professional HR case studies

This dataset does not contain personally identifiable information and is safe for public sharing. It serves purely as a digital learning resource inspired by real HR scenarios.

Please note: for a correct view and use of this dataset it is advisable to consult it at original page on the Arezzo Portal. At the same address there are also, for the enabled datasets, additional access formats, the preview of the visualization via API call, the consultation of the fields in DCAT-AP IT format, the possibility to express an evaluation and comment on the dataset itself. All resource formats available for this dataset can be downloaded as ZIP packages: inside the package sarà available the resource in the chosen format, complete with all the information on the metadata and the license associated with it. The dataset contains the table in document "E6 Explanatory Summary Report" of the Operational Plan, paragraph "8.3. Dimensioning of expansion and transformation areas" on pages 53-55 and represents the dimensioning of expansion or transformation areas with new building quotas, articulated in transformation areas subject to implementing urban plans, areas subject to Unitary Conventioned Plans and direct agreed interventions. The dataset is a spreadsheet in Microsoft Excel *.xls format.

This dataset was created as part of a data analysis project to build an interactive Excel dashboard for performance monitoring and decision making. The data is either simulated or aggregated from multiple open-source references and does not reflect any specific real-world company or institution.

The goal was to analyze and visualize trends, patterns, and key performance indicators using Microsoft Excel’s advanced features such as Pivot Tables, Slicers, Charts, and Conditional Formatting.

Project Focus: Dashboard creation and performance analysis

Tools Used: Microsoft Excel 2016+

Purpose: Practice data analysis, insights generation, and dashboard design

nspiration: Business intelligence, operational monitoring, and reporting needs across various industries (e.g., healthcare, finance, education)

This dataset is ideal for learners, analysts, or professionals looking to understand how structured Excel files can be used for real time insights and visualization storytelling.

Grid-based building morphological parameters with global coverage at 30-arc second spatial resolution are currently available in GeoTIFF format. Provided datasets contains three-building morphological parameters (the mean building height Have, plan area density PAD and frontal area density FAD) and two-aerodynamic parameters (aerodynamic roughness length z0 and zero-place displacement d) and sky-view factor (svf).The building morphological datasets were estimated from the global databases such as population, nighttime light, impervious surface area and gross domestic products. Two aerodynamic parameters and sky-view factors are calculated using the empirical equations discussed by Kanda et al. (2013) and Kanda et al. (2005), respectively.1. Raster files: (parameter name)_2013.tifFormat: GeoTIFFProjection: WGS 1984 World Mercator projectionSpatial resolution: 30-arc secondData list: Have_2013.tif, PAD_2013.tif, FAD_2013.tif, d_2013.tif, z0_2013.tif, svf_2013.tif2. Building Original DataFormat: Microsoft Excel WorkbookOriginal_building_data.xlsx contains observed building morphological parameters calculated from three- and two-dimensional building databases, and global databases (impervious surface area ISA and population density adjusted by nighttime light PopdenVIIRS) at each grid code.Validation_analysis.xlsx contains building morphological parameters calculated from three-dimensional building database (observed) and parameters estimated from global databases (predicted) at one-km spatial resolution in Berlin, Singapore and Osaka.Additional_validation_UScities.xlsx contains building morphological parameters at one-km resolution by NUDAPT database (observed) and estimated from global databases (predicted) for 42 US cities. We used this data in the Supplementary Discussion. Megacities_statistic.xlsx contains GDPcity, the maximum, minimum, mean value and standard deviation of each predicted building morphological parameters at 37 megacities. 3. Source CodeProgramming language 1: Python site package in ArcGIS v10.3.1Calculate_parameters.py contains code for calculating observed building morphological parameters from grid-based two- and three-dimensional building database input. We recommend using this script after using the Split By Attributing Tools to convert a fishnet building footprint map into multiple grids.Modifying_population_by_nightlight.py contains code for adjusted population density by nighttime light at each grid.Programming language 2: Python v2.7Converting_grids.py contains code for converting grid-based population density adjusted by nighttime light into a global map. This source code is used after running Modifying_population_by_nightlight.py.

Please note: for a correct view and use of this dataset it is advisable to consult it at original page on the Arezzo Portal. At the same address there are also, for the enabled datasets, additional access formats, the preview of the visualization via API call, the consultation of the fields in DCAT-AP IT format, the possibility to express an evaluation and comment on the dataset itself. All resource formats available for this dataset can be downloaded as ZIP packages: inside the package sarà available the resource in the chosen format, complete with all the information on the metadata and the license associated with it. The dataset contains the table set out in document ‘E1 Implementing technical standards’ of the operational plan, ‘Article 29(2)’. Historicized gardens " on pages 59-60. It represents the list of Historic Gardens identified in the draft ‘E2.1d Areas of application of the rules on building fabrics and transformation areas – Historic centre of the capital’. The dataset is a spreadsheet in Microsoft Excel *.xls format.

Introduction

We are enclosing the database used in our research titled "Concentration and Geospatial Modelling of Health Development Offices' Accessibility for the Total and Elderly Populations in Hungary", along with our statistical calculations. For the sake of reproducibility, further information can be found in the file Short_Description_of_Data_Analysis.pdf and Statistical_formulas.pdf

The sharing of data is part of our aim to strengthen the base of our scientific research. As of March 7, 2024, the detailed submission and analysis of our research findings to a scientific journal has not yet been completed.

The dataset was expanded on 23rd September 2024 to include SPSS statistical analysis data, a heatmap, and buffer zone analysis around the Health Development Offices (HDOs) created in QGIS software.

Short Description of Data Analysis and Attached Files (datasets):

Our research utilised data from 2022, serving as the basis for statistical standardisation. The 2022 Hungarian census provided an objective basis for our analysis, with age group data available at the county level from the Hungarian Central Statistical Office (KSH) website. The 2022 demographic data provided an accurate picture compared to the data available from the 2023 microcensus. The used calculation is based on our standardisation of the 2022 data. For xlsx files, we used MS Excel 2019 (version: 1808, build: 10406.20006) with the SOLVER add-in.

Hungarian Central Statistical Office served as the data source for population by age group, county, and regions: https://www.ksh.hu/stadat_files/nep/hu/nep0035.html, (accessed 04 Jan. 2024.) with data recorded in MS Excel in the Data_of_demography.xlsx file.

In 2022, 108 Health Development Offices (HDOs) were operational, and it's noteworthy that no developments have occurred in this area since 2022. The availability of these offices and the demographic data from the Central Statistical Office in Hungary are considered public interest data, freely usable for research purposes without requiring permission.

The contact details for the Health Development Offices were sourced from the following page (Hungarian National Population Centre (NNK)): https://www.nnk.gov.hu/index.php/efi (n=107). The Semmelweis University Health Development Centre was not listed by NNK, hence it was separately recorded as the 108th HDO. More information about the office can be found here: https://semmelweis.hu/egeszsegfejlesztes/en/ (n=1). (accessed 05 Dec. 2023.)

Geocoordinates were determined using Google Maps (N=108): https://www.google.com/maps. (accessed 02 Jan. 2024.) Recording of geocoordinates (latitude and longitude according to WGS 84 standard), address data (postal code, town name, street, and house number), and the name of each HDO was carried out in the: Geo_coordinates_and_names_of_Hungarian_Health_Development_Offices.csv file.

The foundational software for geospatial modelling and display (QGIS 3.34), an open-source software, can be downloaded from:

https://qgis.org/en/site/forusers/download.html. (accessed 04 Jan. 2024.)

The HDOs_GeoCoordinates.gpkg QGIS project file contains Hungary's administrative map and the recorded addresses of the HDOs from the

Geo_coordinates_and_names_of_Hungarian_Health_Development_Offices.csv file,

imported via .csv file.

The OpenStreetMap tileset is directly accessible from www.openstreetmap.org in QGIS. (accessed 04 Jan. 2024.)

The Hungarian county administrative boundaries were downloaded from the following website: https://data2.openstreetmap.hu/hatarok/index.php?admin=6 (accessed 04 Jan. 2024.)

HDO_Buffers.gpkg is a QGIS project file that includes the administrative map of Hungary, the county boundaries, as well as the HDO offices and their corresponding buffer zones with a radius of 7.5 km.

Heatmap.gpkg is a QGIS project file that includes the administrative map of Hungary, the county boundaries, as well as the HDO offices and their corresponding heatmap (Kernel Density Estimation).

A brief description of the statistical formulas applied is included in the Statistical_formulas.pdf.

Recording of our base data for statistical concentration and diversification measurement was done using MS Excel 2019 (version: 1808, build: 10406.20006) in .xlsx format.

• Aggregated number of HDOs by county: Number_of_HDOs.xlsx
• Standardised data (Number of HDOs per 100,000 residents): Standardized_data.xlsx
• Calculation of the Lorenz curve: Lorenz_curve.xlsx
• Calculation of the Gini index: Gini_Index.xlsx
• Calculation of the LQ index: LQ_Index.xlsx
• Calculation of the Herfindahl-Hirschman Index: Herfindahl_Hirschman_Index.xlsx
• Calculation of the Entropy index: Entropy_Index.xlsx
• Regression and correlation analysis calculation: Regression_correlation.xlsx

Using the SPSS 29.0.1.0 program, we performed the following statistical calculations with the databases Data_HDOs_population_without_outliers.sav and Data_HDOs_population.sav:

• Regression curve estimation with elderly population and number of HDOs, excluding outlier values (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_elderly_without_outlier.spv
• Pearson correlation table between the total population, elderly population, and number of HDOs per county, excluding outlier values such as Budapest and Pest County: Pearson_Correlation_populations_HDOs_number_without_outliers.spv.
• Dot diagram including total population and number of HDOs per county, excluding outlier values such as Budapest and Pest Counties: Dot_HDO_total_population_without_outliers.spv.
• Dot diagram including elderly (64<) population and number of HDOs per county, excluding outlier values such as Budapest and Pest Counties: Dot_HDO_elderly_population_without_outliers.spv
• Regression curve estimation with total population and number of HDOs, excluding outlier values (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_without_outlier.spv
• Dot diagram including elderly (64<) population and number of HDOs per county: Dot_HDO_elderly_population.spv
• Dot diagram including total population and number of HDOs per county: Dot_HDO_total_population.spv
• Pearson correlation table between the total population, elderly population, and number of HDOs per county: Pearson_Correlation_populations_HDOs_number.spv
• Regression curve estimation with total population and number of HDOs, (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_total_population.spv

For easier readability, the files have been provided in both SPV and PDF formats.

The translation of these supplementary files into English was completed on 23rd Sept. 2024.

If you have any further questions regarding the dataset, please contact the corresponding author: domjan.peter@phd.semmelweis.hu

Identifiers of many kinds are the key to creating unambiguous and persistent connections between research objects and other items in the global research infrastructure (GRI). Many repositories are implementing mechanisms to collect and integrate these identifiers into their submission and record curation processes. This bodes well for a well-connected future, but many existing resources submitted in the past are missing these identifiers, thus missing the connections required for inclusion in the connected infrastructure. Re-curation of these metadata is required to make these connections. The Dryad Data Repository has existed since 2008 and has successfully re-curated the repository metadata several times, adding identifiers for research organizations, funders, and researchers. Understanding and quantifying these successes depends on measuring repository and identifier connectivity. Metrics are described and applied to the entire repository here. Identifiers for papers (DOIs) connected to datasets in Dryad have long been a critical part of the Dryad metadata creation and curation processes. Since 2019, the % of datasets with connected papers has decreased from 100% to less than 40%. This decrease has significant ramifications for the re-curation efforts described above as connected papers are an important source of metadata. In addition, missing connections to papers make understanding and re-using datasets more difficult. Connections between datasets and papers are many times difficult to make because of time lags between submission and publication, lack of clear mechanisms for citing datasets and other research objects from papers, changing focus of researchers, and other obstacles. The Dryad community of members, i.e. users, research institutions, publishers, and funders have vested interests in identifying these connections and critical roles in the curation and re-curation efforts. Their engagement will be critical in building on the successes Dryad has already achieved and ensuring sustainable connectivity in the future. Methods These data are Dryad metadata retrieved from https://datadryad.org and translated into csv files. There are two datasets: 1. DryadJournalDataset was retrieved from Dryad using the ISSNs in the file DryadJournalDataset_ISSNs.txt, although some had no data. 2. DryadOrganizationDataset was retrieved from Dryad using the RORs in the file DryadOrganizationDataset_RORs.txt, although some had no data. Each dataset includes four types of metadata: identifiers, funders, keywords, and related works, each in a separate comma (.csv) or tab (.tsv) delimited files. There are also Microsoft Excel files (.xlsx) for the identifier metadata and connectivity summaries for each dataset (*.html). The connectivity summaries include summaries of each parameter in all four data files with definitions, counts, unique counts, most frequent values, and completeness. These data formed the basis for an analysis of the connectivity of the Dryad repository for organizations, funders, and people.

Dataset underpinning manuscript describing the design, building, and testing of the B-SAFE tool. B-SAFE is an Microsoft Excel-based, user-friendly tool that allows researchers to quickly identify surrogate microorganisms to use in place of pathogenic microorganisms, in just-in-time research.

Summary:

The files contained herein represent green roof footprints in NYC visible in 2016 high-resolution orthoimagery of NYC (described at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_AerialImagery.md). Previously documented green roofs were aggregated in 2016 from multiple data sources including from NYC Department of Parks and Recreation and the NYC Department of Environmental Protection, greenroofs.com, and greenhomenyc.org. Footprints of the green roof surfaces were manually digitized based on the 2016 imagery, and a sample of other roof types were digitized to create a set of training data for classification of the imagery. A Mahalanobis distance classifier was employed in Google Earth Engine, and results were manually corrected, removing non-green roofs that were classified and adjusting shape/outlines of the classified green roofs to remove significant errors based on visual inspection with imagery across multiple time points. Ultimately, these initial data represent an estimate of where green roofs existed as of the imagery used, in 2016.

These data are associated with an existing GitHub Repository, https://github.com/tnc-ny-science/NYC_GreenRoofMapping, and as needed and appropriate pending future work, versioned updates will be released here.

Terms of Use:

The Nature Conservancy and co-authors of this work shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any sale, distribution, loan, or offering for use of these digital data, in whole or in part, is prohibited without the approval of The Nature Conservancy and co-authors. The use of these data to produce other GIS products and services with the intent to sell for a profit is prohibited without the written consent of The Nature Conservancy and co-authors. All parties receiving these data must be informed of these restrictions. Authors of this work shall be acknowledged as data contributors to any reports or other products derived from these data.

Associated Files:

As of this release, the specific files included here are:

• GreenRoofData2016_20180917.geojson is in the human-readable, GeoJSON format, in geographic coordinates (Lat/Long, WGS84; EPSG 4263).
• GreenRoofData2016_20180917.gpkg is in the GeoPackage format, which is an Open Standard readable by most GIS software including Esri products (tested on ArcMap 10.3.1 and multiple versions of QGIS). This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917_Shapefile.zip is a zipped folder containing a Shapefile and associated files. Please note that some field names were truncated due to limitations of Shapefiles, but columns are in the same order as for other files and in the same order as listed below. This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917.csv is a comma-separated values file (CSV) with coordinates for centroids for the green roofs stored in the table itself. This allows for easily opening the data in a tool like spreadsheet software (e.g., Microsoft Excel) or a text editor.

Column Information for the datasets:

Some, but not all fields were joined to the green roof footprint data based on building footprint and tax lot data; those datasets are embedded as hyperlinks below.

• fid - Unique identifier
• bin - NYC Building ID Number based on overlap between green roof areas and a building footprint dataset for NYC from August, 2017. (Newer building footprint datasets do not have linkages to the tax lot identifier (bbl), thus this older dataset was used). The most current building footprint dataset should be available at: https://data.cityofnewyork.us/Housing-Development/Building-Footprints/nqwf-w8eh. Associated metadata for fields from that dataset are available at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_BuildingFootprints.md.
• bbl - Boro Block and Lot number as a single string. This field is a tax lot identifier for NYC, which can be tied to the Digital Tax Map (http://gis.nyc.gov/taxmap/map.htm) and PLUTO/MapPLUTO (https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page). Metadata for fields pulled from PLUTO/MapPLUTO can be found in the PLUTO Data Dictionary found on the aforementioned page. All joins to this bbl were based on MapPLUTO version 18v1.
• gr_area - Total area of the footprint of the green roof as per this data layer, in square feet, calculated using the projected coordinate system (EPSG 2263).
• bldg_area - Total area of the footprint of the associated building, in square feet, calculated using the projected coordinate system (EPSG 2263).
• prop_gr - Proportion of the building covered by green roof according to this layer (gr_area/bldg_area).
• cnstrct_yr - Year the building was constructed, pulled from the Building Footprint data.
• doitt_id - An identifier for the building assigned by the NYC Dept. of Information Technology and Telecommunications, pulled from the Building Footprint Data.
• heightroof - Height of the roof of the associated building, pulled from the Building Footprint Data.
• feat_code - Code describing the type of building, pulled from the Building Footprint Data.
• groundelev - Lowest elevation at the building level, pulled from the Building Footprint Data.
• qa - Flag indicating a positive QA/QC check (using multiple types of imagery); all data in this dataset should have 'Good'
• notes - Any notes about the green roof taken during visual inspection of imagery; for example, it was noted if the green roof appeared to be missing in newer imagery, or if there were parts of the roof for which it was unclear whether there was green roof area or potted plants.
• classified - Flag indicating whether the green roof was detected image classification. (1 for yes, 0 for no)
• digitized - Flag indicating whether the green roof was digitized prior to image classification and used as training data. (1 for yes, 0 for no)
• newlyadded - Flag indicating whether the green roof was detected solely by visual inspection after the image classification and added. (1 for yes, 0 for no)
• original_source - Indication of what the original data source was, whether a specific website, agency such as NYC Dept. of Parks and Recreation (DPR), or NYC Dept. of Environmental Protection (DEP). Multiple sources are separated by a slash.
• address - Address based on MapPLUTO, joined to the dataset based on bbl.
• borough - Borough abbreviation pulled from MapPLUTO.
• ownertype - Owner type field pulled from MapPLUTO.
• zonedist1 - Zoning District 1 type pulled from MapPLUTO.
• spdist1 - Special District 1 pulled from MapPLUTO.
• bbl_fixed - Flag to indicate whether bbl was manually fixed. Since tax lot data may have changed slightly since the release of the building footprint data used in this work, a small percentage of bbl codes had to be manually updated based on overlay between the green roof footprint and the MapPLUTO data, when no join was feasible based on the bbl code from the building footprint data. (1 for yes, 0 for no)

For GreenRoofData2016_20180917.csv there are two additional columns, representing the coordinates of centroids in geographic coordinates (Lat/Long, WGS84; EPSG 4263):

• xcoord - Longitude in decimal degrees.
• ycoord - Latitude in decimal degrees.

Acknowledgements:

This work was primarily supported through funding from the J.M. Kaplan Fund, awarded to the New York City Program of The Nature Conservancy, with additional support from the New York Community Trust, through New York City Audubon and the Green Roof Researchers Alliance.

A number of education data sets are available for use by policymakers, educators, the public, program directors and researchers through the Virginia Longitudinal Data System. For a complete list of all the table descriptions and data elements, refer to the data dictionary https://www.doe.virginia.gov/about-vdoe/search?q=data%20dictionary

These datasets are intended to be used in applications that have filtering and query building capabilities such as spreadsheet applications ( MS Excel or Numbers), analytical applications (SPSS or SAS), or development-type applications. The datasets are compiled using all the possible combinations of all the demographics about students so each row within the dataset contains a rate or count in addition to the demographics used to arrive at the rate or count.

The Ontario government, generates and maintains thousands of datasets. Since 2012, we have shared data with Ontarians via a data catalogue. Open data is data that is shared with the public. Click here to learn more about open data and why Ontario releases it. Ontario’s Open Data Directive states that all data must be open, unless there is good reason for it to remain confidential. Ontario’s Chief Digital and Data Officer also has the authority to make certain datasets available publicly. Datasets listed in the catalogue that are not open will have one of the following labels: If you want to use data you find in the catalogue, that data must have a licence – a set of rules that describes how you can use it. A licence: Most of the data available in the catalogue is released under Ontario’s Open Government Licence. However, each dataset may be shared with the public under other kinds of licences or no licence at all. If a dataset doesn’t have a licence, you don’t have the right to use the data. If you have questions about how you can use a specific dataset, please contact us. The Ontario Data Catalogue endeavors to publish open data in a machine readable format. For machine readable datasets, you can simply retrieve the file you need using the file URL. The Ontario Data Catalogue is built on CKAN, which means the catalogue has the following features you can use when building applications. APIs (Application programming interfaces) let software applications communicate directly with each other. If you are using the catalogue in a software application, you might want to extract data from the catalogue through the catalogue API. Note: All Datastore API requests to the Ontario Data Catalogue must be made server-side. The catalogue's collection of dataset metadata (and dataset files) is searchable through the CKAN API. The Ontario Data Catalogue has more than just CKAN's documented search fields. You can also search these custom fields. You can also use the CKAN API to retrieve metadata about a particular dataset and check for updated files. Read the complete documentation for CKAN's API. Some of the open data in the Ontario Data Catalogue is available through the Datastore API. You can also search and access the machine-readable open data that is available in the catalogue. How to use the API feature: Read the complete documentation for CKAN's Datastore API. The Ontario Data Catalogue contains a record for each dataset that the Government of Ontario possesses. Some of these datasets will be available to you as open data. Others will not be available to you. This is because the Government of Ontario is unable to share data that would break the law or put someone's safety at risk. You can search for a dataset with a word that might describe a dataset or topic. Use words like “taxes” or “hospital locations” to discover what datasets the catalogue contains. You can search for a dataset from 3 spots on the catalogue: the homepage, the dataset search page, or the menu bar available across the catalogue. On the dataset search page, you can also filter your search results. You can select filters on the left hand side of the page to limit your search for datasets with your favourite file format, datasets that are updated weekly, datasets released by a particular organization, or datasets that are released under a specific licence. Go to the dataset search page to see the filters that are available to make your search easier. You can also do a quick search by selecting one of the catalogue’s categories on the homepage. These categories can help you see the types of data we have on key topic areas. When you find the dataset you are looking for, click on it to go to the dataset record. Each dataset record will tell you whether the data is available, and, if so, tell you about the data available. An open dataset might contain several data files. These files might represent different periods of time, different sub-sets of the dataset, different regions, language translations, or other breakdowns. You can select a file and either download it or preview it. Make sure to read the licence agreement to make sure you have permission to use it the way you want. Read more about previewing data. A non-open dataset may be not available for many reasons. Read more about non-open data. Read more about restricted data. Data that is non-open may still be subject to freedom of information requests. The catalogue has tools that enable all users to visualize the data in the catalogue without leaving the catalogue – no additional software needed. Have a look at our walk-through of how to make a chart in the catalogue. Get automatic notifications when datasets are updated. You can choose to get notifications for individual datasets, an organization’s datasets or the full catalogue. You don’t have to provide and personal information – just subscribe to our feeds using any feed reader you like using the corresponding notification web addresses. Copy those addresses and paste them into your reader. Your feed reader will let you know when the catalogue has been updated. The catalogue provides open data in several file formats (e.g., spreadsheets, geospatial data, etc). Learn about each format and how you can access and use the data each file contains. A file that has a list of items and values separated by commas without formatting (e.g. colours, italics, etc.) or extra visual features. This format provides just the data that you would display in a table. XLSX (Excel) files may be converted to CSV so they can be opened in a text editor. How to access the data: Open with any spreadsheet software application (e.g., Open Office Calc, Microsoft Excel) or text editor. Note: This format is considered machine-readable, it can be easily processed and used by a computer. Files that have visual formatting (e.g. bolded headers and colour-coded rows) can be hard for machines to understand, these elements make a file more human-readable and less machine-readable. A file that provides information without formatted text or extra visual features that may not follow a pattern of separated values like a CSV. How to access the data: Open with any word processor or text editor available on your device (e.g., Microsoft Word, Notepad). A spreadsheet file that may also include charts, graphs, and formatting. How to access the data: Open with a spreadsheet software application that supports this format (e.g., Open Office Calc, Microsoft Excel). Data can be converted to a CSV for a non-proprietary format of the same data without formatted text or extra visual features. A shapefile provides geographic information that can be used to create a map or perform geospatial analysis based on location, points/lines and other data about the shape and features of the area. It includes required files (.shp, .shx, .dbt) and might include corresponding files (e.g., .prj). How to access the data: Open with a geographic information system (GIS) software program (e.g., QGIS). A package of files and folders. The package can contain any number of different file types. How to access the data: Open with an unzipping software application (e.g., WinZIP, 7Zip). Note: If a ZIP file contains .shp, .shx, and .dbt file types, it is an ArcGIS ZIP: a package of shapefiles which provide information to create maps or perform geospatial analysis that can be opened with ArcGIS (a geographic information system software program). A file that provides information related to a geographic area (e.g., phone number, address, average rainfall, number of owl sightings in 2011 etc.) and its geospatial location (i.e., points/lines). How to access the data: Open using a GIS software application to create a map or do geospatial analysis. It can also be opened with a text editor to view raw information. Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. A text-based format for sharing data in a machine-readable way that can store data with more unconventional structures such as complex lists. How to access the data: Open with any text editor (e.g., Notepad) or access through a browser. Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. A text-based format to store and organize data in a machine-readable way that can store data with more unconventional structures (not just data organized in tables). How to access the data: Open with any text editor (e.g., Notepad). Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. A file that provides information related to an area (e.g., phone number, address, average rainfall, number of owl sightings in 2011 etc.) and its geospatial location (i.e., points/lines). How to access the data: Open with a geospatial software application that supports the KML format (e.g., Google Earth). Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. This format contains files with data from tables used for statistical analysis and data visualization of Statistics Canada census data. How to access the data: Open with the Beyond 20/20 application. A database which links and combines data from different files or applications (including HTML, XML, Excel, etc.). The database file can be converted to a CSV/TXT to make the data machine-readable, but human-readable formatting will be lost. How to access the data: Open with Microsoft Office Access (a database management system used to develop application software). A file that keeps the original layout and

This dataset contains sales transaction records used to create an interactive Excel Sales Performance Dashboard for business analytics practice.

It includes six columns capturing essential sales metrics such as date, region, product, quantity, sales revenue, and profit. The data is structured to help analysts and learners explore data visualization, PivotTable summarization, and dashboard design concepts in Excel.

The dataset was created for educational and demonstration purposes to help users:

1. Build dashboards that visualize total sales and profit trends
2. Identify top-performing products and high-profit regions
3. Practice Excel-based business analytics workflows

Columns: Date – Transaction date (daily sales record) Region – Geographic area of the sale (East, West, North, South) Product – Product category or item sold Sales – Total revenue generated from the sale (USD) Profit – Net profit made per transaction Quantity – Number of units sold

Typical uses include: Excel or Power BI dashboard projects PivotTable practice for business reporting Data cleaning and chart-building exercises Portfolio development for business analytics students Built and tested in Microsoft Excel using PivotTables, Charts, and Conditional Formatting.

These data are damage and loss estimates obtained from various Hazus outputs covering all census tracts in 17 counties in and around the San Francisco Bay region in California, for the HayWired earthquake scenario and sixteen M5 or greater aftershocks occurring in the region during the two years following the HayWired mainshock. The HayWired earthquake scenario is a magnitude 7.0 earthquake hypothesized to occur on the Hayward Fault on April 18, 2018, with an epicenter in the city of Oakland, CA. The estimates contained in this dataset are a subset of the many results products generated by FEMA's Hazus-MH 2.1 application, and reflect potential damage due to the HayWired earthquake scenario mainshock and its aftershocks. The data included in this data release were obtained directly from Hazus or by using Hazus outputs to create derivative results. Products include: Hazus building inventory replacement value estimates, Hazus building contents value estimates, estimates of injuries and fatalities (mainshock and three aftershocks), estimates of displaced households and population requiring short-term shelter (mainshock and three aftershocks), value of building damage estimates (mainshock and sum of mainshock and 16 M5 or greater aftershocks), damage ratio estimates (mainshock and sum of mainshock and 16 M5 or greater aftershocks), estimates of damaged square footage by damage state (mainshock), and direct economic losses (mainshock and 16 M5 or greater aftershocks). For additional information on each dataset, please refer to the metadata accompanying the specific dataset of interest. These tab-delimited .TXT datasets were developed and intended for use in standalone spreadsheet or database applications (such as Microsoft Excel or Access). Please note that some data included in this data release are not optimized for use in GIS applications (such as ESRI's ArcGIS software suite) as-is--census tracts are repeated (the data are not "one-to-one"), so not all information belonging to a tract would necessarily be associated with a single record. Separate preparation is needed in a standalone spreadsheet or database application like Microsoft Excel or Microsoft Access before using these data in a GIS. These data support the following publication: Seligson, H.A., Wein, A.M., and Jones, J.L., 2018, HayWired scenario--Hazus analyses of the mainshock and aftershocks, chap. J of Detweiler, S.T., and Wein, A.M., eds., The HayWired earthquake scenario--Earthquake implications: U.S. Geological Survey Scientific Investigations Report 2017-5013-I-Q, 41 p., https://doi.org/10.3133/sir20175013.

The GAPs Data Repository provides a comprehensive overview of available qualitative and quantitative data on national return regimes, now accessible through an advanced web interface at https://data.returnmigration.eu/.

This updated guideline outlines the complete process, starting from the initial data collection for the return migration data repository to the development of a comprehensive web-based platform. Through iterative development, participatory approaches, and rigorous quality checks, we have ensured a systematic representation of return migration data at both national and comparative levels.

The Repository organizes data into five main categories, covering diverse aspects and offering a holistic view of return regimes: country profiles, legislation, infrastructure, international cooperation, and descriptive statistics. These categories, further divided into subcategories, are based on insights from a literature review, existing datasets, and empirical data collection from 14 countries. The selection of categories prioritizes relevance for understanding return and readmission policies and practices, data accessibility, reliability, clarity, and comparability. Raw data is meticulously collected by the national experts.

The transition to a web-based interface builds upon the Repository’s original structure, which was initially developed using REDCap (Research Electronic Data Capture). It is a secure web application for building and managing online surveys and databases.The REDCAP ensures systematic data entries and store them on Uppsala University’s servers while significantly improving accessibility and usability as well as data security. It also enables users to export any or all data from the Project when granted full data export privileges. Data can be exported in various ways and formats, including Microsoft Excel, SAS, Stata, R, or SPSS for analysis. At this stage, the Data Repository design team also converted tailored records of available data into public reports accessible to anyone with a unique URL, without the need to log in to REDCap or obtain permission to access the GAPs Project Data Repository. Public reports can be used to share information with stakeholders or external partners without granting them access to the Project or requiring them to set up a personal account. Currently, all public report links inserted in this report are also available on the Repository’s webpage, allowing users to export original data.

This report also includes a detailed codebook to help users understand the structure, variables, and methodologies used in data collection and organization. This addition ensures transparency and provides a comprehensive framework for researchers and practitioners to effectively interpret the data.

The GAPs Data Repository is committed to providing accessible, well-organized, and reliable data by moving to a centralized web platform and incorporating advanced visuals. This Repository aims to contribute inputs for research, policy analysis, and evidence-based decision-making in the return and readmission field.

Explore the GAPs Data Repository at https://data.returnmigration.eu/.

This data release is comprised of geospatial and tabular data developed for the HayWired communities at risk analysis. The HayWired earthquake scenario is a magnitude 7.0 earthquake hypothesized to occur on the Hayward Fault on April 18, 2018, with an epicenter in the city of Oakland, CA. The following 17 counties are included in this analysis unless otherwise specified: Alameda, Contra Costa, Marin, Merced, Monterey, Napa, Sacramento, San Benito, San Francisco, San Joaquin, San Mateo, Santa Clara, Santa Cruz, Solano, Sonoma, Stanislaus, and Yolo. The vector data are a geospatial representation of building damage based on square footage damage estimates by Hazus occupancy class for developed areas covering all census tracts in 17 counties in and around the San Francisco Bay region in California, for (1) earthquake hazards (ground shaking, landslide, and liquefaction) and (2) all hazards (ground shaking, landslide, liquefaction, and fire) resulting from the HayWired earthquake scenario mainshock. The tabular data cover: (1) damage estimates, by Hazus occupancy class, of square footage, building counts, and households affected by the HayWired earthquake scenario mainshock for all census tracts in 17 counties in and around the San Francisco Bay region in California; (2) potential total population residing in block groups in nine counties in the San Francisco Bay region in California (Alameda, Contra Costa, Marin, Napa, San Francisco, San Mateo, Santa Clara, Solano, and Sonoma); (3) a subset of select tables for 17 counties in and around the San Francisco Bay region in California from the U.S. Census Bureau American Community Survey 5-year (2012-2016) estimates at the block group level selected to represent potentially vulnerable populations that may, in the event of a major disaster, leave an area rather than stay; and (4) building and contents damage estimates (in thousands of dollars, 2005 vintage), by Hazus occupancy class, for the HayWired earthquake scenario mainshock for 17 counties in and around the San Francisco Bay region in California. The vector .SHP datasets were developed and intended for use in GIS applications such as ESRI's ArcGIS software suite. The tab-delimited .TXT datasets were developed and intended for use in standalone spreadsheet or database applications (such as Microsoft Excel or Access). Please note that some of these data are not optimized for use in GIS applications (such as ESRI's ArcGIS software suite) as-is--census tracts or counties are repeated (the data are not "one-to-one"), so not all information belonging to a tract or county would necessarily be associated with a single record. Separate preparation is needed in a standalone spreadsheet or database application like Microsoft Excel or Microsoft Access before using these data in a GIS. These data support the following publications: Johnson, L.A., Jones, J.L., Wein, A.M., and Peters, J., 2020, Communities at risk analysis of the HayWired scenario, chaps. U1-U5 of Detweiler, S.T., and Wein, A.M., eds., The HayWired earthquake scenario--Societal consequences: U.S. Geological Survey Scientific Investigations Report 2017-5013, https://doi.org/10.3133/sir20175013.