This layer features special areas of interest (AOIs) that have been contributed to Esri Community Maps using the new Community Maps Editor app. The data that is accepted by Esri will be included in selected Esri basemaps, including our suite of Esri Vector Basemaps, and made available through this layer to export and use offline. Export DataThe contributed data is also available for contributors and other users to export (or extract) and re-use for their own purposes. Users can export the full layer from the ArcGIS Online item details page by clicking the Export Data button and selecting one of the supported formats (e.g. shapefile, or file geodatabase (FGDB)). User can extract selected layers for an area of interest by opening in Map Viewer, clicking the Analysis button, viewing the Manage Data tools, and using the Extract Data tool. To display this data with proper symbology and metadata in ArcGIS Pro, you can download and use this layer file.Data UsageThe data contributed through the Community Maps Editor app is primarily intended for use in the Esri Basemaps. Esri staff will periodically (e.g. weekly) review the contents of the contributed data and either accept or reject the data for use in the basemaps. Accepted features will be added to the Esri basemaps in a subsequent update and will remain in the app for the contributor or others to edit over time. Rejected features will be removed from the app.Esri Community Maps Contributors and other ArcGIS Online users can download accepted features from this layer for their internal use or map publishing, subject to the terms of use below.

The USGS National Hydrography Dataset (NHD) service from The National Map is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD is available nationwide in two seamless datasets, one based on 1:24,000 (or larger) scale and referred to as high resolution NHD, and the other based on 1:100,000 scale and referred to as medium resolution NHD. The NHD from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. The NHD is commonly combined with other data themes, such as boundaries, elevation, structures, and transportation, to produce general reference base maps. The National Map download client allows free downloads of public domain NHD data in either Esri File Geodatabase or Shapefile formats. For additional information on the NHD, go to https://www.usgs.gov/national-hydrography/national-hydrography-dataset. See https://apps.nationalmap.gov/help/ for assistance with The National Map viewer, download client, services, or metadata. Data Refreshed January, 2024.

This layer shows median household income by race and by age of householder. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. Median income and income source is based on income in past 12 months of survey. This layer is symbolized to show median household income. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B19013B, B19013C, B19013D, B19013E, B19013F, B19013G, B19013H, B19013I, B19049, B19053Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

The USGS National Hydrography Dataset (NHD) service from The National Map is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD is available nationwide in two seamless datasets, one based on 1:24,000 (or larger) scale and referred to as high resolution NHD, and the other based on 1:100,000 scale and referred to as medium resolution NHD. The NHD from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. The NHD is commonly combined with other data themes, such as boundaries, elevation, structures, and transportation, to produce general reference base maps. The National Map download client allows free downloads of public domain NHD data in either Esri File Geodatabase or Shapefile formats. For additional information on the NHD, go to https://www.usgs.gov/national-hydrography/national-hydrography-dataset. See https://apps.nationalmap.gov/help/ for assistance with The National Map viewer, download client, services, or metadata. Data Refreshed January, 2024.

One-eighth of the United States (247 million acres) is managed by the Bureau of Land Management. As part of the Department of the Interior, the agency oversees the 30 million acre National Conservation Lands system, a collection of lands that includes 221 wilderness areas, 23 national monuments and 636 other protected areas. Bureau of Land Management Lands contain over 63,000 oil and gas wells and provide forage for over 18,000 grazing permit holders on 155 million acres of land.Dataset SummaryPhenomenon Mapped: United States lands managed by the US Department of the Interior Bureau of Land Management. Coordinate System: Web Mercator Auxiliary SphereExtent: Contiguous United States and AlaskaVisible Scale: The data is visible at all scales but draws best at scales larger than 1:2,000,000.Source: BLM Surface Management Agency layerPublication Date: November 2023This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Bureau of Land Management lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "bureau of land management" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "bureau of land management" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

NOTICE TO PROVISIONAL 2023 LAND USE DATA USERS: Please note that on December 6, 2024 the Department of Water Resources (DWR) published the Provisional 2023 Statewide Crop Mapping dataset. The link for the shapefile format of the data mistakenly linked to the wrong dataset. The link was updated with the appropriate data on January 27, 2025. If you downloaded the Provisional 2023 Statewide Crop Mapping dataset in shapefile format between December 6, 2024 and January 27, we encourage you to redownload the data. The Map Service and Geodatabase formats were correct as posted on December 06, 2024.

