This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

This folder contains .gpkg format files for book layover and waypoint places, and auto, boat and train routes that can be loaded into GIS applications such as ArcGIS and QGIS.

Overview:This document describes the 2021 accessibility data released by the Accessibility Observatory at the University of Minnesota. The data are included in the National Accessibility Evaluation Project for 2021, and this information can be accessed for each state in the U.S. at https://access.umn.edu/research/america. The following sections describe the format, naming, and content of the data files.Data Formats: The data files are provided in a Geopackage format. Geopackage (.gpkg) files are an open-source, geospatial filetype that can contain multiple layers of data in a single file, and can be opened with most GIS software, including both ArcGIS and QGIS.Within this zipfile, there are six geopackage files (.gpkg) structured as follows. Each of them contains the blocks shapes layer, results at the block level for all LEHD variables (jobs and workers), with a layer of results for each travel time (5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 minutes). {MPO ID}_tr_2021_0700-0859-avg.gpkg = Average Transit Access Departing Every Minute 7am-9am{MPO ID}_au_2021_08.gpkg = Average Auto Access Departing 8am{MPO ID}_bi_2021_1200_lts1.gpkg = Average Bike Access on LTS1 Network{MPO ID}_bi_2021_1200_lts2.gpkg = Average Bike Access on LTS2 Network{MPO ID}_bi_2021_1200_lts3.gpkg = Average Bike Access on LTS3 Network{MPO ID}_bi_2021_1200_lts4.gpkg = Average Bike Access on LTS4 NetworkFor mapping and geospatial analysis, the blocks shape layer within each geopackage can be joined to the blockid of the access attribute data. Opening and Using Geopackages in ArcGIS:Unzip the zip archiveUse the "Add Data" function in Arc to select the .gpkg fileSelect which layer(s) are needed — always select "main.blocks" as this layer contains the Census block shapes; select any other attribute data layers as well.There are three types of layers in the geopackage file — the "main.blocks" layer is the spatial features layer, and all other layers are either numerical attribute data tables, or the "fieldname_descriptions" metadata layer. The numerical attribute layers are named with the following format:[mode]_[threshold]_minutes[mode] is a two-character code indicating the transport mode used[threshold] is an integer indicating the travel time threshold used for this data layerTo use the data spatially, perform a join between the "main.blocks" layer and the desired numerical data layer, using either the numerical "id" fields, or 15-digit "blockid" fields as join fields.

Overview:This document describes the 2021 accessibility data released by the Accessibility Observatory at the University of Minnesota. The data are included in the National Accessibility Evaluation Project for 2021, and this information can be accessed for each state in the U.S. at https://access.umn.edu/research/america. The following sections describe the format, naming, and content of the data files.Data Formats: The data files are provided in a Geopackage format. Geopackage (.gpkg) files are an open-source, geospatial filetype that can contain multiple layers of data in a single file, and can be opened with most GIS software, including both ArcGIS and QGIS.Within this zipfile, there are six geopackage files (.gpkg) structured as follows. Each of them contains the blocks shapes layer, results at the block level for all LEHD variables (jobs and workers), with a layer of results for each travel time (5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 minutes). {MPO ID}_tr_2021_0700-0859-avg.gpkg = Average Transit Access Departing Every Minute 7am-9am{MPO ID}_au_2021_08.gpkg = Average Auto Access Departing 8am{MPO ID}_bi_2021_1200_lts1.gpkg = Average Bike Access on LTS1 Network{MPO ID}_bi_2021_1200_lts2.gpkg = Average Bike Access on LTS2 Network{MPO ID}_bi_2021_1200_lts3.gpkg = Average Bike Access on LTS3 Network{MPO ID}_bi_2021_1200_lts4.gpkg = Average Bike Access on LTS4 NetworkFor mapping and geospatial analysis, the blocks shape layer within each geopackage can be joined to the blockid of the access attribute data. Opening and Using Geopackages in ArcGIS:Unzip the zip archiveUse the "Add Data" function in Arc to select the .gpkg fileSelect which layer(s) are needed — always select "main.blocks" as this layer contains the Census block shapes; select any other attribute data layers as well.There are three types of layers in the geopackage file — the "main.blocks" layer is the spatial features layer, and all other layers are either numerical attribute data tables, or the "fieldname_descriptions" metadata layer. The numerical attribute layers are named with the following format:[mode]_[threshold]_minutes[mode] is a two-character code indicating the transport mode used[threshold] is an integer indicating the travel time threshold used for this data layerTo use the data spatially, perform a join between the "main.blocks" layer and the desired numerical data layer, using either the numerical "id" fields, or 15-digit "blockid" fields as join fields.

A. Takhtajan defined 35 floristic regions in the world (Takhtajan 1986). The delineation of such floristic regions has been manually georeferenced and is provided here as a spatial vectorial data file (geopackage), suitable to be used in any GIS or mapping software (coordinate reference system: EPSG 4326).

