Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Overview The Stack Overflow Developer Survey Dataset represents one of the most trusted and comprehensive sources of information about the global developer community. Collected by Stack Overflow through its annual survey, the dataset provides insights into the demographics, preferences, habits, and career paths of developers.
This dataset is frequently used for: - Analyzing trends in programming languages, tools, and technologies. - Understanding developer job satisfaction, compensation, and work environments. - Studying global and regional differences in developer demographics and experience.
The data has of two CSV files, "survey_results_public" that consist of data and "survey_results_schema" that describes each column in detail.
Data Dictionary: All the details are in "survey_results_schema.csv"
Demographic & Background Information - Respondent: A unique identifier for each survey participant. - MainBranch: Describes whether the respondent is a professional developer, student, hobbyist, etc. - Country: The country where the respondent lives. - Age: The respondent's age. - Gender: The gender identity of the respondent. - Ethnicity: Ethnic background (when available). - EdLevel: The highest level of formal education completed. - UndergradMajor: The respondent's undergraduate major. - Hobbyist: Indicates whether the person codes as a hobby (Yes/No).
Employment & Professional Experience - Employment: Employment status (full-time, part-time, unemployed, student, etc.). - DevType: Types of developer roles the respondent identifies with (e.g., Web Developer, Data Scientist). - YearsCode: Number of years the respondent has been coding. - YearsCodePro: Number of years coding professionally. - JobSat: Job satisfaction level. - CareerSat: Career satisfaction level. - WorkWeekHrs: Approximate hours worked per week. - RemoteWork: Whether the respondent works remotely and how frequently.
Compensation - CompTotal: Total compensation in USD (including salary, bonuses, etc.). - CompFreq: Frequency of compensation (e.g., yearly, monthly).
Learning & Education - LearnCode: How the respondent first learned to code (e.g., online courses, university). - LearnCodeOnline: Online resources used (e.g., YouTube, freeCodeCamp). - LearnCodeCoursesCert: Whether the respondent has taken online courses or earned certifications.
Technology & Tools - LanguageHaveWorkedWith: Programming languages the respondent has used. - LanguageWantToWorkWith: Languages the respondent is interested in learning or using more. - DatabaseHaveWorkedWith: Databases the respondent has experience with. - PlatformHaveWorkedWith: Platforms used (e.g., Linux, AWS, Android). - OpSys: The operating system used most often. - NEWCollabToolsHaveWorkedWith: Collaboration tools used (e.g., Slack, Teams, Zoom). - NEWStuck: How often the respondent feels stuck when coding. - ToolsTechHaveWorkedWith: Frameworks and technologies respondents have worked with.
Online Presence & Community - SOAccount: Whether the respondent has a Stack Overflow account. - SOPartFreq: How often the respondent participates on Stack Overflow. - SOVisitFreq: Frequency of visiting Stack Overflow. - SOComm: Whether the respondent feels welcome in the Stack Overflow community. - OpenSourcer: Level of involvement in open-source contributions.
Opinions & Preferences - WorkChallenge: Challenges faced at work (e.g., unclear requirements, unrealistic expectations). - JobFactors: Important job factors (e.g., salary, work-life balance, technologies used). - MentalHealth: Questions on how mental health affects or is affected by their job.
Facebook
Twitterhttps://cdla.io/sharing-1-0/https://cdla.io/sharing-1-0/
The Public 2023 Stack Overflow Developer Survey Results
Description:
The enclosed data set is the complete, cleaned results of the 2023 Stack Overflow Developer Survey. Free response submissions have been removed. There are three files besides this README:
The survey was fielded from May 8, 2023 to May 19, 2023. The median time spent on the survey for qualified responses was 17 minutes.
Respondents were recruited primarily through channels owned by Stack Overflow. The top 5 sources of respondents were onsite messaging, blog posts, email lists, meta.stackoverflow posts, banner ads, and social media posts. Since respondents were recruited in this way, highly engaged users on Stack Overflow were more likely to notice the links for the survey and click to begin it.
You can find the official published results here:
https://survey.stackoverflow.co/2023/
Find previous survey results here:
https://insights.stackoverflow.com/survey
Legal:
This database - The Public 2023 Stack Overflow Developer Survey Results - is made available under the Open Database License (ODbL): http://opendatacommons.org/licenses/odbl/1.0/. Any rights in individual contents of the database are licensed under the Database Contents License: http://opendatacommons.org/licenses/dbcl/1.0/
TLDR: You are free to share, adapt, and create derivative works from The Public 2023 Stack Overflow Developer Survey Results as long as you attribute Stack Overflow, keep the database open (if you redistribute it), and continue to share-alike any adapted database under the ODbl.
Acknowledgment:
Massive, heartfelt thanks to all Stack Overflow contributors and lurking developers of the world who took part in the survey this year. We value your generous participation more than you know. <3
Facebook
TwitterMonthly average radiance composite images using nighttime data from the Visible Infrared Imaging Radiometer Suite (VIIRS) Day/Night Band (DNB). As these data are composited monthly, there are many areas of the globe where it is impossible to get good quality data coverage for that month. This can be due to …
Facebook
TwitterExtensive Developer Coverage: Our employee dataset includes a diverse range of developer profiles from GitHub, spanning various skill levels, industries, and expertise. Access information on developers from all corners of the software development world.
Developer Profiles: Explore detailed developer profiles, including user bios, locations, company affiliations, and skills. Understand developer backgrounds, experiences, and areas of expertise.
Repositories and Contributions: Access information about the repositories created by developers and their contributions to open-source projects. Analyze the projects they've worked on, their coding activity, and the impact they've made on the developer community.
Programming Languages: Gain insights into the programming languages that developers are proficient in. Identify skilled developers in specific programming languages that align with your project needs.
Customizable Data Delivery: The dataset is available in flexible formats, such as CSV, JSON, or API integration, allowing seamless integration with your existing data infrastructure. Customize the data to meet your specific research and analysis requirements.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Modern programming languages are constantly evolving, introducing new language features and APIs to enhance software development practices. Software developers often face the tedious task of upgrading their codebase to new programming language versions. Recently, large language models (LLMs) have demonstrated potential in automating various code generation and editing tasks, suggesting their applicability in automating code upgrade. However, there exists no benchmark for evaluating the code upgrade ability of LLMs, as distilling code changes related to programming language evolution from real-world software repositories’ commit histories is a complex challenge.
In this work, we introduce CoUpJava, the first large-scale dataset for code upgrade, focusing on the code changes related to the evolution of Java. CoUpJava comprises 10,697 code upgrade samples, distilled from the commit histories of 1,379 open-source Java repositories and covering Java versions 7–23. The dataset is divided into two subsets: CoUpJava-Fine, which captures fine-grained method-level refactorings towards new language features; and CoUpJava-Coarse, which includes coarse-grained repository-level changes encompassing new language features, standard library APIs, and build configurations. Our proposed dataset provides high-quality samples by filtering irrelevant and noisy changes and verifying the compilability of upgraded code. Moreover, CoUpJava reveals diversity in code upgrade scenarios, ranging from small, fine-grained refactorings to large-scale repository modifications.
Facebook
Twitterhttps://choosealicense.com/licenses/odc-by/https://choosealicense.com/licenses/odc-by/
CodeChat: Developer–LLM Conversations Dataset
Paper: https://arxiv.org/abs/2509.10402
GitHub: https://github.com/Software-Evolution-Analytics-Lab-SEAL/CodeChat
CodeChat is a large-scale dataset comprising 82,845 real-world developer–LLM conversations, containing 368,506 code snippets generated across more than 20 programming languages, derived from the WildChat (i.e., general Human-LLMs conversations dataset). The dataset enables empirical analysis of how developers interact… See the full description on the dataset page: https://huggingface.co/datasets/Suzhen/CodeChat.
Facebook
TwitterAs of June 2024, the most popular database management system (DBMS) worldwide was Oracle, with a ranking score of *******; MySQL and Microsoft SQL server rounded out the top three. Although the database management industry contains some of the largest companies in the tech industry, such as Microsoft, Oracle and IBM, a number of free and open-source DBMSs such as PostgreSQL and MariaDB remain competitive. Database Management Systems As the name implies, DBMSs provide a platform through which developers can organize, update, and control large databases. Given the business world’s growing focus on big data and data analytics, knowledge of SQL programming languages has become an important asset for software developers around the world, and database management skills are seen as highly desirable. In addition to providing developers with the tools needed to operate databases, DBMS are also integral to the way that consumers access information through applications, which further illustrates the importance of the software.
Facebook
TwitterAfter 2022-01-25, Sentinel-2 scenes with PROCESSING_BASELINE '04.00' or above have their DN (value) range shifted by 1000. The HARMONIZED collection shifts data in newer scenes to be in the same range as in older scenes. Sentinel-2 is a wide-swath, high-resolution, multi-spectral imaging mission supporting Copernicus Land Monitoring studies, including the …
Facebook
TwitterThe Shuttle Radar Topography Mission (SRTM) digital elevation dataset was originally produced to provide consistent, high-quality elevation data at near global scope. This version of the SRTM digital elevation data has been processed to fill data voids, and to facilitate its ease of use.
Facebook
TwitterApache License, v2.0https://www.apache.org/licenses/LICENSE-2.0
License information was derived automatically
🪩 VibeCoding Dataset Project
Collecting the vibes of coding — one log at a time.
📢 Call for Volunteers
We’re building an open dataset to capture real-world coding interactions between developers and AI coding assistants — and we need your help! This dataset will help researchers and developers better understand how humans and code models interact across different tools, and improve the future of AI-assisted software development.
🎯 Project Overview
The… See the full description on the dataset page: https://huggingface.co/datasets/QuixiAI/VibeCoding.
Facebook
TwitterSuccess.ai’s Beauty & Cosmetics Data for Cosmetics, Beauty & Wellness Professionals Worldwide delivers a powerful dataset tailored to connect businesses with key stakeholders in the global beauty and wellness industries. Covering professionals such as product developers, brand managers, wellness coaches, and salon owners, this dataset provides verified work emails, phone numbers, and actionable professional insights.
With access to over 700 million verified global profiles and detailed insights from 170 million professional datasets, Success.ai ensures your outreach, marketing, and strategic initiatives are powered by accurate, continuously updated, and AI-validated data. Supported by our Best Price Guarantee, this solution is ideal for businesses aiming to lead in the competitive beauty and wellness market.
Why Choose Success.ai’s Beauty & Cosmetics Data?
Verified Contact Data for Effective Outreach
Comprehensive Global Coverage
Continuously Updated Datasets
Ethical and Compliant
Data Highlights:
Key Features of the Dataset:
Comprehensive Professional Profiles
Advanced Filters for Precision Targeting
Global Trend Insights and Market Data
AI-Driven Enrichment
Strategic Use Cases:
Marketing and Brand Outreach
Product Development and Innovation
Sales and Partnership Development
Market Research and Competitive Analysis
Why Choose Success.ai?
Facebook
TwitterSuccess.ai’s Consumer Marketing Data for Food, Beverage & Consumer Goods Professionals Globally provides a comprehensive dataset tailored for businesses seeking to connect with decision-makers and marketing professionals in these dynamic industries. Covering roles such as brand managers, marketing strategists, and product developers, this dataset offers verified contact details, decision-maker insights, and actionable business data.
With access to over 700 million verified global profiles, Success.ai ensures your marketing, sales, and research efforts are powered by accurate, continuously updated, and AI-validated data. Backed by our Best Price Guarantee, this solution is essential for businesses aiming to lead in the food, beverage, and consumer goods sectors.
Why Choose Success.ai’s Consumer Marketing Data?
Verified Contact Data for Precision Targeting
Comprehensive Coverage Across Global Markets
Continuously Updated Datasets
Ethical and Compliant
Data Highlights:
Key Features of the Dataset:
Comprehensive Professional Profiles
Advanced Filters for Precision Campaigns
Regional Trends and Consumer Insights
AI-Driven Enrichment
Strategic Use Cases:
Marketing Campaigns and Brand Outreach
Product Development and Launch Strategies
Sales and Partnership Development
Market Research and Competitive Analysis
Why Choose Success.ai?
Best Price Guarantee
Seamless Integration
Data Acc...
Facebook
TwitterMSZSI: Multi-Scale Zonal Statistics [AgriClimate] Inventory
--------------------------------------------------------------------------------------
MSZSI is a data extraction tool for Google Earth Engine that aggregates time-series remote sensing information to multiple administrative levels using the FAO GAUL data layers. The code at the bottom of this page (metadata) can be pasted into the Google Earth Engine JavaScript code editor and ran at https://code.earthengine.google.com/.
Please refer to the associated publication:
Peter, B.G., Messina, J.P., Breeze, V., Fung, C.Y., Kapoor, A. and Fan, P., 2024. Perspectives on modifiable spatiotemporal unit problems in remote sensing of agriculture: evaluating rice production in Vietnam and tools for analysis. Frontiers in Remote Sensing, 5, p.1042624.
https://www.frontiersin.org/journals/remote-sensing/articles/10.3389/frsen.2024.1042624
Input options:
[1] Country of interest
[2] Start and end year
[3] Start and end month
[4] Option to mask data to a specific land-use/land-cover type
[5] Land-use/land-cover type code from CGLS LULC
[6] Image collection for data aggregation
[7] Desired band from the image collection
[8] Statistics type for the zonal aggregations
[9] Statistic to use for annual aggregation
[10] Scaling options
[11] Export folder and label suffix
Output: Two CSVs containing zonal statistics for each of the FAO GAUL administrative level boundaries
Output fields: system:index, 0-ADM0_CODE, 0-ADM0_NAME, 0-ADM1_CODE, 0-ADM1_NAME, 0-ADMN_CODE, 0-ADMN_NAME, 1-AREA_PERCENT_LULC, 1-AREA_SQM_LULC, 1-AREA_SQM_ZONE, 2-X_2001, 2-X_2002, 2-X_2003, ..., 2-X_2020, .geo
PREPROCESSED DATA DOWNLOAD
The datasets available for download contain zonal statistics at 2 administrative levels (FAO GAUL levels 1 and 2). Select countries from Southeast Asia and Sub-Saharan Africa (Cambodia, Indonesia, Lao PDR, Myanmar, Philippines, Thailand, Vietnam, Burundi, Kenya, Malawi, Mozambique, Rwanda, Tanzania, Uganda, Zambia, Zimbabwe) are included in the current version, with plans to extend the dataset to contain global metrics. Each zip file is described below and two example NDVI tables are available for preview.
Key: [source, data, units, temporal range, aggregation, masking, zonal statistic, notes]
Currently available:
MSZSI-V2_V-NDVI-MEAN.tar: [NASA-MODIS, NDVI, index, 2001–2020, annual mean, agriculture, mean, n/a]
MSZSI-V2_T-LST-DAY-MEAN.tar: [NASA-MODIS, LST Day, °C, 2001–2020, annual mean, agriculture, mean, n/a]
MSZSI-V2_T-LST-NIGHT-MEAN.tar: [NASA-MODIS, LST Night, °C, 2001–2020, annual mean, agriculture, mean, n/a]
MSZSI-V2_R-PRECIP-SUM.tar: [UCSB-CHG-CHIRPS, Precipitation, mm, 2001–2020, annual sum, agriculture, mean, n/a]
MSZSI-V2_S-BDENS-MEAN.tar: [OpenLandMap, Bulk density, g/cm3, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200]
MSZSI-V2_S-ORGC-MEAN.tar: [OpenLandMap, Organic carbon, g/kg, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200]
MSZSI-V2_S-PH-MEAN.tar: [OpenLandMap, pH in H2O, pH, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200]
MSZSI-V2_S-WATER-MEAN.tar: [OpenLandMap, Soil water, % at 33kPa, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200]
MSZSI-V2_S-SAND-MEAN.tar: [OpenLandMap, Sand, %, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200]
MSZSI-V2_S-SILT-MEAN.tar: [OpenLandMap, Silt, %, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200]
MSZSI-V2_S-CLAY-MEAN.tar: [OpenLandMap, Clay, %, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200]
MSZSI-V2_E-ELEV-MEAN.tar: [MERIT, [elevation, slope, flowacc, HAND], [m, degrees, km2, m], static, n/a, agriculture, mean, n/a]
Coming soon
MSZSI-V2_C-STAX-MEAN.tar: [OpenLandMap, Soil taxonomy, category, static, n/a, agriculture, area sum, n/a]
MSZSI-V2_C-LULC-MEAN.tar: [CGLS-LC100-V3, LULC, category, 2015–2019, mode, none, area sum, n/a]
Data sources:
/*/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// MSZSI: Multi-Scale Zonal Statistics Inventory Authors: Brad G. Peter, Department of Geography, University of Alabama Joseph Messina, Department of Geography, University of Alabama Austin Raney, Department of Geography, University of Alabama Rodrigo E. Principe, AgriCircle AG Peilei Fan, Department of Geography, Environment, and Spatial Sciences, Michigan State University Citation: Peter, Brad; Messina, Joseph; Raney, Austin; Principe, Rodrigo; Fan, Peilei, 2021, 'MSZSI: Multi-Scale Zonal Statistics Inventory', https://doi.org/10.7910/DVN/YCUBXS, Harvard Dataverse, V# SEAGUL: Southeast Asia Globalization, Urbanization, Land and Environment Changes http://seagul.info/ https://lcluc.umd.edu/projects/divergent-local-responses-globalization-urbanization-land-transition-and-environmental This project was made possible by the the NASA Land-Cover/Land-Use Change Program (Grant #: 80NSSC20K0740)
Facebook
TwitterThe MOD13Q1 V6.1 product provides a Vegetation Index (VI) value at a per pixel basis. There are two primary vegetation layers. The first is the Normalized Difference Vegetation Index (NDVI) which is referred to as the continuity index to the existing National Oceanic and Atmospheric Administration-Advanced Very High Resolution Radiometer (NOAA-AVHRR) derived NDVI. The second vegetation layer is the Enhanced Vegetation Index (EVI) that minimizes canopy background variations and maintains sensitivity over dense vegetation conditions. The EVI also uses the blue band to remove residual atmosphere contamination caused by smoke and sub-pixel thin cloud clouds. The MODIS NDVI and EVI products are computed from atmospherically corrected bi-directional surface reflectances that have been masked for water, clouds, heavy aerosols, and cloud shadows. Documentation: User's Guide Algorithm Theoretical Basis Document (ATBD) General Documentation
Facebook
TwitterThis dataset contains estimates of the number of persons per 30 arc-second grid cell consistent with national censuses and population registers. There is one image for each modeled year. General Documentation Note: Because this collection has a pyramid policy of MEAN, zooming out results in information loss. Calculations need to be performed at native resolution. The Gridded Population of World Version 4 (GPWv4), Revision 11 models the distribution of global human population for the years 2000, 2005, 2010, 2015, and 2020 on 30 arc-second (approximately 1 km) grid cells. Population is distributed to cells using proportional allocation of population from census and administrative units. Population input data are collected at the most detailed spatial resolution available from the results of the 2010 round of censuses, which occurred between 2005 and 2014. The input data are extrapolated to produce population estimates for each modeled year.
Facebook
TwitterThe MOD11A1 V6.1 product provides daily land surface temperature (LST) and emissivity values in a 1200 x 1200 kilometer grid. The temperature value is derived from the MOD11_L2 swath product. Above 30 degrees latitude, some pixels may have multiple observations where the criteria for clear-sky are met. When this occurs, the pixel value is the average of all qualifying observations. Provided along with both the day-time and night-time surface temperature bands and their quality indicator layers are MODIS bands 31 and 32 and six observation layers. Documentation: User's Guide Algorithm Theoretical Basis Document (ATBD) General Documentation
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This dataset provides insights into the Indian developer community on GitHub, one of the world’s largest platforms for developers to collaborate, share, and contribute to open-source projects. Whether you're interested in analyzing trends, understanding community growth, or identifying popular programming languages, this dataset offers a comprehensive look at the profiles of GitHub users from India.
The dataset includes anonymized profile information for a diverse range of GitHub users based in India. Key features include: - Username: Unique identifier for each user (anonymized) - Location: City or region within India - Programming Languages: Most commonly used languages per user - Repositories: Public repositories owned and contributed to - Followers and Following: Social network connections within the platform - GitHub Join Date: Date the user joined GitHub - Organizations: Affiliated organizations (if publicly available)
This dataset is curated from publicly available GitHub profiles with a specific focus on Indian users. It is inspired by the need to understand the growth of the tech ecosystem in India, including the languages, tools, and topics that are currently popular among Indian developers. This dataset aims to provide valuable insights for recruiters, data scientists, and anyone interested in the open-source contributions of Indian developers.
This dataset is perfect for: - Data scientists looking to explore and visualize developer trends - Recruiters interested in talent scouting within the Indian tech ecosystem - Tech enthusiasts who want to explore the dynamics of India's open-source community - Students and educators looking for real-world data to practice analysis and modeling
Facebook
TwitterExponentially Expanded AI Programmer Training Dataset (Quantum, Classical, Agentic, Multi-Domain, Production-Ready)
Purpose:
This dataset is designed for maximum breadth, depth, and diversity. It is a plug-and-play, production-grade JSONL set for training truly autonomous, agentic AI programmers—covering quantum/classical algorithms, all major languages, many real-world domains, and full-spectrum agentic behaviors, validation, and compliance.
1. Quantum Algorithmic… See the full description on the dataset page: https://huggingface.co/datasets/SpiralGanglionNeuronLabyrinths/autonomous-agency-trainingset.
Facebook
TwitterThis dataset provides monthly summaries of evapotranspiration (ET) data from OpenET v2.0 image collections for the period 2008-2023 for all National Watershed Boundary Dataset subwatersheds (12-digit hydrologic unit codes [HUC12s]) in the US that overlap the spatial extent of OpenET datasets. For each HUC12, this dataset contains spatial aggregation statistics (minimum, mean, median, and maximum) for each of the ET variables from each of the publicly available image collections from OpenET for the six available models (DisALEXI, eeMETRIC, geeSEBAL, PT-JPL, SIMS, SSEBop) and the Ensemble image collection, which is a pixel-wise ensemble of all 6 individual models after filtering and removal of outliers according to the median absolute deviation approach (Melton and others, 2022). Data are available in this data release in two different formats: comma-separated values (CSV) and parquet, a high-performance format that is optimized for storage and processing of columnar data. CSV files containing data for each 4-digit HUC are grouped by 2-digit HUCs for easier access of regional data, and the single parquet file provides convenient access to the entire dataset. For each of the ET models (DisALEXI, eeMETRIC, geeSEBAL, PT-JPL, SIMS, SSEBop), variables in the model-specific CSV data files include: -huc12: The 12-digit hydrologic unit code -ET: Actual evapotranspiration (in millimeters) over the HUC12 area in the month calculated as the sum of daily ET interpolated between Landsat overpasses -statistic: Max, mean, median, or min. Statistic used in the spatial aggregation within each HUC12. For example, maximum ET is the maximum monthly pixel ET value occurring within the HUC12 boundary after summing daily ET in the month -year: 4-digit year -month: 2-digit month -count: Number of Landsat overpasses included in the ET calculation in the month -et_coverage_pct: Integer percentage of the HUC12 with ET data, which can be used to determine how representative the ET statistic is of the entire HUC12 -count_coverage_pct: Integer percentage of the HUC12 with count data, which can be different than the et_coverage_pct value because the “count” band in the source image collection extends beyond the “et” band in the eastern portion of the image collection extent For the Ensemble data, these additional variables are included in the CSV files: -et_mad: Ensemble ET value, computed as the mean of the ensemble after filtering outliers using the median absolute deviation (MAD) -et_mad_count: The number of models used to compute the ensemble ET value after filtering for outliers using the MAD -et_mad_max: The maximum value in the ensemble range, after filtering for outliers using the MAD -et_mad_min: The minimum value in the ensemble range, after filtering for outliers using the MAD -et_sam: A simple arithmetic mean (across the 6 models) of actual ET average without outlier removal Below are the locations of each OpenET image collection used in this summary: DisALEXI: https://developers.google.com/earth-engine/datasets/catalog/OpenET_DISALEXI_CONUS_GRIDMET_MONTHLY_v2_0 eeMETRIC: https://developers.google.com/earth-engine/datasets/catalog/OpenET_EEMETRIC_CONUS_GRIDMET_MONTHLY_v2_0 geeSEBAL: https://developers.google.com/earth-engine/datasets/catalog/OpenET_GEESEBAL_CONUS_GRIDMET_MONTHLY_v2_0 PT-JPL: https://developers.google.com/earth-engine/datasets/catalog/OpenET_PTJPL_CONUS_GRIDMET_MONTHLY_v2_0 SIMS: https://developers.google.com/earth-engine/datasets/catalog/OpenET_SIMS_CONUS_GRIDMET_MONTHLY_v2_0 SSEBop: https://developers.google.com/earth-engine/datasets/catalog/OpenET_SSEBOP_CONUS_GRIDMET_MONTHLY_v2_0 Ensemble: https://developers.google.com/earth-engine/datasets/catalog/OpenET_ENSEMBLE_CONUS_GRIDMET_MONTHLY_v2_0
Facebook
TwitterThe Sentinel-1 mission provides data from a dual-polarization C-band Synthetic Aperture Radar (SAR) instrument at 5.405GHz (C band). This collection includes the S1 Ground Range Detected (GRD) scenes, processed using the Sentinel-1 Toolbox to generate a calibrated, ortho-corrected product. The collection is updated daily. New assets are ingested within two days after they become available. This collection contains all of the GRD scenes. Each scene has one of 3 resolutions (10, 25 or 40 meters), 4 band combinations (corresponding to scene polarization) and 3 instrument modes. Use of the collection in a mosaic context will likely require filtering down to a homogeneous set of bands and parameters. See this article for details of collection use and preprocessing. Each scene contains either 1 or 2 out of 4 possible polarization bands, depending on the instrument's polarization settings. The possible combinations are single band VV, single band HH, dual band VV+VH, and dual band HH+HV: VV: single co-polarization, vertical transmit/vertical receive HH: single co-polarization, horizontal transmit/horizontal receive VV + VH: dual-band cross-polarization, vertical transmit/horizontal receive HH + HV: dual-band cross-polarization, horizontal transmit/vertical receive Each scene also includes an additional 'angle' band that contains the approximate incidence angle from ellipsoid in degrees at every point. This band is generated by interpolating the 'incidenceAngle' property of the 'geolocationGridPoint' gridded field provided with each asset. Each scene was pre-processed with Sentinel-1 Toolbox using the following steps: Thermal noise removal Radiometric calibration Terrain correction using SRTM 30 or ASTER DEM for areas greater than 60 degrees latitude, where SRTM is not available. The final terrain-corrected values are converted to decibels via log scaling (10*log10(x)). For more information about these pre-processing steps, please refer to the Sentinel-1 Pre-processing article. For further advice on working with Sentinel-1 imagery, see Guido Lemoine's tutorial on SAR basics and Mort Canty's tutorial on SAR change detection. This collection is computed on-the-fly. If you want to use the underlying collection with raw power values (which is updated faster), see COPERNICUS/S1_GRD_FLOAT.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Overview The Stack Overflow Developer Survey Dataset represents one of the most trusted and comprehensive sources of information about the global developer community. Collected by Stack Overflow through its annual survey, the dataset provides insights into the demographics, preferences, habits, and career paths of developers.
This dataset is frequently used for: - Analyzing trends in programming languages, tools, and technologies. - Understanding developer job satisfaction, compensation, and work environments. - Studying global and regional differences in developer demographics and experience.
The data has of two CSV files, "survey_results_public" that consist of data and "survey_results_schema" that describes each column in detail.
Data Dictionary: All the details are in "survey_results_schema.csv"
Demographic & Background Information - Respondent: A unique identifier for each survey participant. - MainBranch: Describes whether the respondent is a professional developer, student, hobbyist, etc. - Country: The country where the respondent lives. - Age: The respondent's age. - Gender: The gender identity of the respondent. - Ethnicity: Ethnic background (when available). - EdLevel: The highest level of formal education completed. - UndergradMajor: The respondent's undergraduate major. - Hobbyist: Indicates whether the person codes as a hobby (Yes/No).
Employment & Professional Experience - Employment: Employment status (full-time, part-time, unemployed, student, etc.). - DevType: Types of developer roles the respondent identifies with (e.g., Web Developer, Data Scientist). - YearsCode: Number of years the respondent has been coding. - YearsCodePro: Number of years coding professionally. - JobSat: Job satisfaction level. - CareerSat: Career satisfaction level. - WorkWeekHrs: Approximate hours worked per week. - RemoteWork: Whether the respondent works remotely and how frequently.
Compensation - CompTotal: Total compensation in USD (including salary, bonuses, etc.). - CompFreq: Frequency of compensation (e.g., yearly, monthly).
Learning & Education - LearnCode: How the respondent first learned to code (e.g., online courses, university). - LearnCodeOnline: Online resources used (e.g., YouTube, freeCodeCamp). - LearnCodeCoursesCert: Whether the respondent has taken online courses or earned certifications.
Technology & Tools - LanguageHaveWorkedWith: Programming languages the respondent has used. - LanguageWantToWorkWith: Languages the respondent is interested in learning or using more. - DatabaseHaveWorkedWith: Databases the respondent has experience with. - PlatformHaveWorkedWith: Platforms used (e.g., Linux, AWS, Android). - OpSys: The operating system used most often. - NEWCollabToolsHaveWorkedWith: Collaboration tools used (e.g., Slack, Teams, Zoom). - NEWStuck: How often the respondent feels stuck when coding. - ToolsTechHaveWorkedWith: Frameworks and technologies respondents have worked with.
Online Presence & Community - SOAccount: Whether the respondent has a Stack Overflow account. - SOPartFreq: How often the respondent participates on Stack Overflow. - SOVisitFreq: Frequency of visiting Stack Overflow. - SOComm: Whether the respondent feels welcome in the Stack Overflow community. - OpenSourcer: Level of involvement in open-source contributions.
Opinions & Preferences - WorkChallenge: Challenges faced at work (e.g., unclear requirements, unrealistic expectations). - JobFactors: Important job factors (e.g., salary, work-life balance, technologies used). - MentalHealth: Questions on how mental health affects or is affected by their job.