Thank you for your interest in DWR land use datasets.

The California Department of Water Resources (DWR) has been collecting land use data throughout the state and using it to develop agricultural water use estimates for statewide and regional planning purposes, including water use projections, water use efficiency evaluations, groundwater model developments, climate change mitigation and adaptations, and water transfers. These data are essential for regional analysis and decision making, which has become increasingly important as DWR and other state agencies seek to address resource management issues, regulatory compliances, environmental impacts, ecosystem services, urban and economic development, and other issues. Increased availability of digital satellite imagery, aerial photography, and new analytical tools make remote sensing-based land use surveys possible at a field scale that is comparable to that of DWR’s historical on the ground field surveys. Current technologies allow accurate large-scale crop and land use identifications to be performed at desired time increments and make possible more frequent and comprehensive statewide land use information. Responding to this need, DWR sought expertise and support for identifying crop types and other land uses and quantifying crop acreages statewide using remotely sensed imagery and associated analytical techniques. Currently, Statewide Crop Maps are available for the Water Years 2014, 2016, 2018- 2022 and PROVISIONALLY for 2023.

Historic County Land Use Surveys spanning 1986 - 2015 may also be accessed using the CADWR Land Use Data Viewer: https://gis.water.ca.gov/app/CADWRLandUseViewer.

For Regional Land Use Surveys follow: https://data.cnra.ca.gov/dataset/region-land-use-surveys.

For County Land Use Surveys follow: https://data.cnra.ca.gov/dataset/county-land-use-surveys.

For a collection of ArcGIS Web Applications that provide information on the DWR Land Use Program and our data products in various formats, visit the DWR Land Use Gallery: https://storymaps.arcgis.com/collections/dd14ceff7d754e85ab9c7ec84fb8790a.

Recommended citation for DWR land use data: California Department of Water Resources. (Water Year for the data). Statewide Crop Mapping—California Natural Resources Agency Open Data. Retrieved “Month Day, YEAR,” from https://data.cnra.ca.gov/dataset/statewide-crop-mapping.

The blank geodatabase has the required fields for submitting wetland determination polygons and requested map edits for the Vermont Significant Wetlands Inventory. The valid NWI codes are included in the a separate table inside the file geodatabase. Consider joining the Wetland Program's ArcGIS Online Group for submitting determination or wetlands edits. If your organization has an ArcGIS organizational account, make a request to join this group:https://www.arcgis.com/home/group.html?id=164aab9de6e44ec79aa0dfa7ee41dfcb#overviewJoin a groupTo join a group, do the following:Verify that you are signed in.Click Groups at the top of the site, and use the tabs, filters, sort options, and search as needed to find the group you want to join.Click the name of the group to open its group page.On the Overview tab, click Join this group. If necessary, click Submit Request.Depending on the group's membership settings, you will see a message indicating that you are now a member of the group or that your request has been sent to the group owner (after clicking Submit Request). If a request is sent, the owner of the group sees it on the group page and accepts or denies your request for membership. If the owner accepts your request, you are added as a member, and the group appears on your Groups page.

The US Fish and Wildlife Service manages the nation's 560 National Wildlife Refuges and thousands of small wetlands and other special management areas including Wildlife Management Areas and Waterfowl Production Areas. These lands cover more than 150 million acres that protect fish, wildlife, plants, and their habitats for the continuing benefit of the American people.Dataset SummaryPhenomenon Mapped: United States lands managed by the US Fish and Wildlife Service. Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, and the Northern Mariana Islands. The layer also includes large National Monuments and Wildlife Refuges in the Pacific Ocean.Visible Scale: The data is visible at all scales.Source: USFWS Interest Simplified layer Publication Date: January 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Fish and Wildlife Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "fish and wildlife service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "fish and wildlife service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