If using this dataset, please cite both Takhtajan's book as well as this data source:

Takhtajan, A. 1986. Floristic Regions of the World. Berkeley: University of California Press.

Rodríguez-Sánchez, Francisco. 2023. Takhtajan's floristic regions of the world (geopackage). https://doi.org/10.5281/zenodo.8206377

Funding: Fondo Europeo de Desarrollo Regional (FEDER) and Consejería de Transformación Económica, Industria, Conocimiento y Universidades of Junta de Andalucía (proyecto US-1381388, Universidad de Sevilla).

We provide the entire dataset of the paper "Dataset of seismic ambient vibrations from the Quaternary Norcia basin (central Italy)" submitted to "Data in Brief" journal, including geophysical and geospatial data.

The dataset was used and analysed in the article:

Di Giulio, G., Ercoli, M., Vassallo, M., Porreca, M. (2020). Investigation of the Norcia basin (Central Italy) through ambient vibration measurements and geological surveys, Engineering Geology, 267, 105501, https://doi.org/10.1016/j.enggeo.2020.105501

The geophysical dataset was collected in the Norcia basin in Central Italy, area struck by a long earthquake sequence during the 2016-2017, including five main-shocks with Mw>5.0.

The Mw 6.5 mainshock occurred on 30 October 2016 close to the town of Norcia. Different degrees of damages were observed during this seismic crisis, with a variable seismic shaking controlled, among many factors, by important 1D and 2D variation of Quaternary fluvio-lacustrine sediments infilling the basin.

Following this seismic sequence, we registered seismic vibration measurements, mainly single-seismic station noise data. We aimed to determine the distribution of resonant frequency (f0) of the basin and, though a join analysis with the available geological information, to infer the subsurface basin architecture.

A total of 60 sites were measured to cover the entire extension in the basin. We deployed seismometers along three transects of a total length of 21 km, mostly along the main structural directions of the basin (i.e. NNW-SSE and NE-SW).

Two 2D arrays of seismic stations with a elicoidal-shaped geometry, and a set of MASW active data were also acquired in the northern sector of the basin, in order to better constrain the seismic velocity of the sedimentary infilling.

In comparison to the data used in the paper Di Giulio et al. (2020), seven additional records have been here recovered across the basin (i.e. N54-N60).

We also provide geospatial ancillary data, both as a complete open-source Geographical Information Systems (GIS) project and as a set of single GeoPackage (.gpkg) and Keyhole Markup Language (.kml) files.

The dataset can be used for different purposes: specific researches on the Norcia basin, comparative studies on similar areas around the world, development of new data modeling/analysis software.

Dataset for: Regional Correlations in the layered deposits of Arabia Terra, Mars

Overview:

This repository contains the map-projected HiRISE Digital Elevation Models (DEMs) and the map-projected HiRISE image for each DEM and for each site in the study. Also contained in the repository is a GeoPackage file (beds_2019_08_28_09_29.gpkg) that contains the dip corrected bed thickness measurements, longitude and latitude positions, and error information for each bed measured in the study. GeoPackage files supersede shapefiles as a standard geospatial data format and can be opened in a variety of open source tools including QGIS, and proprietary tools such as recent versions of ArcGIS. For more information about GeoPackage files, please use https://www.geopackage.org/ as a resource. A more detailed description of columns in the beds_2019_08_28_09_29.gpkg file is described below in a dedicated section. Table S1 from the supplementary is also included as an excel spreadsheet file (table_s1.xlsx).

HiRISE DEMs and Images:

Each HiRISE DEM, and corresponding map-projected image used in the study are included in this repository as GeoTiff files (ending with .tif). The file names correspond to the combination of the HiRISE Image IDs listed in Table 1 that were used to produce the DEM for the site, with the image with the smallest emission angle (most-nadir) listed first. Files ending with “_align_1-DEM-adj.tif” are the DEM files containing the 1 meter per pixel elevation values, and files ending with “_align_1-DRG.tif” are the corresponding map-projected HiRISE (left) image. Table 1 Image Pairs correspond to filenames in this repository in the following way: In Table 1, Sera Crater corresponds to HiRISE Image Pair: PSP_001902_1890/PSP_002047_1890, which corresponds to files: “PSP_001902_1890_PSP_002047_1890_align_1-DEM-adj.tif” for the DEM file and “PSP_001902_1890_PSP_002047_1890_align_1-DRG.tif” for the map-projected image file. Each site is listed below with the DEM and map-projected image filenames that correspond to the site as listed in Table 1. The DEM and Image files can be opened in a variety of open source tools including QGIS, and proprietary tools such as recent versions of ArcGIS.

· Sera

o DEM: PSP_001902_1890_PSP_002047_1890_align_1-DEM-adj.tif

o Image: PSP_001902_1890_PSP_002047_1890_align_1-DRG.tif

