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

This dataset contains soil type and soil classification, by area.

This dataset is harvested on a weekly basis from Allegheny County’s GIS data portal. The full metadata record for this dataset can also be found on Allegheny County's GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the "Explore button (and choosing the "Go to resource" option) to the right of the "ArcGIS Open Dataset" text below.

Category: Environment

Department: Geographic Information Systems Group; Department of Administrative Services

Development Notes: This data set is a digital soil survey and generally is the most detailed level of soil geographic data developed by the National Cooperative Soil Survey. The information was prepared by digitizing maps, by compiling information onto a planimetric correct base and digitizing, or by revising digitized maps using remotely sensed and other information. This data set consists of georeferenced digital map data and computerized attribute data. The map data are in a soil survey area extent format and include a detailed, field verified inventory of soils and miscellaneous areas that normally occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped. A special soil features layer (point and line features) is optional. This layer displays the location of features too small to delineate at the mapping scale, but they are large enough and contrasting enough to significantly influence use and management. The soil map units are linked to attributes in the National Soil Information System relational database, which gives the proportionate extent of the component soils and their properties. The soil map and data used in the SSURGO product were prepared by soil scientists as part of the National Cooperative Soil Survey.

Related Documents: Data Dictionary for SOIL_CODE, https://www.nrcs.usda.gov/Internet/FSE_MANUSCRIPTS/pennsylvania/PA003/0/legends.pdf (the last page includes the soil legend for this dataset)

The FDOT GIS Roads with Median Types feature class provides spatial information on Florida Median Types distinguishing between lawn, paved, painted, and curbed medians. It also notes where a fence, guardrail, or barrier wall divides the two sides of a divided road. A median is defined as a barrier or other physical separation between two lanes of traffic traveling in opposite directions, which can either be raised, painted, or paved. This information is required for all functionally classified roadways On or Off the SHS. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 11/08/2025.For more details please review the FDOT RCI Handbook Download Data: Enter Guest as Username to download the source shapefile from here: https://ftp.fdot.gov/file/d/FTP/FDOT/co/planning/transtat/gis/shapefiles/median_type.zip

The data were derived from scanned soil maps. Attributes include a soil number (2-180), corresponding to runoff coefficient values in a Hydrology Manual, provided by the Los Angeles County Department of Public Works, Water Resources Division.Purpose: For use in DPW’s Modified Rational Method Hydrology Model.Supplemental Information:Stormwater Engineering is a Division of the Los Angeles County Department of Public Works. Please visit their website for posted publications, including the above mentioned Hydrology Manual.

This dataset is a compilation of address point data for the City of Tempe. The dataset contains a point location, the official address (as defined by The Building Safety Division of Community Development) for all occupiable units and any other official addresses in the City. There are several additional attributes that may be populated for an address, but they may not be populated for every address. Contact: Lynn Flaaen-Hanna, Development Services Specialist Contact E-mail Link: Map that Lets You Explore and Export Address Data Data Source: The initial dataset was created by combining several datasets and then reviewing the information to remove duplicates and identify errors. This published dataset is the system of record for Tempe addresses going forward, with the address information being created and maintained by The Building Safety Division of Community Development.Data Source Type: ESRI ArcGIS Enterprise GeodatabasePreparation Method: N/APublish Frequency: WeeklyPublish Method: AutomaticData Dictionary

Soils of Dukes County per the USDA Natural Resource Conservation Service. Survey data from 2003 (version date 2018-01-25). Data compiled via Soil Data Viewer.

The Soil Data Viewer tool was used to generate the classification of Soil Type and Farmland Soil Classifications. The 3 letter codes utilized in earlier soil data reports has been joined to the Soil Type layer via the MUSYM field.The Martha's Vineyard Commission used these data to extract the Prime Agricultural Soils which are used in the MVC's DRI (Development of Regional Impact) Checklist v14 Map B-4.For more details about the Dukes County Soil Survey, visit the NRCS Web Soil Survey website. To learn the distinctions of of the 3 Farmland Soil Classifications, please read this info from the USDA. The 1986 publication of the Dukes County Soil Survey.NOTE: MassGIS does have more recent compilation of the NRCS soil data (downloaded June 2020; publ Nov. 2021). The MVC has not completed a comparison of these two datasets but anticipates the differences to be minimal. Also, given the use of the 2018 version in the MVC's DRI Checklist, for historic purposes, it is important to have this version available to the public.