Please note that this dataset is not an official City of Toronto land use dataset. It was created for personal and academic use using City of Toronto Land Use Maps (2019) found on the City of Toronto Official Plan website at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/official-plan-maps-copy, along with the City of Toronto parcel fabric (Property Boundaries) found at https://open.toronto.ca/dataset/property-boundaries/ and Statistics Canada Census Dissemination Blocks level boundary files (2016). The property boundaries used were dated November 11, 2021. Further detail about the City of Toronto's Official Plan, consolidation of the information presented in its online form, and considerations for its interpretation can be found at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/ Data Creation Documentation and Procedures Software Used The spatial vector data were created using ArcGIS Pro 2.9.0 in December 2021. PDF File Conversions Using Adobe Acrobat Pro DC software, the following downloaded PDF map images were converted to TIF format. 9028-cp-official-plan-Map-14_LandUse_AODA.pdf 9042-cp-official-plan-Map-22_LandUse_AODA.pdf 9070-cp-official-plan-Map-20_LandUse_AODA.pdf 908a-cp-official-plan-Map-13_LandUse_AODA.pdf 978e-cp-official-plan-Map-17_LandUse_AODA.pdf 97cc-cp-official-plan-Map-15_LandUse_AODA.pdf 97d4-cp-official-plan-Map-23_LandUse_AODA.pdf 97f2-cp-official-plan-Map-19_LandUse_AODA.pdf 97fe-cp-official-plan-Map-18_LandUse_AODA.pdf 9811-cp-official-plan-Map-16_LandUse_AODA.pdf 982d-cp-official-plan-Map-21_LandUse_AODA.pdf Georeferencing and Reprojecting Data Files The original projection of the PDF maps is unknown but were most likely published using MTM Zone 10 EPSG 2019 as per many of the City of Toronto's many datasets. They could also have possibly been published in UTM Zone 17 EPSG 26917 The TIF images were georeferenced in ArcGIS Pro using this projection with very good results. The images were matched against the City of Toronto's Centreline dataset found here The resulting TIF files and their supporting spatial files include: TOLandUseMap13.tfwx TOLandUseMap13.tif TOLandUseMap13.tif.aux.xml TOLandUseMap13.tif.ovr TOLandUseMap14.tfwx TOLandUseMap14.tif TOLandUseMap14.tif.aux.xml TOLandUseMap14.tif.ovr TOLandUseMap15.tfwx TOLandUseMap15.tif TOLandUseMap15.tif.aux.xml TOLandUseMap15.tif.ovr TOLandUseMap16.tfwx TOLandUseMap16.tif TOLandUseMap16.tif.aux.xml TOLandUseMap16.tif.ovr TOLandUseMap17.tfwx TOLandUseMap17.tif TOLandUseMap17.tif.aux.xml TOLandUseMap17.tif.ovr TOLandUseMap18.tfwx TOLandUseMap18.tif TOLandUseMap18.tif.aux.xml TOLandUseMap18.tif.ovr TOLandUseMap19.tif TOLandUseMap19.tif.aux.xml TOLandUseMap19.tif.ovr TOLandUseMap20.tfwx TOLandUseMap20.tif TOLandUseMap20.tif.aux.xml TOLandUseMap20.tif.ovr TOLandUseMap21.tfwx TOLandUseMap21.tif TOLandUseMap21.tif.aux.xml TOLandUseMap21.tif.ovr TOLandUseMap22.tfwx TOLandUseMap22.tif TOLandUseMap22.tif.aux.xml TOLandUseMap22.tif.ovr TOLandUseMap23.tfwx TOLandUseMap23.tif TOLandUseMap23.tif.aux.xml TOLandUseMap23.tif.ov Ground control points were saved for all georeferenced images. The files are the following: map13.txt map14.txt map15.txt map16.txt map17.txt map18.txt map19.txt map21.txt map22.txt map23.txt The City of Toronto's Property Boundaries shapefile, "property_bnds_gcc_wgs84.zip" were unzipped and also reprojected to EPSG 26917 (UTM Zone 17) into a new shapefile, "Property_Boundaries_UTM.shp" Mosaicing Images Once georeferenced, all images were then mosaiced into one image file, "LandUseMosaic20211220v01", within the project-generated Geodatabase, "Landuse.gdb" and exported TIF, "LandUseMosaic20211220.tif" Reclassifying Images Because the original images were of low quality and the conversion to TIF made the image colours even more inconsistent, a method was required to reclassify the images so that different land use classes could be identified. Using Deep learning Objects, the images were re-classified into useful consistent colours. Deep Learning Objects and Training The resulting mosaic was then prepared for reclassification using the Label Objects for Deep Learning tool in ArcGIS Pro. A training sample, "LandUseTrainingSamples20211220", was created in the geodatabase for all land use types as follows: Neighbourhoods Insitutional Natural Areas Core Employment Areas Mixed Use Areas Apartment Neighbourhoods Parks Roads Utility Corridors Other Open Spaces General Employment Areas Regeneration Areas Lettering (not a land use type, but an image colour (black), used to label streets). By identifying the letters, it then made the reclassification and vectorization results easier to clean up of unnecessary clutter caused by the labels of streets. Reclassification Once the... Visit https://dataone.org/datasets/sha256%3A3e3f055bf6281f979484f847d0ed5eeb96143a369592149328c370fe5776742b for complete metadata about this dataset.

