Skip to main content
Powered by ShareScore

Find research datasets worth reusing

Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.

138

datasets available to search

ShareScore release 0.7.1

Reset

Dataset results

138 results for “Geospatial”

Learn how ShareScore rates datasets ↗
edi60/100

LAGOS-US GEO v1.0: Data module of lake geospatial ecological context at multiple spatial and temporal scales in the conterminous U.S.

The LAGOS-US GEO data package is one of the core data modules of LAGOS-US, an extensible research-ready platform designed to study the 479,950 lakes and reservoirs larger than or equal to 1 ha in the conterminous US (48 states plus the District of Columbia). The GEO module contains data on the geospatial and temporal ecological setting (e.g., land use, terrain, soils, climate, hydrology, atmospheric deposition, and human influence) quantified at multiple spatial divisions (e.g., equidistant buffers around lakes, watersheds, hydrologic basins, political boundaries, and ecoregions) relevant to the LAGOS-US lake population defined in the LAGOS-US LOCUS module. The database design that supports the LAGOS-US research platform was created based on several important design features: lakes are the fundamental unit of consideration, all lakes in the spatial extent above the minimum size must be represented, and most information is connected to individual lakes. The design is modular, interoperable (the modules can be used with each other), and extensible (future database modules can be developed and used in the LAGOS-US research platform by others). Users are encouraged to use the other two core data modules that are part of the LAGOS-US platform: LOCUS (location, identifiers, and physical characteristics of lakes and their watersheds) and LIMNO (in situ lake physical, chemical, and biological measurements through time) that are each found in their own data packages.

openCC BYSep 2022View details →
edi56/100

MacroSheds: a synthesis of long-term biogeochemical, hydroclimatic, and geospatial data from small watershed ecosystem studies