This feature contains vector lines representing the shoreline and coastal habitats of California. Line segments are classified according to the Environmental Sensitivity Index (ESI) classification system and are a compilation of the ESI data from the most recent ESI atlas publications. The ESI data includes information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. This California dataset contains only the ESI shoreline data layer and is a merged set of individual ESI data sets to cover the entire California coast. For many parts of the California shoreline, the NOAA-ESI database lists several shoreline types present at a given location, described from landward to seaward. A simplified singular classification [Map_Class] was created to generalize the most dominant features of the multiple shore type attributes present in the raw data. More information can be found at the source citation at ESI Guidelines | response.restoration.noaa.gov Attributes: Line: Type of geographic feature (H: Hydrography, P: Pier, S: Shoreline) Most_sensitive: If multiple shoreline types appear in ESI classification, this field represents the highest value (most sensitive type); otherwise it is the same value as the ESI field. Shore_code: The ESI shoreline type. In many cases shorelines are ranked with multiple codes, such as "6B/3A" (listed landward to seaward). Source: Original year of ESI data. Esi_description: Concatenation of shore type descriptions (listed landward to seaward) Shoretype_1: Numeric classification for the first (most landward) ESI type. Shoretype_1_name: Physical description for the first ESI type. Shoretype_2: Numeric classification for the second ESI type. Shoretype_2_name: Physical description for the second ESI type Shoretype_3: Numeric classification for the third (most seaward) ESI type. Shoretype_3_name: Physical description for the third ESI type. Map_class: Generalized ESI shoreline type for simplified sym

This dataset is a compilation of available oil and gas pipeline data and is maintained by BSEE. Pipelines are used to transport and monitor oil and/or gas from wells within the outer continental shelf (OCS) to resource collection locations. Currently, pipelines managed by BSEE are found in Gulf of Mexico and southern California waters.

© MarineCadastre.gov This layer is a component of BOEMRE Layers.

This Map Service contains many of the primary data types created by both the Bureau of Ocean Energy Management (BOEM) and the Bureau of Safety and Environmental Enforcement (BSEE) within the Department of Interior (DOI) for the purpose of managing offshore federal real estate leases for oil, gas, minerals, renewable energy, sand and gravel. These data layers are being made available as REST mapping services for the purpose of web viewing and map overlay viewing in GIS systems. Due to re-projection issues which occur when converting multiple UTM zone data to a single national or regional projected space, and line type changes that occur when converting from UTM to geographic projections, these data layers should not be used for official or legal purposes. Only the original data found within BOEM/BSEE’s official internal database, federal register notices or official paper or pdf map products may be considered as the official information or mapping products used by BOEM or BSEE. A variety of data layers are represented within this REST service are described further below. These and other cadastre information the BOEM and BSEE produces are generated in accordance with 30 Code of Federal Regulations (CFR) 256.8 to support Federal land ownership and mineral resource management.

For more information – Contact: Branch Chief, Mapping and Boundary Branch, BOEM, 381 Elden Street, Herndon, VA 20170. Telephone (703) 787-1312; Email: mapping.boundary.branch@boem.gov

The REST services for National Level Data can be found here: http://gis.boemre.gov/arcgis/rest/services/BOEM_BSEE/MMC_Layers/MapServer

REST services for regional level data can be found by clicking on the region of interest from the following URL: http://gis.boemre.gov/arcgis/rest/services/BOEM_BSEE

Individual Regional Data or in depth metadata for download can be obtained in ESRI Shape file format by clicking on the region of interest from the following URL: http://www.boem.gov/Oil-and-Gas-Energy-Program/Mapping-and-Data/Index.aspx

Currently the following layers are available from this REST location:

OCS Drilling Platforms -Locations of structures at and beneath the water surface used for the purpose of exploration and resource extraction. Only platforms in federal Outer Continental Shelf (OCS) waters are included. A database of platforms and rigs is maintained by BSEE.

OCS Oil and Natural Gas Wells -Existing wells drilled for exploration or extraction of oil and/or gas products. Additional information includes the lease number, well name, spud date, the well class, surface area/block number, and statistics on well status summary. Only wells found in federal Outer Continental Shelf (OCS) waters are included. Wells information is updated daily. Additional files are available on well completions and well tests. A database of wells is maintained by BSEE.

OCS Oil & Gas Pipelines -This dataset is a compilation of available oil and gas pipeline data and is maintained by BSEE. Pipelines are used to transport and monitor oil and/or gas from wells within the outer continental shelf (OCS) to resource collection locations. Currently, pipelines managed by BSEE are found in Gulf of Mexico and southern California waters.

Unofficial State Lateral Boundaries - The approximate location of the boundary between two states seaward of the coastline and terminating at the Submerged Lands Act Boundary. Because most State boundary locations have not been officially described beyond the coast, are disputed between states or in some cases the coastal land boundary description is not available, these lines serve as an approximation that was used to determine a starting point for creation of BOEM’s OCS Administrative Boundaries. GIS files are not available for this layer due to its unofficial status.

BOEM OCS Administrative Boundaries - Outer Continental Shelf (OCS) Administrative Boundaries Extending from the Submerged Lands Act Boundary seaward to the Limit of the United States OCS (The U.S. 200 nautical mile Limit, or other marine boundary)For additional details please see the January 3, 2006 Federal Register Notice.