QuesterTangent’s SWATHVIEW seabed classification software to post-process the 410 kHz side scan sonar signal. This software analyzes the side scan sonar backscatter signal to produce a classification map based on the acoustical reflectivity characteristics of bottom sediments. Employing proprietary algorithms SWATHVIEW uses multivariate analysis to find patterns in the side scan acoustic backscatter signal which reflect bottom textural parameters. Cluster analysis is used to group together regions of similar acoustic backscatter characteristics, or classes.Once the acoustic classes were determined, they were correlated with bottom samples and imagery. Bottom grab samples were obtained using a Van Veen sampler with a 4-inch depth capacity. Sampling sites were chosen based on the side scan data. We took samples on acoustically distinct bottom types to confirm our estimates of those types. The seabed classification data were layered over the side scan mosaics and bathymetry. These data sets were used to correlate side scan reflectivity with acoustic seabed classes and detect any influences that abrupt changes in seafloor slope may have on the acoustic data. Steep slopes tend to scatter the acoustic signals and produce anomalous data.REFS: Conkwright, R.D., Van Ryswick, S, Sylvia, E.R. 2014. Seafloor Survey of Nearshore Ocean City Maryland. Maryland Geological Survey. Funding to compile these datasets provided by BOEM under cooperative agreement number: M14AC00007. Data processing and compilation was executed by Maryland Geological Survey.The views expressed herein are those of the authors and do not necessarily reflect the views of the Bureau of Ocean Energy Management (BOEM) or any of its sub-agencies. This geodatabase was created to provide planners and managers access to data about aggregate resources off the coast of Maryland. This geodatabase should not be used for navigational purposes.This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Feature Service Link: https://geodata.md.gov/imap/rest/services/Geoscientific/MD_OffshoreOceanResources/FeatureServer/4

This dataset provides locations and technical specifications of wind turbines in the United States, almost all of which are utility-scale. Utility-scale turbines are ones that generate power and feed it into the grid, supplying a utility with energy. They are usually much larger than turbines that would feed a homeowner or business.

The data formats downloadable from the Minnesota Geospatial Commons contain just the Minnesota turbines. Data, maps and services accessed from the USWTDB website provide nationwide turbines.

The regularly updated database has wind turbine records that have been collected, digitized, and locationally verified. Turbine data were gathered from the Federal Aviation Administration's (FAA) Digital Obstacle File (DOF) and Obstruction Evaluation Airport Airspace Analysis (OE-AAA), the American Wind Energy Association (AWEA), Lawrence Berkeley National Laboratory (LBNL), and the United States Geological Survey (USGS), and were merged and collapsed into a single data set.

Verification of the turbine positions was done by visual interpretation using high-resolution aerial imagery in Esri ArcGIS Desktop. A locational error of plus or minus 10 meters for turbine locations was tolerated. Technical specifications for turbines were assigned based on the wind turbine make and models as provided by manufacturers and project developers directly, and via FAA datasets, information on the wind project developer or turbine manufacturer websites, or other online sources. Some facility and turbine information on make and model did not exist or was difficult to obtain. Thus, uncertainty may exist for certain turbine specifications. Similarly, some turbines were not yet built, not built at all, or for other reasons cannot be verified visually. Location and turbine specifications data quality are rated and a confidence is recorded for both. None of the data are field verified.