· Banes

o DEM: ESP_013611_1910_ESP_014033_1910_align_1-DEM-adj.tif

o Image: ESP_013611_1910_ESP_014033_1910_align_1-DRG.tif

· Wulai 1

o DEM: ESP_028129_1905_ESP_028195_1905_align_1-DEM-adj.tif

o Image: ESP_028129_1905_ESP_028195_1905_align_1-DRG.tif

· Wulai 2

o DEM: ESP_028129_1905_ESP_028195_1905_align_1-DEM-adj.tif

o Image: ESP_028129_1905_ESP_028195_1905_align_1-DRG.tif

· Jiji

o DEM: ESP_016657_1890_ESP_017013_1890_align_1-DEM-adj.tif

o Image: ESP_016657_1890_ESP_017013_1890_align_1-DRG.tif

· Alofi

o DEM: ESP_051825_1900_ESP_051970_1900_align_1-DEM-adj.tif

o Image: ESP_051825_1900_ESP_051970_1900_align_1-DRG.tif

· Yelapa

o DEM: ESP_015958_1835_ESP_016235_1835_align_1-DEM-adj.tif

o Image: ESP_015958_1835_ESP_016235_1835_align_1-DRG.tif

· Danielson 1

o DEM: PSP_002733_1880_PSP_002878_1880_align_1-DEM-adj.tif

o Image: PSP_002733_1880_PSP_002878_1880_align_1-DRG.tif

· Danielson 2

o DEM: PSP_008205_1880_PSP_008930_1880_align_1-DEM-adj.tif

o Image: PSP_008205_1880_PSP_008930_1880_align_1-DRG.tif

· Firsoff

o DEM: ESP_047184_1820_ESP_039404_1820_align_1-DEM-adj.tif

o Image: ESP_047184_1820_ESP_039404_1820_align_1-DRG.tif

· Kaporo

o DEM: PSP_002363_1800_PSP_002508_1800_align_1-DEM-adj.tif

o Image: PSP_002363_1800_PSP_002508_1800_align_1-DRG.tif

Description of beds_2019_08_28_09_29.gpkg:

The GeoPackage file “beds_2019_08_28_09_29.gpkg” contains the dip corrected bed thickness measurements among other columns described below. The file can be opened in a variety of open source tools including QGIS, and proprietary tools such as recent versions of ArcGIS.

(Column_Name: Description)

sitewkn: Site name corresponding to the bed (i.e. Danielson 1)

section: Section ID of the bed (sections contain multiple beds)

meansl: The mean slope (dip) in degrees for the section

meanaz: The mean azimuth (dip-direction) in degrees for the section

ang_error: Angular error for a section derived from individual azimuths in the section

B_1: Plane coefficient 1 for the section

B_2: Plane coefficient 2 for the section

lon: Longitude of the centroid of the Bed

lat: Latitude of the centroid of the Bed

thickness: Thickness of the bed BEFORE dip correction

dipcor_thick: Dip-corrected bed thickness

lon1: Longitude of the centroid of the lower layer for the bed (each bed has a lower and upper layer)

lon2: Longitude of the centroid of the upper layer for the bed

lat1: Latitude of the centroid of the lower layer for the bed

lat2: Latitude of the centroid of the upper layer for the bed

meanc1: Mean stratigraphic position of the lower layer for the bed

meanc2: Mean stratigraphic position of the upper layer for the bed

uuid1: Universally unique identifier of the lower layer for the bed

uuid2: Universally unique identifier of the upper layer for the bed

stdc1: Standard deviation of the stratigraphic position of the lower layer for the bed

stdc2: Standard deviation of the stratigraphic position of the upper layer for the bed

sl1: Individual Slope (dip) of the lower layer for the bed

sl2: Individual Slope (dip) of the upper layer for the bed

az1: Individual Azimuth (dip-direction) of the lower layer for the bed

az2: Individual Azimuth (dip-direction) of the upper layer for the bed

meanz: Mean elevation of the bed

meanz1: Mean elevation of the lower layer for the bed

meanz2: Mean elevation of the upper layer for the bed

rperr1: Regression error for the plane fit of the lower layer for the bed

rperr2: Regression error for the plane fit of the upper layer for the bed

rpstdr1: Standard deviation of the residuals for the plane fit of the lower layer for the bed

rpstdr2: Standard deviation of the residuals for the plane fit of the upper layer for the bed