BOEM Limit of OCSLA ‘8(g)’ zone - The Outer Continental Shelf Lands Act '8(g) Zone' lies between the Submerged Lands Act (SLA) boundary line and a line projected 3 nautical miles seaward of the SLA boundary line. Within this zone, oil and gas revenues are shared with the coastal state(s). The official version of the ‘8(g)’ Boundaries can only be found on the BOEM Official Protraction Diagrams (OPDs) or Supplemental Official Protraction described below.

Submerged Lands Act Boundary - The SLA boundary defines the seaward limit of a state's submerged lands and the landward boundary of federally managed OCS lands. The official version of the SLA Boundaries can only be found on the BOEM Official Protraction Diagrams (OPDs) or Supplemental Official Protraction Diagrams described below.

Atlantic Wildlife Survey Tracklines(2005-2012) - These data depict tracklines of wildlife surveys conducted in the Mid-Atlantic region since 2005. The tracklines are comprised of aerial and shipboard surveys. These data are intended to be used as a working compendium to inform the diverse number of groups that conduct surveys in the Mid-Atlantic region.The tracklines as depicted in this dataset have been derived from source tracklines and transects. The tracklines have been simplified (modified from their original form) due to the large size of the Mid-Atlantic region and the limited ability to map all areas simultaneously.The tracklines are to be used as a general reference and should not be considered definitive or authoritative. This data can be downloaded from http://www.boem.gov/uploadedFiles/BOEM/Renewable_Energy_Program/Mapping_and_Data/ATL_WILDLIFE_SURVEYS.zip

BOEM OCS Protraction Diagrams & Leasing Maps - This data set contains a national scale spatial footprint of the outer boundaries of the Bureau of Ocean Energy Management’s (BOEM’s) Official Protraction Diagrams (OPDs) and Leasing Maps (LMs). It is updated as needed. OPDs and LMs are mapping products produced and used by the BOEM to delimit areas available for potential offshore mineral leases, determine the State/Federal offshore boundaries, and determine the limits of revenue sharing and other boundaries to be considered for leasing offshore waters. This dataset shows only the outline of the maps that are available from BOEM.Only the most recently published paper or pdf versions of the OPDs or LMs should be used for official or legal purposes. The pdf maps can be found by going to the following link and selecting the appropriate region of interest. http://www.boem.gov/Oil-and-Gas-Energy-Program/Mapping-and-Data/Index.aspx Both OPDs and LMs are further subdivided into individual Outer Continental Shelf(OCS) blocks which are available as a separate layer. Some OCS blocks that also contain other boundary information are known as Supplemental Official Block Diagrams (SOBDs.) Further information on the historic development of OPD's can be found in OCS Report MMS 99-0006: Boundary Development on the Outer Continental Shelf: http://www.boemre.gov/itd/pubs/1999/99-0006.PDF Also see the metadata for each of the individual GIS data layers available for download. The Official Protraction Diagrams (OPDs) and Supplemental Official Block Diagrams (SOBDs), serve as the legal definition for BOEM offshore boundary coordinates and area descriptions.

BOEM OCS Lease Blocks - Outer Continental Shelf (OCS) lease blocks serve as the legal definition for BOEM offshore boundary coordinates used to define small geographic areas within an Official Protraction Diagram (OPD) for leasing and administrative purposes. OCS blocks relate back to individual Official Protraction Diagrams and are not uniquely numbered. Only the most recently published paper or pdf

City of Cambridge, MA, GIS basemap development project encompasses the land area of City of Cambridge with a 200-foot fringe surrounding the area and Charles River shoreline towards Boston. The basemap data was developed at 1" = 40' mapping scale using digital photogrammetric techniques. Planimetric features; both man-made and natural features like vegetation, rivers have been depicted. These features are important to all GIS/mapping applications and publication. A set of data layers such as Buildings, Roads, Rivers, Utility structures, 1 ft interval contours are developed and represented in the geodatabase. The features are labeled and coded in order to represent specific feature class for thematic representation and topology between the features is maintained for an accurate representation at the 1:40 mapping scale for both publication and analysis. The basemap data has been developed using procedures designed to produce data to the National Standard for Spatial Data Accuracy (NSSDA) and is intended for use at 1" = 40 ' mapping scale. Where applicable, the vertical datum is NAVD1988.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription TYPE type: Stringwidth: 50precision: 0 Type of sports facility

EditDate type: Stringwidth: 4precision: 0