The U.S. Wind Turbine Database website provides the national data in many different formats: shapefile, CSV, GeoJSON, web services (cached and dynamic), API, and web viewer. See: https://eerscmap.usgs.gov/uswtdb/

The web viewer provides many options to search; filter by attribute, date and location; and customize the map display. For details and screenshots of these options, see: https://eerscmap.usgs.gov/uswtdb/help/

------------
This metadata record was adapted by the Minnesota Geospatial Information Office (MnGeo) from the national version of the metadata. It describes the Minnesota extract of the shapefile data that has been projected from geographic to UTM coordinates and converted to Esri file geodatabase (fgdb) format. There may be more recent updates available on the national website. Accessing the data via the national web services or API will always provide the most recent data.

This dataset is called the Gridded SSURGO (gSSURGO) Database and is derived from the Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into a Conterminous US-wide extent, and adding a Conterminous US-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map" attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format.The raster and vector map data have a Conterminous US-wide extent. The raster map data have a 30 meter cell size. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data.The value added look up (valu) table contains attribute data summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria.The Gridded SSURGO dataset was created for use in national, regional, and state-wide resource planning and analysis of soils data. The raster map layer data can be readily combined with other national, regional, and local raster layers, e.g., National Land Cover Database (NLCD), the National Agricultural Statistics Service (NASS) Crop Data Layer, or the National Elevation Dataset (NED).

The USGS National Hydrography Dataset (NHD) service from The National Map is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD is available nationwide in two seamless datasets, one based on 1:24,000 (or larger) scale and referred to as high resolution NHD, and the other based on 1:100,000 scale and referred to as medium resolution NHD. The NHD from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. The NHD is commonly combined with other data themes, such as boundaries, elevation, structures, and transportation, to produce general reference base maps. The National Map download client allows free downloads of public domain NHD data in either Esri File Geodatabase or Shapefile formats. For additional information on the NHD, go to https://www.usgs.gov/national-hydrography/national-hydrography-dataset. See https://apps.nationalmap.gov/help/ for assistance with The National Map viewer, download client, services, or metadata.

The U.S. Defense Department oversees the nation's armed forces and manages over 30 million acres of land. With over 2.8 million service members and civilian employees the department is the world's largest employer.Dataset SummaryPhenomenon Mapped: Lands managed by the U.S. Department of DefenseCoordinate System: Web Mercator Auxiliary SphereExtent: United States, Guam, Puerto RicoVisible Scale: The data is visible at all scalesSource: DOD Military Installations Ranges and Training Areas layer Publication Date: December 2023This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Department of Defense lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "department of defense" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "department of defense" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

The US National Park Service manages 84.4 million acres that include the nation's 59 national parks, many national monuments, and other conservation and historical properties. These lands range from the 13 million acre Wrangell-St. Elias National Park and Preserve in Alaska to the 0.02 acre Thaddeus Kosciuszko National Memorial in Pennsylvania.Dataset SummaryPhenomenon Mapped: Administrative boundaries of units in the United States National Park Service system. Not all lands within the administrative boundaries are owned by the National Park Service.Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States, District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana IslandsVisible Scale: The data is visible at all scalesSource: NPS Administrative Boundaries National Park System Units layerPublication Date: January 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Park Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "national park service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "national park service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

Gridded National Soil Survey Geographic Database (gNATSGO)gNATSGO for AllRaster Soil Surveys (RSS)Web Soil SurveyGridded Soil Survey Geographic (gSSURGO) DatabasegNATSGO now uses the GeoPackage version of the SQLite SSURGO Template database instead of an ESRI File Geodatabase.

In 2025, only a single large gNATSGO database was created for all areas of the United States and Island Jurisdictions. State tiles were not produced.

This database is designed to be used with the new SSURGO Portal application Soil Data Viewer (SDV) tool, which has the same ratings as Web Soil Survey.
Access SSURGO Portal at https://www.nrcs.usda.gov/resources/data-and-reports/ssurgo-portal. Refer to the Quick Start Guide for SSURGO Portal installation instructions.
You can install SSURGO Portal and then use SDV to make thematic maps for the entire United States. Refer to the SSURGO Portal User Guide for SDV instructions. You can also refer to the 6 minute mark of this youtube video. https://www.youtube.com/watch?v=4FGuxqxbCG0 SDV is a replacement for the old Soil Data Viewer ArcMap tool and the old GSSURGO Create Soil Map ArcMap tool.