Overview:This document describes the 2021 accessibility data released by the Accessibility Observatory at the University of Minnesota. The data are included in the National Accessibility Evaluation Project for 2021, and this information can be accessed for each state in the U.S. at https://access.umn.edu/research/america. The following sections describe the format, naming, and content of the data files.Data Formats: The data files are provided in a Geopackage format. Geopackage (.gpkg) files are an open-source, geospatial filetype that can contain multiple layers of data in a single file, and can be opened with most GIS software, including both ArcGIS and QGIS.Within this zipfile, there are six geopackage files (.gpkg) structured as follows. Each of them contains the blocks shapes layer, results at the block level for all LEHD variables (jobs and workers), with a layer of results for each travel time (5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 minutes). {MPO ID}_tr_2021_0700-0859-avg.gpkg = Average Transit Access Departing Every Minute 7am-9am{MPO ID}_au_2021_08.gpkg = Average Auto Access Departing 8am{MPO ID}_bi_2021_1200_lts1.gpkg = Average Bike Access on LTS1 Network{MPO ID}_bi_2021_1200_lts2.gpkg = Average Bike Access on LTS2 Network{MPO ID}_bi_2021_1200_lts3.gpkg = Average Bike Access on LTS3 Network{MPO ID}_bi_2021_1200_lts4.gpkg = Average Bike Access on LTS4 NetworkFor mapping and geospatial analysis, the blocks shape layer within each geopackage can be joined to the blockid of the access attribute data. Opening and Using Geopackages in ArcGIS:Unzip the zip archiveUse the "Add Data" function in Arc to select the .gpkg fileSelect which layer(s) are needed — always select "main.blocks" as this layer contains the Census block shapes; select any other attribute data layers as well.There are three types of layers in the geopackage file — the "main.blocks" layer is the spatial features layer, and all other layers are either numerical attribute data tables, or the "fieldname_descriptions" metadata layer. The numerical attribute layers are named with the following format:[mode]_[threshold]_minutes[mode] is a two-character code indicating the transport mode used[threshold] is an integer indicating the travel time threshold used for this data layerTo use the data spatially, perform a join between the "main.blocks" layer and the desired numerical data layer, using either the numerical "id" fields, or 15-digit "blockid" fields as join fields.