The MacroSheds dataset is an ongoing synthesis of data records from small-watershed ecosystem studies, including those managed by LTER, CZO/CZNet, NEON, and many other networks. While details of instrumentation and sampling methods vary across these studies, the types of data collected and the questions that motivate their analysis are remarkably similar. Nevertheless, little effort toward the compilation of these datasets has previously been made, and comparative watershed analyses have remained limited in scale. The MacroSheds dataset includes daily time series of streamflow (discharge) and stream chemistry, as well as precipitation and precipitation chemistry where available. Each of the 200+ watersheds included in the MacroSheds dataset is described by a comprehensive collection of watershed attributes, summarized from a diverse set of gridded data products. A subset of these watershed attributes conform as closely as possible to the specifications of the CAMELS dataset (https://ral.ucar.edu/solutions/products/camels), allowing the MacroSheds dataset to function as a small-watershed supplement to that corpus, and a resource for hydrologists as well as biogeochemists and watershed ecosystem scientists. Data paper: https://aslopubs.onlinelibrary.wiley.com/doi/full/10.1002/lol2.10325 Data dashboard for visualization: macrosheds.org R package for data access and analysis: https://github.com/MacroSHEDS/macrosheds R package vignettes: https://macrosheds.org/pages/vignettes Live dataset changelog: https://macrosheds.org/pages/changelog.html Questions: mail@macrosheds.org

openCustomOct 2024View details →
edi56/100

LAGOS - Lake nitrogen, phosphorus, stoichiometry, and geospatial data for a 17-state region of the U.S.

This dataset includes information about total nitrogen (TN) concentrations, total phosphorus (TP) concentrations, TN:TP stoichiometry, and 12 driver variables that might predict nutrient concentrations and ratios. All observed values came from LAGOSLIMNO v. 1.054.1 and LAGOSGEO v. 1.03 (LAke multi-scaled GeOSpatial and temporal database), an integrated database of lake ecosystems (Soranno et al. 2015). LAGOS contains a complete census of lakes greater than or equal to 4 ha with corresponding geospatial information for a 17-state region of the U.S., and a subset of the lakes has observational data on morphometry and chemistry. Approximately 54 different sources of data were compiled for this dataset and were mostly generated by government agencies (state, federal, tribal) and universities. Here, we compiled chemistry data from lakes with concurrent observations of TN and TP from the summer stratified season (June 15-September 15) in the most recent 10 years of data included in LAGOSLIMNO v. 1.054.1 (2002-2011). We report the median TN, TP and molar TN:TP values for each lake, which was calculated as the grand median of each yearly median value. We also include data for lake and landscape characteristics that might be important controls on lake nutrients, including: land use (agricultural, pasture, row crop, urban, forest), nitrogen deposition, temperature, precipitation, hydrology (baseflow), maximum depth, and the ratio of lake area to watershed area, which is used to approximate residence time. These data were used to identify drivers of lake nutrient stoichiometry at sub-continental and regional scales (Collins et al, submitted). This research was supported by the NSF Macrosystems Biology program (awards EF-1065786 and EF-1065818) and by the NSF Postdoctoral Research Fellowship in Biology (DBI-1401954).

openCC (other)Dec 2022View details →
zenodo52/100

Shoreline series of the Doniños coastal system, NW Iberia (1945-2020): A Geospatial Dataset

<p>This repository stores shoreline data spanning from 1945 to 2020, derived from aerial photography and orthophotos, for the Doni&ntilde;os coastal system in NW Iberia. The shoreline indicator is defined as the boundary between vegetated dunes and bare beach sand. The methodology and dataset are detailed in the following publication:</p> <p><em><strong>Rita Gonz&aacute;lez-Villanueva, Marti&ntilde;o Pastoriza, Armand Hern&aacute;ndez, Rafael Carballeira, Alberto S&aacute;ez, Roberto Bao. "Primary drivers of dune cover and shoreline dynamics: A conceptual model based on the Iberian Atlantic coast." Geomorphology, Volume 423, 2023, 108556, ISSN 0169-555X. <a href="https://doi.org/10.1016/j.geomorph.2022.108556" target="_new">https://doi.org/10.1016/j.geomorph.2022.108556</a>.</strong></em></p> <p>The shoreline dataset is encapsulated in a single GEOJSON file: <code>SHORES_1945_2020.geojson</code>. This dataset encompasses the shorelines mapped from all available aerial data for the Doni&ntilde;os coastal system, on the Galician coast, NW Iberia, from 1945 to 2020. It comprises a total of 15 shorelines. The geospatial layer employs the ETRS89/UTM zone 29N coordinate system (EPSG: 25829).</p> <p><strong>SHORES_1945_2020.geojson</strong>: This layer presents the shorelines, where each feature is a MultiLinestring with the following attributes:</p> <ul> <li><code>objectid</code>: Identifier of the shoreline.</li> <li><code>date</code>: Date of the shoreline capture, in month/year format (mm/yyyy).</li> <li><code>SHAPE_Leng</code>: Length of the mapped shoreline, in meters.</li> <li><code>Source</code>: Source of the original image from which the shoreline was derived, including the Centro Nacional de Informaci&oacute;n Geogr&aacute;fica (CNIG) and the Centro Cartogr&aacute;fico y Fotogr&aacute;fico del Ej&eacute;rcito del Aire (CECAF).</li> <li><code>Type</code>: 'O' signifies an orthophotograph, and 'AP' signifies an aerial photograph.</li> <li><code>GEO_Error</code>: Georeferencing error for each manually georeferenced photograph.</li> <li><code>geometry</code>: The type of geometry used in the file, specified as MultiLineString.</li> <li><code>coordinates</code>: UTM coordinates for each node in the multiline.</li> </ul>

opencc-by-4.0Mar 2024View details →
edi52/100

LAGOS-NE-LIMNO v1.087.3: A module for LAGOS-NE, a multi-scaled geospatial and temporal database of lake ecological context and water quality for thousands of U.S. Lakes: 1925-2013

This data package, LAGOS-NE-LIMNO v1.087.3, is 1 of 5 data packages associated with the LAGOS-NE database-- the LAke multi-scaled GeOSpatial and temporal database. With this release, only this data package is being updated and users are expected to use prior releases of the other types of data. Please see the attached additional documentation for a full description of the changes that have been made for this new release.The data packages that make up LAGOS-NE include the following information on lakes and reservoirs in 17 lake-rich states in the Northeastern and upper Midwestern U.S. (1) LAGOS-NE-LOCUS v1.01: lake location and physical characteristics for all lakes greater than one hectare. (2) LAGOS-NE-GEO v1.05: ecological context (i.e., the land use, geologic, climatic, and hydrologic setting of lakes) for all lakes and for all spatial resolutions, also called ‘zones’ (i.e., ecoregions, states, counties). These geospatial data were created by processing national-scale and publicly-accessible datasets to quantify numerous metrics at multiple spatial resolutions. (3) LAGOS-NE-LIMNO v1.087.3: in-situ measurements of lake water quality from the past three decades for approximately 2,600-12,000 lakes, depending on the variable. This module was created by harmonizing 87 water quality datasets from federal, state, tribal, and non-profit agencies, university researchers, and citizen scientists. This module includes variables that are most commonly measured by state agencies and researchers for studying eutrophication. For each water quality data value, we also include metadata related to the sampling program, methods, qualifiers with data flags from the original program (qual, not standardized for LAGOS-NE), censor codes from our quality control procedures (censorcode, standardized for LAGOS-NE), and the date of each sample. (4) LAGOS-NE-GIS v1.0: the GIS data layers for lakes, wetlands, and streams, as well as the spatial resolutions that were used to create the LAGOS-N

openCC (other)Jul 2019View details →
edi52/100

SBC LTER: Reef: Kelp Forest Community Dynamics: Transect geospatial metadata

The data table provides summaries of depth information (mean, standard deviation and coefficient of variation) for all of the transects surveyed as part of the SBC LTER Kelp Forest Monitoring program. All data are expressed in meters, reference to mean lower low water (MLLW). Each value is the result of 160 observations, four at each meter (n=160). The sampling locations in this dataset are 40 meter transects at nine reef sites along the mainland coast of the Santa Barbara Channel and at two sites on the north side of Santa Cruz Island. The PDF document provides descriptive information of the transect such as headings and relative locations of the points along the transect. Data were recorded in 2010 and 2011, except that IVEE transect 3, 4, 5, 6, 7, and 8 were recorded in 2024.

openCC (other)Oct 2025View details →
edi52/100

Gaviota Fire Perimeter (Santa Barbara County, CA), June 9, 2004 - From Geospatial Multi-Agency Coordination Group (GeoMAC)

The Gaviota Fire burned from 2004-06-05 to 2004-06-12, 15 miles west of Santa Barbara, Santa Barbara County. Approximately 7440 acres were burned (information per http://cdfdata.fire.ca.gov). This dataset contains a KML polygon showing the extent of the fire on 2004-06-09, and was acquired by request from the Geospatial Multi-Agency Coordination Group (GeoMAC, http://www.geomac.gov). These data are based upon input from incident intelligence sources, Global Positioning System (GPS) data, and infrared (IR) imagery. See methods for more information.

openCC (other)Oct 2022View details →
edi52/100

Tea Fire Perimeter (Santa Barbara County, CA), November 15, 2008 - From Geospatial Multi-Agency Coordination Group (GeoMAC)

The Tea Fire burned from 2008-11-13 to 2008-11-17, Montecito, Cold Springs Creek and Hot Springs Road, Santa Barbara County. Approximately 1940 acres were burned (information per http://cdfdata.fire.ca.gov). This dataset contains a KML polygon showing the extent of the fire on 2008-11-15, and was acquired by request from the Geospatial Multi-Agency Coordination Group (GeoMAC, http://www.geomac.gov). These data are based upon input from incident intelligence sources, Global Positioning System (GPS) data, and infrared (IR) imagery. See methods for more information.

openCC (other)Oct 2022View details →
edi52/100

Jesusita Fire Perimeter (Santa Barbara County, CA), May 10, 2009 - From Geospatial Multi-Agency Coordination Group (GeoMAC)

The Jesusita Fire burned from 2008-05-05 to 2008-05-18, Northwest of Mission Canyon and Santa Barbara City, Santa Barbara County. Approximately 8733 acres were burned (information per http://cdfdata.fire.ca.gov). This dataset contains a KML polygon showing the extent of the fire on 2008-05-10, and was acquired by request from the Geospatial Multi-Agency Coordination Group (GeoMAC, http://www.geomac.gov). These data are based upon input from incident intelligence sources, Global Positioning System (GPS) data, and infrared (IR) imagery. See methods for more information.

openCC (other)Oct 2022View details →
zenodo48/100

Modern China Geospatial Database - Main Dataset

<p>MCGD_Data_V2.2 contains all the data that we have collected on locations in modern China, plus a number of locations outside of China that we encounter frequently in historical sources on China. All further updates will appear under the name "MCGD_Data" with a time stamp (e.g., MCGD_Data2023-06-21)</p> <p>You can also have access to this dataset and all the datasets that the ENP-China makes available on GitLab: https://gitlab.com/enpchina/IndexesEnp</p> <p>Altogether there are 464,970 entries. The data include seven variables:<br>- Name: &nbsp;Place names and their variants in Chinese, pinyin, and any recorded transliteration<br>- Prov_Zh: Chinese province names in Chinese characters (新疆, 江蘇, 河北, etc.)<br>- Prov_Py: Chinese province names in pinyin<br>- LAT: Latitude coordinates<br>- LONG: Longitude coordinates<br>- LocID: Location identifiers<br>- NameID: Location name identifiers</p> <p>The Name IDs all start with H followed by seven digits. This is the internal ID system of MCGD.</p> <p>Locations IDs that start with "D" are data points extracted from China Historical GIS (Harvard University); those that start with "E" are locations extracted from the data points in Geonames or data points we have added from various map sources.</p> <p>One of the main features of the MCGD Main Dataset is the systematic collection and compilation of place names from non-Chinese language historical sources. Locations were designated in transliteration systems that are hardly comprehensible today, which makes it very difficult to find the actual locations they correspond to. This dataset allows for the conversion from these obsolete transliterations to the current names and geocoordinates.</p> <p>From June 2021 onward, we have adopted a different file naming system to keep track of versions. From MCGD_Data_V1 we have moved to MCGD_Data_V2. In June 2022, we introduced time stamps, which result in the following naming convention: MCGD_Data_YYYY.MM.DD.&nbsp;</p> <p>&nbsp;</p> <p><strong>UPDATES</strong></p> <p><strong>MCGD_Data2025_08_06</strong> introduces a significant update with the addition of the <strong>&lsquo;Code&rsquo;</strong> column. This column categorizes place names as follows:</p> <ul> <li> <p><strong>A</strong>: Canonical Chinese name</p> </li> <li> <p><strong>C</strong>: Alternative Chinese name</p> </li> <li> <p><strong>P</strong>: Romanized name in pinyin</p> </li> <li> <p><strong>W</strong>: Romanized name in another transliteration system</p> </li> </ul> <p>When the codes <strong>P</strong> or <strong>W</strong> are doubled (<strong>PP</strong>, <strong>WW</strong>), this indicates that the place name does not match any existing Chinese name in the dataset. These unmatched names will be reviewed and linked progressively, rather than through a systematic batch process, due to their high volume.The coding system is designed to facilitate name-matching operations between MCGD and place names extracted from historical sources using programming tools. It also enables filtering for more precise and efficient matching. The dataset contains a total of <strong>472,749 entries</strong>.</p> <p>MCGD_Data2025_02_28 includes a major change with the duplication of all the locations listed under Beijing, Shanghai, Tianjin, and Chongqing (北京, 上海, 天津, 重慶) and their listing under the name of the provinces to which they belonge origially before the creation of the four special municipalities after 1949. This is meant to facilitate the matching of data from historical sources. Each location has a unique NameID. Altogether there are 472,818 entries</p> <p>MCGD_Data2025_02_27 inclues an update on locations extracted from&nbsp; Minguo zhengfu ge yuanhui keyuan yishang zhiyuanlu 國民政府各院部會科員以上職員錄 (Directory of staff members and above in the ministries and committees of the National Government). Nanjing: Guomin zhengfu wenguanchu yinzhuju 國民政府文官處印鑄局國民政府文官處印鑄局, 1944). We also made corrections in the Prov_Py and Prov_Zh columns as there were some misalignments between the pinyin name and the name in Chines characters. The file now includes 465,128 entries.</p> <p>MCGD_Data2024_03_23 includes an update on locations in Taiwan from the Asia Directories. Altogether there are 465,603 entries (of which 187 place names without geocoordinates, labelled in the Lat Long columns as "Unknown").</p> <p>MCGD_Data2023.12.22 contains all the data that we have collected on locations in China, whatever the period. Altogether there are 465,603 entries (of which 187 place names without geocoordinates, labelled in the Lat Long columns as "Unknown"). The dataset also includes locations outside of China for the purpose of matching such locations to the place names extracted from historical sources. For example, one may need to locate individuals born outside of China. Rather than maintaining two separate files, we made the decision to incorporate all the place names found in historical sources in the gazetteer. Such place names can easily be removed by selecting all the entries where the 'Province' data is missing.</p>

opencc-by-4.0Nov 2021View details →
zenodo48/100

Modern China Geospatial Database - Republican China Dataset

<p><strong>MCGD_Rep</strong> is a sample of spatial data for China in the first half of twentieth century (1900-1949). The data was extracted from the MCGD Main Dataset. It is based mostly on the list of <em>xian</em> (county) seats in 1931 [Source: Zang, Lihe&nbsp; 臧励龢, ed. Zhongguo gujin diming da cidian 中国古今地名大辞典. Shanghai 上海: Commercial Press, 1931], with the addition of some external data [Source: Crow Newspaper Directories]. By and large, it presents a list of the major locations in China between 1900 and 1949. It contains 1,977 entries with the following variables: name in Chinese, name in pinyin; name of the province in Chinese and in pinyin; latitude and longitude, and Name ID and Location ID.</p>

opencc-by-4.0Nov 2021View details →
zenodo48/100

Geospatial Modelling of Australia's National Electricity Market - Dataset

<p>This dataset contains information relating to the topology of Australia&#39;s largest electricity transmission network, along with details pertaining to the technical and economic characteristics of generators operating within this grid. Information has been compiled from publicly available datasets released by the Australian Energy Market Operator (AEMO) [1, 2] and Geoscience Australia (GA) [3, 4, 5]. Potential applications include the development of economic dispatch, power-flow, and unit commitment models.</p> <p>The network is comprised of 912 nodes, 1406 AC edges, and three HVDC links. Information regarding forward and reverse power-flow limits for two AC interconnectors is also provided. Latitude and longitude coordinates are given for each node, with the network based off of geospatial datasets obtained from GA [3, 4, 5]. Signals for electricity demand at each node were derived using regional load profiles in combination with population data obtained from the Australian Bureau of Statistics (ABS) [6]. Allocation methods outlined in [7, 8] were used to disaggregate regional load profiles according to the geospatial distribution of Australia&#39;s population. Construction of the generator dataset involved compiling information obtained from AEMO&#39;s Market Management System Data Model (MMSDM) [1] and National Transmission Network Development Plan (NTNDP)&nbsp;[2] datasets. Historic generator dispatch signals were also obtained from AEMO [1], allowing the output of market models to be compared with realised outcomes.</p> <p>For further information regarding the contents of each csv file please refer to <code>dataset_summary.pdf</code>. Jupyter Notebooks at [9] contain the Python code necessary to reproduce these datasets.</p> <p><strong>Version history:</strong></p> <p><strong>v1.3 - Documentation update:</strong></p> <ul> <li>The document summarising datasets, <code>dataset_summary.pdf</code>, has been updated.</li> </ul> <p><strong>v1.2 - Startup cost correction:</strong></p> <ul> <li>Startup cost column labels in <code>generators.csv</code> were mistakenly switched (specifically, SU_COST_WARM and SU_COST_HOT). This has now been corrected.</li> </ul> <p><strong>v1.1 - Transmission line parameters and demand allocation update</strong></p> <ul> <li><strong>Transmission lines: </strong>Line resistance and shunt susceptance values have been updated. Transmission line lengths and voltages have also been added to <code>network_edges.csv</code>. AC interconnector information is split over two files to better capture aggregate flow limits defined over the New South Wales - Victoria interconnector. Connection points for these interconnectors are described in <code>network_ac_interconnector_links.csv</code>, while <code>network_ac_interconnector_flow_limits.csv</code> contains aggregate forward and reverse power flow limits.</li> <li><strong>Demand allocation: </strong>The algorithm used to approximate demand at different nodes has been updated. The new method constructs a Voronoi tessellation based on network nodes. These cells are then overlapped with geospatial ABS population data, which are used to estimate the number of people served by each node.</li> </ul> <p><strong>v1.0 - First release</strong></p>

opencc-by-4.0Apr 2018View details →
zenodo48/100

A high-resolution 4D geospatial laser scan dataset of the beach at Mariakerke Bad, Belgium

<p>This dataset contains a high resolution (in both time and space) laser scan data set of a 1-year measurement campaign in 2017 and 2018 in the seaside resort of Mariakerke Bad in Belgium. The measurements consist of 8417 hourly laserscans of a 400 meter stretch of beach. The measurement campained was performed to study variations in shoreward sand transport at urbanized beaches.&nbsp;</p> <p>Laserscan data is stored in local coordinates. Time dependent corrections per laserscan epoch are provided next to a global transformation matrix to transform the local coordinates to the Belgium Lambert 2008 coordinate system.</p> <p>This data is provided as is and is licensed under the Creative Commons Attribution 4.0 International (CC-BY-4.0). See the provided PDF on more information about the CC-BY-4.0.</p> <p>Version 1 contained an error in the global transformation matrix. Version 2 corrects this.</p>

opencc-by-4.0Feb 2024View details →
zenodo48/100

Geospatial Input Datasets for Urban Teleconnections Analysis

<p>This dataset includes all of the necessary input layers for the `gamut` software package. Layers were downloaded from the sources in the references&nbsp;and were either directly used in the `gamut` software or processed prior to being used in the software. Processing and data information for each dataset is included in the metadata.</p>

opencc-by-4.0Apr 2021View details →
zenodo48/100

Pan-EU Landmask: 10m Resolution Geospatial Land Coverage with Administrative Boundary details on country and regional level

<p><strong>Pan-EU Land Mask Summary</strong></p> <p>Considering the land mask for pan-EU, we will closely match the data coverage of <a href="https://land.copernicus.eu/pan-european">https://land.copernicus.eu/pan-european</a> i.e. the official selection of countries listed here: <a href="https://land.copernicus.eu/portal_vocabularies/geotags/eea39">https://lanEEA39d.copernicus.eu/portal_vocabularies/geotags/eea39</a>.</p> <p>There are a total of three landmask files available, each of which is aligned with the standard spatial/temporal resolution and sizes of <a href="https://ai4soilheath.eu">AI4SoilHealth</a> Data Cube specifications, which is: Xmin = 900,000, Ymin = 899,000, Xmax = 7,401,000, Ymax = 5,501,000, with Coordinate reference system of epsg:3035. Additionally, these files include a corresponding look-up table that provides explanations for the values present in the raster data. The scripts used to generate these masks can be found <a href="https://github.com/AI4SoilHealth/SoilHealthDataCube/tree/main/paneu_landmask">here</a>.</p> <p>The masks are:</p> <ol> <li> <p>Landmask</p> </li> <li> <p>ISO-code country mask</p> </li> <li> <p>NUTS3 mask</p> </li> </ol> <p><strong>Name convention</strong></p> <p>To ensure consistency and ease of use across and within the projects, the files here are named according to the standard OpenLandMap file-naming convention. The OpenLandMap file-naming convention works with 10 fields that basically define the most important properties of the data, this way users can search files, prepare data analysis etc, without even needing to access or open files. The 10 fields include:</p> <ol> <li> <p>Generic variable name: country.code</p> </li> <li> <p>Variable procedure combination i.e. method standard (standard abbreviation): iso.3166</p> </li> <li> <p>Position in the probability distribution / variable type: c</p> </li> <li> <p>Spatial support (usually horizontal block) in m or km: 30m</p> </li> <li> <p>Depth reference or depth interval e.g. below (&quot;b&quot;), above (&quot;a&quot;) ground or at surface (&quot;s&quot;): s</p> </li> <li> <p>Time reference begin time (YYYYMMDD): 20210101</p> </li> <li> <p>Time reference end time: 20211231</p> </li> <li> <p>Bounding box (2 letters max): eu&nbsp;</p> </li> <li> <p>EPSG code: epsg.3035</p> </li> <li> <p>Version code i.e. creation date: v20230722</p> </li> </ol> <p>An example of a file-name based on the description above:</p> <p><em>country.code_iso.3166_c_100m_s_20210101_20211231_eu_epsg.3035_v20230722</em></p> <p><strong>Landmask</strong></p> <p>The basic principle to create the land mask is to include as much as land as possible, to avoid missing any land pixels and ensure precise differentiation between land, ocean and inland water bodies.</p> <p>Two reference datasets are used,&nbsp;</p> <ol> <li> <p><a href="https://esa-worldcover.org/en">WorldCover</a>, 10 m resolution.</p> </li> <li> <p><a href="https://www.mapsforeurope.org/datasets/euro-global-map">EuroGlobalMap</a>, with shapefiles of administrative boundaries, inland water bodies, ocean and landmask.</p> </li> </ol> <p>When generating the land mask, the two reference datasets in a way that:</p> <ul> <li> <p>If either of the two reference datasets identifies a pixel as land, it is considered a land pixel in our mask.&nbsp;</p> </li> <li> <p>Regarding ocean and inland water bodies, a pixel is classified as a water pixel only when both reference datasets confirm its identification as water.</p> </li> </ul> <p>The landmask consists of 4 values:</p> <ul> <li> <p>10: not in the pan-EU area, i.e. out of mapping scope</p> </li> <li> <p>1: land</p> </li> <li> <p>2: inland water</p> </li> <li> <p>3: ocean</p> </li> </ul> <p>This landmask is available in 10m, 30m, 100m, 250m, and 1km resolution formats respectively. The coarse resolution landmasks (&gt;10 m) are generated by resampling from the 10m resolution base map using resampling method &ldquo;min&rdquo; in GDAL. This &ldquo;min&rdquo; method allows taking the minimum values from the contributing pixels, to keep as much land as possible.</p> <p><strong>ISO-3166 country code mask</strong></p> <p>This ISO-3166 country code mask is created from <a href="https://www.mapsforeurope.org/datasets/euro-global-map">EuroGlobalMap</a> country shapefile. This mask is available in 10m, 30m and 100m resolution. In this raster file, each country is assigned a unique value, which allows for the interpretation and analysis of data associated with a specific country.</p> <p>The values are assigned to each country according to iso-3166 country code, which can be found in the corresponding look-up table. The coarse resolution masks (&gt;10 m) are generated by resampling from the 10m resolution base map using resampling method &ldquo;mode&rdquo; in GDAL.</p> <p><strong>NUTS-3 mask</strong></p> <p>The nuts-3 code mask is created from the European NUTS3 shapefile. In this raster file, each unique NUT3 level area is assigned a unique value, which allows for the interpretation and analysis of data associated with specific NUTS3 regions.</p> <p>The values of pixels and its associated meanings can be found in the corresponding look-up table. This nut-3 code mask is available in 10m, 30m and 100m resolution formats. The coarse resolution masks (&gt;10 m) are generated by resampling from the 10m resolution base map using resampling method &ldquo;mode&rdquo; in GDAL.</p> <p>It should be noted that the ISO-code country mask covers a more extensive area compared to the NUTS3 mask. This broader coverage includes countries like Ukraine and others beyond the NUTS3 mask, while NUTS mask shows more details about regional&nbsp;administrative boundaries.</p>

opencc-by-4.0Jul 2023View details →
edi48/100

LAGOS-NE-LOCUS v1.01: A module for LAGOS-NE, a multi-scaled geospatial and temporal database of lake ecological context and water quality for thousands of U.S. Lakes: 1925-2013

This data package, LAGOS-NE-LOCUS v1.01, is 1 of 5 data packages associated with the LAGOS-NE database-- the LAke multi-scaled GeOSpatial and temporal database. Three of the data packages each contain different types of data for 51,101 lakes and reservoirs larger than 4 ha in 17 lake-rich U.S. states to support research on thousands of lakes. These three package are: (1) LAGOS-NE-LOCUS v1.01: lake location and physical characteristics for all lakes. (2) LAGOS-NEGEO v1.05: ecological context (i.e., the land use, geologic, climatic, and hydrologic setting of lakes) for all lakes. These geospatial data were created by processing national-scale and publicly-accessible datasets to quantify numerous metrics at multiple spatial resolutions. And, (3) LAGOS-NE-LIMNO v1.087.1: in-situ measurements of lake water quality from the past three decades for approximately 2,600-12,000 lakes, depending on the variable. This module was created by harmonizing 87 water quality datasets from federal, state, tribal, and non-profit agencies, university researchers, and citizen scientists. The other two data packages contain supporting data for the LAGOS-NE database: (4) LAGOS-NE-GIS v1.0: the GIS data layers for lakes, wetlands, and streams, as well as the spatial resolutions that were used to create the LAGOS-NE-GEO module. (5) LAGOS-NE-RAWDATA: the original 87 datasets of lake water quality prior to processing, the R code that converts the original data formats into LAGOS-NE data format, and the log file from this procedure to create LAGOS-NE. This latter data package supports the reproducibility of LAGOS-NE-LIMNO. The LAGOS-NE-LOCUS v1.01 module includes information on the physical location and features of all lakes > 4 ha. The information provided for this population of lakes includes: lake unique identifiers, lake area, perimeter, latitude and longitude, and the zone IDs that the lake is located within (e.g., state, county, the hydrologic unit at each level (4, 8, and 12). Citation for

openCC0Apr 2017View details →
edi48/100

LAGOS-NE-GEO v1.05: A module for LAGOS-NE, a multi-scaled geospatial and temporal database of lake ecological context and water quality for thousands of U.S. Lakes: 1925-2013

This data package, LAGOS-NE-GEO v1.05, is 1 of 5 data packages associated with the LAGOS-NE database-- the LAke multi-scaled GeOSpatial and temporal database. Three of the data packages each contain different types of data for 51,101 lakes and reservoirs larger than 4 ha in 17 lake-rich U.S. states to support research on thousands of lakes. These three package are: (1) LAGOS-NE-LOCUS: lake location and physical characteristics for all lakes. (2) LAGOS-NE-GEO: ecological context (i.e., the land use, geologic, climatic, and hydrologic setting of lakes) for all lakes. These geospatial data were created by processing national-scale and publicly-accessible datasets to quantify numerous metrics at multiple spatial resolutions. And, (3) LAGOS-NE-LIMNO: in-situ measurements of lake water quality from the past three decades for approximately 2,600-12,000 lakes, depending on the variable. This module was created by harmonizing 87 water quality datasets from federal, state, tribal, and non-profit agencies, university researchers, and citizen scientists. The other two data packages contain supporting data for the LAGOS-NE database: (4) LAGOS-NE-GIS v1.0: the GIS data layers for lakes, wetlands, and streams, as well as the spatial resolutions that were used to create the LAGOS-NEGEO module. (5) LAGOS-NE-RAWDATA: the original 87 datasets of lake water quality prior to processing, the R code that converts the original data formats into LAGOS-NE data format, and the log file from this procedure to create LAGOS-NE. This latter data package supports the reproducibility of LAGOS-NE-LIMNO. The LAGOS-NE-GEO v1.05 module includes information on the ecological context of the census lakes, all lakes > 4 ha in the study extent, their watersheds, and their regions. The information provided in the data tables for this module is organized into three main themes: CHAG - climate, hydrology, atmospheric deposition of nitrogen and sulfur, and surficial geology; LULC - land use/cover, impervious co

openCC0May 2017View details →
edi48/100

Geospatial data for Luquillo Mountains, Puerto Rico: Mean annual precipitation, elevation, watershed outlines, and rain gage locations

The data archive is here: https://doi.org/10.5066/F74F1PM2 please use this DOI when citing this data set. These geospatial data sets were developed as part of a new analysis of all known current and historical rain gages in the Luquillo Mountains, Puerto Rico published in the journal article Murphy, S.F., Stallard, R.F., Scholl, M.A., Gonzalez, G., and Torres-Sanchez, A.J., 2017, Reassessing rainfall in the Luquillo Mountains, Puerto Rico: Local and global ecohydrological implications: PLOS One 12(7): e0180987, p. 1-26, https://doi.org/10.1371/journal.pone.0180987. That article provides a revised map of mean annual precipitation developed using elevation regression functions and residual interpolation, and that map is presented here in a raster file. Most previous forest- and watershed-wide estimates of precipitation (and evapotranspiration, as inferred by a water balance) have assumed that precipitation increases consistently with elevation in the Luquillo Mountains; therefore, precipitation in leeward Luquillo watersheds has been overestimated by up to 40%.Because the Luquillo Mountains often serve as a wet tropical archetype in global assessments of basic ecohydrological processes, these revised estimates are relevant to regional and global assessments of runoff efficiency, hydrologic effects of reforestation, geomorphic processes, and climate change. \<para\> Support for this work was provided by grants BSR-8811902, DEB-9411973, DEB-9705814 , DEB-0080538, DEB-0218039 , DEB-0620910 , DEB-1239764, DEB-1546686, and DEB-1831952 from the National Science Foundation to the University of Puerto Rico as part of the Luquillo Long-Term Ecological Research Program. Additional support provided by the University of Puerto Rico and the International Institute of Tropical Forestry, USDA Forest Service.\</para\>

openCC (other)Apr 2023View details →
edi48/100

SBC LTER: Reef: Geospatial structure of microsatellite markers for the giant kelp, Macrocystis pyrifera, Santa Barbara CA, 2009

Data package includes data and R code for the examination of geospatial genetic structure (SGS) and simulation of inbreeding in giant kelp (Macrocystis pyrifera) from the Santa Barbara Channel, California. Data are reported for microsatellite markers from individual giant kelp plants from Carpinteria Reef, Mohawk Reef and Goleta Bay, collected during September 2009. Relative X and Y coordinates (meters) were recorded for each specimen sampled. R code consists of two scripts, a) to calculate mean number of alleles per locus, and observed and expected heterozygosity, and b) to simulate self-fertilization and sibling/cousin relationships. These data were presented in: Johansson, Mattias L, Raimondi, Peter T, Reed, Daniel C, Coelho, Nelson C, Serrão, Ester A, Alberto, Filipe A. In press. Looking into the black box: simulating the role of self-fertilization and mortality in the genetic structure of Macrocystis pyrifera. Molecular Ecology, 22:4842–4854. These data are also available from: Johansson ML, Raimondi PT, Reed DC, Coelho NC, Serrão EA, Alberto FA (2013) Data from: Looking into the black box: simulating the role of self-fertilization and mortality in the genetic structure of Macrocystis pyrifera. Dryad Digital Repository. doi:10.5061/dryad.s1b07.

openCC (other)Oct 2022View details →
zenodo44/100

Geospatial Dataset of GNSS Anomalies and Political Violence Events

<p><strong>Geospatial Dataset of GNSS Anomalies and Political Violence Events</strong></p> <p><strong>Overview</strong></p> <p>The <strong>Geospatial Dataset of GNSS Anomalies and Political Violence Events&nbsp;</strong>is a collection of data that integrates aircraft flight information, GNSS (Global Navigation Satellite System) anomalies, and political violence events from the ACLED (Armed Conflict Location &amp; Event Data Project) database.</p> <p><strong>Dataset Files</strong></p> <p>The dataset consists of three CSV files:</p> <ol> <li><strong>Daily_GNSS_Anomalies_and_ACLED-2023-V1.csv</strong></li> <ul> <li><strong>Description:</strong> Contains all grids and dates that had aircraft traffic during 2023.</li> <li><strong>Number of Records:</strong> 6,777,228</li> <li><strong>Purpose:</strong> Provides a complete view of aircraft movements and associated data, including grids without any GNSS anomalies.</li> </ul> <li><strong>Daily_GNSS_Anomalies_and_ACLED-2023-V2.csv</strong></li> <ul> <li><strong>Description:</strong> A filtered version of V1, including only the grids and dates where GNSS anomalies (jumps or gaps) were reported.</li> <li><strong>Number of Records:</strong> 718,237</li> <li><strong>Purpose:</strong> Focuses on areas and times with GNSS anomalies for targeted analysis.</li> </ul> <li><strong>Monthly_GNSS_Anomalies_and_ACLED-2023-V9.csv</strong></li> <ul> <li><strong>Description:</strong> Contains aggregated monthly data for each grid cell, combining GNSS anomalies and ACLED political violence events. Summarizes aircraft traffic, anomaly counts, and conflict activity at a monthly resolution.</li> <li><strong>Number of Records:</strong> 25,770</li> <li><strong>Purpose:</strong> Enables temporal trend analysis and spatial correlation studies between GNSS interference and political violence, using reduced data volume suitable for modeling and visualization.</li> </ul> </ol> <p><strong>Data Fields:&nbsp; &nbsp; </strong>Daily_GNSS_Anomalies_and_ACLED-2023-V1.csv and&nbsp;Daily_GNSS_Anomalies_and_ACLED-2023-V2.csv</p> <ol> <li><strong>grid_id</strong></li> <ul> <li><strong>Description:</strong> Unique identifier for a grid cell on Earth measuring 0.5 degrees latitude by 0.5 degrees longitude.</li> <li><strong>Format:</strong> String combining latitude and longitude (e.g., -10.0_-36.0).</li> </ul> <li><strong>day</strong></li> <ul> <li><strong>Description:</strong> Date of the recorded data.</li> <li><strong>Format:</strong> YYYY-MM-DD (e.g., 2023-03-28).</li> </ul> <li><strong>geometry</strong></li> <ul> <li><strong>Description:</strong> Polygon coordinates of the grid cell in Well-Known Text (WKT) format.</li> <li><strong>Format:</strong> POLYGON((longitude latitude, ...)) (e.g., POLYGON((-36.0 -10.0, -35.5 -10.0, -35.5 -9.5, -36.0 -9.5, -36.0 -10.0))).</li> </ul> <li><strong>flights</strong></li> <ul> <li><strong>Description:</strong> Number of aircraft flights that passed through the grid on that day.</li> <li><strong>Format:</strong> Integer (e.g., 28).</li> </ul> <li><strong>GPS_jumps</strong></li> <ul> <li><strong>Description:</strong> Number of reported GNSS "jump" anomalies (possible spoofing incidents) in the grid on that day.</li> <li><strong>Format:</strong> Integer (e.g., 1).</li> </ul> <li><strong>GPS_gaps</strong></li> <ul> <li><strong>Description:</strong> Number of reported GNSS "gap" anomalies, indicating gaps in aircraft routes, in the grid on that day.</li> <li><strong>Format:</strong> Integer (e.g., 0).</li> </ul> <li><strong>gaps_density</strong></li> <ul> <li><strong>Description:</strong> Density of GNSS gaps, calculated as the number of gaps divided by the number of flights.</li> <li><strong>Format:</strong> Decimal (e.g., 0).</li> </ul> <li><strong>jumps_density</strong></li> <ul> <li><strong>Description:</strong> Density of GNSS jumps, calculated as the number of jumps divided by the number of flights.</li> <li><strong>Format:</strong> Decimal (e.g., 0.035714286).</li> </ul> <li><strong>event_id_cnty</strong></li> <ul> <li><strong>Description:</strong> ACLED event ID corresponding to political violence events in the grid on that day.</li> <li><strong>Format:</strong> String (e.g., BRA69267).</li> </ul> <li><strong>disorder_type</strong></li> <ul> <li><strong>Description:</strong> Type of disorder as classified by ACLED (e.g., "Political violence").</li> <li><strong>Format:</strong> String.</li> </ul> <li><strong>event_type</strong></li> <ul> <li><strong>Description:</strong> General category of the event according to ACLED (e.g., "Violence against civilians").</li> <li><strong>Format:</strong> String.</li> </ul> <li><strong>sub_event_type</strong></li> <ul> <li><strong>Description:</strong> Specific subtype of the event as per ACLED classification (e.g., "Attack").</li> <li><strong>Format:</strong> String.</li> </ul> <li><strong>acled_count</strong></li> <ul> <li><strong>Description:</strong> Number of ACLED events in the grid on that day.</li> <li><strong>Format:</strong> Integer (e.g., 1).</li> </ul> <li><strong>acled_flag</strong></li> <ul> <li><strong>Description:</strong> Indicator of ACLED event presence in the grid on that day (0 for no events, 1 for one or more events).</li> <li><strong>Format:</strong> Integer (0 or 1).</li> </ul> </ol> <p><strong>&nbsp;</strong></p> <p><strong>Data Fields: </strong>Monthly_GNSS_Anomalies_and_ACLED-2023-V9.csv</p> <p>The file contains monthly aggregated GNSS anomaly and ACLED event data per grid cell. The structure and meaning of each field are detailed below:</p> <ol> <li><strong>grid_id</strong></li> <ul> <li><strong>Description</strong>: Unique identifier for a grid cell on Earth measuring 0.5&deg; latitude by 0.5&deg; longitude.</li> <li><strong>Format</strong>: String combining latitude and longitude (e.g., -0.5_-79.0).</li> </ul> <li><strong>year_month</strong></li> <ul> <li><strong>Description</strong>: Month and year of the aggregated data.</li> <li><strong>Format</strong>: String in Mon-YY format (e.g., Jan-23).</li> </ul> <li><strong>geometry</strong></li> <ul> <li><strong>Description</strong>: Polygon coordinates of the grid cell in Well-Known Text (WKT) format.</li> <li><strong>Format</strong>: POLYGON((longitude latitude, ...))<br>(e.g., POLYGON((-79.0 -0.5, -78.5 -0.5, -78.5 0.0, -79.0 0.0, -79.0 -0.5))).</li> </ul> <li><strong>flights</strong></li> <ul> <li><strong>Description</strong>: Total number of aircraft flights that passed through the grid cell during the month.</li> <li><strong>Format</strong>: Integer (e.g., 1230).</li> </ul> <li><strong>GPS_jumps</strong></li> <ul> <li><strong>Description</strong>: Total number of GNSS "jump" anomalies (possible spoofing events) in the grid cell during the month.</li> <li><strong>Format</strong>: Integer (e.g., 13).</li> </ul> <li><strong>GPS_gaps</strong></li> <ul> <li><strong>Description</strong>: Total number of GNSS "gap" anomalies, indicating interruptions in aircraft routes, during the month.</li> <li><strong>Format</strong>: Integer (e.g., 0).</li> </ul> <li><strong>event_id_cnty</strong></li> <ul> <li><strong>Description</strong>: Semicolon-separated list of ACLED event IDs associated with the grid cell during the month.</li> <li><strong>Format</strong>: String (e.g., ECU3151;ECU3158;ECU3150).</li> </ul> <li><strong>disorder_type</strong></li> <ul> <li><strong>Description</strong>: Semicolon-separated list of disorder types (e.g., "Political violence", "Demonstrations") reported by ACLED in that grid cell during the month.</li> <li><strong>Format</strong>: String.</li> </ul> <li><strong>event_type</strong></li> <ul> <li><strong>Description</strong>: Semicolon-separated list of high-level ACLED event types (e.g., "Riots", "Protests").</li> <li><strong>Format</strong>: String.</li> </ul> <li><strong>sub_event_type</strong></li> </ol> <ul> <li><strong>Description</strong>: Semicolon-separated list of detailed subtypes of ACLED events (e.g., "Mob violence", "Armed clash").</li> <li><strong>Format</strong>: String.</li> </ul> <ol> <li><strong>acled_count</strong></li> </ol> <ul> <li><strong>Description</strong>: Total number of ACLED conflict events in the grid cell during the month.</li> <li><strong>Format</strong>: Integer (e.g., 2).</li> </ul> <ol> <li><strong>acled_flag</strong></li> </ol> <ul> <li><strong>Description</strong>: Conflict presence indicator: 1 if any ACLED event occurred in the grid cell during the month, otherwise 0.</li> <li><strong>Format</strong>: Integer (0 or 1).</li> </ul> <ol> <li><strong>gaps_density</strong></li> </ol> <ul> <li><strong>Description</strong>: Monthly density of GNSS gaps, calculated as GPS_gaps / flights.</li> <li><strong>Format</strong>: Decimal (e.g., 0.0).</li> </ul> <ol> <li><strong>jumps_density</strong></li> </ol> <ul> <li><strong>Description</strong>: Monthly density of GNSS jumps, calculated as GPS_jumps / flights.</li> <li><strong>Format</strong>: Decimal (e.g., 0.0106).</li> </ul> <p><strong>&nbsp;</strong></p> <p><strong>Data Sources</strong></p> <ul> <li><strong>GNSS Anomalies Data:</strong></li> <ul> <li>Calculated from ADS-B (Automatic Dependent Surveillance-Broadcast) messages obtained via the OpenSky Network's Trino database.</li> <li>GNSS anomalies include "jumps" (potential spoofing incidents) and "gaps" (interruptions in aircraft route data).</li> </ul> <li><strong>Political Violence Events Data:</strong></li> <ul> <li>Sourced from the ACLED database, which provides detailed information on political violence and protest events worldwide.</li> </ul> </ul> <p><strong>Temporal and Spatial Coverage</strong></p> <ul> <li><strong>Temporal Coverage:</strong></li> <ul> <li>From January 1, 2023, to December 31, 2023.</li> <li>Daily records provide temporal granularity for time-series analysis.</li> </ul> <li><strong>Spatial Coverage:</strong></li> <ul> <li>Global coverage with grid cells measuring 0.5 degrees latitude by 0.5 degrees longitude.</li> <li>Each grid cell represents an area on Earth's surface, facilitating spatial analysis.</li> </ul> </ul> <p><strong>Usage and Applications</strong></p> <ul> <li><strong>Security Analysis:</strong></li> <ul> <li>Assess potential correlations between GNSS anomalies and political violence events.</li> <li>Identify regions with increased risk of GNSS spoofing or signal disruption.</li> </ul> <li><strong>Research and Development:</strong></li> <ul> <li>Develop models to predict socio-political events based on GNSS anomalies.</li> <li>Study the impact of political instability on aviation safety.</li> </ul> <li><strong>Policy and Decision Making:</strong></li> <ul> <li>Inform aviation authorities and policymakers about regions requiring enhanced navigation security measures.</li> <li>Support conflict analysis and monitoring efforts.</li> </ul> </ul> <p>&nbsp;</p> <p>&nbsp;</p>

opencc-by-4.0Nov 2024View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated datasets

Allen Brain Atlas

Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

Annotated Behaviour and Observability Dataset (ABODe)

ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

DANDI Archive for NWB datasets

DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

International Brain Laboratory public data

The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

OpenNeuro

OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record