DB Browser is a free application for viewing and querying SQLite files. GeoPackages are SQLite files and can be opened in DB Browser.

Rasters of soil map units are delivered as 30m cell size tif files, with dbf attribute tables, statistics, and pyramids pre built.

The source.shp file shows the original source of data, with the options being Raster Soil Survey (RSS), SSURGO, and STATSGO.

The mupolygon, mupoint, muline, featpoint, featline, featdesc, and sapolygon feature classes with the database are empty but were retained due to database schema requirements.

Contact soilshotline@usda.gov for assistance.

Historic sites include areas where significant historical events of cultural interest occurred. These range from National Historic Parks, Sites, Trails, and Preserves to state, local, and areas held in trust.Dataset SummaryPhenomenon Mapped: Historic Sites from the Protected Areas Database of the United States version 3.0Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States and GuamVisible Scale: Visible at all scalesSource: USGS National Gap Analysis Program PAD-US version 3.0Publication Date: July 2022What can you do with this layer?This layer can be used to create maps and to visualize the underlying data across the ArcGIS platform. It can also be used as an analytic input in ArcGIS Online.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of the description page.

REC2 (River Environment Classification, v2.5) - June 2019 [Hosted Feature Layer]This service depicts rivers as lines and catchments as polygons The River Environment Classification (REC) is a database of catchment spatial attributes, summarised for every segment in New Zealand's network of rivers. The attributes were compiled for the purposes of river classification, while the river network description has been used to underpin models. Typically, models (e.g. CLUES and TopNet) would use the dendritic (branched) linkages of REC river segments to perform their calculations. Since its release and use over the last decade, some errors in the location and connectivity of these linkages have been identified. The current revision corrects those errors, and updates a number of spatial attributes with the latest data. REC2 provides a re-cut framework of rivers for modelling and classification. It is built on a newer version of the 30m digital elevation model, in which the original 20m contours were supplemented with, for example, more spot elevation data and a better coastline contour. Boundary errors were minimised by processing contiguous areas (such as the whole of the North Island) together, which wasn't possible when it was originally created.Major updates include the revision of catchment land use information, by overlaying with the land cover database (LCDB3, current as at 2008), and the update of river and rainfall statistics with data from 1960-2006. The river network and associated attributes have been assembled within an ArcGIS geodatabase. Topological connectivity has been established to allow upstream and downstream tracing within the network. REC2 can be downloaded or streamed and used directly in ArcMap. (A file geodatabase version for ArcGIS of REC2 can be downloaded as a zip file and used directly for analyses in ArcMap from here)This layer is using Esri's ArcGIS Online Optimizations for fast rendering.This is REC2 (Version 5) , June 2019 - a publicly available dataset from NIWA Taihoro Nukurangi.NIWA acknowledges funding from the MBIE SSIF towards the preparation of REC v2.5Coordinate Reference System: NZTM (New Zealand Transverse Mercator, EPSG: 2193)Geometric Representation of Rivers: LinesExtent (Bounding Box):

Top(Latitude) -33.9534Bottom(Latitude) -47.4867

Left (Longitude) 166.2634

Right (Longitude) 178.9733

Riverlines table Attributes associated directly with network:

Field Type Description

Catarea Real Watershed area in m2 CUM_Area Real Area upstream of a reach (and including this reach area) in m2. Nzsegment Integer Reach identifier to be used with REC2 (supercedes nzreach in REC1).

Lengthdown Real The distance to coast from any reach to its outlet reach, where the river drains (m). Headwater Integer Number (0) denoting whether a stream is a “source” (headwater) stream. Non-zero for non-headwater streams.

Hydseq Integer A unique number denoting the hydrological processing order of a river segment relative to others in the network.

StreamOrder Integer A number describing the Strahler order a reach in a network of reaches.

euclid_dist Real The straight line distance of a reach from the reach “inlet” to its “outlet”. upElev Real Height (asl) of the upstream end of a reach section in a watershed (m). downElev Real Height (asl) of the downstream end of a reach section in a watershed (m).