The Digital Geologic-GIS Map of Santa Rosa Island, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (sris_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (sris_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (sris_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (sris_geology_metadata_faq.pdf). Please read the chis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sris_geology_metadata.txt or sris_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Overview This dataset is part of the RhECAST project, focusing on sustainable land use strategies, agroforestry, and computer-based modelling to tackle climate change. Python Script codes available at: - Zenodo: https://doi.org/10.5281/zenodo.15389080 - GitHub: https://github.com/Filbra/ORE_2025 Project Repository: https://doi.org/10.5281/zenodo.13929576 Folder Structure DatasetThis folder contains the following sub-folders:- csv: Contains CSV files related to geospatial or environmental data used in the project.- gpkg: Contains GeoPackage (.gpkg) files, which are used for storing geospatial data in a compact format.

The Digital Surficial Geologic-GIS Map of Noatak National Preserve and Vicinity, Alaska is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (noat_surficial_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (noat_surficial_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (noat_surficial_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (noat_geology_gis_readme_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (noat_surficial_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (noat_surficial_geology_metadata_faq.pdf). Please read the noat_geology_gis_readme_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (noat_surficial_geology_metadata.txt or noat_surficial_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:250,000 and United States National Map Accuracy Standards features are within (horizontally) 127 meters or 416.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Dataset for: Bedding scale correlation on Mars in western Arabia Terra

A.M. Annex et al.

Data Product Overview

This repository contains all source data for the publication. Below is a description of each general data product type, software that can load the data, and a list of the file names along with the short description of the data product.

HiRISE Digital Elevation Models (DEMs).

HiRISE DEMs produced using the Ames Stereo Pipeline are in geotiff format ending with ‘*X_0_DEM-adj.tif’, the “X” prefix denotes the spatial resolution of the data product in meters. Geotiff files are able to be read by free GIS software like QGIS.

HiRISE map-projected imagery (DRGs).

Map-projected HiRISE images produced using the Ames Stereo Pipeline are in geotiff format ending with ‘*0_Y_DRG-cog.tif’, the “Y” prefix denotes the spatial resolution of the data product in centimeters. Geotiff files are able to be read by free GIS software like QGIS. The DRG files are formatted as COG-geotiffs for enhanced compression and ease of use.

3D Topography files (.ply).

Traingular Mesh versions of the HiRISE/CTX topography data used for 3D figures in “.ply” format. Meshes are greatly geometrically simplified from source files. Topography files can be loaded in a variety of open source tools like ParaView and Meshlab. Textures can be applied using embedded texture coordinates.

3D Geological Model outputs (.vtk)

VTK 3D file format files of model output over the spatial domain of each study site. VTK files can be loaded by ParaView open source software. The “block” files contain the model evaluation over a regular grid over the model extent. The “surfaces” files contain just the bedding surfaces as interpolated from the “block” files using the marching cubes algorithm.

Geological Model geologic maps (geologic_map.tif).

Geologic maps from geological models are standard geotiffs readable by conventional GIS software. The maximum value for each geologic map is the “no-data” value for the map. Geologic maps are calculated at a lower resolution than the topography data for storage efficiency.

Beds Geopackage File (.gpkg).

Geopackage vector data file containing all mapped layers and associated metadata including dip corrected bed thickness as well as WKB encoded 3D linestrings representing the sampled topography data to which the bedding orientations were fit. Geopackage files can be read using GIS software like QGIS and ArcGIS as well as the OGR/GDAL suite. A full description of each column in the file is provided below.

    Column
    Type
    Description




    uuid
    String
    unique identifier


    stratum_order
    Real
    0-indexed bed order


    section
    Real
    section number


    layer_id
    Real
    bed number/index


    layer_id_bk
    Real
    unused backup bed number/index


    source_raster
    String
    dem file path used


    raster
    String
    dem file name


    gsd
    Real
    ground sampling distant for dem


    wkn
    String
    well known name for dem


    rtype
    String
    raster type


    minx
    Real
    minimum x position of trace in dem crs


    miny
    Real
    minimum y position of trace in dem crs


    maxx
    Real
    maximum x position of trace in dem crs


    maxy
    Real
    maximum y position of trace in dem crs


    method
    String
    internal interpolation method


    sl
    Real
    slope in degrees


    az
    Real
    azimuth in degrees


    error
    Real
    maximum error ellipse angle


    stdr
    Real
    standard deviation of the residuals


    semr
    Real
    standard error of the residuals


    X
    Real
    mean x position in CRS


    Y
    Real
    mean y position in CRS


    Z
    Real
    mean z position in CRS


    b1
    Real
    plane coefficient 1


    b2
    Real
    plane coefficient 2


    b3
    Real
    plane coefficient 3


    b1_se
    Real
    standard error plane coefficient 1


    b2_se
    Real
    standard error plane coefficient 2


    b3_se
    Real
    standard error plane coefficient 3


    b1_ci_low
    Real
    plane coefficient 1 95% confidence interval low


    b1_ci_high
    Real
    plane coefficient 1 95% confidence interval high


    b2_ci_low
    Real
    plane coefficient 2 95% confidence interval low


    b2_ci_high
    Real
    plane coefficient 2 95% confidence interval high


    b3_ci_low
    Real
    plane coefficient 3 95% confidence interval low


    b3_ci_high
    Real
    plane coefficient 3 95% confidence interval high


    pca_ev_1
    Real
    pca explained variance ratio pc 1


    pca_ev_2
    Real
    pca explained variance ratio pc 2


    pca_ev_3
    Real
    pca explained variance ratio pc 3


    condition_number
    Real
    condition number for regression


    n
    Integer64
    number of data points used in regression


    rls
    Integer(Boolean)
    unused flag


    demeaned_regressions
    Integer(Boolean)
    centering indicator


    meansl
    Real
    mean section slope


    meanaz
    Real
    mean section azimuth


    angular_error
    Real
    angular error for section


    mB_1
    Real
    mean plane coefficient 1 for section


    mB_2
    Real
    mean plane coefficient 2 for section


    mB_3
    Real
    mean plane coefficient 3 for section


    R
    Real
    mean plane normal orientation vector magnitude


    num_valid
    Integer64
    number of valid planes in section


    meanc
    Real
    mean stratigraphic position


    medianc
    Real
    median stratigraphic position


    stdc
    Real
    standard deviation of stratigraphic index


    stec
    Real
    standard error of stratigraphic index


    was_monotonic_increasing_layer_id
    Integer(Boolean)
    monotonic layer_id after projection to stratigraphic index


    was_monotonic_increasing_meanc
    Integer(Boolean)
    monotonic meanc after projection to stratigraphic index


    was_monotonic_increasing_z
    Integer(Boolean)
    monotonic z increasing after projection to stratigraphic index


    meanc_l3sigma_std
    Real
    lower 3-sigma meanc standard deviation


    meanc_u3sigma_std
    Real
    upper 3-sigma meanc standard deviation


    meanc_l2sigma_sem
    Real
    lower 3-sigma meanc standard error


    meanc_u2sigma_sem
    Real
    upper 3-sigma meanc standard error


    thickness
    Real
    difference in meanc


    thickness_fromz
    Real
    difference in Z value


    dip_cor
    Real
    dip correction


    dc_thick
    Real
    thickness after dip correction


    dc_thick_fromz
    Real
    z thickness after dip correction


    dc_thick_dev
    Integer(Boolean)
    dc_thick <= total mean dc_thick


    dc_thick_fromz_dev
    Integer(Boolean)
    dc_thick <= total mean dc_thick_fromz


    thickness_fromz_dev
    Integer(Boolean)
    dc_thick <= total mean thickness_fromz


    dc_thick_dev_bg
    Integer(Boolean)
    dc_thick <= section mean dc_thick


    dc_thick_fromz_dev_bg
    Integer(Boolean)
    dc_thick <= section mean dc_thick_fromz


    thickness_fromz_dev_bg
    Integer(Boolean)
    dc_thick <= section mean thickness_fromz


    slr
    Real
    slope in radians


    azr
    Real
    azimuth in radians


    meanslr
    Real
    mean slope in radians


    meanazr
    Real
    mean azimuth in radians


    angular_error_r
    Real
    angular error of section in radians


    pca_ev_1_ok
    Integer(Boolean)
    pca_ev_1 < 99.5%


    pca_ev_2_3_ratio
    Real
    pca_ev_2/pca_ev_3


    pca_ev_2_3_ratio_ok
    Integer(Boolean)
    pca_ev_2_3_ratio > 15


    xyz_wkb_hex
    String
    hex encoded wkb geometry for all points used in regression

Geological Model input files (.gpkg).

Four geopackage (.gpkg) files represent the input dataset for the geological models, one per study site as specified in the name of the file. The files contain most of the columns described above in the Beds geopackage file, with the following additional columns. The final seven columns (azimuth, dip, polarity, formation, X, Y, Z) constituting the actual parameters used by the geological model (GemPy).

    Column
    Type
    Description




    azimuth_mean
    String
    Mean section dip azimuth 


    azimuth_indi
    Real
    Individual bed azimuth


    azimuth
    Real
    Azimuth of trace used by the geological model


    dip
    Real
    Dip for the trace used by the geological mode


    polarity
    Real
    Polarity of the dip vector normal vector 


    formation
    String
    String representation of layer_id required for GemPy models


    X
    Real
    X position in the CRS of the sampled point on the trace


    Y
    Real
    Y position in the CRS of the sampled point on the trace


    Z
    Real
    Z position in the CRS of the sampled point on the trace

Stratigraphic Column Files (.gpkg).

Stratigraphic columns computed from the Geological Models come in three kinds of Geopackage vector files indicated by the postfixes _sc, rbsc, and rbssc. File names include the wkn site name.

sc (_sc.gpkg).

Geopackage vector data file containing measured bed thicknesses from Geological Model joined with corresponding Beds Geopackage file, subsetted partially. The columns largely overlap with the the list above for the Beds Geopackage but with the following additions

    Column
    Type
    Description




    X
    Real
    X position of thickness measurement


    Y
    Real
    Y position of thickness measurement


    Z
    Real
    Z position of thickness measurement


    formation
    String
    Model required string representation of bed index


    bed thickness (m)
    Real
    difference of bed elevations


    azimuths
    Real
    azimuth as measured from model in degrees


    dip_degrees
    Real
    dip as measured from model in

QDGC tables delivered in geopackage file
- - - - - - - - - - - - - - - - - - - - - -
QDGC represents a way of making (almost) equal area squares covering a specific area to represent specific qualities of the area covered. The squares themselves are based on the degree squares covering earth. Around the equator we have 360 longitudinal lines , and from the north to the south pole we have 180 latitudinal lines. Together this gives us 64800 segments or tiles covering earth.


Within each geopackage file you will find a number of tables with these names:
-tbl_qdgc_01
-tbl_qdgc_02
-tbl_qdgc_03
-tbl_qdgc_04
-tbl_qdgc_05
-etc


The attributes for each table are:
qdgc Unique Quarter Degree Grid Cell reference string
area_reference Country
level_qdgc QDGC level
cellsize degrees decimal degree for the longitudal and latitudal length of the cell
lon_center Longitude center of the cell
lat_center Latitudal center of the cell
area_km2 Calculated area for the cell
geom Geometry


Metadata
--------
Geodata GCS_WGS_1984
Datum: D_WGS_1984
Prime Meridian: 0


Areas are calculated with different versions of Albers Equal Area Conic using the PostGIS function st_area. For the African continent I have used Africa Albers Equal Area Conic which will look like this:
- st_area(st_transform(geom, 102022))/1000000)


Conditions
----------
Delivered to the user as-is. No guarantees. If you find errors, please tell me and I will try to fix it. Suggestions for improvements can be addressed to the github repository: https://github.com/ragnvald/qdgc


Thankyou
--------
The work has over the years been supported and received advice and moral support from many organisations and stakeholders. Here are some of them:
- Tanzania Wildlife Research Institute
- Dept of Biology, NTNU, Norway
- Norwegian Environment Agency
- Eivin Røskaft, Steven Prager, Howard Frederick, Julian Blanc, Honori Maliti, Paul Ramsey


References
----------
* http://en.wikipedia.org/wiki/QDGC
* http://www.mindland.com/wp/projects/quarter-degree-grid-cells/about-qdgc/
* http://en.wikipedia.org/wiki/Lambert_azimuthal_equal-area_projection
* http://www.safe.com

The Digital Geologic-GIS Map of the Mammoth Cave Quadrangle, Kentucky is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (macv_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (macv_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (macv_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (maca_abli_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (maca_abli_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (macv_geology_metadata_faq.pdf). Please read the maca_abli_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (macv_geology_metadata.txt or macv_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Overview:This document describes the 2021 accessibility data released by the Accessibility Observatory at the University of Minnesota. The data are included in the National Accessibility Evaluation Project for 2021, and this information can be accessed for each state in the U.S. at https://access.umn.edu/research/america. The following sections describe the format, naming, and content of the data files.Data Formats: The data files are provided in a Geopackage format. Geopackage (.gpkg) files are an open-source, geospatial filetype that can contain multiple layers of data in a single file, and can be opened with most GIS software, including both ArcGIS and QGIS.Within this zipfile, there are six geopackage files (.gpkg) structured as follows. Each of them contains the blocks shapes layer, results at the block level for all LEHD variables (jobs and workers), with a layer of results for each travel time (5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 minutes). {MPO ID}_tr_2021_0700-0859-avg.gpkg = Average Transit Access Departing Every Minute 7am-9am{MPO ID}_au_2021_08.gpkg = Average Auto Access Departing 8am{MPO ID}_bi_2021_1200_lts1.gpkg = Average Bike Access on LTS1 Network{MPO ID}_bi_2021_1200_lts2.gpkg = Average Bike Access on LTS2 Network{MPO ID}_bi_2021_1200_lts3.gpkg = Average Bike Access on LTS3 Network{MPO ID}_bi_2021_1200_lts4.gpkg = Average Bike Access on LTS4 NetworkFor mapping and geospatial analysis, the blocks shape layer within each geopackage can be joined to the blockid of the access attribute data. Opening and Using Geopackages in ArcGIS:Unzip the zip archiveUse the "Add Data" function in Arc to select the .gpkg fileSelect which layer(s) are needed — always select "main.blocks" as this layer contains the Census block shapes; select any other attribute data layers as well.There are three types of layers in the geopackage file — the "main.blocks" layer is the spatial features layer, and all other layers are either numerical attribute data tables, or the "fieldname_descriptions" metadata layer. The numerical attribute layers are named with the following format:[mode]_[threshold]_minutes[mode] is a two-character code indicating the transport mode used[threshold] is an integer indicating the travel time threshold used for this data layerTo use the data spatially, perform a join between the "main.blocks" layer and the desired numerical data layer, using either the numerical "id" fields, or 15-digit "blockid" fields as join fields.

QDGC tables delivered in geopackage file - - - - - - - - - - - - - - - - - - - - - - QDGC represents a way of making (almost) equal area squares covering a specific area to represent specific qualities of the area covered. The squares themselves are based on the degree squares covering earth. Around the equator we have 360 longitudinal lines , and from the north to the south pole we have 180 latitudinal lines. Together this gives us 64800 segments or tiles covering earth. Within each geopackage file you will find a number of tables with these names: -tbl_qdgc_01 -tbl_qdgc_02 -tbl_qdgc_03 -tbl_qdgc_04 -tbl_qdgc_05 -etc The attributes for each table are: qdgc Unique Quarter Degree Grid Cell reference string area_reference Country level_qdgc QDGC level cellsize degrees decimal degree for the longitudal and latitudal length of the cell lon_center Longitude center of the cell lat_center Latitudal center of the cell area_km2 Calculated area for the cell geom Geometry Metadata -------- Geodata GCS_WGS_1984 Datum: D_WGS_1984 Prime Meridian: 0 Areas are calculated with different versions of Albers Equal Area Conic using the PostGIS function st_area. For the African continent I have used Africa Albers Equal Area Conic which will look like this: - st_area(st_transform(geom, 102022))/1000000) Conditions ---------- Delivered to the user as-is. No guarantees. If you find errors, please tell me and I will try to fix it. Suggestions for improvements can be addressed to the github repository: https://github.com/ragnvald/qdgc Thankyou -------- The work has over the years been supported and received advice and moral support from many organisations and stakeholders. Here are some of them: - Tanzania Wildlife Research Institute - Dept of Biology, NTNU, Norway - Norwegian Environment Agency - Eivin Røskaft, Steven Prager, Howard Frederick, Julian Blanc, Honori Maliti, Paul Ramsey References ---------- * http://en.wikipedia.org/wiki/QDGC * http://www.mindland.com/wp/projects/quarter-degree-grid-cells/about-qdgc/ * http://en.wikipedia.org/wiki/Lambert_azimuthal_equal-area_projection * http://www.safe.com QDGC goes to level 9 for Israel. DEcompressed size is 0,67 GB.

Contains the plain csv files of the ID tables and link tables as well as a geopackage of the base geometries from which most spatial datasets of HGIS de las Indias (especially doi.org/10.7910/DVN/JSL0ND) are processed, using an automated workflow (doi:10.7910/DVN/FIK7RH). Also includes three intermediate dump tables with a crucial function between raw data and output. Does not include "aggregated data". Raw tables for aggregated data are stored along with the respective resulting geodata. Raw tables: -gz_entidades (place entities) -gz_cabildo (municipal institutions of places, over time) -gz_categoria (settlement type of places, over time) -gz_iglesia (church institutions of places over time) -gz_nombres (main names of places, over time) -entidades (territorial entities) -infotable (instances of territorial entities, over time) -LCG_All_levels (relates LCG features with territorial entities over time) -entidades_fuentes (relates used sources to territorial entities) -entidades_wiki (descriptive comments on territorial entities, in wiki format) Geopackage: -the_geom.gpkg -LCG (polygon layer). "Least common geometries" (areas that share the same information across the database) -gz_the_geom (point layer). Coordinates of the place entities, over time Intermediate dump files: -gz_info_1 ("places" - a computed aggregate of the tables with prefix gz_ with a unified chronology) -Niveles (relates corresponding instances of territorial entities to LCG_All_levels, over time) -cabeceras (capital cities, relates gz_info_1 and Niveles over time)

This data package contains extracts from open datasets to support
the tutorials available at https://github.com/nismod/snail/

This version of the data goes with v0.1 of the tutorials:

https://github.com/nismod/snail/releases/tag/v0.1

WRI Aqueduct Flood Hazard Maps

`flood_layer` contains data extracted and derived from the Aqueduct
Flood Hazard Maps (version 2, updated October 20, 2020).

See https://www.wri.org/resources/data-sets/aqueduct-floods-hazard-maps

These data are shared under the CC-BY Creative Commons Attribution
License 4.0 - https://creativecommons.org/licenses/by/4.0/

Citation: Ward, P.J., H.C. Winsemius, S. Kuzma,
M.F.P. Bierkens, A. Bouwman, H. de Moel, A. Díaz Loaiza, et
al. 2020. “Aqueduct Floods Methodology.” Technical Note.
Washington, D.C.: World Resources Institute. Available online at:
www.wri.org/publication/aqueduct-floods-methodology.

Ghana - Subnational Administrative Boundaries

`gha_admbnda_gss_20210308_shp` contains data from Ghana Statistical
Services (GSS) contributed to Humanitarian Data Exchange by the OCHA
Regional Office for West and Central Africa, updated 11 March 2021.

See https://data.humdata.org/m/dataset/ghana-administrative-boundaries

These data are shared under the Creative Commons Attribution for
Intergovernmental Organisations (CC BY-IGO) - https://creativecommons.org/licenses/by/3.0/igo/

Ghana OpenStreetMap Extract

`ghana-latest-free.shp` contains data extracted from OpenStreetMap
and downloaded from GeoFabrik.

The files in this archive have been created from OpenStreetMap data
and are licensed under the Open Database 1.0 License. See
www.openstreetmap.org for details about the project.

This file contains OpenStreetMap data as of 2021-03-22T21:21:57Z.

More recent updates will be made available daily here:

http://download.geofabrik.de/africa/ghana-latest-free.shp.zip

A documentation of the layers in this shape file is available here:

http://download.geofabrik.de/osm-data-in-gis-formats-free.pdf

Ghana Road Network

`GHA_OSM_roads.gpkg` contains data derived from the OpenStreetMap
extract above, and can be reproduced by running through nismod/snail
tutorial 01.

These data are shared under the same Open Database 1.0 License. See
www.openstreetmap.org for details about the project.

Natural Earth Country Boundaries

`ne_10m_admin_0_countries` contains Natural Earth 1:10m Cultural Vectors,
Admin ) - Countries version 4.1.0

See https://www.naturalearthdata.com/downloads/10m-cultural-vectors/10m-admin-0-countries/

These data are declared to be in the public domain, and may be shared
and modified without restriction - https://www.naturalearthdata.com/about/terms-of-use/

QGIS project

`overview.qgz` is a QGIS project intended to help preview and explore
the data in this package.

It is shared under the CC-BY Creative Commons Attribution
License 4.0 - https://creativecommons.org/licenses/by/4.0/

Please cite it as part of this data package, by Tom Russell (2021).

Results

`results` contains the results of analysis that can be reproduced
by running through all the nismod/snail tutorials.

These are derived from all the data above, shared under the
combined terms of Open Database 1.0 License and CC-BY licenses as
applicable to derived, extracted and modified data.

UK air pollution removal A GeoPackage (see https://www.geopackage.org/) that contains the spatial data used in this article:https://www.ons.gov.uk/economy/environmentalaccounts/articles/ukairpollutionremovalhowmuchpollutiondoesvegetationremoveinyourarea/2018-07-30The methodology used to develop estimates for the valuation of air pollution in ecosystem accounts can be found here:https://www.ons.gov.uk/economy/environmentalaccounts/articles/developingestimatesforthevaluationofairpollutioninecosystemaccounts/2017-07-25Download file size: 110 MB