The GDAL/OGR libraries are open-source, geo-spatial libraries that work with a wide range of raster and vector data sources. One of many impressive features of the GDAL/OGR libraries is the ViRTual (VRT) format. It is an XML format description of how to transform raster or vector data sources on the fly into a new dataset. The transformations include: mosaicking, re-projection, look-up table (raster), change data type (raster), and SQL SELECT command (vector). VRTs can be used by GDAL/OGR functions and utilities as if they were an original source, even allowing for chaining of functionality, for example: have a VRT mosaic hundreds of VRTs that use look-up tables to transform original GeoTiff files. We used the VRT format for the presentation of hydrologic model results, allowing for thousands of small VRT files representing all components of the monthly water balance to be transformations of a single land cover GeoTiff file.

Presentation at 2018 AWRA Spring Specialty Conference: Geographic Information Systems (GIS) and Water Resources X, Orlando, Florida, April 23-25, http://awra.org/meetings/Orlando2018/

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.

The European Copernicus Coastal Flood Awareness System (ECFAS) project will contribute to the evolution of the Copernicus Emergency Monitoring Service by demonstrating the technical and operational feasibility of a European Coastal Flood Awareness System. Specifically, ECFAS will provide a much-needed solution to bolster coastal resilience to climate risk and reduce population and infrastructure exposure by monitoring and supporting disaster preparedness, two factors that are fundamental to damage prevention and recovery if a storm hits.

The ECFAS Proof-of-Concept development will run from January 2021-December 2022. The ECFAS project is a collaboration between Istituto Universitario di Studi Superiori IUSS di Pavia (Italy, ECFAS Coordinator), Mercator Ocean International (France), Planetek Hellas (Greece), Collecte Localisation Satellites (France), Consorzio Futuro in Ricerca (Italy), Universitat Politecnica de Valencia (Spain), University of the Aegean (Greece), and EurOcean (Portugal), and is funded by the European Commission H2020 Framework Programme within the call LC-SPACE-18-EO-2020 - Copernicus evolution: research activities in support of the evolution of the Copernicus services.

This project has received funding from the European Union’s Horizon 2020 programme

Description of the containing files inside the Dataset.

The dataset was divided at European country level, except the Adriatic area which was extracted as a region and not on a country level due to the small size of the countries. The buffer zone of each data was 10km inland in order to be correlated with the new Copernicus product Coastal Zone LU/LC.

Specifically, the dataset includes the new Coastal LU/LC product which was implemented by the EEA and became available at the end of 2020. Additional information collected in relation to the location and characteristics of transport (road and railway) and utility networks (power plants), population density and time variability. Furthermore, some of the publicly available datasets that were used in CEMS related to the abovementioned assets were gathered such as OpenStreetMap (building footprints, road and railway network infrastructures), GeoNames (populated places but also names of administrative units, rivers and lakes, forests, hills and mountains, parks and recreational areas, etc.), the Global Human Settlement Layer (GHS) and Global Human Settlement Population Grid (GHS-POP) generated by JRC. Below there are tables which present the dataset. Finally, the dataset contains statistics information regarding the population of Europe per sex and age divided in administrative units NUTS level 3.

Copernicus Land Monitoring Service	Resolution	Comment
Coastal LU/LC	1:10.000	A Copernicus hotspot product to monitor landscape dynamics in coastal zones
EU-Hydro - Coastline	1:30.000	EU-Hydro is a dataset for all European countries providing the coastline
Natura 2000	1: 100000	A Copernicus hotspot product to monitor important areas for nature conservation
European Settlement Map	10m	A spatial raster dataset that is mapping human settlements in Europe
Imperviousness Density	10m	The percentage of sealed area
Impervious Built-up	10m	The part of the sealed surfaces where buildings can be found
Grassland 2018	10m	A binary grassland/non-grassland product
Tree Cover Density 2018	10m	Level of tree cover density in a range from 0-100%

Joint Research Center	Resolution	Comment
Global Human Settlement Population Grid GHS-POP)	250m	Residential population estimates for target year 2015
GHS settlement model layer (GHS-SMOD)	1km	The GHS Settlement Model grid delineates and classify settlement typologies via a logic of population size, population and built-up area densities
GHS-BUILT	10m	Built-up grid derived from Sentinel-2 global image composite for reference year 2018
ENACT 2011 Population Grid (ENACT-POP R2020A)	1km	The ENACT is a population density for the European Union that take into account major daily and monthly population variations
JRC Open Power Plants Database (JRC-PPDB-OPEN)	-	Europe’s open power plant database
GHS functional urban areas (GHS-FUA R2019A)	1km	City and its commuting zone (area of influence of the city in terms of labour market flows)
GHS Urban Centre Database (GHS-UCDB R2019A)	1km	Urban Centres defined by specific cut-off values on resident population and built-up surface

Additional Data	Resolution	Comment
Open Street Map (OSM)	-	BF, Transportation Network, Utilities Network, Places of Interest
CEMS	-	Data from Rapid Mapping activations in Europe
GeoNames	-	Populated places, Adm. units, Hydrography, Forests, Hills/Mountains, Parks, etc.
Global Administrative Areas	-	Administrative areas of all countries, at all levels of sub-division
NUTS3 Population Age/Sex Group	-	Eurostat population by age and sex statistics intersected with the NUTS3 Units

Disclaimer:

ECFAS partners provide the data "as is" and "as available" without warranty of any kind. The ECFAS partners shall not be held liable resulting from the use of the information and data provided.

This project has received funding from the Horizon 2020 research and innovation programme under grant agreement No. 101004211

Geospatial Data Pack for Visualization 🗺️

Learn Geographic Mapping with Altair, Vega-Lite and Vega using Curated Datasets

Complete geographic and geophysical data collection for mapping and visualization. This consolidation includes 18 complementary datasets used by 31+ Vega, Vega-Lite, and Altair examples 📊. Perfect for learning geographic visualization techniques including projections, choropleths, point maps, vector fields, and interactive displays.

Source data lives on GitHub and can also be accessed via CDN. The vega-datasets project serves as a common repository for example datasets used across these visualization libraries and related projects.

Why Use This Dataset? 🤔

• Comprehensive Geospatial Types: Explore a variety of core geospatial data models:
  • Vector Data: Includes points (like airports.csv), lines (like londonTubeLines.json), and polygons (like us-10m.json).
  • Raster-like Data: Work with gridded datasets (like windvectors.csv, annual-precip.json).
• Diverse Formats: Gain experience with standard and efficient geospatial formats like GeoJSON (see Table 1, 2, 4), compressed TopoJSON (see Table 1), and plain CSV/TSV (see Table 2, 3, 4) for point data and attribute tables ready for joining.
• Multi-Scale Coverage: Practice visualization across different geographic scales, from global and national (Table 1, 4) down to the city level (Table 1).
• Rich Thematic Mapping: Includes multiple datasets (Table 3) specifically designed for joining attributes to geographic boundaries (like states or counties from Table 1) to create insightful choropleth maps.
• Ready-to-Use & Example-Driven: Cleaned datasets tightly integrated with 31+ official examples (see Appendix) from Altair, Vega-Lite, and Vega, allowing you to immediately practice techniques like projections, point maps, network maps, and interactive displays.
• Python Friendly: Works seamlessly with essential Python libraries like Altair (which can directly read TopoJSON/GeoJSON), Pandas, and GeoPandas, fitting perfectly into the Kaggle notebook environment.

Table of Contents

• Why Use This Dataset?
• Dataset Inventory
• Usage Guide
• Appendix: Geospatial Examples by Technique
• Licenses
• Sources
• Learning Resources

Dataset Inventory 🗂️

This pack includes 18 datasets covering base maps, reference points, statistical data for choropleths, and geophysical data.

1. BASE MAP BOUNDARIES (Topological Data)

Dataset	File	Size	Format	License	Description	Key Fields / Join Info
US Map (1:10m)	us-10m.json	627 KB	TopoJSON	CC-BY-4.0	US state and county boundaries. Contains states and counties objects. Ideal for choropleths.	id (FIPS code) property on geometries
World Map (1:110m)	world-110m.json	117 KB	TopoJSON	CC-BY-4.0	World country boundaries. Contains countries object. Suitable for world-scale viz.	id property on geometries
London Boroughs	londonBoroughs.json	14 KB	TopoJSON	CC-BY-4.0	London borough boundaries.	properties.BOROUGHN (name)
London Centroids	londonCentroids.json	2 KB	GeoJSON	CC-BY-4.0	Center points for London boroughs.	properties.id, properties.name
London Tube Lines	londonTubeLines.json	78 KB	GeoJSON	CC-BY-4.0	London Underground network lines.	properties.name, properties.color