upcoordX Real Easting of the upstream end of a river segment in m (NZTM2000). upcoordY Real Northing of the upstream end of a river segment in m (NZTM2000). downcoordX Real Easting of the downstream end of a river segment in m (NZTM2000).

downcoordY Real Northing of the downstream end of a river segment in m (NZTM2000). sinuosity Real Actual distance divided by the straight line distance giving the degree of curvature of the stream nzreach_re Integer The REC1 identifiying number for the corresponding\closest reach from REC1 (can be used to retrieve the REC management classes) headw_dist Integer Distance of the furthermost “source” or headwater reach from any reach (m). Shape_leng Real The length of the reach (vector) as calculated by ArcGIS. Segslpmean Real Mean segment slope along length of reach.

LID Integer Lake Identifier number(LID) of overlapping lake.

Reachtype

Integer A value of 2 is assigned if the segment is an outlet to the lake, otherwise 0 or null. nextdownid integer segment number of the most downstream reach

_Item Page Created: 2019-06-13 00:29 Item Page Last Modified: 2025-03-15 15:14Owner: NIWA_OpenDataRiver LinesNo data edit dates availableFields: OBJECTID_1,HydroID,NextDownID,CATAREA,CUM_AREA,nzsegment,Enabled,LENGTHDOWN,Headwater,Hydseq,StreamOrde,euclid_dis,upElev,downElev,upcoordX,downcoordX,downcoordY,upcoordY,sinuosity,nzreach_re,headw_dist,segslpmean,LID,reachtype,FROM_NODE,TO_NODE,Shape_Leng,FLOWDIRWatershedsNo data edit dates availableFields: OBJECTID_1,HydroID,nzsegment,nzreach_rec1,Area

PHS On The Web (POTW) is a web-based, interactive mapping tool for citizens, landowners, local governments, developers, conservation groups and others to find basic information about known locations of Priority Habitats and Species (PHS) in Washington State. PHS is a source of best available science that can inform local planning activities, development projects, conservation strategies, incentive programs, and numerous other applications. The three GIS layers provided in this file geodatabase are the layers displayed in the POTW (Public) online map application. The three layers are scheduled to be updated on the first Monday of each month. These three GIS layers are: WDFWPHSPlusPublicLine, WDFWPHSPlusPublicPoint, and WDFWPHSPlusPublicPolygon. In these three layers, sensitive species are not shown as mapped (as a point, line, or polygon) but the locations are masked as a Section (one square mile), Quarter Township (nine square miles), or Township (thirty-six square miles) polygons.Sensitive species and habitat information are defined in WDFW Policy 5210. Priority habitats and species locations deemed sensitive by WDFW are not publicly displayed beyond a certain resolution (e.g., township or section) due to an increased risk of human interference. Sensitive data is exempt from public disclosure under the Public Records Act; this term is defined in RCW 42.56.430. Sensitive species are any wildlife species likely to become endangered or threatened; this term is defined in WAC 200-200-100. Qualifying landowners, university researchers, government agencies, and tribes may request PHS maps that contain this sensitive data.Since this GIS layer contains non-sensitive species information, it can be used without limitations, but please acknowledge the Washington Department of Fish and Wildlife (WDFW) as the source of this information. Please do not distribute this data, instead refer others to WDFW. If you have any questions about this layer, you can contact PHS at this email address: phsproducts@dfw.wa.gov with a subject line of the email being "POTW Public Dataset Question".Please note, although mapped PHS data is useful for determining the general extent of priority species or habitats, the department has not surveyed the entire state of Washington. PHS map data is meant to serve as a starting point to identify priority habitats and species. It is not meant to replace or preempt more detailed field-based, site-level mapping. Site-specific surveys are usually needed to rule out the presence of priority habitats or species. PHS maps do not provide an official agency determination of the potential impacts to fish and wildlife of a specific project.Additional ResourcesPHS On The Web Application: https://geodataservices.wdfw.wa.gov/hp/phs/PHS On the Web Map Service: https://geodataservices.wdfw.wa.gov/arcgis/rest/services/PHSOnTheWeb/PHSOnTheWebPublic/MapServer

