Have you ever wanted to create your own maps, or integrate and visualize spatial datasets to examine changes in trends between locations and over time? Follow along with these training tutorials on QGIS, an open source geographic information system (GIS) and learn key concepts, procedures and skills for performing common GIS tasks – such as creating maps, as well as joining, overlaying and visualizing spatial datasets. These tutorials are geared towards new GIS users. We’ll start with foundational concepts, and build towards more advanced topics throughout – demonstrating how with a few relatively easy steps you can get quite a lot out of GIS. You can then extend these skills to datasets of thematic relevance to you in addressing tasks faced in your day-to-day work.

In this course, you will explore a variety of open-source technologies for working with geosptial data, performing spatial analysis, and undertaking general data science. The first component of the class focuses on the use of QGIS and associated technologies (GDAL, PROJ, GRASS, SAGA, and Orfeo Toolbox). The second component of the class introduces Python and associated open-source libraries and modules (NumPy, Pandas, Matplotlib, Seaborn, GeoPandas, Rasterio, WhiteboxTools, and Scikit-Learn) used by geospatial scientists and data scientists. We also provide an introduction to Structured Query Language (SQL) for performing table and spatial queries. This course is designed for individuals that have a background in GIS, such as working in the ArcGIS environment, but no prior experience using open-source software and/or coding. You will be asked to work through a series of lecture modules and videos broken into several topic areas, as outlined below. Fourteen assignments and the required data have been provided as hands-on opportunites to work with data and the discussed technologies and methods. If you have any questions or suggestions, feel free to contact us. We hope to continue to update and improve this course. This course was produced by West Virginia View (http://www.wvview.org/) with support from AmericaView (https://americaview.org/). This material is based upon work supported by the U.S. Geological Survey under Grant/Cooperative Agreement No. G18AP00077. The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the opinions or policies of the U.S. Geological Survey. Mention of trade names or commercial products does not constitute their endorsement by the U.S. Geological Survey. After completing this course you will be able to: apply QGIS to visualize, query, and analyze vector and raster spatial data. use available resources to further expand your knowledge of open-source technologies. describe and use a variety of open data formats. code in Python at an intermediate-level. read, summarize, visualize, and analyze data using open Python libraries. create spatial predictive models using Python and associated libraries. use SQL to perform table and spatial queries at an intermediate-level.

The Digital Geomorphic-GIS Map of Gulf Islands National Seashore (5-meter accuracy and 1-foot resolution 2006-2007 mapping), Mississippi and Florida 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 (guis_geomorphology.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 (guis_geomorphology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (guis_geomorphology.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 GIS readme file (guis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (guis_geomorphology.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 (guis_geomorphology_metadata_faq.pdf). Please read the guis_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: 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 (guis_geomorphology_metadata.txt or guis_geomorphology_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:26,000 and United States National Map Accuracy Standards features are within (horizontally) 13.2 meters or 43.3 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).

Total file size: about 367M in zip format and about 600M after extracted. (To download: click the Download button at the upper right area of this page)Alternatively, you can download the data by chapters:- Go to https://go.esri.com/gtkwebgis4- Under Group Categories on the left, click each chapter, you will see the data file to download for that chapter.

This resource contains data inputs and a Jupyter Notebook that is used to introduce Hydrologic Analysis using Terrain Analysis Using Digital Elevation Models (TauDEM) and Python. TauDEM is a free and open-source set of Digital Elevation Model (DEM) tools developed at Utah State University for the extraction and analysis of hydrologic information from topography. This resource is part of a HydroLearn Physical Hydrology learning module available at https://edx.hydrolearn.org/courses/course-v1:Utah_State_University+CEE6400+2019_Fall/about

In this activity, the student learns how to (1) derive hydrologically useful information from Digital Elevation Models (DEMs); (2) describe the sequence of steps involved in mapping stream networks, catchments, and watersheds; and (3) compute an approximate water balance for a watershed-based on publicly available data.

Please note that this exercise is designed for the Logan River watershed, which drains to USGS streamflow gauge 10109000 located just east of Logan, Utah. However, this Jupyter Notebook and the analysis can readily be applied to other locations of interest. If running the terrain analysis for other study sites, you need to prepare a DEM TIF file, an outlet shapefile for the area of interest, and the average annual streamflow and precipitation data. - There are several sources to obtain DEM data. In the U.S., the DEM data (with different spatial resolutions) can be obtained from the National Elevation Dataset available from the national map (http://viewer.nationalmap.gov/viewer/). Another DEM data source is the Shuttle Radar Topography Mission (https://www2.jpl.nasa.gov/srtm/), an international research effort that obtained digital elevation models on a near-global scale (search for Digital Elevation at https://www.usgs.gov/centers/eros/science/usgs-eros-archive-products-overview?qt-science_center_objects=0#qt-science_center_objects). - If not already available, you can generate the outlet shapefile by applying basic terrain analysis steps in geospatial information system models such as ArcGIS or QGIS. - You also need to obtain average annual streamflow and precipitation data for the watershed of interest to assess the annual water balance and calculate the runoff ratio in this exercise. In the U.S., the streamflow data can be obtained from the USGS NWIS website (https://waterdata.usgs.gov/nwis) and the precipitation from PRISM (https://prism.oregonstate.edu/normals/). Note that using other datasets may require preprocessing steps to make data ready to use for this exercise.

The Minnesota DNR Toolbox and Hydro Tools provide a number of convenience geoprocessing tools used regularly by MNDNR staff. Many of these may be useful to the wider public. However, some tools may rely on data that is not available outside of the DNR. All tools require at least ArcGIS 10+.

If you create a GDRS using GDRS Manager and include this toolbox resource and MNDNR Quick Layers, the DNR toolboxes will automatically be added to the ArcToolbox window whenever Quick Layers GDRS Location is set to the GDRS location that has the toolboxes.

Toolsets included in MNDNR Tools V10:
- Analysis Tools
- Conversion Tools
- Division Tools
- General Tools
- Hydrology Tools
- LiDAR and DEM Tools
- Raster Tools
- Sampling Tools

These toolboxes are provided free of charge and are not warrantied for any specific use. We do not provide support or assistance in downloading or using these tools. We do, however, strive to produce high-quality tools and appreciate comments you have about them.

Database created for replication of GeoStoryTelling. Our life stories evolve in specific and contextualized places. Although our homes may be our primarily shaping environment, our homes are themselves situated in neighborhoods that expose us to the immediate “real world” outside home. Indeed, the places where we are currently experiencing, and have experienced life, play a fundamental role in gaining a deeper and more nuanced understanding of our beliefs, fears, perceptions of the world, and even our prospects of social mobility. Despite the immediate impact of the places where we experience life in reaching a better understanding of our life stories, to date most qualitative and mixed methods researchers forego the analytic and elucidating power that geo-contextualizing our narratives bring to social and health research. From this view then, most research findings and conclusions may have been ignoring the spatial contexts that most likely have shaped the experiences of research participants. The main reason for the underuse of these geo-contextualized stories is the requirement of specialized training in geographical information systems and/or computer and statistical programming along with the absence of cost-free and user-friendly geo-visualization tools that may allow non-GIS experts to benefit from geo-contextualized outputs. To address this gap, we present GeoStoryTelling, an analytic framework and user-friendly, cost-free, multi-platform software that enables researchers to visualize their geo-contextualized data narratives. The use of this software (available in Mac and Windows operative systems) does not require users to learn GIS nor computer programming to obtain state-of-the-art, and visually appealing maps. In addition to providing a toy database to fully replicate the outputs presented, we detail the process that researchers need to follow to build their own databases without the need of specialized external software nor hardware. We show how the resulting HTML outputs are capable of integrating a variety of multi-media inputs (i.e., text, image, videos, sound recordings/music, and hyperlinks to other websites) to provide further context to the geo-located stories we are sharing (example https://cutt.ly/k7X9tfN). Accordingly, the goals of this paper are to describe the components of the methodology, the steps to construct the database, and to provide unrestricted access to the software tool, along with a toy dataset so that researchers may interact first-hand with GeoStoryTelling and fully replicate the outputs discussed herein. Since GeoStoryTelling relied on OpenStreetMap its applications may be used worldwide, thus strengthening its potential reach to the mixed methods and qualitative scientific communities, regardless of location around the world. Keywords: Geographical Information Systems; Interactive Visualizations; Data StoryTelling; Mixed Methods & Qualitative Research Methodologies; Spatial Data Science; Geo-Computation.

The Digital Geohazard-GIS Map of the Zion National Park Study Area, Utah is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (zion_geohazards.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 3.X map file (.mapx) file (zion_geohazards.mapx) and individual Pro 3.X layer (.lyrx) 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 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 (zion_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (zion_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 (zion_geohazards_metadata_faq.pdf). Please read the zion_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: 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: Utah 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 (zion_geohazards_metadata.txt or zion_geohazards_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 Pro, 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).

RTB Maps is a cloud-based electronic Atlas. We used ArGIS 10 for Desktop with Spatial Analysis Extension, ArcGIS 10 for Server on-premise, ArcGIS API for Javascript, IIS web services based on .NET, and ArcGIS Online combining data on the cloud with data and applications on our local server to develop an Atlas that brings together many of the map themes related to development of roots, tubers and banana crops. The Atlas is structured to allow our participating scientists to understand the distribution of the crops and observe the spatial distribution of many of the obstacles to production of these crops. The Atlas also includes an application to allow our partners to evaluate the importance of different factors when setting priorities for research and development. The application uses weighted overlay analysis within a multi-criteria decision analysis framework to rate the importance of factors when establishing geographic priorities for research and development.Datasets of crop distribution maps, agroecology maps, biotic and abiotic constraints to crop production, poverty maps and other demographic indicators are used as a key inputs to multi-objective criteria analysis.Further metadata/references can be found here: http://gisweb.ciat.cgiar.org/RTBmaps/DataAvailability_RTBMaps.htmlDISCLAIMER, ACKNOWLEDGMENTS AND PERMISSIONS:This service is provided by Roots, Tubers and Bananas CGIAR Research Program as a public service. Use of this service to retrieve information constitutes your awareness and agreement to the following conditions of use.This online resource displays GIS data and query tools subject to continuous updates and adjustments. The GIS data has been taken from various, mostly public, sources and is supplied in good faith.RTBMaps GIS Data Disclaimer• The data used to show the Base Maps is supplied by ESRI.• The data used to show the photos over the map is supplied by Flickr.• The data used to show the videos over the map is supplied by Youtube.• The population map is supplied to us by CIESIN, Columbia University and CIAT.• The Accessibility map is provided by Global Environment Monitoring Unit - Joint Research Centre of the European Commission. Accessibility maps are made for a specific purpose and they cannot be used as a generic dataset to represent "the accessibility" for a given study area.• Harvested area and yield for banana, cassava, potato, sweet potato and yam for the year 200, is provided by EarthSat (University of Minnesota’s Institute on the Environment-Global Landscapes initiative and McGill University’s Land Use and the Global Environment lab). Dataset from Monfreda C., Ramankutty N., and Foley J.A. 2008.• Agroecology dataset: global edapho-climatic zones for cassava based on mean growing season, temperature, number of dry season months, daily temperature range and seasonality. Dataset from CIAT (Carter et al. 1992)• Demography indicators: Total and Rural Population from Center for International Earth Science Information Network (CIESIN) and CIAT 2004.• The FGGD prevalence of stunting map is a global raster datalayer with a resolution of 5 arc-minutes. The percentage of stunted children under five years old is reported according to the lowest available sub-national administrative units: all pixels within the unit boundaries will have the same value. Data have been compiled by FAO from different sources: Demographic and Health Surveys (DHS), UNICEF MICS, WHO Global Database on Child Growth and Malnutrition, and national surveys. Data provided by FAO – GIS Unit 2007.• Poverty dataset: Global poverty headcount and absolute number of poor. Number of people living on less than $1.25 or $2.00 per day. Dataset from IFPRI and CIATTHE RTBMAPS GROUP MAKES NO WARRANTIES OR GUARANTEES, EITHER EXPRESSED OR IMPLIED AS TO THE COMPLETENESS, ACCURACY, OR CORRECTNESS OF THE DATA PORTRAYED IN THIS PRODUCT NOR ACCEPTS ANY LIABILITY, ARISING FROM ANY INCORRECT, INCOMPLETE OR MISLEADING INFORMATION CONTAINED THEREIN. ALL INFORMATION, DATA AND DATABASES ARE PROVIDED "AS IS" WITH NO WARRANTY, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, FITNESS FOR A PARTICULAR PURPOSE. By accessing this website and/or data contained within the databases, you hereby release the RTB group and CGCenters, its employees, agents, contractors, sponsors and suppliers from any and all responsibility and liability associated with its use. In no event shall the RTB Group or its officers or employees be liable for any damages arising in any way out of the use of the website, or use of the information contained in the databases herein including, but not limited to the RTBMaps online Atlas product.APPLICATION DEVELOPMENT:• Desktop and web development - Ernesto Giron E. (GeoSpatial Consultant) e.giron.e@gmail.com• GIS Analyst - Elizabeth Barona. (Independent Consultant) barona.elizabeth@gmail.comCollaborators:Glenn Hyman, Bernardo Creamer, Jesus David Hoyos, Diana Carolina Giraldo Soroush Parsa, Jagath Shanthalal, Herlin Rodolfo Espinosa, Carlos Navarro, Jorge Cardona and Beatriz Vanessa Herrera at CIAT, Tunrayo Alabi and Joseph Rusike from IITA, Guy Hareau, Reinhard Simon, Henry Juarez, Ulrich Kleinwechter, Greg Forbes, Adam Sparks from CIP, and David Brown and Charles Staver from Bioversity International.Please note these services may be unavailable at times due to maintenance work.Please feel free to contact us with any questions or problems you may be having with RTBMaps.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 0.0497 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.0117 and 0.0111 (in million kms), corressponding to 23.4856% and 22.3095% respectively of the total road length in the dataset region. 0.0269 million km or 54.2049% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0008 million km of information (corressponding to 3.0011% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

This is a collection of 124 global and free datasets allowing for spatial (and temporal) analyses of floods, droughts and their interactions with human societies. We have structured the datasets into seven categories: hydrographic baseline, hydrological dynamics, hydrological extremes, land cover & agriculture, human presence, water management, and vulnerability. Please refer to Lindersson et al. (accepted february 2020 in WIREs Water) for further information about review methodology.

The collection is a descriptive list, holding the following information for each dataset:

• Category - as structured in Lindersson et al. (in preparation).
• Sub-category- as structured in Lindersson et al. (in preparation).
• Abbreviation - official or as specified in Lindersson et al. (in preparation).
• Title - full title of dataset.
• Product(s) - type of product(s) offered by the dataset.
• Period - time period covered by the dataset, not defined for all datasets.
• Temporal resolution - not defined for static datasets.
• Angular spatial resolution - only defined for gridded datasets.
• Metric spatial resolution - only defined for gridded datasets.
• Map scale
• Extent - geographic coverage of dataset given in latitude limits.
• Description
• Creating institute(s)
• Data type - raster, vector or tabular.
• File format
• Primary EO type - specifies if the product primarily is based on remote sensing, ground-based data, or a hybrid between remote sensing and ground-based data.
• Data sources - lists the data sources behind the dataset, to the extent this is feasible.
• Data sources also in this table - data sources that are also included as datasets in this collection.
• Intentionally compatible with - defines other datasets in this collection that the dataset is intentinoally compatible with.
• Citation - dataset reference or credit.
• Documentation - dataset documentation.
• Web address - dataset access link.

NOTE: Carefully consult the data usage licenses as given by the data providers, to assure that the exact permissions and restrictions are followed.

This is the GIS data and imagery used for analyses in the article
Sixty-seven years of land-use change in southern Costa Rica by Zahawi
et al. currently in revision at PLOS One.

This study required the orthorectification of historic aerial photographs, as well as forest cover mapping and landscape analysis of 320 km² around the Las Cruces Biological Station in San Vito de Coto Brus, Costa Rica. The imagery and GIS data generated were used to account for forest cover change over five different time periods from 1947 to 2014.

The datasets supplied include GIS files for:

• Extent of the study area (shapefile).
• Forest cover mapped for each time period (geotiff).
• Imagery of the mosaics generated with the orthorectified historic aerial photographs (geotiff).
• Age in studied time periods of the current forest patches (shapefile).
• Connectivity lines inside the studied area (shapefiles).

All files are in Costa Rica Transverse Mercator 2005 (CRTM05) projected coordinate reference system. For transformation between coordinate systems please refer to http://epsg.io/5367

Aerial photographs for the years 1947, 1960, 1980 and 1997 were acquired from the Organization for Tropical Studies GIS Lab and the Instituto Geográfico Nacional of Costa Rica. The orthorectification process was done first on the 1997 set of images and used the current 1:50,000 and 1:25,000 Costa Rican cartography to identify geographical reference points. The set of 1997 orthophotos was used as a reference set to orthorectify remaining years with the exception of 1947 images. The orthorectification process and all other geospatial analyses were done on the CRTM05 spatial reference system and the resulting orthophotos had a 2m cell size. The largest Root Mean Square error (RMSE) of the orthorectification of these three time slices of aerial photographs was 15 m.

Given the lack of information on flight parameters, and the expansive forest coverage in 1947 photographs, images were georeferenced and built into a mosaic using river basins and the few forest clearings that had a similar shape in the 1960 flyover. The 1947 set of images did not cover the whole study area, having empty areas without photographs that represented ˜12.1% of the analysis extent. Nonetheless, these areas were classified as forested given that forest was present in these same areas in the 1960 imagery.

Forest mapping was done by visual interpretation of orthophotos and Google imagery. The areas were considered forested if tree crowns were easily identified when viewing the images at a scale of 1:10,000. In areas where it was difficult to discern the type of land cover, a scale of 1:5,000 was used. This was done to eliminate agroforestry systems such as shaded coffee areas (with trees planted in rows) or very early stages of forest regeneration from the forest land-cover class. The analysis was done only in areas that were cloud free in the five time slices. This resulted in the elimination of 134 ha (~0.4%) from of the original area outlined above. Polygons were drawn over the different areas using QGIS and were transformed into raster files of 10 m cell size.

The USGS National Hydrography Dataset (NHD) downloadable data collection from The National Map (TNM) is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. For additional information on NHD, go to https://www.usgs.gov/core-science-systems/ngp/national-hydrography.

DWR was the steward for NHD and Watershed Boundary Dataset (WBD) in California. We worked with other organizations to edit and improve NHD and WBD, using the business rules for California. California's NHD improvements were sent to USGS for incorporation into the national database. The most up-to-date products are accessible from the USGS website. Please note that the California portion of the National Hydrography Dataset is appropriate for use at the 1:24,000 scale.

For additional derivative products and resources, including the major features in geopackage format, please go to this page: https://data.cnra.ca.gov/dataset/nhd-major-features Archives of previous statewide extracts of the NHD going back to 2018 may be found at https://data.cnra.ca.gov/dataset/nhd-archive.

In September 2022, USGS officially notified DWR that the NHD would become static as USGS resources will be devoted to the transition to the new 3D Hydrography Program (3DHP). 3DHP will consist of LiDAR-derived hydrography at a higher resolution than NHD. Upon completion, 3DHP data will be easier to maintain, based on a modern data model and architecture, and better meet the requirements of users that were documented in the Hydrography Requirements and Benefits Study (2016). The initial releases of 3DHP include NHD data cross-walked into the 3DHP data model. It will take several years for the 3DHP to be built out for California. Please refer to the resources on this page for more information.

The FINAL,STATIC version of the National Hydrography Dataset for California was published for download by USGS on December 27, 2023. This dataset can no longer be edited by the state stewards. The next generation of national hydrography data is the USGS 3D Hydrography Program (3DHP).

Questions about the California stewardship of these datasets may be directed to nhd_stewardship@water.ca.gov.

Crowther_Nature_Files.zip This description pertains to the original download. Details on revised (newer) versions of the datasets are listed below. When more than one version of a file exists in Figshare, the original DOI will take users to the latest version, though each version technically has its own DOI. -- Two global maps (raster files) of tree density. These maps highlight how the number of trees varies across the world. One map was generated using biome-level models of tree density, and applied at the biome scale. The other map was generated using ecoregion-level models of tree density, and applied at the ecoregion scale. For this reason, transitions between biomes or between ecoregions may be unrealistically harsh, but large-scale estimates are robust (see Crowther et al 2015 and Glick et al 2016). At the outset, this study was intended to generate reliable estimates at broad spatial scales, which inherently comes at the cost of fine-scale precision. For this reason, country-scale (or larger) estimates are generally more robust than individual pixel-level estimates. Additionally, due to data limitations, estimates for Mangroves and Tropical coniferous forest (as identified by WWF and TNC) were generated using models constructed from Topical moist broadleaf forest data and Temperate coniferous forest data, respectively. Because we used ecological analogy, the estimates for these two biomes should be considered less reliable than those of other biomes . These two maps initially appeared in Crowther et al (2015), with the biome map being featured more prominently. Explicit publication of the data is associated with Glick et al (2016). As they are produced, updated versions of these datasets, as well as alternative formats, will be made available under Additional Versions (see below).

Methods: We collected over 420,000 ground-sources estimates of tree density from around the world. We then constructed linear regression models using vegetative, climatic, topographic, and anthropogenic variables to produce forest tree density estimates for all locations globally. All modeling was done in R. Mapping was done using R and ArcGIS 10.1.

Viewing Instructions: Load the files into an appropriate geographic information system (GIS). For the original download (ArcGIS geodatabase files), load the files into ArcGIS to view or export the data to other formats. Because these datasets are large and have a unique coordinate system that is not read by many GIS, we suggest loading them into an ArcGIS dataframe whose coordinate system matches that of the data (see File Format). For GeoTiff files (see Additional Versions), load them into any compatible GIS or image management program.

Comments: The original download provides a zipped folder that contains (1) an ArcGIS File Geodatabase (.gdb) containing one raster file for each of the two global models of tree density – one based on biomes and one based on ecoregions; (2) a layer file (.lyr) for each of the global models with the symbology used for each respective model in Crowther et al (2015); and an ArcGIS Map Document (.mxd) that contains the layers and symbology for each map in the paper. The data is delivered in the Goode homolosine interrupted projected coordinate system that was used to compute biome, ecoregion, and global estimates of the number and density of trees presented in Crowther et al (2015). To obtain maps like those presented in the official publication, raster files will need to be reprojected to the Eckert III projected coordinate system. Details on subsequent revisions and alternative file formats are list below under Additional Versions.----------

Additional Versions: Crowther_Nature_Files_Revision_01.zip contains tree density predictions for small islands that are not included in the data available in the original dataset. These predictions were not taken into consideration in production of maps and figures presented in Crowther et al (2015), with the exception of the values presented in Supplemental Table 2. The file structure follows that of the original data and includes both biome- and ecoregion-level models.

Crowther_Nature_Files_Revision_01_WGS84_GeoTiff.zip contains Revision_01 of the biome-level model, but stored in WGS84 and GeoTiff format. This file was produced by reprojecting the original Goode homolosine files to WGS84 using nearest neighbor resampling in ArcMap. All areal computations presented in the manuscript were computed using the Goode homolosine projection. This means that comparable computations made with projected versions of this WGS84 data are likely to differ (substantially at greater latitudes) as a product of the resampling. Included in this .zip file are the primary .tif and its visualization support files.

References:

Crowther, T. W., Glick, H. B., Covey, K. R., Bettigole, C., Maynard, D. S., Thomas, S. M., Smith, J. R., Hintler, G., Duguid, M. C., Amatulli, G., Tuanmu, M. N., Jetz, W., Salas, C., Stam, C., Piotto, D., Tavani, R., Green, S., Bruce, G., Williams, S. J., Wiser, S. K., Huber, M. O., Hengeveld, G. M., Nabuurs, G. J., Tikhonova, E., Borchardt, P., Li, C. F., Powrie, L. W., Fischer, M., Hemp, A., Homeier, J., Cho, P., Vibrans, A. C., Umunay, P. M., Piao, S. L., Rowe, C. W., Ashton, M. S., Crane, P. R., and Bradford, M. A. 2015. Mapping tree density at a global scale. Nature, 525(7568): 201-205. DOI: http://doi.org/10.1038/nature14967Glick, H. B., Bettigole, C. B., Maynard, D. S., Covey, K. R., Smith, J. R., and Crowther, T. W. 2016. Spatially explicit models of global tree density. Scientific Data, 3(160069), doi:10.1038/sdata.2016.69.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 0.2839 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.026 and 0.0089 (in million kms), corressponding to 9.1664% and 3.1261% respectively of the total road length in the dataset region. 0.249 million km or 87.7075% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0003 million km of information (corressponding to 0.1046% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

This database contains 4976 planetary images of boulder fields located on Earth, Mars and Moon. The data was collected during the BOULDERING Marie Skłodowska-Curie Global fellowship between October 2021 and 2024. The data was already splitted into train, validation and test datasets, but feel free to re-organize the labels at your convenience.

For each image, all of the boulder outlines within the image were carefully mapped in QGIS. More information about the labelling procedure can be found in the following manuscript (https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2023JE008013). This dataset differs from the previous dataset included along with the manuscript https://zenodo.org/records/8171052, as it contains more mapped images, especially of boulder populations around young impact structures on the Moon (cold spots). In addition, the boulder outlines were also pre-processed so that it can be ingested directly in YOLOv8.

A description of what is what is given in the README.txt file (in addition in how to load the custom datasets in Detectron2 and YOLO). Most of the other files are mostly self-explanatory. Please see previous dataset or manuscript for more information. If you want to have more information about specific lunar and martian planetary images, the IDs of the images are still available in the name of the file. Use this ID to find more information (e.g., M121118602_00875_image.png, ID M121118602 ca be used on https://pilot.wr.usgs.gov/). I will also upload the raw data from which this pre-processed dataset was generated (see https://zenodo.org/records/14250970).

Thanks to this database, you can easily train a Detectron2 Mask R-CNN or YOLO instance segmentation models to automatically detect boulders.

How to cite:

Please refer to the "how to cite" section of the readme file of https://github.com/astroNils/YOLOv8-BeyondEarth.

Structure:

.
└── boulder2024/
 ├── jupyter-notebooks/
 │ └── REGISTERING_BOULDER_DATASET_IN_DETECTRON2.ipynb
 ├── test/
 │ └── images/
 │  ├── 

detectron2_inst_seg_boulder_dataset.json

is a json file containing the masks as expected by Detectron2 (see https://detectron2.readthedocs.io/en/latest/tutorials/datasets.html for more information on the format). In order to use this custom dataset, you need to register the dataset before using it in the training. There is an example how to do that in the jupyter-notebooks folder. You need to have detectron2, and all of its depedencies installed.

yolo_inst_seg_boulder_dataset.yaml

can be used as it is, however you need to update the paths in the .yaml file, to the test, train and validation folders. More information about the YOLO format can be found here (https://docs.ultralytics.com/datasets/segment/).

Xverum’s Global GIS & Geospatial Data is a high-precision dataset featuring 230M+ verified points of interest across 249 countries. With rich metadata, structured geographic attributes, and continuous updates, our dataset empowers businesses, researchers, and governments to extract location intelligence and conduct advanced geospatial analysis.

Perfectly suited for GIS systems, mapping tools, and location intelligence platforms, this dataset covers everything from businesses and landmarks to public infrastructure, all classified into over 5000 categories. Whether you're planning urban developments, analyzing territories, or building location-based products, our data delivers unmatched coverage and accuracy.

Key Features: ✅ 230M+ Global POIs Includes commercial, governmental, industrial, and service locations - updated regularly for accurate relevance.

✅ Comprehensive Geographic Coverage Worldwide dataset covering 249 countries, with attributes including latitude, longitude, city, country code, postal code, etc.

✅ Detailed Mapping Metadata Get structured address data, place names, categories, and location, which are ideal for map visualization and geospatial modeling.

✅ Bulk Delivery for GIS Platforms Available in .json - delivered via S3 Bucket or cloud storage for easy integration into ArcGIS, QGIS, Mapbox, and similar systems.

✅ Continuous Discovery & Refresh New POIs added and existing ones refreshed on a regular refresh cycle, ensuring reliable, up-to-date insights.

✅ Compliance & Scalability 100% compliant with global data regulations and scalable for enterprise use across mapping, urban planning, and retail analytics.

Use Cases: 📍 Location Intelligence & Market Analysis Identify high-density commercial zones, assess regional activity, and understand spatial relationships between locations.

🏙️ Urban Planning & Smart City Development Design infrastructure, zoning plans, and accessibility strategies using accurate location-based data.

🗺️ Mapping & Navigation Enrich digital maps with verified business listings, categories, and address-level geographic attributes.

📊 Retail Site Selection & Expansion Analyze proximity to key POIs for smarter retail or franchise placement.

📌 Risk & Catchment Area Assessment Evaluate location clusters for insurance, logistics, or regional outreach strategies.

Why Xverum? ✅ Global Coverage: One of the largest POI geospatial databases on the market ✅ Location Intelligence Ready: Built for GIS platforms and spatial analysis use ✅ Continuously Updated: New POIs discovered and refreshed regularly ✅ Enterprise-Friendly: Scalable, compliant, and customizable ✅ Flexible Delivery: Structured format for smooth data onboarding

Request a free sample and discover how Xverum’s geospatial data can power your mapping, planning, and spatial analysis projects.

This layer is part of Hamilton City Council's Freshwater Dataset.If you wish to download and consume this entire dataset - click on the link for the file format(s) of your choosing: CAD (DWG)

Please note that the links above may change at any time. For best practice, please refer to this page for the correct links.

If any of the links are above are not functioning, please let us know at gis@hcc.govt.nz.

This Water (Freshwater) dataset contains the following layers:

Water Valve (A tap on a main that controls the flow of water along that main) Water Service Valve (A tap on a service line that controls the flow of water along that line) Water Service Line/Connection (A pipe that delivers water from the main to a building for consumption) Water Meter (A device that measures and displays the amount of water passing through the associated main or service line) Water Main Offset (A point along a main indicating the distance of the main from another known point such as the property boundary or kerb) Water Main Crossover Junction (The junction of one or more pipes where the pipes do not intersect - aka crossover junction) Water Main Abandoned (A water main that is still in the ground, but is now disused and no longer forms part of the active network) Water Hydrant (A tap supplying access to high-pressure water to fight fires, flush pipes and fill water trucks) Water Chamber MH (An opening/structure in a water chamber for the purpose of allowing operators or equipment access to the inside of the chamber) Water Chamber (A chamber on a water main (except bulk mains) containing operational or monitoring devices such as valves or flow meters) Water BM Chamber (A chamber on a water bulk main containing operational devices such as valves or flow meters) Water BM AV Chamber (A chamber on a water bulk main containing an air valve) Water Backflow Device (A device which prevents the accidental backflow of contaminated water into the water system) Water Asbuilts (Plans showing the location and alignment of basic water infrastructure as it was constructed on site, as provided by the contractor or their representatives. Data has not yet been fully incorporated into the Council GIS or asset management system)

Hamilton City Council 3 Waters data is derived from the Council’s GIS (ArcGIS) dataset. The GIS dataset is synchronised with asset data contained in the Council’s Asset Management (IPS) database. A subset of the GIS dataset has been made available for download.

This GIS dataset is currently updated weekly which in turn dynamically updates to the WLASS open data site. Any questions pertaining to this data should be directed to the City Waters Asset Information Team at CityWatersAssetInfo@hcc.govt.nz

Hamilton City Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the data released for public download. Levels, locations and dimensions of works depicted in the data may not be accurate due to circumstances not notified to Council. A physical check should be made on all levels, locations and dimensions before starting design or works.

Hamilton City Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data.

While you are free to crop, export and re-purpose the data, we ask that you attribute the Hamilton City Council and clearly state that your work is a derivative and not the authoritative data source. Please include the following statement when distributing any work derived from this data:

‘This work is derived entirely or in part from Hamilton City Council data; the provided information may be updated at any time, and may at times be out of date, inaccurate, and/or incomplete.'

A log of dataset alerts open, monitored or resolved on the open data portal. Alerts can include issues as well as deprecation or discontinuation notices.

Chicago sites that offer free or affordable technology resources and services, like computers with Internet access, Wi-Fi hotspots and technology training. Call or visit the organization's website before going to the location. For more information, visit http://locations.weconnectchicago.org/.