2. GEOGRAPHIC REFERENCE POINTS (Point Data) 📍

Dataset	File	Size	Format	License	Description	Key Fields / Join Info
US Airports	airports.csv	205 KB	CSV	Public Domain	US airports with codes and coordinates.	iata, state, `l...

Wadi Hasa Sample Dataset — GRASS GIS Location
Version 1.0 (2025-09-19)

Overview
--------
This archive contains a complete GRASS GIS *Location* for the Wadi Hasa region (Jordan), including base data and exemplar analyses used in the Geomorphometry chapter. It is intended for teaching and reproducible research in archaeological GIS.

How to use
----------
1) Unzip the archive into your GRASSDATA directory (or a working folder) and add the Location to your GRASS session.
2) Start GRASS and open the included workspace (Workspace.gxw) or choose a Mapset to work in.
3) Set the computational region to the default extent/resolution for reproducibility:
g.region n=3444220 s=3405490 e=796210 w=733450 nsres=30 ewres=30 -p
4) Inspect layers as needed:
g.list type=rast,vector
r.info

Citation & License
------------------
Please cite this dataset as:

Isaac I. Ullah. 2025. *Wadi Hasa Sample Dataset (GRASS GIS Location)*. Zenodo. https://doi.org/10.5281/zenodo.17162040

All contents are released under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. The original Wadi Hasa survey dataset is available at: https://figshare.com/articles/dataset/Wadi_Hasa_Ancient_Pastoralism_Project/1404216 The original Wadi Hasa survey dataset is available at: https://figshare.com/articles/dataset/Wadi_Hasa_Ancient_Pastoralism_Project/1404216

Coordinate Reference System
---------------------------
- Projection: UTM, Zone 36N
- Datum/Ellipsoid: WGS84
- Units: meter
- Coordinate system and units are defined in the GRASS Location (PROJ_INFO/UNITS).

Default Region (computational extent & resolution)
--------------------------------------------------
- North: 3444220
- South: 3405490
- East: 796210
- West: 733450
- Resolution: 30 (NS), 30 (EW)
- Rows x Cols: 1291 x 2092 (cells: 2700772)

Directory / Mapset Structure
----------------------------
This Location contains the following Mapsets (data subprojects), each with its own raster/vector layers and attribute tables (SQLite):
- Boolean_Predictive_Modeling: 8 raster(s), 4 vector(s)
- ISRIC_soilgrid: 31 raster(s), 0 vector(s)
- Landsat_Imagery: 3 raster(s), 0 vector(s)
- Landscape_Evolution_Modeling: 41 raster(s), 0 vector(s)
- Least_Cost_Analysis: 13 raster(s), 4 vector(s)
- Machine_Learning_Predictive_Modeling: 70 raster(s), 11 vector(s)
- PERMANENT: 4 raster(s), 2 vector(s)
- Sentinel2_Imagery: 4 raster(s), 0 vector(s)
- Site_Buffer_Analysis: 0 raster(s), 2 vector(s)
- Terrain_Analysis: 27 raster(s), 2 vector(s)
- Territory_Modeling: 14 raster(s), 2 vector(s)
- Trace21k_Paleoclimate_Downscale_Example: 4 raster(s), 2 vector(s)
- Visibility_Analysis: 11 raster(s), 5 vector(s)

Data Content (summary)
----------------------
- Total raster maps: 230
- Total vector maps: 34

Raster resolutions present:
- 10 m: 13 raster(s)
- 30 m: 183 raster(s)
- 208.01 m: 2 raster(s)
- 232.42 m: 30 raster(s)
- 1000 m: 2 raster(s)

Major content themes include:
- Base elevation surfaces and terrain derivatives (e.g., DEMs, slope, aspect, curvature, flow accumulation, prominence).
- Hydrology, watershed, and stream-related layers.
- Visibility analyses (viewsheds; cumulative viewshed analyses for Nabataean and Roman towers).
- Movement and cost-surface analyses (isotropic/anisotropic costs, least-cost paths, time-to-travel surfaces).
- Predictive modeling outputs (boolean/inductive/deductive; regression/classification surfaces; training/test rasters).
- Satellite imagery products (Landsat NIR/RED/NDVI; Sentinel‑2 bands and RGB composite).
- Soil and surficial properties (ISRIC SoilGrids 250 m products).
- Paleoclimate downscaling examples (CHELSA TraCE21k MAT/AP).

Vectors include:
- Archaeological point datasets (e.g., WHS_sites, WHNBS_sites, Nabatean_Towers, Roman_Towers).
- Derived training/testing samples and buffer polygons for modeling.
- Stream network and paths from least-cost analyses.

Important notes & caveats
-------------------------
- Mixed resolutions: Analyses span 10 m (e.g., Sentinel‑2 composites, some derived surfaces), 30 m (majority of terrain and modeling rasters), ~232 m (SoilGrids products), and 1 km (CHELSA paleoclimate). Set the computational region appropriately (g.region) before processing or visualization.
- NoData handling: The raw SRTM import (Hasa_30m_SRTM) reports extreme min/max values caused by nodata placeholders. Use the clipped/processed DEMs (e.g., Hasa_30m_clipped_wshed*) and/or set nodata with r.null as needed.
- Masks: MASK rasters are provided for analysis subdomains where relevant.
- Attribute tables: Vector attribute data are stored in per‑Mapset SQLite databases (sqlite/sqlite.db) and connected via layer=1.

Provenance (brief)
------------------
- Primary survey points and site datasets derive from the Wadi Hasa projects (see Figshare record above).
- Base elevation and terrain derivatives are built from SRTM and subsequently processed/clipped for the watershed.
- Soil variables originate from ISRIC SoilGrids (~250 m).
- Paleoclimate examples use CHELSA TraCE21k surfaces (1 km) that are interpolated to higher resolutions for demonstration.
- Satellite imagery layers are derived from Landsat and Sentinel‑2 scenes.

Reproducibility & quick commands
--------------------------------
- Restore default region: g.region n=3444220 s=3405490 e=796210 w=733450 nsres=30 ewres=30 -p
- Set region to a raster: g.region raster=

Change log
----------
- v1.0: Initial public release of the teaching Location on Zenodo (CC BY 4.0).

Contact
-------
For questions, corrections, or suggestions, please contact Isaac I. Ullah

The "Gridded Soil Survey Geographic (gSSURGO) Database State-tile Package" product is derived from the Soil Survey Geographic (2.2) Database dated October 1, 2019. The gSSURGO data were prepared by merging SSURGO digital vector map and tabular data into State-wide extents, and adding a State-wide gridded map layer derived from the vector, plus a new value added look up (valu) table that contains “ready to map attributes”.

SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into State-wide extents, and adding a State-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map” attributes. The gridded map layer is offered in an ArcGIS™ 10.0 file geodatabase raster format.

The raster and vector map data have a State-wide extent. The raster map data have a 10 meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key (MUKEY). A unique map unit key is used to link raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data.

Constraints:
Not to be used for navigation, for informational purposes only. See full disclaimer for more information

These data were produced as part of the study "An empirical social vulnerability map for flood risk assessment at global scale ('GlobE-SoVI')" (in press in Earth's Future, https://doi.org/10.1029/2023EF003895). We provide raster data at 30 arc seconds spatial resolution (folder 'raster') and vector and table data per administrative unit (folder 'admin') of five social vulnerability variables and the final Global Empirical Social Vulnerability Index (GlobE-SoVI) calculated from the five variables. Please see 'overview_table.pdf' for names and units.

The code for data processing and analysis is available at https://github.com/lena-reimann/GlobE-SoVI (https://doi.org/10.5281/zenodo.10671539).

SummaryThis is a zipped package containing details including dataset title, scale and creation dates for the original attribute and spatial data about the input datasets which were used to create NVISv7.0. This package contains a geodatabase, layer file and a readme file.There are three feature classes contained within this geodatabase:- NVIS7_0_KEY_DSET_EXT - NVIS Key to the sources of the extant data- NVIS7_0_KEY_DSET_PRE - NVIS Key to the sources of the pre1750 data- NVIS7_0_LUT_KEY_DSET - NVIS Lookup Table for history of Key LayersThis package is intended to document and describe the input datasets and assist in dynamic analyses of data quality and gaps in the NVIS extant and pre1750 theme datasets. Important information in the spatial feature class includes the dataset spatial extent (i.e. its "footprint") and dataset number and the state of origin of the underlying dataset. Where more than one dataset have been combined within a footprint, the polygons from each data source are represented separately (particularly in NSW and NT); however, "veg clearing" datasets have not been included directly, to keep the number of polygons manageable. See the real NVIS vector or raster data for such data. Important information in the associated lookup table (NVIS7_0_LUT_KEY_DSET) joined via DATA_SET_NUMBER includes data source (e.g. State and Territory NVIS or gap-fill), dataset name, publication scale and the on-ground range of dates of the vegetation surveyInstructions:Join DATA_SET_NUMBER in the table to DATA_SET_NUMBER in the respective spatial key layer, above.

Collated data from disparate sources including vector, raster, and published reports and maps to produce a global delta protection measures database. The dataset includes three layers and a table. Polygon layer containing leveed areas (Leveed Areas) imported from vector data or drawn from suitably georeferencing raster/published data Polygon layer containg boundary area for research focus (Delta Polygons), as created by Edmonds et. al. (2020, doi:10.1038/s41467-020-18531-4) Line layer containing levee, defence, or similar features imported from vector data or drawn from suitably georeferencing raster/published data (Levee Lines). Table recording methodology and decision making process (Delta Index) for each delta polygon, as well as reasons for excluding data, country code, and processing/review fields. Metadata for the dataset in its entirety and the individual layers is additionally published and confirms to the INSPIRE standard. The dataset is structure so that each metadata file is within the respective file when downloaded as a zipped archive. In line with an agreed change, the dataset is now attributed to the student only, and the paper, which contains further work using the data can be found at doi:10.5194/nhess-2021-291

This dataset contains the common Map Unit attributes for each polygon within the gSSURGO database plus NRCS derived attributes from a data summary table called the National Valu Added Look Up (valu) Table #1. It is comprised of 57 pre-summarized or "ready to map" derived soil survey geographic database attributes including soil organic carbon, available water storage, crop productivity indices, crop root zone depths, available water storage within crop root zone depths, drought vulnerable soil landscapes, and potential wetland soil landscapes. Related metadata values for themes are included. These attribute data are pre-summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria. These themes were prepared to better meet the mapping needs of users of soil survey information and can be used with both SSURGO and Gridded SSURGO (gSSURGO) datasets. Gridded SSURGO (gSSURGO) Database is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into State-wide extents, and adding a State-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map" attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format. The raster and vector map data have a State-wide extent. The raster map data have a 10 meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data.VALU Table Content:The map unit average Soil Organic Carbon (SOC) values are given in units of g C per square meter for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), o-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average Available Water Storage (AWS) values are given in units of millimeters for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), 0-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average National Commodity Crop Productivity Index (NCCPI) values (low index values indicate low productivity and high index values indicate high productivity) are provided for major earthy components. NCCPI values are included for corn/soybeans, small grains, and cotton crops. Of these crops, the highest overall NCCPI value is also identified. Earthy components are those soil series or higher level taxa components that can support crop growth. Major components are those soil components where the majorcompflag = 'Yes' in the SSURGO component table. A map unit percent composition for earthy major components is provided. See Dobos, R. R., H. R. Sinclair, Jr, and M. P. Robotham. 2012. National Commodity Crop Productivity Index (NCCPI) User Guide, Version 2. USDA-NRCS. Available at: ftp://ftp-fc.sc.egov.usda.gov/NSSC/NCCPI/NCCPI_user_guide.pdfThe map unit average root zone depth values for commodity crops are given in centimeters for major earthy components. Criteria for root-limiting soil depth include: presence of hard bedrock, soft bedrock, a fragipan, a duripan, sulfuric material, a dense layer, a layer having a pH of less than 3.5, or a layer having an electrical conductivity of more than 12 within the component soil profile. If no root-restricting zone is identified, a depth of 150 cm is used to approximate the root zone depth (Dobos et al., 2012). The map unit average available water storage within the root zone depth for major earthy components value is given in millimeters.Drought vulnerable soil landscapes comprise those map units that have available water storage within the root zone for commodity crops that is less than or equal to 6 inches (152 mm) expressed as "1" for a drought vulnerable soil landscape map unit or "0" for a nondroughty soil landscape map unit or NULL for miscellaneous areas (includes water bodies).The potential wetland soil landscapes (PWSL version 1) information is given as the percentage of the map unit (all components) that meet the criteria for a potential wetland soil landscape. See table column (field) description for criteria details. If water was determined to account for 80 or greater percent of a map unit, a value of 999 was used to indicate a water body. This is not a perfect solution, but is helpful to identifying a general water body class for mapping.The map unit sum of the component percentage representative values is also provided as useful metadata. For all valu table columns, NULL values are presented where data are incomplete or not available. How NoData or NULL values and incomplete data were handled during VALU table SOC and AWS calculations:The gSSURGO calculations for SOC and AWS as reported in the VALU table use the following data checking and summarization rules. The guiding principle was to only use the official data in the SSURGO database, and not to make assumptions in case there were some data entry errors. However, there were a few exceptions to this principle if there was a good reason for a Null value in a critical variable, or to accommodate the data coding conventions used in some soil surveys.Horizon depths considerations:If the depth to the top of the surface horizon was missing, but otherwise the horizon depths were all okay, then the depth to the top of the surface horizon (hzdept_r) was set to zero.If the depth to the bottom of the last horizon was missing, and the horizon represented bedrock or had missing bulk density, the depth to the bottom was set to equal to the depth to the top of the same horizon (hzdepb_r = hzdept_r), effectively giving the horizon zero thickness (and thus zero SOC or AWS), but not blocking calculation of other horizons in the profile due to horizon depth errors.Other types of horizon depth errors were considered uncorrectable, and led to all horizon depths for the component being set to a NoData value, effectively eliminating the component from the analysis. The errors included gaps or overlaps in the horizon depths of the soil profile, other cases of missing data for horizon depths, including missing data for the bottom depth of the last horizon if the soil texture information did not indicate bedrock and a bulk density value was coded. The SOC or AWS values were effectively set to zero for components eliminated in this way, so the values at the map unit level could be an underestimate for some soils.Horizon rock fragment considerations:Part of the algorithm for calculating the SOC requires finding the volume of soil that is not rock. This requires three SSURGO variables that indicate rock fragments (fraggt10_r, frag3to10_r, and sieveno10_r). If the soil is not organic, and any of these are missing, then the ratio of the volume of soil fines to the total soil volume was set to “NoData†, and the SOC results were coded as “NoData†and effectively set to zero for the horizon. If the soil is organic, then it may be logical that no measurement of rock fragments was made, and default values for the “zero rock†situation was assumed for these variables (i.e., fraggt10_r = 0, frag3to10_r = 0, sieveno10_r = 100). Organic soils were identified by an “O†in the horizon designator or the texture code represented “Peat†, “Muck†or “Decomposed Plant Material†. If all three of the fragment variables were present, but indicated more than 100% rock, then 100% rock was assumed (zero volume of soil and thus zero for SOC). The rock fragment variables do not influence the AWS calculation because rock content is already accounted for in the available water capacity (awc_r) variable at the horizon level.Horizon to component summary:To summarize data from the horizon level to the component level, the evaluation proceeded downward from the surface. If a valid value for AWS could not be calculated for any horizon, then the result for that horizon and all deeper horizons was set to NoData. The same rule was separately applied to the SOC calculation, so it was possible to have results for SOC but not AWS, or vice versa.Component to mapunit summary:To summarize data from the component level to the map unit level, the component percentages must be valid. There are tests both of the individual component percentage (comppct_r) data, and also of the sum of the component percentages at the map unit level (mu_sum_comppct_r). For the gSSURGO VALU table, the following rules were applied for the individual components: 1) The comppct_r must be in the range from 0 to 100, inclusive. 2) Individual components with a comppct_r that was Null (nothing coded) were ignored. A zero comppct_r value excludes

The gSSURGO dataset provides detailed soil survey mapping in raster format with ready-to-map attributes organized in statewide tiles for desktop GIS. gSSURGO is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO generally has the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes and are derived from properties and characteristics stored in the National Soil Information System (NASIS).

The gSSURGO data were prepared by merging the traditional vector-based SSURGO digital map data and tabular data into statewide extents, adding a statewide gridded map layer derived from the vector layer, and adding a new value-added look up table (valu) containing ready-to-map attributes. The gridded map layer is in an ArcGIS file geodatabase in raster format, thus it has the capacity to store significantly more data and greater spatial extents than the traditional SSURGO product. The raster map data have a 10-meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link the raster cells and polygons to attribute tables.

For more information, see the gSSURGO webpage: https://www.nrcs.usda.gov/resources/data-and-reports/description-of-gridded-soil-survey-geographic-gssurgo-database

Data about the top and bottom altitude, depth from land surface and/or the thickness of three geologic units in Tennessee were converted into geospatial format for this USGS data release from previously published paper maps and converted into digital formats for use by the public. The three geologic units were the Chattanooga Shale of Mississippian-Devonian age (Moore and Horton, 1999), the Wells Creek Dolomite of middle Ordovician age (Smith, 1959), and the Knox Group of lower Ordovician age (Newcome, 1954). These geologic units represent important geologic horizons across Tennessee. Geologic structure maps provide important information and, in digital format, support investigative and modeling efforts pertaining to water and mineral resources. Prior to this work, the paper source maps used for this data release existed in limited quantities, mainly restricted to the Nashville, TN offices of the Tennessee Department of Environment and Conservation (TDEC) and United States Geological Survey (USGS). The work for this project included (1) scanning and georeferencing original paper maps to create georeferenced images (GRI), (2) digitizing well _location points and contour lines, (3) populating well and contour attribute tables with data from maps and associated reports, and (4) when possible, interpolating raster surfaces for the three geologic units of top and bottom altitude, depth from land surface to the top and bottom surface, and thickness. All raster surfaces were aligned to a modified version of the National Hydrogeologic Grid (Clark and others, 2018) to support USGS Lower Mississippi Gulf Water Science Center efforts to create a statewide hydrogeologic framework. All horizontal coordinated data are projected to NAD 1983 USGS Contiguous USA Albers. The raster vertical coordinate information was referenced to the North American Vertical Datum of 1988 (NAVD 88). This data release includes GRIs, vector data of the wells and mapped contours of top, bottom, or thickness, raster data, and related metadata files for each three geologic units under the associated child item tab. Dataset types can be identified by the following naming convention: i_ = georeferenced map images (GRI) po_ = points c_ = contours and closed depressions f_= faults and other structural features p_ = extent polygon ra_ = altitude raster rd_ = depth from land surface raster rt_ = thickness raster The datasets included on this main landing page are as follows: project_metadata.xml – metadata file for general project information studyarea_ext.zip: p_chttshl_ext.shp - mapped extent of the Chattanooga Shale in Tennessee p_wllscr_ext.shp - mapped extent of the Wells Creek Dolomite in Tennessee p_knx_ext.shp - mapped extent of the Knox Group in Tennessee The datasets included on the child item pages are as follows: Chattanooga Shale: geospatial geologic structural datasets in Tennessee: chttshl_metadata.xml - metadata file chttshl_alldata.zip: GRI/ i_chttshl_btm.tif - structure contour map of the bottom of the Chattanooga Shale (Moore and Horton, 1999) i_chttshl_data.tif - map of data used to create structure and isopach maps (Moore and Horton, 1999) i_chttshl_thk.tif - thickness contour map for the Chattanooga Shale (Moore and Horton, 1999) polygons/ p_knx_ext.shp - study area extent for the Chattanooga Shale p_hohenwald.shp - polygon for extend of the Hohenwald Platform (Moore and Horton, 1999) - supplemental data rasters/ ra_chttshl_btm.tif - altitude raster for the bottom of the Chattanooga Shale ra_chttshl_tp.tif - altitude raster for the top of the Chattanooga Shale rd_chttshl_btm.tif - depth from land surface raster of the bottom of the Chattanooga Shale rd_chttshl_tp.tif - depth from land surface raster of the top of the Chattanooga Shale rt_chttshl.tif - thickness raster for the Chattanooga Shale vectors/ c_chttshl_btm.shp - structure contours for the bottom of the Chattanooga Shale c_chttshl_btm_modified.shp - modified structure contours for the bottom of the Chattanooga Shale (hachures removed from closed basins). This vector used to interpolated raster for the bottom of the Chattanooga Shale c_chttshl_thk.shp - thickness contours for the Chattanooga Shale c_chttshl_thk_modified.shp - modified thickness contours for the Chattanooga Shale (hachures removed from closed basins). This vector used to interpolated raster for the thickness of the Chattanooga Shale po_chttshl.shp - point data of altitude and thickness for the Chattanooga Shale Knox Group: geospatial geologic structural datasets in Middle Tennessee: knx_metadata.xml - metadata file knx_alldata.zip: GRI/ i_knx_tp.tif - structure contour map on the top of the Knox Group (Newcome, 1954) i_knx_outcrop.tif - map of the Wells Creek Disturbance (Wilson and Stearns, 1968) polygons/ p_chttshl_ext.shp - study area extent for the Knox Group p_hohenwald.shp - extent of the Hohenwald Platform - supplemental data rasters/ ra_knx_tp.tif - altitude raster for the top of the Knox Group rd_knx_tp.tif - depth from land surface raster of the top of Knox Group vectors/ c_knx_tp.shp - structure contours for the top of the Knox Group c_knx_tp_modified.shp - modified structure contours for the top of the Knox Group (hachures removed from closed basins). This vector used to interpolated raster for the top of the Knox Group po_knx_tp.shp - point data for the altitude of top of the Knox Group Wells Creek Dolomite: geospatial geologic structural datasets in Tennessee: wllscr_metadata.xml - metadata file wllscr_alldata.zip: GRI/ i_wllscr.tif - thickness contour map for the Wells Creek Dolomite (Smith, 1959) polygons/ p_wllscr_ext.shp - study area extent for the Wells Creek Dolomite rasters/ ra_wllscr_btm.tif - altitude raster for the bottom of the Wells Creek Dolomite (same dataset as ra_knx_tp.tif [Newcome, 1954; Smith, 1959]) ra_wllscr_tp.tif - altitude raster for the top of the Wells Creek Dolomite rd_wllscr_btm.tif - depth from land surface raster of the bottom of the Wells Creek Dolomite (same dataset as ra_knx_tp.tif [Newcome, 1954; Smith, 1959]) rd_wllscr_tp.tif - depth from land surface raster of the top of the Wells Creek Dolomite rt_wllscr.tif - thickness raster for the Wells Creek Dolomite vectors/ c_wllscr.shp - thickness contours for the Wells Creek Dolomite po_wllscr.shp - point data for the thickness of Wells Creek Dolomite References: Moore, J.L., and Horton, A.B., 1999, Structure and Isopach Maps of the Chattanooga Shale in Tennessee, Tennessee Dept. of Conservation, Division of Geology, Report of Investigations 48, 3 plates. Newcome, R. Jr., 1954, Structure contour map on top of the Knox Dolomite in Middle Tennessee, Tennessee Division of Geology, Ground-Water Investigations Preliminary Chart 5, 1 sheet. Smith, O. Jr., 1959, Isopach map of the Wells Creek Dolomite in Middle Tennessee: Tennessee Division of Water Resources, one sheet. Wilson, C.W. and Stearns, R.G., 1968 Geology of the Wells Creek Structure, Tennessee: Tennessee Division of Geology, Bulletin 68, 248 p.

This is a collection of 134 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. (2020) 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. (2020). Sub-category- as structured in Lindersson et al. (2020). Abbreviation - official or as specified in Lindersson et al. (2020). 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 digital GIS dataset and accompanying nonspatial files synthesize model outputs from a regional-scale volumetric 3-D geologic model that portrays the generalized subsurface geology of the Powder River Basin and Williston Basin regions from a wide variety of input data sources. The study area includes the Hartville Uplift, Laramie Range, Bighorn Mountains, Powder River Basin, and Williston Basin. The model data released here consist of the stratigraphic contact elevation of major Phanerozoic sedimentary units that broadly define the geometry of the subsurface, the elevation of Tertiary intrusive and Precambrian basement rocks, and point data that illustrate an estimation of the three-dimensional geometry of fault surfaces. The presence of folds and unconformities are implied by the 3D geometry of the stratigraphic units, but these are not included as discrete features in this data release. The 3D geologic model was constructed from a wide variety of publicly available surface and subsurface geologic data; none of these input data are part of this Data Release, but data sources are thoroughly documented such that a user could obtain these data from other sources if desired. The PowderRiverWilliston3D geodatabase contains 40 subsurface horizons in raster format that represent the tops of modeled subsurface units, and a feature dataset “GeologicModel”. The GeologicModel feature dataset contains a feature class of 30 estimated faults served in elevation grid format (FaultPoints), a feature class illustrating the spatial extent of 22 fault blocks (FaultBlockFootprints), and a feature class containing a polygon delineating the study areas (ModelBoundary). Nonspatial tables define the data sources used (DataSources), define terms used in the dataset (Glossary), and provide a description of the modeled surfaces (DescriptionOfModelUnits). Separate file folders contain the vector data in shapefile format, the raster data in ASCII format, and the tables as comma-separated values. In addition, a tabular data dictionary describes the entity and attribute information for all attributes of the geospatial data and the accompanying nonspatial tables (EntityAndAttributes). An included READ_ME file documents the process of manipulating and interpreting publicly available surface and subsurface geologic data to create the model. It additionally contains critical information about model units, and uncertainty regarding their ability to predict true ground conditions. Accompanying this data release is the “PowderRiverWillistonInputSummaryTable.csv”, which tabulates the global settings for each fault block, the stratigraphic horizons modeled in each fault block, the types and quantity of data inputs for each stratigraphic horizon, and then the settings associated with each data input.

This is an updated and extended record of the Global Fire Atlas introduced by Andela et al. (2019). Input data (burned area and land cover products) are updated to the MODIS Collection 6.1 (the previous version was based on collection 6.0 burned area and collection 5.1 land cover products, respectively). The timeseries is extended to cover the period 2002 to February 2024.

Methodological Notes:

The method employed to create the dataset precisely follows the approach described by Andela et al. (2019).

The input burned area product is MCD64A1 Collection 6.1. It is described by Giglio et al. (2018) and available at: https://lpdaac.usgs.gov/products/mcd64a1v061/.

The input land cover product is MCD12Q1 Collection 6.1. It is described by Sulla-Menashe et al. (2019) and available at: https://lpdaac.usgs.gov/products/mcd12q1v061/.

Note that while the methods have remained the same compared to Andela et al. (2019), we do observe small differences between the Global Fire Atlas products originating from differences between the MCD64A1 collection 6.1 burned area data used here and the collection 6 data used in the original product. In addition, we observe more substantial differences in the dominant land cover class associated with each fire due to the differences between the MCD12Q1 collection 6.1 data used here and collection 5.1 data used in the original product.

The original dataset included time series from 2003 to 2016, including the full fire season for each year. For each MODIS tile, the fire season is defined as the twelve months centred on the month with peak burend area (see Andela et al., 2019). Here we extended the time-series to include the fire season of 2002, and extended the time-series until February 2024. Therefore, both the 2023 and 2024 files will contain incomplete records. For example, for a MODIS tile with peak burned area in December, the 2023 fire season would be defined as the period from July 2023 to June 2024, with the current record ending in February 2024. For the purpose of time-series analysis, we note that the 2002 product may have been affected by outages of Terra-MODIS (most notably, June 15 2001 - July 3 2001 and March 19 2002 - March 28 2002), which affects the burn date estimates and Global Fire Atlas product. Following the launch of Aqua-MODIS in May 2002 burn date estimates are more reliable as estimated from both MODIS sensors onboard Terra and Aqua.

Usage Notes:

Table 1: Overview of the Global Fire Atlas data layers. The shapefiles of ignition locations (point) and fire perimeters (polygon) contain attribute tables with summary information for each individual fire, while the underlying 500 m gridded layers reflect the day-to-day behavior of the individual fires. In addition, we provide aggregated monthly summary layers at a 0.25° resolution for regional and global analyses.

File name Content

SHP_ignitions.zip Shapefiles of ignition locations with attribute tables (see Table 2)

SHP_perimeters.zip Shapefiles of final fire perimeters with attribute tables (see Table 2)

GeoTIFF_direction.zip 500 m resolution daily gridded data on direction of spread (8 classes)

GeoTIFF_day_of_burn.zip 500 m resolution daily gridded data on day of burn (day of year; 1-366)

GeoTIFF_speed.zip 500 m resolution daily gridded data on speed (km/day)

GeoTIFF_fire_line.zip 500 m resolution daily gridded data on the fire line (day of year; 1-366)

GeoTIFF_monthly_summaries.zip Aggregated 0.25° resolution monthly summary layers. These files include the sum of ignitions, average size (km2), average duration (days), average daily fire line (km), average daily fire expansion (km2/day), average speed (km/day), and dominant direction of spread (8 classes).

Table 2: Overview of the Global Fire Atlas shapefile attribute tables. The shapefiles of ignition locations (point) and fire perimeters (polygon) contain attribute tables with summary information for each individual fire.

Attribute Explanation / units

lat, lon Coordinates of ignition location (°)

size Fire size (km2)

perimeter Fire perimeter (km)

start_date, start_DOY Start date (yyyy-mm-dd), start day of year (1-366)

end_date, end_DOY End date (yyyy-mm-dd), end day of year (1-366)

duration Duration (days)

fire_line Average length of daily fire line (km)

spread Average daily fire growth (km2/day)

speed Average speed (km/day)

direction, direc_frac Dominant direction of spread (N, NE, E, SE, S, SW, W, NW) and associated fraction

MODIS_tile MODIS tile id

landcover, landc_frac MCD12Q1 dominant land cover class and fraction (UMD classification), provided for 2002-2023

GFED_regio GFED region (van der Werf et al., 2017; available at https://www.globalfiredata.org/)

File Naming Convention:

GFA_v{time-stamp}_{data-type}_{fire_season}.{file_type}

{time-stamp} = Date that code was run.

{data-type} = “ignitions” or “perimeters” for vector files; “day_of_burn”, “direction”, “fire_line”, or “speed” for raster files.

{fire_season} = the locally-defined fire season in which the fire was ignited (see more below).

{file_type} = ".shp" for vector files; ".tif" for raster files.

Fire Season Convention:

Please note that the year string in filenames refers to the locally-defined fire season in which the fire ignited, not the calendar year. Hence the file GFA_v20240409_perimeters_2003.shp can include fires from the 2003 fire season that ignited in the calendar years 2002 or 2004. This is particularly relevant in the Southern extratropics and the northern hemisphere subtropics, where the fire seasons often span the new year. The local definition of the fire season is based on climatological peak in burned area as described by Andela et al. (2019).

Projections:

Vector data are provided on the WGS84 projection.

Raster data are provided on the MODIS sinusoidal projection used in NASA tiled products.

This digital GIS dataset and accompanying nonspatial files synthesize the model outputs from a regional-scale volumetric 3-D geologic model that portrays the generalized subsurface geology of western South Dakota from a wide variety of input data sources.The study area includes all of western South Dakota from west of the Missouri River to the Black Hills uplift and Wyoming border. The model data released here consist of the stratigraphic contact elevation of major Phanerozoic sedimentary units that broadly define the geometry of the subsurface, the elevation of Tertiary intrusive and Precambrian basement rocks, and point data representing the three-dimensional geometry of fault surfaces. the presence of folds and unconformities are implied by the 3D geometry of the stratigraphic units, but these are not included as discrete features in this data release. The 3D geologic model was constructed from a wide variety of publicly available surface and subsurface geologic data; none of these input data are part of this Data Release, but data sources are thoroughly documented such that a user could obtain these data from other sources if desired. This model was created as part of the U.S. Geological Survey’s (USGS) National Geologic Synthesis (NGS) project—a part of the National Cooperative Geologic Mapping Program (NCGMP). The WSouthDakota3D geodatabase contains twenty-five (25) subsurface horizons in raster format that represent the tops of modeled subsurface units, and a feature dataset “GeologicModel”. The GeologicModel feature dataset contains a feature class of thirty-five (35) faults served in elevation grid format (FaultPoints). The feature class “ModelBoundary” describes the footprint of the geologic model, and was included to meet the NCGMP’s GeMS data schema. Nonspatial tables define the data sources used (DataSources), define terms used in the dataset (Glossary), and provide a description of the modeled surfaces (DescriptionOfModelUnits). Separate file folders contain the vector data in shapefile format, the raster data in ASCII format, and the nonspatial tables as comma-separated values. In addition, a tabular data dictionary describes the entity and attribute information for all attributes of the geospatial data and the accompanying nonspatial tables (EntityAndAttributes). An included READ_ME file documents the process of manipulating and interpreting publicly available surface and subsurface geologic data to create the model. It additionally contains critical information about model units, and uncertainty regarding their ability to predict true ground conditions. Accompanying this data release is the “WSouthDakotaInputSummaryTable.csv”, which tabulates the global settings for each fault block, the stratigraphic horizons modeled in each fault block, the types and quantity of data inputs for each stratigraphic horizon, and then the settings associated with each data input.

The datasets used in the creation of the predicted Habitat Suitability models includes the CWHR range maps of Californias regularly-occurring vertebrates which were digitized as GIS layers to support the predictions of the CWHR System software. These vector datasets of CWHR range maps are one component of California Wildlife Habitat Relationships (CWHR), a comprehensive information system and predictive model for Californias wildlife. The CWHR System was developed to support habitat conservation and management, land use planning, impact assessment, education, and research involving terrestrial vertebrates in California. CWHR contains information on life history, management status, geographic distribution, and habitat relationships for wildlife species known to occur regularly in California. Range maps represent the maximum, current geographic extent of each species within California. They were originally delineated at a scale of 1:5,000,000 by species-level experts and have gradually been revised at a scale of 1:1,000,000. For more information about CWHR, visit the CWHR webpage (https://www.wildlife.ca.gov/Data/CWHR). The webpage provides links to download CWHR data and user documents such as a look up table of available range maps including species code, species name, and range map revision history; a full set of CWHR GIS data; .pdf files of each range map or species life history accounts; and a User Guide.The models also used the CALFIRE-FRAP compiled "best available" land cover data known as Fveg. This compilation dataset was created as a single data layer, to support the various analyses required for the Forest and Rangeland Assessment, a legislatively mandated function. These data are being updated to support on-going analyses and to prepare for the next FRAP assessment in 2015. An accurate depiction of the spatial distribution of habitat types within California is required for a variety of legislatively-mandated government functions. The California Department of Forestry and Fire Protections CALFIRE Fire and Resource Assessment Program (FRAP), in cooperation with California Department of Fish and Wildlife VegCamp program and extensive use of USDA Forest Service Region 5 Remote Sensing Laboratory (RSL) data, has compiled the "best available" land cover data available for California into a single comprehensive statewide data set. The data span a period from approximately 1990 to 2014. Typically the most current, detailed and consistent data were collected for various regions of the state. Decision rules were developed that controlled which layers were given priority in areas of overlap. Cross-walks were used to compile the various sources into the common classification scheme, the California Wildlife Habitat Relationships (CWHR) system.CWHR range data was used together with the FVEG vegetation maps and CWHR habitat suitability ranks to create Predicted Habitat Suitability maps for species. The Predicted Habitat Suitability maps show the mean habitat suitability score for the species, as defined in CWHR. CWHR defines habitat suitability as NO SUITABILITY (0), LOW (0.33), MEDIUM (0.66), or HIGH (1) for reproduction, cover, and feeding for each species in each habitat stage (habitat type, size, and density combination). The mean is the average of the reproduction, cover, and feeding scores, and can be interpreted as LOW (less than 0.34), MEDIUM (0.34-0.66), and HIGH (greater than 0.66) suitability. Note that habitat suitability ranks were developed based on habitat patch sizes >40 acres in size, and are best interpreted for habitat patches >200 acres in size. The CWHR Predicted Habitat Suitability rasters are named according to the 4 digit alpha-numeric species CWHR ID code. The CWHR Species Lookup Table contains a record for each species including its CWHR ID, scientific name, common name, and range map revision history (available for download at https://www.wildlife.ca.gov/Data/CWHR).

This versatile agricultural land data is a collection of raster datasets (GeoTIFF format) used to provide a synopsis of the land suitability data of the 21 crop groups and their specific irrigation management systems and seasons in the Southern Gulf catchments of the Northern Territory and Queensland. Five datasets are in this collection. The definitive versatile agricultural land dataset (Ag_Versatility_14_Crops_S.tif) was determined by identifying where the largest number of the 14 selected land management options were mapped as being suitable (i.e. suitability classes 1 to 3, refer to report cited with this metadata record). This analysis summarised the suitability of the selected land management options for each pixel, and highlights those pixels that are potentially more versatile for agricultural development because they are likely to suit a larger range of land management options and enterprises eg the score of zero represents the least versatile land, while the score of 14 represents the most versatile. The data values represent the number of land management options suitable for that pixel. The selected land management options were chosen to be relative to general potential agronomic experience and development aspirations of potential stakeholders in the catchments and were derived in consultation with the agricultural viability activity in SOGWRA. These selections are presented in Table 3-26 of the published report; ' Soils and land suitability for the Southern Gulf catchments’. A technical report from the CSIRO Southern Gulf Water Resource Assessment to the Government of Australia. Similarly, the selection of a different representative set from the land management options would result in a different versatility map outcome. In addition to the selected set of 14 land management options, versatile agricultural land is also presented using the subsets of each of the irrigation types (and rainfed cropping). In this case, the land management options were assigned to rainfed (8), furrow (17), spray (23) or trickle irrigation (10). The data values represent the number of land management options suitable for that pixel. Analytical products like these help to identify land where particular types of irrigation-related infrastructure investment may be best targeted. This data provides improved land evaluation information to identify opportunities and promote detailed investigation for a range of sustainable development options. It is important to emphasize that this is a regional-scale assessment: further data collection and detailed soil physical, chemical and nutrient analyses would be required to plan development at a scheme, enterprise or property scale. Several limitations that may have a bearing on land suitability were out of scope and not assessed as part of this activity (refer to the report), these limitations include biophysical and socio-cultural. For example these versatile agricultural land raster datasets do not include consideration of the licensing of water, flood risk, contiguous land, risk of irrigation induced secondary salinity, or land tenure and other legislative controls. Some of these may be addressed elsewhere in SOGWRA eg flooding was investigated by the Earth observation remote sensing group in the surface water activity. The Southern Gulf Water Resource Assessment provides a comprehensive overview and integrated evaluation of the feasibility of aquaculture and agriculture development in the Southern Gulf catchments NT and Qld as well as the ecological, social and cultural (indigenous water values, rights and aspirations) impacts of development. Lineage: These versatile agricultural land raster datasets have been generated from a range of inputs and processing steps. Following is an overview. For more information refer to the CSIRO SOGWRA published report ' Soils and land suitability for the Southern Gulf catchments’. A technical report from the CSIRO Southern Gulf Water Resource Assessment to the Government of Australia. 1. Collated existing data (relating to: soils, climate, topography, natural resources, remotely sensed, of various formats: reports, spatial vector, spatial raster etc). 2. Selection of additional soil and land attribute site data locations by a conditioned Latin hypercube statistical sampling method applied across the covariate data space. 3. Fieldwork was carried out to collect new attribute data, soil samples for analysis and build an understanding of geomorphology and landscape processes. 4. Database analysis was performed to extract the data to specific selection criteria required for the attribute to be modelled. 5. The R statistical programming environment was used for the attribute computing. Models were built from selected input data and covariate data using predictive learning from a Random Forest approach implemented in the ranger R package. 6. Create Digital Soil Mapping (DSM) attribute raster datasets. DSM data is a geo-referenced dataset, generated from field observations and laboratory data, coupled with environmental covariate data through quantitative relationships. It applies pedometrics - the use of mathematical and statistical models that combine information from soil observations with information contained in correlated environmental variables, remote sensing images and some geophysical measurements. 7. Land management options were chosen and suitability rules created for DSM attributes. 8. Suitability rules were run to produce limitation subclass datasets using a modification on the FAO methods. 9. Final suitability data created for all land management options. 10. Companion predicted reliability data was produced from the 500 individual Random Forest attribute models created. 11. QA Quality assessment of these land suitability data was conducted by two methods. Method 1: Statistical (quantitative) assessment of the "reliability" of the spatial output data presented as a raster of the Confusion Index. Method 2: A workshop was conducted in March 2023 to review DSM soil attribute and land suitability products and facilitated an alternative to the field external validation carried out in other northern Australia water resource assessments. Stakeholders from the NT and Qld jurisdictions reviewed, evaluated and discussed the soundness of the data and processes. The workshop desk top assessment approach provided recommendations for acceptance, improvement and re-modelling of attributes based on expert knowledge and understanding of the soil distribution and landscape in the study area and available data. 12. Select the 14 land management options for the catchments in consultation with the agricultural viability activity. 13. Calculate the versatile agricultural land datasets

The Federal Emergency Management Agency (FEMA) produces Flood Insurance Rate maps and identifies Special Flood Hazard Areas as part of the National Flood Insurance Program's floodplain management. Special Flood Hazard Areas have regulations that include the mandatory purchase of flood insurance for holders of federally regulated mortgages. In addition, this layer can help planners and firms avoid areas of flood risk and also avoid additional cost to carry insurance for certain planned activities. Dataset SummaryPhenomenon Mapped: Flood Hazard AreasGeographic Extent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands and American Samoa.Projection: Web Mercator Auxiliary SphereData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii), Western Pacific Albers Equal Area Conic (Guam, Northern Mariana Islands, and American Samoa)Cell Sizes: 10 meters (default), 30 meters, and 90 metersUnits: NoneSource Type: ThematicPixel Type: Unsigned integerSource: Federal Emergency Management Agency (FEMA)Update Frequency: AnnualPublication Date: May 7, 2025 This layer is derived from the May 7, 2025 version Flood Insurance Rate Map feature class S_FLD_HAZ_AR. The vector data were then flagged with an index of 94 classes, representing a unique combination of values displayed by three renderers. (In three resolutions the three renderers make nine processing templates.) Repair Geometry was run on the set of features, then the features were rasterized using the 94 class index at a resolutions of 10, 30, and 90 meters, using the Polygon to Raster tool and the "MAXIMUM_COMBINED_AREA" option. Not every part of the United States is covered by flood rate maps. This layer compiles all the flood insurance maps available at the time of publication. To make analysis easier, areas that were NOT mapped by FEMA for flood insurance rates no longer are served as NODATA but are filled in with a value of 250, representing any unmapped areas which appear in the US Census boundary of the USA states and territories. The attribute table corresponding to value 250 will indicate that the area was not mapped.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application. Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "flood hazard areas" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "flood hazard areas" in the search box, browse to the layer then click OK. In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro. The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one. Processing TemplatesCartographic Renderer - The default. These are meaningful classes grouped by FEMA which group its own Flood Zone Type and Subtype fields. This renderer uses FEMA's own cartographic interpretations of its flood zone and zone subtype fields to help you identify and assess risk. Flood Zone Type Renderer - Specifically renders FEMA FLD_ZONE (flood zone) attribute, which distinguishes the original, broadest categories of flood zones. This renderer displays high level categories of flood zones, and is less nuanced than the Cartographic Renderer. For example, a fld_zone value of X can either have moderate or low risk depending on location. This renderer will simply render fld_zone X as its own color without identifying "500 year" flood zones within that category.Flood Insurance Requirement Renderer - Shows Special Flood Hazard Area (SFHA) true-false status. This may be helpful if you want to show just the places where flood insurance is required. A value of True means flood insurance is mandatory in a majority of the area covered by each 10m pixel. Each of these three renderers have templates at three different raster resolutions depending on your analysis needs. To include the layer in web maps to serve maps and queries, the 10 meter renderers are the preferred option. These are served with overviews and render at all resolutions. However, when doing analysis of larger areas, we now offer two coarser resolutions of 30 and 90 meters in processing templates for added convenience and time savings.Data DictionaryMaking a copy of your area of interest using copyraster in arcgis pro will copy the layer's attribute table to your network alongside the local output raster. The raster attribute table in the copied raster will contain the flood zone, zone subtype, and special flood hazard area true/false flag which corresponds to each value in the layer for your area of interest. For your convienence, we also included a table in CSV format in the box below as a data dictionary you can use as an index to every value in the layer. Value,FLD_ZONE,ZONE_SUBTY,SFHA_TF 2,A,, 3,A,,F 4,A,,T 5,A,,T 6,A,,T 7,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 8,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 9,A,ADMINISTRATIVE FLOODWAY,T 10,A,COASTAL FLOODPLAIN,T 11,A,FLOWAGE EASEMENT AREA,T 12,A99,,T 13,A99,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 14,AE,,F 15,AE,,T 16,AE,,T 17,AE,,T 18,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 19,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 20,AE,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",T 21,AE,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",T 22,AE,ADMINISTRATIVE FLOODWAY,T 23,AE,AREA OF SPECIAL CONSIDERATION,T 24,AE,COASTAL FLOODPLAIN,T 25,AE,COLORADO RIVER FLOODWAY,T 26,AE,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 27,AE,COMMUNITY ENCROACHMENT,T 28,AE,COMMUNITY ENCROACHMENT AREA,T 29,AE,DENSITY FRINGE AREA,T 30,AE,FLOODWAY,T 31,AE,FLOODWAY CONTAINED IN CHANNEL,T 32,AE,FLOODWAY CONTAINED IN STRUCTURE,T 33,AE,FLOWAGE EASEMENT AREA,T 34,AE,RIVERINE FLOODWAY IN COMBINED RIVERINE AND COASTAL ZONE,T 35,AE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 36,AE,STATE ENCROACHMENT AREA,T 37,AH,,T 38,AH,,T 39,AH,FLOODWAY,T 40,AO,,T 41,AO,COASTAL FLOODPLAIN,T 42,AO,FLOODWAY,T 43,AREA NOT INCLUDED,,F 44,AREA NOT INCLUDED,,T 45,AREA NOT INCLUDED,,U 46,D,,F 47,D,,T 48,D,AREA WITH FLOOD RISK DUE TO LEVEE,F 49,OPEN WATER,,F 50,OPEN WATER,,T 51,OPEN WATER,,U 52,V,,T 53,V,COASTAL FLOODPLAIN,T 54,VE,,T 55,VE,,T 56,VE,COASTAL FLOODPLAIN,T 57,VE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 58,X,,F 59,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,F 60,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,T 61,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,U 62,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,F 63,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,F 64,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COASTAL ZONE,F 65,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COMBINED RIVERINE AND COASTAL ZONE,F 66,X,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",F 67,X,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",F 68,X,1 PCT DEPTH LESS THAN 1 FOOT,F 69,X,1 PCT DRAINAGE AREA LESS THAN 1 SQUARE MILE,F 70,X,1 PCT FUTURE CONDITIONS,F 71,X,1 PCT FUTURE CONDITIONS CONTAINED IN STRUCTURE,F 72,X,"1 PCT FUTURE CONDITIONS, COMMUNITY ENCROACHMENT",F 73,X,"1 PCT FUTURE CONDITIONS, FLOODWAY",F 74,X,"1 PCT FUTURE IN STRUCTURE, COMMUNITY ENCROACHMENT",F 75,X,"1 PCT FUTURE IN STRUCTURE, FLOODWAY",F 76,X,AREA OF MINIMAL FLOOD HAZARD, 77,X,AREA OF MINIMAL FLOOD HAZARD,F 78,X,AREA OF MINIMAL FLOOD HAZARD,T 79,X,AREA OF MINIMAL FLOOD HAZARD,U 80,X,AREA OF SPECIAL CONSIDERATION,F 81,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,F 82,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 83,X,FLOWAGE EASEMENT AREA,F 84,X,1 PCT FUTURE CONDITIONS,T 85,AH,COASTAL FLOODPLAIN,T 86,AE,,U 87,AE,FLOODWAY,F 88,X,AREA WITH REDUCED FLOOD HAZARD DUE TO ACCREDITED LEVEE SYSTEM,F 89,X,530,F 90,VE,100,T 91,AE,100,T 92,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO LEVEE SYSTEM,T 93,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO NON-ACCREDITED LEVEE SYSTEM,T 94,A,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 250,AREA NOT INCLUDED,Not Mapped by FEMA, Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.

Resource contains an ArcGIS file geodatabase raster for the National Vegetation Information System (NVIS) Major Vegetation Groups - Australia-wide, present extent (FGDB_NVIS4_1_AUST_MVG_EXT).

Related datasets are also included: FGDB_NVIS4_1_KEY_LAYERS_EXT - ArcGIS File Geodatabase Feature Class of the Key Datasets that make up NVIS Version 4.1 - Australia wide; and FGDB_NVIS4_1_LUT_KEY_LAYERS - Lookup table for Dataset Key Layers.

This raster dataset provides the latest summary information (November 2012) on Australia's present (extant) native vegetation. It is in Albers Equal Area projection with a 100 m x 100 m (1 Ha) cell size. A comparable Estimated Pre-1750 (pre-european, pre-clearing) raster dataset is available: - NVIS4_1_AUST_MVG_PRE_ALB. State and Territory vegetation mapping agencies supplied a new version of the National Vegetation Information System (NVIS) in 2009-2011. Some agencies did not supply new data for this version but approved re-use of Version 3.1 data. Summaries were derived from the best available data in the NVIS extant theme as at June 2012. This product is derived from a compilation of data collected at different scales on different dates by different organisations. Please refer to the separate key map showing scales of the input datasets. Gaps in the NVIS database were filled by non-NVIS data, notably parts of South Australia and small areas of New South Wales such as the Curlewis area. The data represent on-ground dates of up to 2006 in Queensland, 2001 to 2005 in South Australia (depending on the region) and 2004/5 in other jurisdictions, except NSW. NVIS data was partially updated in NSW with 2001-09 data, with extensive areas of 1997 data remaining from the earlier version of NVIS. Major Vegetation Groups were identified to summarise the type and distribution of Australia's native vegetation. The classification contains different mixes of plant species within the canopy, shrub or ground layers, but are structurally similar and are often dominated by a single genus. In a mapping sense, the groups reflect the dominant vegetation occurring in a map unit where there are a mix of several vegetation types. Subdominant vegetation groups which may also be present in the map unit are not shown. For example, the dominant vegetation in an area may be mapped as dominated by eucalypt open forest, although it contains pockets of rainforest, shrubland and grassland vegetation as subdominants. The (related) Major Vegetation Subgroups represent more detail about the understorey and floristics of the Major Vegetation Groups and are available as separate raster datasets: - NVIS4_1_AUST_MVS_EXT_ALB - NVIS4_1_AUST_MVS_PRE_ALB A number of other non-vegetation and non-native vegetation land cover types are also represented as Major Vegetation Groups. These are provided for cartographic purposes, but should not be used for analyses. For further background and other NVIS products, please see the links on http://www.environment.gov.au/erin/nvis/index.html.

The current NVIS data products are available from http://www.environment.gov.au/land/native-vegetation/national-vegetation-information-system.

Purpose

For use in Bioregional Assessment land classification analyses

Dataset History

NVIS Version 4.1

The input vegetation data were provided from over 100 individual projects representing the majority of Australia's regional vegetation mapping over the last 50 years. State and Territory custodians translated the vegetation descriptions from these datasets into a common attribute framework, the National Vegetation Information System (ESCAVI, 2003). Scales of input mapping ranged from 1:25,000 to 1:5,000,000. These were combined into an Australia-wide set of vector data. Non-terrestrial areas were mostly removed by the State and Territory custodians before supplying the data to the Environmental Resources Information Network (ERIN), Department of Sustainability Environment Water Population and Communities (DSEWPaC).

Each NVIS vegetation description was written to the NVIS XML format file by the custodian, transferred to ERIN and loaded into the NVIS database at ERIN. A considerable number of quality checks were performed automatically by this system to ensure conformity to the NVIS attribute standards (ESCAVI, 2003) and consistency between levels of the NVIS Information Hierarchy within each description. Descriptions for non-vegetation and non-native vegetation mapping codes were transferred via CSV files.

The NVIS vector (polygon) data for Australia comprised a series of jig-saw pieces, eachup to approx 500,000 polygons - the maximum tractable size for routine geoprocesssing. The spatial data was processed to conform to the NVIS spatial format (ESCAVI, 2003; other papers). Spatial processing and attribute additions were done mostly in ESRI File Geodatabases. Topology and minor geometric corrections were also performed at this stage. These datasets were then loaded into ESRI Spatial Database Engine as per the ERIN standard. NVIS attributes were then populated using Oracle database tables provided by custodians, mostly using PL/SQL Developer or in ArcGIS using the field calculator (where simple).

Each spatial dataset was joined to and checked against a lookup table for the relevant State/Territory to ensure that all mapping codes in the dominant vegetation type of each polygon (NVISDSC1) had a valid lookup description, including an allocated MVG. Minor vegetation components of each map unit (NVISDSC2-6) were not checked, but could be considered mostly complete.

Each NVIS vegetation description was allocated to a Major Vegetation Group (MVG) by manual interpretation at ERIN. The Australian Natural Resources Atlas (http://www.anra.gov.au/topics/vegetation/pubs/native_vegetation/vegfsheet.html) provides detailed descriptions of most Major Vegetation Groups. Three new MVGs were created for version 4.1 to better represent open woodland formations and forests (in the NT) with no further data available. NVIS vegetation descriptions were reallocated into these classes, if appropriate:

• Unclassified Forest

• Other Open Woodlands

• Mallee Open Woodlands and Sparse Mallee Shublands

(Thus there are a total of 33 MVGs existing as at June 2012). Data values defined as cleared or non-native by data custodians were attributed specific MVG values such as 25 - Cleared or non native, 27 - naturally bare, 28 - seas & estuaries, and 99 - Unknown.

As part of the process to fill gaps in NVIS, the descriptive data from non-NVIS sources was also referenced in the NVIS database, but with blank vegetation descriptions. In general. the gap-fill data comprised (a) fine scale (1:250K or better) State/Territory vegetation maps for which NVIS descriptions were unavailable and (b) coarse-scale (1:1M) maps from Commonwealth and other sources. MVGs were then allocated to each description from the available desciptions in accompanying publications and other sources.

Parts of New South Wales, South Australia, QLD and the ACT have extensive areas of vector "NoData", thus appearing as an inland sea. The No Data areas were dealt with differently by state. In the ACT and SA, the vector data was 'gap-filled' and attributed using satellite imagery as a guide prior to rasterising. Most of these areas comprised a mixture of MVG 24 (inland water) and 25 (cleared), and in some case 99 (Unknown). The NSW & QLD 'No Data' areas were filled using a raster mask to fill the 'holes'. These areas were attributed with MVG 24, 26 (water & unclassified veg), MVG 25 (cleared); or MVG 99 Unknown/no data, where these areas were a mixture of unknown proportions.

Each spatial dataset with joined lookup table (including MVG_NUMBER linked to NVISDSC1) was exported to a File Geodatabase as a feature class. These were reprojected into Albers Equal Area projection (Central_Meridian: 132.000000, Standard_Parallel_1: -18.000000, Standard_Parallel_2: -36.000000, Linear Unit: Meter (1.000000), Datum GDA94, other parameters 0).

Each feature class was then rasterised to a 100m raster with extents to a multiple of 1000 m, to ensure alignment. In some instances, areas of 'NoData' had to be modelled in raster. For example, in NSW where non-native areas (cleared, water bodies etc) have not been mapped. The rasters were then merged into a 'state wide' raster. State rasters were then merged into this 'Australia wide' raster dataset.

November 2012 Corrections

Closer inspection of the original 4.1 MVG Extant raster dataset highlighted some issues with the raster creation process which meant that raster pixels in some areas did not align as intended. These were corrected, and the new properly aligned rasters released in November 2012.

Dataset Citation

Department of the Environment (2012) Australia - Present Major Vegetation Groups - NVIS Version 4.1 (Albers 100m analysis product). Bioregional Assessment Source Dataset. Viewed 10 July 2017, http://data.bioregionalassessments.gov.au/dataset/57c8ee5c-43e5-4e9c-9e41-fd5012536374.