This web map can also be accessed via the LINZ Storymap about NZ Key Datasets for Resilience and Climate Change https://storymaps.arcgis.com/stories/b4dd46f15cea4234a098b4c8caae5b3d The River Environment Classification (REC) is a database of catchment spatial attributes, summarised for every segment in New Zealand's network of rivers. The attributes were compiled for the purposes of river classification, while the river network description has been used to underpin models. Typically, models (e.g. CLUES and TopNet) would use the dendritic (branched) linkages of REC river segments to perform their calculations. Since its release and use over the last decade, some errors in the location and connectivity of these linkages have been identified. The current revision corrects those errors, and updates a number of spatial attributes with the latest data. REC2 provides a recut framework of rivers for modelling and classification. It is built on a newer version of the 30m digital elevation model, in which the original 20m contours were supplemented with, for example, more spot elevation data and a better coastline contour. Boundary errors were minimized by processing contiguous areas (such as the whole of the North Island) together, which wasn't possible when the REC was first created. Major updates include the revision of catchment land use information, by overlaying with land cover database (LCDB3, current as at 2008), and the update of river and rainfall statistics with data from 1960-2006. The river network and associated attributes have been assembled within an ArcGIS geodatabase. Topological connectivity has been established to allow upstream and downstream tracing within the network. REC2 can be downloaded as a zip file and used directly in ArcMap. Alternatively, the layers can be extracted as shape files. The three REC2 based layers contained within this web map consist of the following (metadata is contained in the Layers section below).NZ Large Catchments, are basically the local watersheds of the REC2V5 dissolved into large sea draining catchments.River Environment Classification REC2 V5 (as National and local rivers) NZ Rivers and Names is a cut down version of the REC2V5 with river and waterway names added where available.

Field Type Descriptions for all REC2 associated feature layers within this webmap.RivName The names for any waterway where available taken from original topo data ( only for the NZ Large Catchments and NZ River and Names layers)

Catarea Real Watershed area in m2 CUM_Area Real Area upstream of a reach (and including this reach area) in m2. Nzsegment Integer Reach identifier to be used with REC2 (supercedes nzreach in REC1).

Lengthdown Real The distance to coast from any reach to its outlet reach, where the river drains (m). Headwater Integer Number (0) denoting whether a stream is a “source” (headwater) stream. Non-zero for non-headwater streams.

Hydseq Integer A unique number denoting the hydrological processing order of a river segment relative to others in the network.

StreamOrder Integer A number describing the Strahler order a reach in a network of reaches.

euclid_dist Real The straight line distance of a reach from the reach “inlet” to its “outlet”. upElev Real Height (asl) of the upstream end of a reach section in a watershed (m). downElev Real Height (asl) of the downstream end of a reach section in a watershed (m).

upcoordX Real Easting of the upstream end of a river segment in m (NZTM2000). upcoordY Real Northing of the upstream end of a river segment in m (NZTM2000). downcoordX Real Easting of the downstream end of a river segment in m (NZTM2000).

downcoordY Real Northing of the downstream end of a river segment in m (NZTM2000). sinuosity Real Actual distance divided by the straight line distance giving the degree of curvature of the stream nzreach_re Integer The REC1 identifiying number for the corresponding\closest reach from REC1 (can be used to retrieve the REC management classes) headw_dist Integer Distance of the furthermost “source” or headwater reach from any reach (m). Shape_leng Real The length of the reach (vector) as calculated by ArcGIS. Segslpmean Real Mean segment slope along length of reach.

LID Integer Lake Identifier number(LID) of overlapping lake.

Reachtype

Integer A value of 2 is assigned if the segment is an outlet to the lake, otherwise 0 or null. nextdownid integer segment number of the most downstream reach

NIWA acknowledges funding from the MBIE SSIF towards the preparation of REC v2.5 River Environment Classification._Item Page Created: 2021-07-09 05:37 Item Page Last Modified: 2025-03-15 18:55Owner: steinmetzt_NIWANZ River Names (REC2)Item id: 502212e71bce4c029de8a82cd5bc6302NZ Regional Rivers (REC2)Item id: 502212e71bce4c029de8a82cd5bc6302NZ National Rivers (REC2)Item id: 3a4b6cc2c1c74fbb8ddbe25df28e410cNZ Large River CatchmentsItem id: 28d23ad94c2a4846b7634f4cdbba178f