Flood Hatch ShapefilesIn addition to the three sets of rasters (Maximum Wave Heights, Water Surface Elevations, and DFEs) provided, separate shapefiles were also created to overlap and highlight special areas within the raster datasets produced for calculating DFEs. A flood hatch shapefile is not provided for every ACFEP level or for every region, but when it is provided, it encompasses the special areas for that level and region. The same hatch shapefile is applicable for all datatypes for the particular level and region. Flood hatch shapefiles encompass all areas of special values within the data rasters (including areas of 9999, 9998, and 9997 values). All regions have a 0.1% ACFEP level flood hatch shapefile because all 0.1% ACFEP rasters contain 9999 values.The flood hatch shapefiles contain individual polygons that describe the type of special area underlying that polygon’s spatial extent. For 9999 and 9998 values in the value rasters (water surface elevations, waves, and DFEs), the special hatched polygons will have the same extent of those values within those rasters. For 9997 values in the value rasters, the hatch polygon will always encompass the 9997 values, but may be larger in extent than just the location of those value cells. For these areas, water surface elevation, wave heights, and DFEs values may be provided, but they still represent a special zone.The Hatch polygons have 5 fields (Column headers) that describe each polygon within the shapefile. These fields include FID, Shape, Hatch_Type, Zones_txt, Hatch, and Hatch_Txt. The FID field contains an ID number for each polygon within that shapefile, while the Shape fieldlists the type of shapefile contained (polygon in all cases). The Hatch_Type field contains the numerical value that can be found within the value rasters (wave height, water surface, and DFE) underlying that polygon. Zones_txt and Hatch_txt are string type fields that contain descriptors of the polygon type, while the Hatch Field contains a numerical value for the type of hatching (1 for 0.1% Edge Zone, 2 for Wave Overtopping Zones, 3 for Dynamic Zone). The following table is an example of what a flood hatch file’s attribute table might look like.FIDShapeHatch_TypeZones_TxtHatchHatch_Txt0Polygon9999Shallow water flooding during extreme storms10.1% Edge Zone1Polygon9997Influenced by wave overtopping (incl. 9997 areas)2Wave Overtopping Zone2Polygon9998Dynamic Landform Areas3Dynamic ZoneSpecifically, the various hatch shapefiles can be defined as follows:• FID 0 Hatch Type – These represent areas of shallow water flooding during extreme storms. These are locations where flooding can only be expected during the most extreme events (> 1000-year return period) or where there are only minor flood depths (shallow flooding) during 1000-year return period AEP. These values only appear in 0.1% ACFEP level since they only occur at the very upper extent of extreme flooding. Water surface elevation values in these regions can be set to 0.1 foot above the site-specific land elevation to provide an estimate of the water surface elevation. Site-specific survey information may be needed to determine the land elevation. These hatch areas directly match areas with 9999 values within the rasters.• FID 1 Hatch Type – These represent wave overtopping zones. These hatch layers encompass the 9997 areas, but also include areas that have known values. Hatched areas of this type covering 9997 values would be expected to experience flooding caused by intermittent wave spray and overtopping only. Hatched areas of this type covering locations with values indicate that the flooding is caused by both direct sheet flow and wave overtopping. These hatched zones are provided for informational purposes by identifying zones that may require special design considerations for wave overtopping. Site-specific coastal processes analysis may also be required in these areas.• FID 2 Hatch Type – These represent areas where geomorphology is extremely dynamic and as such expected flooding may vary drastically. These values can appear in any ACFEP level. There are minimal locations of this type. These hatch areas directly match areas with 9998 values within the rasters.

Field Name Data Type Description

Statefp Number US Census Bureau unique identifier of the state

Countyfp Number US Census Bureau unique identifier of the county

Countynm Text County name

Tractce Number US Census Bureau unique identifier of the census tract

Geoid Number US Census Bureau unique identifier of the state + county + census tract

Aland Number US Census Bureau defined land area of the census tract

Awater Number US Census Bureau defined water area of the census tract

Asqmi Number Area calculated in square miles from the Aland

MSSAid Text ID of the Medical Service Study Area (MSSA) the census tract belongs to

MSSAnm Text Name of the Medical Service Study Area (MSSA) the census tract belongs to

Definition Text Type of MSSA, possible values are urban, rural and frontier.

TotalPovPop Number US Census Bureau total population for whom poverty status is determined of the census tract, taken from the 2020 ACS 5 YR S1701

This dataset contains soil type and soil classification, by area.

