Introduction and Rationale: Due to our increasing understanding of the role the surrounding landscape plays in ecological processes, a detailed characterization of land cover, including both agricultural and natural habitats, is ever more important for both researchers and conservation practitioners. Unfortunately, in the United States, different types of land cover data are split across thematic datasets that emphasize agricultural or natural vegetation, but not both. To address this data gap and reduce duplicative efforts in geospatial processing, we merged two major datasets, the LANDFIRE National Vegetation Classification (NVC) and USDA-NASS Cropland Data Layer (CDL), to produce an integrated land cover map. Our workflow leveraged strengths of the NVC and the CDL to produce detailed rasters comprising both agricultural and natural land-cover classes. We generated these maps for each year from 2012-2021 for the conterminous United States, quantified agreement between input layers and accuracy of our merged product, and published the complete workflow necessary to update these data. In our validation analyses, we found that approximately 5.5% of NVC agricultural pixels conflicted with the CDL, but we resolved a majority of these conflicts based on surrounding agricultural land, leaving only 0.6% of agricultural pixels unresolved in our merged product. Contents: Spatial data Attribute table for merged rasters Technical validation data Number and proportion of mismatched pixels Number and proportion of unresolved pixels Producer's and User's accuracy values and coverage of reference data Resources in this dataset:Resource Title: Attribute table for merged rasters. File Name: CombinedRasterAttributeTable_CDLNVC.csvResource Description: Raster attribute table for merged raster product. Class names and recommended color map were taken from USDA-NASS Cropland Data Layer and LANDFIRE National Vegetation Classification. Class values are also identical to source data, except classes from the CDL are now negative values to avoid overlapping NVC values. Resource Title: Number and proportion of mismatched pixels. File Name: pixel_mismatch_byyear_bycounty.csvResource Description: Number and proportion of pixels that were mismatched between the Cropland Data Layer and National Vegetation Classification, per year from 2012-2021, per county in the conterminous United States.Resource Title: Number and proportion of unresolved pixels. File Name: unresolved_conflict_byyear_bycounty.csvResource Description: Number and proportion of unresolved pixels in the final merged rasters, per year from 2012-2021, per county in the conterminous United States. Unresolved pixels are a result of mismatched pixels that we could not resolve based on surrounding agricultural land (no agriculture with 90m radius).Resource Title: Producer's and User's accuracy values and coverage of reference data. File Name: accuracy_datacoverage_byyear_bycounty.csvResource Description: Producer's and User's accuracy values and coverage of reference data, per year from 2012-2021, per county in the conterminous United States. We defined coverage of reference data as the proportional area of land cover classes that were included in the reference data published by USDA-NASS and LANDFIRE for the Cropland Data Layer and National Vegetation Classification, respectively. CDL and NVC classes with reference data also had published accuracy statistics. Resource Title: Data Dictionary. File Name: Data_Dictionary_RasterMerge.csv

The High Resolution Digital Elevation Model (HRDEM) product is derived from airborne LiDAR data (mainly in the south) and satellite images in the north. The complete coverage of the Canadian territory is gradually being established. It includes a Digital Terrain Model (DTM), a Digital Surface Model (DSM) and other derived data. For DTM datasets, derived data available are slope, aspect, shaded relief, color relief and color shaded relief maps and for DSM datasets, derived data available are shaded relief, color relief and color shaded relief maps. The productive forest line is used to separate the northern and the southern parts of the country. This line is approximate and may change based on requirements. In the southern part of the country (south of the productive forest line), DTM and DSM datasets are generated from airborne LiDAR data. They are offered at a 1 m or 2 m resolution and projected to the UTM NAD83 (CSRS) coordinate system and the corresponding zones. The datasets at a 1 m resolution cover an area of 10 km x 10 km while datasets at a 2 m resolution cover an area of 20 km by 20 km. In the northern part of the country (north of the productive forest line), due to the low density of vegetation and infrastructure, only DSM datasets are generally generated. Most of these datasets have optical digital images as their source data. They are generated at a 2 m resolution using the Polar Stereographic North coordinate system referenced to WGS84 horizontal datum or UTM NAD83 (CSRS) coordinate system. Each dataset covers an area of 50 km by 50 km. For some locations in the north, DSM and DTM datasets can also be generated from airborne LiDAR data. In this case, these products will be generated with the same specifications as those generated from airborne LiDAR in the southern part of the country. The HRDEM product is referenced to the Canadian Geodetic Vertical Datum of 2013 (CGVD2013), which is now the reference standard for heights across Canada. Source data for HRDEM datasets is acquired through multiple projects with different partners. Since data is being acquired by project, there is no integration or edgematching done between projects. The tiles are aligned within each project. The product High Resolution Digital Elevation Model (HRDEM) is part of the CanElevation Series created in support to the National Elevation Data Strategy implemented by NRCan. Collaboration is a key factor to the success of the National Elevation Data Strategy. Refer to the “Supporting Document” section to access the list of the different partners including links to their respective data.