If viewing this description on the Western Pennsylvania Regional Data Center’s open data portal (https://www.wprdc.org), this dataset is harvested on a weekly basis from Allegheny County’s GIS data portal (https://openac.alcogis.opendata.arcgis.com/). The full metadata record for this dataset can also be found on Allegheny County’s GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the “Explore” button (and choosing the “Go to resource” option) to the right of the “ArcGIS Open Dataset” text below.

Category: Environment

Organization: Allegheny County

Department: Geographic Information Systems Group; Department of Information Technology

Temporal Coverage: 2000

Data Notes:

Coordinate System: Pennsylvania State Plane South Zone 3702; U.S. Survey Foot

Development Notes: This data set is a digital soil survey and generally is the most detailed level of soil geographic data developed by the National Cooperative Soil Survey. The information was prepared by digitizing maps, by compiling information onto a planimetric correct base and digitizing, or by revising digitized maps using remotely sensed and other information. This data set consists of georeferenced digital map data and computerized attribute data. The map data are in a soil survey area extent format and include a detailed, field verified inventory of soils and miscellaneous areas that normally occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped. A special soil features layer (point and line features) is optional. This layer displays the location of features too small to delineate at the mapping scale, but they are large enough and contrasting enough to significantly influence use and management. The soil map units are linked to attributes in the National Soil Information System relational database, which gives the proportionate extent of the component soils and their properties. The soil map and data used in the SSURGO product were prepared by soil scientists as part of the National Cooperative Soil Survey

Other: none

Related Document(s): https://nrcs.app.box.com/s/if2z8n756yrdx7d6il0e1c60i7cathjy/file/982654700807 - this includes the soil legend for this dataset.

Frequency - Data Change: As needed

Frequency - Publishing: As needed

Data Steward Name: Eli Thomas

Data Steward Email: gishelp@alleghenycounty.us

This dataset is a series of digital map-posters accompanying the AdaptNRM Guide: Helping Biodiversity Adapt: supporting climate adaptation planning using a community-level modelling approach.

These represent supporting materials and information about the community-level biodiversity models applied to climate change. Map posters are organised by four biological groups (vascular plants, mammals, reptiles and amphibians), two climate change scenario (1990-2050 MIROC5 and CanESM2 for RCP8.5), and five measures of change in biodiversity.

The map-posters present the nationally consistent data at locally relevant resolutions in eight parts – representing broad groupings of NRM regions based on the cluster boundaries used for climate adaptation planning (http://www.environment.gov.au/climate-change/adaptation) and also Nationally.

Map-posters are provided in PNG image format at moderate resolution (300dpi) to suit A0 printing. The posters were designed to meet A0 print size and digital viewing resolution of map detail. An additional set in PDF image format has been created for ease of download for initial exploration and printing on A3 paper. Some text elements and map features may be fuzzy at this resolution.

Each map-poster contains four dataset images coloured using standard legends encompassing the potential range of the measure, even if that range is not represented in the dataset itself or across the map extent.

Most map series are provided in two parts: part 1 shows the two climate scenarios for vascular plants and mammals and part 2 shows reptiles and amphibians. Eight cluster maps for each series have a different colour theme and map extent. A national series is also provided. Annotation briefly outlines the topics presented in the Guide so that each poster stands alone for quick reference.

An additional 77 National maps presenting the probability distributions of each of 77 vegetation types – NVIS 4.1 major vegetation subgroups (NVIS subgroups) - are currently in preparation.

Example citations:

Williams KJ, Raisbeck-Brown N, Prober S, Harwood T (2015) Generalised projected distribution of vegetation types – NVIS 4.1 major vegetation subgroups (1990 and 2050), A0 map-poster 8.1 - East Coast NRM regions. CSIRO Land and Water Flagship, Canberra. Available online at www.AdaptNRM.org and https://data.csiro.au/dap/.

Williams KJ, Raisbeck-Brown N, Harwood T, Prober S (2015) Revegetation benefit (cleared natural areas) for vascular plants and mammals (1990-2050), A0 map-poster 9.1 - East Coast NRM regions. CSIRO Land and Water Flagship, Canberra. Available online at www.AdaptNRM.org and https://data.csiro.au/dap/.

This dataset has been delivered incrementally. Please check that you are accessing the latest version of the dataset. Lineage: The map posters show case the scientific data. The data layers have been developed at approximately 250m resolution (9 second) across the Australian continent to incorporate the interaction between climate and topography, and are best viewed using a geographic information system (GIS). Each data layers is 1Gb, and inaccessible to non-GIS users. The map posters provide easy access to the scientific data, enabling the outputs to be viewed at high resolution with geographical context information provided.

Maps were generated using layout and drawing tools in ArcGIS 10.2.2

A check list of map posters and datasets is provided with the collection.

Map Series: 7.(1-77) National probability distribution of vegetation type – NVIS 4.1 major vegetation subgroup pre-1750 #0x

8.1 Generalised projected distribution of vegetation types (NVIS subgroups) (1990 and 2050)

9.1 Revegetation benefit (cleared natural areas) for plants and mammals (1990-2050)

9.2 Revegetation benefit (cleared natural areas) for reptiles and amphibians (1990-2050)

10.1 Need for assisted dispersal for vascular plants and mammals (1990-2050)

10.2 Need for assisted dispersal for reptiles and amphibians (1990-2050)

11.1 Refugial potential for vascular plants and mammals (1990-2050)

11.1 Refugial potential for reptiles and amphibians (1990-2050)

12.1 Climate-driven future revegetation benefit for vascular plants and mammals (1990-2050)

12.2 Climate-driven future revegetation benefit for vascular reptiles and amphibians (1990-2050)

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site2/rest/services/Public_Forest_Practices/WADNR_PUBLIC_FP_Unstable_Slopes/MapServer/3The siteclass data layer was created for use in implementing Forest Practices' Riparian Management Rules. (See WAC 222-30-021 and 222-30-022.)

The siteclass data layer was derived from the DNR soils data layer's site index codes and major tree species codes for western and eastern Washington soils contained in the layer's Soils-Main table and Soils-Pflg (private forest land grade) table. Site index ranges in the Soils_PFLG took precedence over site index ranges in the Soils-Main table where data existed.The siteclass data layer was created for use in implementing new ForestPractices' Riparian Management Rules. (See WAC 222-30-021 and 222-30-022.) The siteclass information was derived from the DNR soils data layer's site indexcodes and major tree species codes for western and eastern Washington soilscontained in the layer's Soils-Main table and Soils-Pflg (private forest landgrade) table. Site index ranges in the Soils_PFLG took precedence over siteindex ranges in the Soils-Main table where data existed.Siteclass codes as derived from the soil survey:For Western Washington, the 50 year site index is used SITECLASS SITE INDEX RANGE I 137+ II 119-136 III 97-118 IV 76-96 V 1-75For Eastern Washington, the 100 year site index is used SITECLASS SITE INDEX RANGE I 120+ II 101-120 III 81-100 IV 61-80 V 1-60In addition to the coding scheme above, the following codes were added forrule compliance: SITECLASS DESCRIPTION 6 (Red Alder) The soils major species code indicated Red Alder 7 (ND/GP) No data), NA, or gravel pit 8 (NC/MFP) Non-commercial or marginal commercial forest land 9 (WAT) Water body(Rule note: If the site index does not exist or indicates red alder,noncommercial, or marginally commercial species, the following apply:If the whole RMZ width is within those categories, use site class V.If those categories occupy only a portion of the RMZ width, then use thesite index for conifer in the adjacent soil polygon.)WADNR SOILS LAYER INFORMATION LAYER: SOILS GEN.SOURCE: State soils mapping program CODE DOCUMENT: State soil surveys CONTACT: NA COVER TYPE: Spatial polygon coverage DATA TYPE: Primary data Information for the SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five year mapping program completed in 1980 for the purpose of forest land taxation. It was funded by the Washington State Department of Revenue in cooperation with the Department of Natural Resources, Soil Conservation Service (SCS), USDA Forest Service and Washington State University. State and private lands which had the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soil survey project, agricultural and non- commercial forest lands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. Approximately 1100 townships wholly or partially contain digitized soils data (2101 townships would provide complete coverage of the state of Washington). SOILS data are currently stored in the Polygon Attribute Table (.PAT) and INFO expansion files. COORDINATE SYSTEM: WA State Plane South Zone (5626) (N. zone converted to S. zone) COORDINATE UNITS: Feet HORIZONTAL DATUM: NAD27 PROJECTION NAME: Lambert Conformal Conic **** MAJOR CODES USED FOR SITECLASS DATA*****PFLG DATA: ITEM: PFLG.MAJ.SPEC TITLE: Potential major tree species for given soil FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 3 3 C 0 0 0 CODE TABLE OR VALUE RANGE: SOIL.MAJ.SPEC.CODE DESCRIPTION: Potentially major tree species for a given soil type. The data carried by this item describes a major commercial tree species that could potentially grow on a specific soil type as identified in the Private Forest Land Grading program (PFLG). Non-tree codes are also included to map non-soil ground cover, e.g. water, gravel pits. ITEM: PFLG.SITE.INDEX TITLE: Mean site index calc.from trees on given soil FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 3 3 I 0 0 0 CODE TABLE OR VALUE RANGE: 0-200 DESCRIPTION: Site index data collected for the Private Forest Land Grading soils program (PFLG). It is a designation of the quality of a forest site based on the height of of the tallest trees (dominant and co-dominant trees) in a stand at an arbitrarily chosen age. Usually the age chosen is 50 or 100 years. For example, if the average height attained by the tallest trees in a fully stocked stand at the age of 50 years is 75 feet, the site index is 75 feet. Westside site conditions are estimated by using an index age of 50 years, while eastside site conditions are estimated by using an index age of 100 years.--------------------------------------------------------------------SOILS-MAIN DATA: CODE TABLE NAME: SOIL.MAJ.SPEC.CODE ----------------------------------------------------------------------------- CODE MAP/REPORT MAP CODE DESCRIPTION LABEL SYMB --------- ------------ ---- -------------------------------------------------- AF ALPINE FIR 0 Subalpine fir DF DOUGLAS FIR 0 Douglas fir GF GRAND FIR 0 Grand fir GP GRAVEL PIT 0 Gravel pit LP LODGEPOLE PN 0 Lodgepole pine MFP MAR FOR PROD 0 Marginal forest productivity NA N/A 0 Not applicable NC NON-COMMERC 0 Non-commercial ND NO DATA 0 No data PP PONDEROSA PN 0 Ponderosa pine RA RED ALDER 0 Red alder WAT WATER 0 Water WH W HEMLOCK 0 Western hemlock WL W LARCH 0 Western larch WP W WHITE PINE 0 Western white pine ITEM: SITE.INDEX.SIDE TITLE: Indicates 100 yr or 50 yr soil site index FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 1 1 C 0 0 0 CODE FILE OR VALUE RANGE: SITE.INDEX.SIDE.CODE DESCRIPTION: Code used to indicate whether 100 year or 50 year site index tables are used to calculate the site index of a soil type. Note that some site indexes for "eastside" soils are based on the 50 year index table. SITE.INDEX.SIDE Indicates 100 yr or 50 yr soil site index CODE FILE SITE.INDEX.SIDE.CODE IS NOT USED BY OTHER ITEMS CODE MAP/REPORT MAP CODE DESCRIPTION LABEL SYMB --------- ------------ ---- -------------------------------------------------- E 100 YR SITE 0 Soil site index based on 100 year table W 50 YR SITE 0 Soil site index based on 50 year table------------------------------------------------------------------

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. were derived from the NVC. NatureServe developed a preliminary list of potential vegetation types. These data were combined with existing plot data (Cully 2002) to derive an initial list of potential types. Additional data and information were gleaned from a field visit and incorporated into the final list of map units. Because of the park’s small size and the large amount of field data, the map units are equivalent to existing vegetation associations or local associations/descriptions (e.g., Prairie Dog Colony). In addition to vegetation type, vegetation structures were described using three attributes: height, coverage density, and coverage pattern. In addition to vegetation structure and context, a number of attributes for each polygon were stored in the associated table within the GIS database. Many of these attributes were derived from the photointerpretation; others were calculated or crosswalked from other classifications. Table 2.7.2 shows all of the attributes and their sources. Anderson Level 1 and 2 codes are also included (Anderson et al. 1976). These codes should allow for a more regional perspective on the vegetation types. Look-up tables for the names associated with the codes is included within the geodatabase and in Appendix D. The look-up tables contain all the NVC formation information as well as alliance names, unique IDs, and the ecological system codes (El_Code) for the associations. These El_Codes often represent a one-to-many relationship; that is, one association may be related to more than one ecological system. The NatureServe conservation status is included as a separate item. Finally, slope (degrees), aspect, and elevation were calculated for each polygon label point using a digital elevation model and an ArcView script. The slope figure will vary if one uses a TIN (triangulated irregular network) versus a GRID (grid-referenced information display) for the calculation (Jenness 2005). A grid was used for the slope figure in this dataset. Acres and hectares were calculated using XTools Pro for ArcGIS Desktop.

Table from the American Community Survey (ACS) 5-year series on household types and population related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B11003 Family Type by Presence and Age of Own Children under 18 Years, B11005 Households by Presence of People Under 18 Years by Household Type, B11007 Households by Presence of People 65 Years and Over by Household Type, B11001 Household Type (Including Living Alone), B11002 Household Type by Relatives and Nonrelatives for Population in Households, B25003 Tenure, B25008 Total Population in Occupied Housing Units by Tenure, B09019 Household Type (Including Living Alone) by Relationship. Data is pulled from block group tables for the most recent ACS vintage and summarized to the neighborhoods based on block group assignment.

Public Open Space Geographic Information System data collection for Perth and Peel Metropolitan Areas

The public open space (POS) dataset contains polygon boundaries of areas defined as publicly available and open. This geographic information system (GIS) dataset was collected in 2011/2012 using ArcGIS software and aerial photography dated from 2010-2011. The data was collected across the Perth Metro and Peel Region.

POS refer to all land reserved for the provision of green space and natural environments (e.g. parks, reserves, bushland) that is freely accessible and intended for use for recreation purposes (active or passive) by the general public. Four types of “green and natural public open spaces” are distinguished: (1) Park; (2) Natural or Conservation Area; (3) School Grounds; and (4) Residual. Areas where the public are not permitted except on payment or which are available to limited and selected numbers by membership (e.g. golf courses and sports centre facilities) or setbacks and buffers required by legislation are not included.

Initially, potential POSs were identified from a combination of existing geographic information system (GIS) spatial data layers to create a generalized representation of ‘green space’ throughout the Perth metropolitan and Peel regions. Base data layers include: cadastral polygons, metropolitan and regional planning scheme polygons, school point locations, and reserve vesting polygons. The ‘green’ space layer was then visually updated and edited to represent the true boundaries of each POS using 2010-2011 aerial photography within the ArcGIS software environment. Each resulting ’green’ polygon was then classified using a decision tree into one of four possible categories: park, natural or conservation area, school grounds, or residual green space.

Following the classification process, amenity and other information about each POS was collected for polygons classified as “Park” following a protocol developed at the Centre for the Built Environment and Health (CBEH) called POSDAT (Public Open Space Desktop Auditing Tool). The parks were audited using aerial photography visualized using ArcGIS software. . The presence or absence of amenities such as sporting facilities (e.g. tennis courts, soccer fields, skate parks etc) were audited as well as information on the environmental quality (i.e. presence of water, adjacency to bushland, shade along paths, etc), recreational amenities (e.g. presence of BBQ’, café or kiosks, public access toilets) and information on selected features related to personal safety.

The data is stored in an ArcGIS File Geodatabase Feature Class (size 4MB) and has restricted access.

Data creation methodology, data definitions, and links to publications based on this data, accompany the dataset.

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

Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations.Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals. Data from the gSSURGO databasewas used to create this layer. To download ready-to-use project packages of useful soil data derived from the SSURGO dataset, please visit the USA SSURGO Downloader app. Dataset SummaryPhenomenon Mapped: Soils of the United States and associated territoriesGeographic Extent: The 50 United States, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaCoordinate System: Web Mercator Auxiliary SphereVisible Scale: 1:144,000 to 1:1,000Source: USDA Natural Resources Conservation ServiceUpdate Frequency: AnnualPublication Date: December 2024 What can you do with this layer?ArcGIS OnlineFeature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro.Below are just a few of the things you can do with a feature service in Online and Pro.Add this layer to a map in the map viewer. The layer is limited to scales of approximately 1:144,000 or larger but avector tile layercreated from the same data can be used at smaller scales to produce awebmapthat displays across the full scale range. The layer or a map containing it can be used in an application.Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections and apply filters. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Change the layer’s style and filter the data. For example, you could set a filter forFarmland Class= "All areas are prime farmland" to create a map of only prime farmland.Add labels and set their propertiesCustomize the pop-up ArcGIS ProAdd this layer to a 2d or 3d map. The same scale limit as Online applies in ProUse as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of theLiving Atlas of the Worldthat provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Data DictionaryAttributesKey fields from nine commonly used SSURGO tables were compiled to create the 173 attribute fields in this layer. Some fields were joined directly to the SSURGO Map Unit polygon feature class while others required summarization and other processing to create a 1:1 relationship between the attributes and polygons prior to joining the tables. Attributes of this layer are listed below in their order of occurrence in the attribute table and are organized by the SSURGO table they originated from and the processing methods used on them. Map Unit Polygon Feature Class Attribute TableThe fields in this table are from the attribute table of the Map Unit polygon feature class which provides the geographic extent of the map units.Area SymbolSpatial VersionMap Unit Symbol Map Unit TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the table using the Map Unit Key field.Map Unit NameMap Unit KindFarmland ClassInterpretive FocusIntensity of MappingIowa Corn Suitability Rating Legend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project Scale Survey Area Catalog TableThe fields in this table have a 1:1 relationship with the polygons and were joined to the Map Unit table using the Survey Area Catalog Key and Legend Key fields.Survey Area VersionTabular Version Map Unit Aggregated Attribute TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the Map Unit attribute table using the Map Unit Key field. Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Mapunit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Mapunit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - PresenceRating for Manure and Food Processing Waste - Weighted Average Component Table – Dominant ComponentMap units have one or more components. To create a 1:1 join component data must be summarized by map unit. For these fields a custom script was used to select the component with the highest value for the Component Percentage Representative Value field (comppct_r). Ties were broken with the Slope Representative Value field (slope_r). Components with lower average slope were selected as dominant. If both soil order and slope were tied, the first value in the table was selected. Component Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoff ClassSoil loss tolerance factorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionHydric RatingAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic ClassTaxonomic OrderTaxonomic SuborderGreat GroupSubgroupParticle SizeParticle Size ModCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoist SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilCalifornia Storie IndexComponent Key Component Table – Weighted AverageMap units may have one or more soil components. To create a 1:1 join, data from the Component table must be summarized by map unit. For these fields a custom script was used to calculate an average value for each map unit weighted by the Component Percentage Representative Value field (comppct_r).Slope Gradient - Low ValueSlope Gradient - Representative ValueSlope Gradient - High ValueSlope Length USLE - Low ValueSlope Length USLE - Representative ValueSlope Length USLE - High ValueElevation - Low ValueElevation - Representative ValueElevation - High ValueAlbedo - Low ValueAlbedo - Representative ValueAlbedo - High ValueMean Annual Air Temperature - Low ValueMean Annual Air Temperature - Representative ValueMean Annual Air Temperature - High ValueMean Annual Precipitation - Low ValueMean Annual Precipitation - Representative ValueMean Annual Precipitation - High ValueRelative Effective Annual Precipitation - Low ValueRelative Effective Annual Precipitation - Representative ValueRelative Effective Annual Precipitation - High ValueDays between Last and First Frost - Low ValueDays between Last and First Frost - Representative ValueDays between Last and First Frost - High ValueRange Forage Annual Potential Production - Low ValueRange Forage Annual Potential Production - Representative ValueRange Forage Annual Potential Production - High ValueInitial Subsidence - Low ValueInitial Subsidence - Representative ValueInitial Subsidence -