USGS is assessing the feasibility of map projections and grid systems for lunar surface operations. We propose developing a new Lunar Transverse Mercator (LTM), the Lunar Polar Stereographic (LPS), and the Lunar Grid Reference Systems (LGRS). We have also designed additional grids designed to NASA requirements for astronaut navigation, referred to as LGRS in Artemis Condensed Coordinates (ACC), but this is not released here. LTM, LPS, and LGRS are similar in design and use to the Universal Transverse Mercator (UTM), Universal Polar Stereographic (LPS), and Military Grid Reference System (MGRS), but adhere to NASA requirements. LGRS ACC format is similar in design and structure to historic Army Mapping Service Apollo orthotopophoto charts for navigation. The Lunar Transverse Mercator (LTM) projection system is a globalized set of lunar map projections that divides the Moon into zones to provide a uniform coordinate system for accurate spatial representation. It uses a transverse Mercator projection, which maps the Moon into 45 transverse Mercator strips, each 8°, longitude, wide. These transverse Mercator strips are subdivided at the lunar equator for a total of 90 zones. Forty-five in the northern hemisphere and forty-five in the south. LTM specifies a topocentric, rectangular, coordinate system (easting and northing coordinates) for spatial referencing. This projection is commonly used in GIS and surveying for its ability to represent large areas with high positional accuracy while maintaining consistent scale. The Lunar Polar Stereographic (LPS) projection system contains projection specifications for the Moon’s polar regions. It uses a polar stereographic projection, which maps the polar regions onto an azimuthal plane. The LPS system contains 2 zones, each zone is located at the northern and southern poles and is referred to as the LPS northern or LPS southern zone. LPS, like is equatorial counterpart LTM, specifies a topocentric, rectangular, coordinate system (easting and northing coordinates) for spatial referencing. This projection is commonly used in GIS and surveying for its ability to represent large polar areas with high positional accuracy, while maintaining consistent scale across the map region. LGRS is a globalized grid system for lunar navigation supported by the LTM and LPS projections. LGRS provides an alphanumeric grid coordinate structure for both the LTM and LPS systems. This labeling structure is utilized in a similar manner to MGRS. LGRS defines a global area grid based on latitude and longitude and a 25×25 km grid based on LTM and LPS coordinate values. Two implementations of LGRS are used as polar areas require a LPS projection and equatorial areas a transverse Mercator. We describe the difference in the techniques and methods report associated with this data release. Request McClernan et. al. (in-press) for more information. ACC is a method of simplifying LGRS coordinates and is similar in use to the Army Mapping Service Apollo orthotopophoto charts for navigation. These data will be released at a later date. Two versions of the shape files are provided in this data release, PCRS and Display only. See LTM_LPS_LGRS_Shapefiles.zip file. PCRS are limited to a single zone and are projected in either LTM or LPS with topocentric coordinates formatted in Eastings and Northings. Display only shapefiles are formatted in lunar planetocentric latitude and longitude, a Mercator or Equirectangular projection is best for these grids. A description of each grid is provided below: Equatorial (Display Only) Grids: Lunar Transverse Mercator (LTM) Grids: LTM zone borders for each LTM zone Merged LTM zone borders Lunar Polar Stereographic (LPS) Grids: North LPS zone border South LPS zone border Lunar Grid Reference System (LGRS) Grids: Global Areas for North and South LPS zones Merged Global Areas (8°×8° and 8°×10° extended area) for all LTM zones Merged 25km grid for all LTM zones PCRS Shapefiles:` Lunar Transverse Mercator (LTM) Grids: LTM zone borders for each LTM zone Lunar Polar Stereographic (LPS) Grids: North LPS zone border South LPS zone border Lunar Grid Reference System (LGRS) Grids: Global Areas for North and South LPS zones 25km Gird for North and South LPS zones Global Areas (8°×8° and 8°×10° extended area) for each LTM zone 25km grid for each LTM zone The rasters in this data release detail the linear distortions associated with the LTM and LPS system projections. For these products, we utilize the same definitions of distortion as the U.S. State Plane Coordinate System. Scale Factor, k - The scale factor is a ratio that communicates the difference in distances when measured on a map and the distance reported on the reference surface. Symbolically this is the ratio between the maps grid distance and distance on the lunar reference sphere. This value can be precisely calculated and is provided in their defining publication. See Snyder (1987) for derivation of the LPS scale factor. This scale factor is unitless and typically increases from the central scale factor k_0, a projection-defining parameter. For each LPS projection. Request McClernan et. al., (in-press) for more information. Scale Error, (k-1) - Scale-Error, is simply the scale factor differenced from 1. Is a unitless positive or negative value from 0 that is used to express the scale factor’s impact on position values on a map. Distance on the reference surface are expended when (k-1) is positive and contracted when (k-1) is negative. Height Factor, h_F - The Height Factor is used to correct for the difference in distance caused between the lunar surface curvature expressed at different elevations. It is expressed as a ratio between the radius of the lunar reference sphere and elevations measured from the center of the reference sphere. For this work, we utilized a radial distance of 1,737,400 m as recommended by the IAU working group of Rotational Elements (Archinal et. al., 2008). For this calculation, height factor values were derived from a LOLA DEM 118 m v1, Digital Elevation Model (LOLA Science Team, 2021). Combined Factor, C_F – The combined factor is utilized to “Scale-To-Ground” and is used to adjust the distance expressed on the map surface and convert to the position on the actual ground surface. This value is the product of the map scale factor and the height factor, ensuring the positioning measurements can be correctly placed on a map and on the ground. The combined factor is similar to linear distortion in that it is evaluated at the ground, but, as discussed in the next section, differs numerically. Often C_F is scrutinized for map projection optimization. Linear distortion, δ - In keeping with the design definitions of SPCS2022 (Dennis 2023), we refer to scale error when discussing the lunar reference sphere and linear distortion, δ, when discussing the topographic surface. Linear distortion is calculated using C_F simply by subtracting 1. Distances are expended on the topographic surface when δ is positive and compressed when δ is negative. The relevant files associated with the expressed LTM distortion are as follows. The scale factor for the 90 LTM projections: LUNAR_LTM_GLOBAL_PLOT_HEMISPHERES_distortion_K_grid_scale_factor.tif Height Factor for the LTM portion of the Moon: LUNAR_LTM_GLOBAL_PLOT_HEMISPHERES_distortion_EF_elevation_factor.tif Combined Factor in LTM portion of the Moon LUNAR_LTM_GLOBAL_PLOT_HEMISPHERES_distortion_CF_combined_factor.tif The relevant files associated with the expressed LPS distortion are as follows. Lunar North Pole The scale factor for the northern LPS zone: LUNAR_LGRS_NP_PLOT_LPS_K_grid_scale_factor.tif Height Factor for the north pole of the Moon: LUNAR_LGRS_NP_PLOT_LPS_EF_elevation_factor.tif Combined Factor for northern LPS zone: LUNAR_LGRS_NP_PLOT_LPS_CF_combined_factor.tif Lunar South Pole Scale factor for the northern LPS zone: LUNAR_LGRS_SP_PLOT_LPS_K_grid_scale_factor.tif Height Factor for the south pole of the Moon: LUNAR_LGRS_SP_PLOT_LPS_EF_elevation_factor.tif Combined Factor for northern LPS zone: LUNAR_LGRS_SP_PLOT_LPS_CF_combined_factor.tif For GIS utilization of grid shapefiles projected in Lunar Latitude and Longitude, referred to as “Display Only”, please utilize a registered lunar geographic coordinate system (GCS) such as IAU_2015:30100 or ESRI:104903. LTM, LPS, and LGRS PCRS shapefiles utilize either a custom transverse Mercator or polar Stereographic projection. For PCRS grids the LTM and LPS projections are recommended for all LTM, LPS, and LGRS grid sizes. See McClernan et. al. (in-press) for such projections. Raster data was calculated using planetocentric latitude and longitude. A LTM and LPS projection or a registered lunar GCS may be utilized to display this data. Note: All data, shapefiles and rasters, require a specific projection and datum. The projection is recommended as LTM and LPS or, when needed, IAU_2015:30100 or ESRI:104903. The datum utilized must be the Jet Propulsion Laboratory (JPL) Development Ephemeris (DE) 421 in the Mean Earth (ME) Principal Axis Orientation as recommended by the International Astronomy Union (IAU) (Archinal et. al., 2008).

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. The polygons in this dataset are a digital representation of the distribution or extent of geological units within the area. Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. These have been extracted from the Rock Units Table held …Show full descriptionAbstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. The polygons in this dataset are a digital representation of the distribution or extent of geological units within the area. Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. These have been extracted from the Rock Units Table held in the Department of Natural Resources, Mines and Energy Merlin Database. Purpose To display the geology polygons which define the extent of rock units. Dataset History Supplemental_Information: Data captured at 1:40 000 scale. The data set is sourced from the Department's Geoscience and Resources Database (GRDB), a component of the Mineral and Energy Resources Location and Information Network (MERLIN) corporate database.(GRDB), a component of the Mineral and Energy Resources Location and Information Network (MERLIN) corporate database. NOTE: GEOLDATA was in most cases compiled based on Datum AGD66. The map tile coverages so compiled have now been projected to geographics based on Datum GDA94. Consequently the boundaries for these map tiles will not conform to the Latitude and Longitude graticule based on Datum GDA94. Entity_and_Attribute_Information: Detailed_Description: Entity_Type: Entity_Type_Label: 9341_r Entity_Type_Definition: Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. Entity_Type_Definition_Source: The Rock Units Table held in the Department of Natural Resources, Mines and Energy Merlin Database. Attribute: Attribute_Label: FID Attribute_Definition: Internal feature number. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Sequential unique whole numbers that are automatically generated. Beginning_Date_of_Attribute_Values: March 2004 Attribute: Attribute_Label: Shape Attribute_Definition: Feature geometry. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Coordinates defining the features. Attribute: Attribute_Label: KEY Attribute_Definition: Unique polygon identifier and relate item for poygon attributes Attribute: Attribute_Label: ROCK_U_NAM Attribute_Definition: The Map Unit Name of the polygon. In the case of named units it comprises of the standard binomial name. Unnamed subdivisions of named units include the binomial name with a letter symbol as a suffix. Unnamed units are represented by a letter symbol, usually in combination with a map sheet number. Attribute: Attribute_Label: AGE Attribute_Definition: Geological age of unit Attribute: Attribute_Label: LITH_SUMMA Attribute_Definition: Provides a brief description of the map units as they have been described in the course of the project work, or as has appeared on relevant hard copy map legends. Attribute: Attribute_Label: ROCK_U_TYP Attribute_Definition: Provides a means of separating map units, eg for constructing a map reference. This item will contain one of the following: STRAT- Stratigraphic unit, including sedimentary, volcanic and metamorphic rock units. INTRU- Intrusive rock units; COMPST- Compound unit where the polygon includes two or more rock units, either stratigraphic, intrusive or both; COMPST- Compound unit, as above where the dominant or topmost unit is of the STRAT type; COMPIN- Compound unit, as above, where the dominant unit is of the INTRU type; WATER- Water bodies- Large dams, lakes, waterholes. Attribute: Attribute_Label: SEQUENCE_N Attribute_Definition: A numeric field to allow sorting of the rock units in approximate stratigraphic order as they would appear on a map legend. Attribute: Attribute_Label: DOMINANT_R Attribute_Definition: A simplified lithological description to allow generation of thematic maps based on broad rock types. Attribute: Attribute_Label: MAP_SYMBOL Attribute_Definition: Provides an abbreviated label for polygons. Mostly based on the letter symbols as they appear on published maps or the original hard copy compilation sheets. These are not unique across the State, but should be unique within a single map tile, and usually adjacent tiles. Attribute: Attribute_Label: NAME_100K Attribute_Definition: Name of 1:100 000 map sheet coincident with the data extent. Overview_Description: Entity_and_Attribute_Overview: Polygon Attribute information includes Polygon Key, Rock Unit Name, Age, Lithology, Rock Unit Type, Map Symbol and 1:100 000 sheet name. Dataset Citation "Queensland Department of Natural Resources, Mines and Energy" (2014) Qld 100k mapsheets - Warwick. Bioregional Assessment Source Dataset. Viewed 28 September 2017, http://data.bioregionalassessments.gov.au/dataset/3e2fa307-1f06-4873-96d3-5c3e5638894a.

Australia's Land Borders is a product within the Foundation Spatial Data Framework (FSDF) suite of datasets. It is endorsed by the ANZLIC - the Spatial Information Council and the Intergovernmental Committee on Surveying and Mapping (ICSM) as a nationally consistent and topologically correct representation of the land borders published by the Australian states and territories.

The purpose of this product is to provide: (i) a building block which enables development of other national datasets; (ii) integration with other geospatial frameworks in support of data analysis; and (iii) visualisation of these borders as cartographic depiction on a map. Although this dataset depicts land borders, it is not nor does it suggests to be a legal definition of these borders. Therefore it cannot and must not be used for those use-cases pertaining to legal context.

This product is constructed by Geoscience Australia (GA), on behalf of the ICSM, from authoritative open data published by the land mapping agencies in their respective Australian state and territory jurisdictions. Construction of a nationally consistent dataset required harmonisation and mediation of data issues at abutting land borders. In order to make informed and consistent determinations, other datasets were used as visual aid in determining which elements of published jurisdictional data to promote into the national product. These datasets include, but are not restricted to: (i) PSMA Australia's commercial products such as the cadastral (property) boundaries (CadLite) and Geocoded National Address File (GNAF); (ii) Esri's World Imagery and Imagery with Labels base maps; and (iii) Geoscience Australia's GEODATA TOPO 250K Series 3. Where practical, Land Borders do not cross cadastral boundaries and are logically consistent with addressing data in GNAF.

It is important to reaffirm that although third-party commercial datasets are used for validation, which is within remit of the licence agreement between PSMA and GA, no commercially licenced data has been promoted into the product. Australian Land Borders are constructed exclusively from published open data originating from state, territory and federal agencies.

This foundation dataset consists of edges (polylines) representing mediated segments of state and/or territory borders, connected at the nodes and terminated at the coastline defined as the Mean High Water Mark (MHWM) tidal boundary. These polylines are attributed to convey information about provenance of the source. It is envisaged that land borders will be topologically interoperable with the future national coastline dataset/s, currently being built through the ICSM coastline capture collaboration program. Topological interoperability will enable closure of land mass polygon, permitting spatial analysis operations such as vector overly, intersect, or raster map algebra. In addition to polylines, the product incorporates a number of well-known survey-monumented corners which have historical and cultural significance associated with the place name.

This foundation dataset is constructed from the best-available data, as published by relevant custodian in state and territory jurisdiction. It should be noted that some custodians - in particular the Northern Territory and New South Wales - have opted out or to rely on data from abutting jurisdiction as an agreed portrayal of their border. Accuracy and precision of land borders as depicted by spatial objects (features) may vary according to custodian specifications, although there is topological coherence across all the objects within this integrated product. The guaranteed minimum nominal scale for all use-cases, applying to complete spatial coverage of this product, is 1:25 000. In some areas the accuracy is much better and maybe approaching cadastre survey specification, however, this is an artefact of data assembly from disparate sources, rather than the product design. As the principle, no data was generalised or spatially degraded in the process of constructing this product.

Some use-cases for this product are: general digital and web map-making applications; a reference dataset to use for cartographic generalisation for a smaller-scale map applications; constraining geometric objects for revision and updates to the Mesh Blocks, the building blocks for the larger regions of the Australian Statistical Geography Standard (ASGS) framework; rapid resolution of cross-border data issues to enable construction and visual display of a common operating picture, etc.

This foundation dataset will be maintained at irregular intervals, for example if a state or territory jurisdiction decides to publish or republish their land borders. If there is a new version of this dataset, past version will be archived and information about the changes will be made available in the change log.

This Web Map is a subset of Above and below ground biomass carbon (tonnes/ha)This dataset represents above- and below-ground terrestrial carbon storage (tonnes (t) of C per hectare (ha)) for circa 2010.This layer supports analysis but, if needed, a direct download of the data can be accessed here.The dataset was constructed by combining the most reliable publicly available datasets and overlying them with the ESA CCI landcover map for the year 2010 [ESA, 2017], assigning to each grid cell the corresponding above-ground biomass value from the biomass map that was most appropriate for the grid cell’s landcover type.Input carbon datasets were identified through a literature review of existing datasets on biomass carbon in terrestrial ecosystems published in peer-reviewed literature. To determine which datasets to combine to produce the global carbon density map, identified datasets were evaluated based on resolution, accuracy, biomass definition and reference date (see table 1 for further information on datasets selected).DatasetScopeYearResolutionDefinitionSantoro et al. 2018Global2010100 mAbove-ground woody biomass for trees that are >10 cm diameter-at-breast-height, masked to Landsat-derived canopy cover for 2010; biomass is expressed as oven-dry weight of the woody parts (stem, bark, branches and twigs) of all living trees excluding stump and roots.Xia et al. 2014Global1982-20068 kmAbove-ground grassland biomass.Bouvet et al. 2018Africa201025 mAbove-ground woodland and savannah biomass; low woody biomass areas, which therefore exclude dense forests and deserts.Spawn et al. 2017Global2010300 mSynthetic, global above- and below-ground biomass maps that combine recently released satellite-based data of standing forest biomass with novel estimates for non-forest biomass stocks.After aggregating each selected dataset to a nominal scale of 300 m resolution, forest categories in the CCI ESA 2010 landcover dataset were used to extract above-ground biomass from Santoro et al. 2018 for forest areas. Woodland and savanna biomass were then incorporated for Africa from Bouvet et al. 2018., and from Santoro et al. 2018 for areas outside of Africa and outside of forest. Biomass from croplands, sparse vegetation and grassland landcover classes from CCI ESA, in addition to shrubland areas outside Africa missing from Santoro et al. 2018, were extracted from were extracted from Xia et al. 2014. and Spawn et al. 2017 averaged by ecological zone for each landcover type.Below-ground biomass were added using root-to-shoot ratios from the 2006 IPCC guidelines for National Greenhouse Gas Inventories (IPCC, 2006). No below-ground values were assigned to croplands as ratios were unavailable. Above- and below-ground biomass were then summed together and multiplied by 0.5 to convert to carbon, generating a single above-and-below-ground biomass carbon layer.This dataset has not been validated.

Gap Analysis Project (GAP) habitat maps are predictions of the spatial distribution of suitable environmental and land cover conditions within the United States for individual species. Mapped areas represent places where the environment is suitable for the species to occur (i.e. suitable to support one or more life history requirements for breeding, resting, or foraging), while areas not included in the map are those predicted to be unsuitable for the species. While the actual distributions of many species are likely to be habitat limited, suitable habitat will not always be occupied because of population dynamics and species interactions. Furthermore, these maps correspond to midscale characterizations of landscapes, but individual animals may deem areas to be unsuitable because of presence or absence of fine-scale features and characteristics that are not represented in our models (e.g. snags, vernal pools, shrubby undergrowth). These maps are intended to be used at a 1:100,000 or smaller map scale. These habitat maps are created by applying a deductive habitat model to remotely-sensed data layers within a species’ range. The deductive habitat models are built by compiling information on species’ habitat associations and entering it into a relational database. Information is compiled from the best available characterizations of species’ habitat, which included species accounts in books and databases, primary peer-reviewed literature. The literature references for each species are included in the "Species Habitat Model Report" and "Machine Readable Habitat Database Parameters" files attached to each habitat map item in the repository. For all species, the compiled habitat information is used by a biologist to determine which of the ecological systems and land use classes represented in the National Gap Analysis Project’s (GAP) Land Cover Map Ver. 1.0 that species is associated with. The name of the biologist who conducted the literature review and assembled the modeling parameters is shown as the "editor" type contact for each habitat map item in the repository. For many species, information on other mapped factors that define the environment that is suitable is also entered into the database. These factors included elevation (i.e. minimum, maximum), proximity to water features, proximity to wetlands, level of human development, forest ecotone width, and forest edge; and each of these factors corresponded to a data layer that is available during the map production. The individual datasets used in the modeling process with these parameters are also made available in the ScienceBase Repository (see the end of this Summary section for details). The "Machine Readable Habitat Database Parameters" JSON file attached to each species habitat map item has an "input_layers" object that contains the specific parameter names and references (via Digital Object Identifier) to the input data used with that parameter. The specific parameters for each species were output from the database used in the modeling and mapping process to the "Species Habitat Model Report" and "Machine Readable Habitat Database Parameters" files attached to each habitat map item in the repository. The maps are generated using a python script that queries the model parameters in the database; reclassifies the GAP Land Cover Ver 1.0 and ancillary data layers within the species’ range; and combines the reclassified layers to produce the final 30m resolution habitat map. Map output is, therefore, not only a reflection of the ecological systems that are selected in the habitat model, but also any other constraints in the model that are represented by the ancillary data layers. Modeling regions were used to stratify the conterminous U.S. into six regions (Northwest, Southwest, Great Plains, Upper Midwest, Southeast, and Northeast). These regions allowed for efficient processing of the species distribution models on smaller, ecologically homogenous extents. The 2008 start date for the models represents the shift in focus from state and regional project efforts to a national one. At that point all of the datasets needed to be standardized across the national extent and the species list derived based on the current understanding of the taxonomy. The end date for the individual models represents when the species model was considered complete, and therefore reflects the current knowledge related to that species concept and the habitat requirements for the species. Versioning, Naming Conventions and Codes: A composite version code is employed to allow the user to track the spatial extent, the date of the ground conditions, and the iteration of the data set for that extent/date. For example, CONUS_2001v1 represents the spatial extent of the conterminous US (CONUS), the ground condition year of 2001, and the first iteration (v1) for that extent/date. In many cases, a GAP species code is used in conjunction with the version code to identify specific data sets or files (i.e. Cooper’s Hawk Habitat Map named bCOHAx_CONUS_2001v1_HabMap). This collection represents the first complete compilation of terrestrial vertebrate species models for the conterminous U.S. based on 2001 ground conditions. The taxonomic concept for the species model being presented is identified through the Integrated Taxonomic Information System – Taxonomic Serial Number. To provide a link to the NatureServe species information the NatureServe Element Code is provided for each species. The identifiers included for each species habitat map item in the repository include references to a vocabulary system in ScienceBase where definitions can be found for each type of identifier. Source Datasets Uses in Species Habitat Modeling: Gap Analysis Project Species Range Maps - Species ranges were used as model delimiters in predicted distribution models. https://www.sciencebase.gov/catalog/item/5951527de4b062508e3b1e79 Hydrologic Units - Modified 12-digit hydrologic units were used as the spatial framework for species ranges. https://www.sciencebase.gov/catalog/item/56d496eee4b015c306f17a42 Modeling regions - Used to stratify the conterminous U.S. into six ecologically homogeneous regions to facilitate efficient processing. https://www.sciencebase.gov/catalog/item/58b9b8cee4b03b285c07ddef Land Cover - Species were linked to individual map units to document habitat affinity in two ways. Primary map units are those land cover types critical for nesting, rearing young, and/or optimal foraging. Secondary or auxiliary map units are those land cover types generally not critical for breeding, but are typically used in conjunction with primary map units for foraging, roosting, and/or sub-optimal nesting locations. These map units are selected only when located within a specified distance from primary map units. https://www.sciencebase.gov/catalog/item/5540e2d7e4b0a658d79395db Human Impact Avoidance - Buffers around urban areas and roads were used to identify areas that would be suitable for urban exploitative species and unsuitable for urban avoiding species. https://www.sciencebase.gov/catalog/item/5540e099e4b0a658d79395d6 Forest & Edge Habitats - The land cover map was used to derive datasets of forest interior and ecotones between forest and open habitats. Forest edge https://www.sciencebase.gov/catalog/item/5540e3fce4b0a658d79395fe Forest/Open Woodland/Shrubland https://www.sciencebase.gov/catalog/item/5540e48fe4b0a658d7939600 Elevation Derivatives - Slope and aspect were used to constrain some of the southwestern models where those variables are good indicators of microclimates (moist north facing slopes) and local topography (cliffs, flats). For species with a documented relationship to altitude the elevation data was used to constrain the mapped distribution. Aspect https://www.sciencebase.gov/catalog/item/5540ec40e4b0a658d7939628 Slope https://www.sciencebase.gov/catalog/item/5540ebe2e4b0a658d7939626 Elevation https://www.sciencebase.gov/catalog/item/5540e111e4b0a658d79395d9 Hydrology - https://www.sciencebase.gov/catalog/item/5540eb44e4b0a658d7939624: A number of water related data layers were used to refine the species distribution including: water type (i.e. flowing, open/standing), distance to and from water, and stream flow and underlying gradient. The source for this data was the USGS National Hydrography Dataset (NHD)(USGS 2007). Hydrographic features were divided into three types: flowing water, open/standing water, and wet vegetation. Canopy Cover - Some species are limited to open woodlands or dense forest, the National Land Cover’s Canopy Cover dataset was used to constrain the species models based on canopy density. https://www.sciencebase.gov/catalog/item/5540eca9e4b0a658d793962b

The following webmap contains individual web layers showing critical habitat for 5 DPSs of Atlantic Sturgeon. Information on each layer is detailed below:SturgeonAtlantic_AtlanticSubspecies_SouthAtlanticDPS_20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the South Atlantic DPS of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Southeast Regional Office (SERO). This dataset includes boundaries for the following Regulated Areas: Critical Habitat South Atlantic Distinct Population Segment of Atlantic Sturgeon: Edisto River, Combahee River, Salkehatchie River, Savannah River, Ogeechee River, Altamaha River, Satilla River and St. Marys River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_NewYorkBightDPS_20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the New York Bight DPS of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). This dataset includes boundaries for the following Regulated Areas: Critical Habitat for New York Bight Distinct Population Segment of Atlantic Sturgeon: Connecticut River, Housatonic River, Hudson River, and Delaware River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_GulfofMaineDPS_20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the Gulf of Maine distinct population segment (DPS) of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). This dataset includes boundaries for the following Regulated Areas: - Critical Habitat for Gulf of Maine Distinct Population Segment of Atlantic Sturgeon: Penobscot River, Kennebec River, Androscoggin River, Piscataqua River, and Merrimack River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_ChesapeakeBayDPS_20170817:This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the Chesapeake Bay distinct population segment (DPS) of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). This dataset includes boundaries for the following Regulated Areas: - Critical Habitat for Chesapeake Bay Distinct Population Segment of Atlantic Sturgeon: Nanticoke River, Potomac River, Rappahannock River, York River, and James River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_CarolinaDPS20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the Carolina DPS of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). Dataset includes boundaries for the following Regulated Areas: Critical Habitat Carolina Distinct Population Segment of Atlantic Sturgeon: Roanoke River, Tar-Pamlico River, Neuse River, Cape Fear River, Pee Dee River, Black River, Santee River and Cooper River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.Link to NOAA Fisheries final rule pageLink to eCFRLink to InPortLink to NOAA Fisheries Critical Habitat Webpage

List of rural municipalities within the meaning of “Eligibility to the GIP”, a global allocation of equipment paid to the department of Saône and Loire. Prefectural Order No. 2017103-001 of 13 April 2017. Article D3334-8-1 of the General Code of Local and Regional Authorities: The following municipalities in metropolitan France are considered to be rural municipalities for the purposes of Articles L. 3334-10 and R. 3334-8: — municipalities whose population does not exceed 2 000 inhabitants; — municipalities whose population exceeds 2 000 inhabitants and does not exceed 5 000 inhabitants, if they do not belong to an urban unit or if they belong to an urban unit whose population does not exceed 5000 inhabitants. The urban reference unit is that defined by the National Institute of Statistics and Economic Studies. The population taken into account is the total population authenticated at the end of the population census.

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network _location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address _location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear _location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection _location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of _location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event _location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

The National Land Cover Database (NLCD), a product suite produced through the Multi-resolution Land Characteristics (MRLC) consortium, is an operational land cover monitoring program. The release of NLCD2019 extends the database to 18 years. We collected land cover reference data for the 2016 and 2019 components of the NLCD2019 database at Level II and Level I of the classification hierarchy. For both dates, Level II land cover overall accuracies (OA) were 77.5% ± 1% (± value is the standard error) when agreement was defined as a match between the map label and primary reference label only and increased to 87.1% ± 0.7% when agreement was defined as a match between the map label and either the primary or alternate reference label. At Level I of the classification hierarchy, land cover OA was 83.1% ± 0.9% for both 2016 and 2019 when agreement was defined as a match between the map label and primary reference label only and increased to 90.3% ± 0.7% when agreement also included the alternate reference label. The Level II and Level I OA for the 2016 land cover in the NLCD2019 database were 5% higher compared to the 2016 land cover component of the NLCD2016 database when agreement was defined as a match between the map label and primary reference label only. No improvement was realized by the NLCD2019 database when agreement also included the alternate reference label. User’s accuracies (UA) for forest loss and grass gain were 70% when agreement included either the primary or alternate label, and UA was generally 50% for all other change themes. Producer’s accuracies (PA) were 70% for grass loss and gain and water gain and generally 50% for the other change themes.

This dataset contains 63 shapefiles that represent the areas of relevance for each research project under the National Environmental Science Program Marine and Coastal Hub, northern and southern node projects for Rounds 1, 2 & 3.

Methods: Each project map is developed using the following steps: 1. The project map was drawn based on the information provided in the research project proposals. 2. The map was refined based on feedback during the first data discussions with the project leader. 3. Where projects are finished most maps were updated based on the extents of datasets generated by the project and followup checks with the project leader.

The area mapped includes on-ground activities of the project, but also where the outputs of the project are likely to be relevant. The maps were refined by project leads, by showing them the initial map developed from the proposal, then asking them "How would you change this map to better represent the area where your project is relevant?". In general, this would result in changes such as removing areas where they were no longer intending research to be, or trimming of the extents to better represent the habitats that are relevant.

The project extent maps are intentionally low resolution (low number of polygon vertices), limiting the number of vertices 100s of points. This is to allow their easy integration into project metadata records and for presenting via interactive web maps and spatial searching. The goal of the maps was to define the project extent in a manner that was significantly more accurate than a bounding box, reducing the number of false positives generated from a spatial search. The geometry was intended to be simple enough that projects leaders could describe the locations verbally and the rough nature of the mapping made it clear that the regions of relevance are approximate.

In some cases, boundaries were drawn manually using a low number of vertices, in the process adjusting them to be more relevant to the project. In others, high resolution GIS datasets (such as the EEZ, or the Australian coastline) were used, but simplified at a resolution of 5-10km to ensure an appopriate vertices count for the final polygon extent. Reference datasets were frequently used to make adjustments to the maps, for example maps of wetlands and rivers were used to better represent the inner boundary of projects that were relevant for wetlands.

In general, the areas represented in the maps tend to show an area larger then the actual project activities, for example a project focusing on coastal restoration might include marine areas up to 50 km offshore and 50 km inshore. This buffering allows the coastline to be represented with a low number of verticies without leading to false negatives, where a project doesn't come up in a search because the area being searched is just outside the core area of a project.

Limitations of the data: The areas represented in this data are intentionally low resolution. The polygon features from the various projects overlap significantly and thus many boundaries are hidden with default styling. This dataset is not a complete representation of the work being done by the NESP MaC projects as it was collected only 3 years into a 7 year program.

Format of the data: The maps were drawn in QGIS using relevant reference layers and saved as shapefiles. These are then converted to GeoJSON or WKT (Well-known Text) and incorporated into the ISO19115-3 project metadata records in GeoNetwork. Updates to the map are made to the original shapefiles, and the metadata record subsequently updated.

All projects are represented as a single multi-polygon. The multiple polygons was developed by merging of separate areas into a single multi-polygon. This was done to improve compatibility with web platforms, allowing easy conversion to GeoJSON and WKT.

This dataset will be updated periodically as new NESP MaC projects are developed and as project progress and the map layers are improved. These updates will typically be annual.

Data dictionary: NAME - Title of the layer PROJ - Project code of the project relating to the layer NODE - Whether the project is part of the Northern or Southern Nodes TITLE - Title of the project P_LEADER - Name of the Project leader and institution managing the project PROJ_LINK - Link to the project metadata MAP_DESC - Brief text description of the map area MAP_TYPE - Describes whether the map extent is a 'general' area of relevance for the project work, or 'specific' where there is on ground survey or sampling activities MOD_DATE - Last modification date to the individual map layer (prior to merging)

Updates & Processing: These maps were created by eAtlas and IMAS Data Wranglers as part of the NESP MaC Data Management activities. As new project information is made available, the maps may be updated and republished. The update log will appear below with notes to indicate when individual project maps are updated: 20220626 - Dataset published (All shapefiles have MOD_DATE 20230626)

Location of the data: This dataset is filed in the eAtlas enduring data repository at: data\custodian esp-mac-3\AU_AIMS-UTAS_NESP-MaC_Project-extents-maps

Reference point samples used in the production of the global maps of annual grassland class and extent for 2000—2022 within the scope of the Global Pasture Wath initiative.

The reference samples (estabilished by Feature Space Coverage Sampling-FSCS) comprises 2.3M points visually classified (using Very High Resolution imagery) in:

1. Cultivated grassland,
2. Natural/semi-natural grassland
3. Other land cover

The file gpw_grassland_fscs.vi.vhr_tile.samples_20000101_20241231_go_epsg.4326_v2.gpkg aggregates the samples by visual interpretation units ( 1x1 km) and includes the follow collumns:

• cluster_id: Cluster id defined by k-means (FSCS),
• cluster_distance: Distance from the sample tile to center of the cluster (FSCS),
• cluster_size: Size of cluster (strata) defined by the FSCS,
• priority: Priority used by the visual interpretation,
• tile_id: Sample tile id,
• imagery: VHR reference images used by the visual interpretation,
• min_year: Minimum of year covered by the reference samples,
• max_year: Maximum of year covered by the reference samples,
• n_years: Number of years covered by the reference samples,
• n_samples_c1: Number of reference samples for "Cultivated grass" (1),
• n_samples_c2: Number of reference samples for "Natural / Semi-natural grass" (2),
• n_samples_c3: Number of reference samples for "Open Shrubland" (2),
• n_samples_c4: Number of reference samples for "Not grass" (3),
• n_samples_all: Total number of reference samples,

The file gpw_grassland_fscs.vi.vhr_point.samples_20000101_20241231_go_epsg.4326_v2.gpkg provides individual points (with 60-m spatial support) and include the follow collumns:

• sample_id: Sample id deribed by MD5 Hash of columns x, y, imagery and year,
• x: Longitude in WGS84 (EPSG:4326),
• y: Latitude in WGS84 (EPSG:4326),
• vi_tile_id: 1-km tile id,
• tile_id: GLAD tile id (1x1 degree)
• imagery: VHR Reference image used by the visual interpretation (Google; Bing; Interpolated),
• ref_date: Reference date of GPW samples (based on VHR image) and of other existing datasets,
• year: Reference year of GPW samples (based on VHR image) and of other existing datasets,
• class: Class id (1: Cultivated grassland; 2: Natural/semi-natural grassland; 3: Open shrubland; 4: Other land cover) ,
• class_label: Class labels (Cultivated grassland; Natural/semi-natural grassland; Open shrubland; Other land cover) ,
• dataset_name: Existing dataset names (CGLS-LC, EuroCrops, GeoWiki, GeoWiki-feedback, LCMap-Conus, LUCAS, MapBiomas, WorldCereal, GPW)
  dataset_class: Original land cover class provided by the maintainer of existing dataset
• esa_worldcover_2020: Land cover class labels extracted from ESA WorldCover 2020,
• glad_glcluc_yyyy: Land cover class labels extracted from UMD GLAD GLCLUC for the reference date,
• glc_fcs30d_yyyy: Land cover class labels extracted from GLC_FCS30D for the reference date,
• gpw_fscs_cluster: K-Means output ranging from 0—9999 according to Feature Space Coverage Sampling (FSCS),
• ml_cv_group: spatial block CV group (based on vi_tile_id),
• ml_type: specify if the sample was used for (1) training or (2) calibration.

The file gpw_grassland_fscs.vi.vhr_grid.samples_20000101_20241231_go_epsg.4326_v2.gpkg provides the grid samples (with 10-m spatial support) and include the follow collumns:

• tile_id: 1-km tile id,
• bing_class: Class labels (Cultivated grassland; Natural/semi-natural grassland; Other land cover) defined using as reference Bing Maps Images,
• bing_image_start_date: Start date of the Bing Maps Images used in the visual interpretation,
• bing_image_end_date: End date of the Bing Maps Images used in the visual interpretation,
• google_class: Class labels (Cultivated grassland; Natural/semi-natural grassland; Other land cover) defined using as reference Google Maps Images,
• google_image_start_date: Start date of the Google Maps Images used in the visual interpretation,
• google_image_end_date: End date of the Google Maps Images used in the visual interpretation,
• missing_image_date: No images available,
• same_image_bing_google: Images from the same date available in Google and Bing Maps.

The dataset was produced through the QGIS plugin Fast Grid Inspection.

Related resources

• Maps of dominant grassland:
  2000-2002 2003-2005 2006-2008 2009-2011 2012-2014 2015-2017 2018-2020 2021-2022
• Probability maps of cultivated grassland:
  2000-2022 (All URLs)
• Probability maps of natural/semi-natural grassland:
  2000-2022 (All URLs)
• Grassland reference samples based on VHR imagery (2000–2022):
  GeoPackage files
• Global machine learning models (Random Forest):
  Parquet and joblib python files
• Reference sampling design derived by FSCV:
  GeoPackage and raster files
• Harmonized reference samples based on existing LULC dataset:
  GeoPackage and raster files
• Source code for reproducibility:
  GitHub release
  
• Mapping feedback tool:
  GeoWiki
• Data catalogues:
  OpenLandMap STAC Google Earth Engine

Support

For questions of bugs/inconsistencies related to the dataset raise a GitHub issue in https://github.com/wri/global-pasture-watch

L_ZI_SARSONNE_2001_LIM_L_019

The study determined the flooding areas of the Sarsonne at Ussel by hydrogeomorphological approach on the upstream and downstream areas of the urbanised part (maximum right-of-way only). The hydrogeomorphological approach is a naturalistic approach based on reading the morphology of the alluvial plain. It is supplemented here by extrapolation of the water line from a flood known to establish the reference flood water line. This reading of the morphology of the alluvial plain has been clarified on the urbanised area, thanks in particular to topographical works, allowing the definition of heights and flow rates in the crossing of the urbanised area. The flooding zone was determined by calculating the water line of a centennial flood (reference) determined by extrapolation of the 1994 flood water line, extrapolation based on topographical knowledge, the difference in flows between the 1994 event and a centennial event. Topographic knowledge has been used to determine water heights (between 0 and 1 m and > 1 m); flow velocities were defined qualitatively from valley morphology primarily. The crossing of these two parameters allowed to map the hazard (strength = H > 2 m or 1 m < H < 2 m and V > 0.5 m/s or 0 m < H < 1 m and V > 1 m/s; mean = 1 m < H < 2 m and V < 0.5 m/s or 0 m < H < 1 m and 0.5 m/s < V < 1 m/s; low hazard 0 m < H < 1 m and V < 0.5 m/s).

This data set is an index identifying Ontario Base Map (OBM) map tiles and digital vector data available for each tile. Eastern and Southern Ontario is covered at a scale of 1:10,000 and Northern Ontario is covered at a scale of 1:20,000.

Ontario Base Maps (OBM) are a series of maps created and updated by the Ontario Ministry of Natural Resources between 1977 and 2000. The MNR extracted the 33 layers from their NAD83 NRVIS dataset to create the NAD83 digital OBM sheets and vector data packages. The data provided may not be spatially defined upon download and may need to be defined using GIS (e.g. NAD 83 UTM Zone 18).

Medical Emergency Response StructuresThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Geological Survey, displays hospitals, medical centers, ambulance services, fire stations and EMS stations in the U.S. Per the USGS, "Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations."Greendale Fire DepartmentData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Medical & Emergency Response) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 135 (USGS National Structures Dataset - USGS National Map Downloadable Data Collection)OGC API Features Link: (Medical Emergency Response Structures - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: The National MapFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Theme CommunityThis data set is part of the NGDA Real Property Theme Community. Per the Federal Geospatial Data Committee (FGDC), Real Property is defined as "the spatial representation (location) of real property entities, typically consisting of one or more of the following: unimproved land, a building, a structure, site improvements and the underlying land. Complex real property entities (that is "facilities") are used for a broad spectrum of functions or missions. This theme focuses on spatial representation of real property assets only and does not seek to describe special purpose functions of real property such as those found in the Cultural Resources, Transportation, or Utilities themes."For other NGDA Content: Esri Federal Datasets

Generally referred to as “urban task”, the urban envelope is defined as the area delimiting a set of parcels built on a given date. This urban envelope is a spatial reference for locating a boundary of construction according to different design criteria. These criteria can be adapted according to the definition assigned to this urban envelope (artificialisation, habitat area, area of activity, etc.). The urban envelope serves as a reference point to contribute to the assessment of space consumption in urban planning documents. Some specific features of the spatial distribution of built-up areas are observed in more detail. These differences can be attributed to the land structure of agricultural areas (cultural typology, parcel geometry, cultural methods of setting up farms, etc.), to land-based urbanisation patterns depending on the territory or, on the contrary, to more intensified forms of this residential development (e.g. regulatory aspect of urban planning documents). This is a data to characterise the urban envelope of dwellings (house, apartment). This envelope was generated from the parcels identified in the land files as bearing at least one dwelling space and having a habitat rather than activity purpose This data also specifies the number of parcels that make up each urban envelope. This allows, by simple processing, to select only the corresponding urban envelopes, those consisting of at least four units.

The following webmap contains individual web layers showing critical habitat for 5 DPSs of Atlantic Sturgeon. Information on each layer is detailed below:SturgeonAtlantic_AtlanticSubspecies_SouthAtlanticDPS_20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the South Atlantic DPS of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Southeast Regional Office (SERO). This dataset includes boundaries for the following Regulated Areas: Critical Habitat South Atlantic Distinct Population Segment of Atlantic Sturgeon: Edisto River, Combahee River, Salkehatchie River, Savannah River, Ogeechee River, Altamaha River, Satilla River and St. Marys River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_NewYorkBightDPS_20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the New York Bight DPS of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). This dataset includes boundaries for the following Regulated Areas: Critical Habitat for New York Bight Distinct Population Segment of Atlantic Sturgeon: Connecticut River, Housatonic River, Hudson River, and Delaware River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_GulfofMaineDPS_20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the Gulf of Maine distinct population segment (DPS) of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). This dataset includes boundaries for the following Regulated Areas: - Critical Habitat for Gulf of Maine Distinct Population Segment of Atlantic Sturgeon: Penobscot River, Kennebec River, Androscoggin River, Piscataqua River, and Merrimack River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_ChesapeakeBayDPS_20170817:This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the Chesapeake Bay distinct population segment (DPS) of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). This dataset includes boundaries for the following Regulated Areas: - Critical Habitat for Chesapeake Bay Distinct Population Segment of Atlantic Sturgeon: Nanticoke River, Potomac River, Rappahannock River, York River, and James River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.SturgeonAtlantic_AtlanticSubspecies_CarolinaDPS20170817: This dataset depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the Carolina DPS of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Service’s Greater Atlantic Regional Fisheries Office (GARFO). Dataset includes boundaries for the following Regulated Areas: Critical Habitat Carolina Distinct Population Segment of Atlantic Sturgeon: Roanoke River, Tar-Pamlico River, Neuse River, Cape Fear River, Pee Dee River, Black River, Santee River and Cooper River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.Link to NOAA Fisheries final rule pageLink to eCFRLink to InPortLink to NOAA Fisheries Critical Habitat WebpageShapefile DownloadPDF Map

This dataset represents above- and below-ground terrestrial carbon storage (tonnes (t) of C per hectare (ha)) for circa 2010.This layer supports analysis but, if needed, a direct download of the data can be accessed here.

The dataset was constructed by combining the most reliable publicly available datasets and overlying them with the ESA CCI landcover map for the year 2010 [ESA, 2017], assigning to each grid cell the corresponding above-ground biomass value from the biomass map that was most appropriate for the grid cell’s landcover type.

Input carbon datasets were identified through a literature review of existing datasets on biomass carbon in terrestrial ecosystems published in peer-reviewed literature. To determine which datasets to combine to produce the global carbon density map, identified datasets were evaluated based on resolution, accuracy, biomass definition and reference date (see table 1 for further information on datasets selected).

Dataset

Scope

Year

Resolution

Definition

Santoro et al. 2018

Global

2010

100 m

Above-ground woody biomass for trees that are >10 cm diameter-at-breast-height, masked to Landsat-derived canopy cover for 2010; biomass is expressed as oven-dry weight of the woody parts (stem, bark, branches and twigs) of all living trees excluding stump and roots.

Xia et al. 2014

Global

1982-2006

8 km

Above-ground grassland biomass.

Bouvet et al. 2018

Africa

2010

25 m

Above-ground woodland and savannah biomass; low woody biomass areas, which therefore exclude dense forests and deserts.

Spawn et al. 2017

Global

2010

300 m

Synthetic, global above- and below-ground biomass maps that combine recently released satellite-based data of standing forest biomass with novel estimates for non-forest biomass stocks.

After aggregating each selected dataset to a nominal scale of 300 m resolution, forest categories in the CCI ESA 2010 landcover dataset were used to extract above-ground biomass from Santoro et al. 2018 for forest areas. Woodland and savanna biomass were then incorporated for Africa from Bouvet et al. 2018., and from Santoro et al. 2018 for areas outside of Africa and outside of forest. Biomass from croplands, sparse vegetation and grassland landcover classes from CCI ESA, in addition to shrubland areas outside Africa missing from Santoro et al. 2018, were extracted from were extracted from Xia et al. 2014. and Spawn et al. 2017 averaged by ecological zone for each landcover type.

Below-ground biomass were added using root-to-shoot ratios from the 2006 IPCC guidelines for National Greenhouse Gas Inventories (IPCC, 2006). No below-ground values were assigned to croplands as ratios were unavailable. Above- and below-ground biomass were then summed together and multiplied by 0.5 to convert to carbon, generating a single above-and-below-ground biomass carbon layer.This dataset has not been validated.

Here we used remote sensing data from multiple sources (time-series of Landsat and Sentinel images) to map the impervious surface area (ISA) at five-year intervals from 1990 to 2015, and then converted the results into a standardized dataset of the built-up area for 433 Chinese cities with 300,000 inhabitants or more, which were listed in the United Nations (UN) World Urbanization Prospects (WUP) database (including Mainland China, Hong Kong, Macao and Taiwan). We employed a range of spectral indices to generate the 1990–2015 ISA maps in urban areas based on remotely sensed data acquired from multiple sources. In this process, various types of auxiliary data were used to create the desired products for urban areas through manual segmentation of peri-urban and rural areas together with reference to several freely available products of urban extent derived from ISA data using automated urban–rural segmentation methods. After that, following the well-established rules adopted by the UN, we carried out the conversion to the standardized built-up area products from the 1990–2015 ISA maps in urban areas, which conformed to the definition of urban agglomeration area (UAA). Finally, we implemented data postprocessing to guarantee the spatial accuracy and temporal consistency of the final product.The standardized urban built-up area dataset (SUBAD–China) introduced here is the first product using the same definition of UAA adopted by the WUP database for 433 county and higher-level cities in China. The comparisons made with contemporary data produced by the National Bureau of Statistics of China, the World Bank and UN-habitat indicate that our results have a high spatial accuracy and good temporal consistency and thus can be used to characterize the process of urban expansion in China.The SUBAD–China contains 2,598 vector files in shapefile format containing data for all China's cities listed in the WUP database that have different urban sizes and income levels with populations over 300,000. Attached with it, we also provided the distribution of validation points for the 1990–2010 ISA products of these 433 Chinese cities in shapefile format and the confusion matrices between classified data and reference data during different time periods as a Microsoft Excel Open XML Spreadsheet (XLSX) file.Furthermore, The standardized built-up area products for such cities will be consistently updated and refined to ensure the quality of their spatiotemporal coverage and accuracy. The production of this dataset together with the usage of population counts derived from the WUP database will close some of the data gaps in the calculation of SDG11.3.1 and benefit other downstream applications relevant to a combined analysis of the spatial and socio-economic domains in urban areas.