Images were acquired from approximately 80 m above ground surface on the 12th of February 2021, using a Phantom 4 Advanced drone with an FC330 camera. The images are in file input_images.zip.

The mission planning software DJI GS Pro was used to automatically acquire images at suitable locations across the survey area to enable the reconstruction of a three dimensional model.

Images 422 to 531 were imported to the photogrammetry software Pix4D (version 4.6.4). The created Pix4D project is Station12Feb2021_limited.p4d, and the processing report is Station12Feb2021_limited_report.pdf.

Four three-dimensional ground control points were used to improve the positioning of the model. No two dimensional control points or check points were used.

These points were in ITRF 2000@2000 datum (UTM Zone 49S), with co-ordinates as per the table below:

Label, Type, X(m), Y(m), Z(m), Accuracy Horz(m), Accuracy Vert(M) BM05, 3D GCP, 478814.460, 2648561.910, 38.558, 0.050, 0.100 EW-05, 3D GCP, 478635.540, 2648617.260, 27.260, 0.050, 0.100 FuelFlange, 3D GCP, 478970.810, 2648642.250, 21.920, 0.050, 0.100 MeltbellFootingA, 3D GCP, 478680.270, 2648466.547, 35.850, 0.050, 0.100

BM-05 is a survey benchmark near the Casey flagpoles, see https://data.aad.gov.au/aadc/survey/display_station.cfm?station_id=600 EW-05 is a 44 gallon drum used as a groundwater extraction well by the remediation project Fuel Flange is the last fuel flange located on the elevated fuel line prior to the fuel line “dipping” under the wharf road. Meltbell footing A is a concrete footing for the Casey melt bell (surveyed in 2019/20).

No point cloud processing (e.g. removal of errant points) was done prior to orthomosaic and model generation.

The resulting orthomosaic (Station12Feb2021_limited_transparent_mosaic_group1.tif) has an average ground sampling distance of 2.9 cm, and covers an area of approximately 15.8 hectares, encompassing the majority of buildings along “main street” at Casey. The quarry, biopiles, helipad, and upper fuel farm area are all visible.

Contour lines were generated in Pix4D at 0.5 m intervals.

Due to the limited number of ground control points, and their imprecision, the estimated residual mean squared error across three dimensions is 0.17 m (17cm), and will be worse on the periphery of the imaged area.

The orthomosaic was exported from ArcGIS to a Google Earth file (CaseyStation Orthomosaic Feb 12 2021.kmz) using XTools Pro Version 17.2.

A map was created in ArcGIS showing the orthomosaic with a background showing contour lines obtained from the AADC data product windmill_is.mdb.

The map was exported in .jpg and .pdf format at 250 dpi. Casey Station Orthomosaic Feb 12 2021.pdf Casey Station Orthomosaic Feb 12 2021.jpg

The Pix4D folder structure has been copied across (with the exception of the temp folder) and is included in this dataset.

Pix4D Folder Structure:

Station12Feb2021_limited.zip 1_intitial • Contains Pix4D files created during the project • Contains the final processing report (as .pdf) 2_densification • Contains the 3D mesh as an .obj file • Contains the point cloud as a .LAS and .PLY file • Contains the point cloud as a .p4b file 3_dsm_ortho • Contains the digital surface model as a georeferenced .tif file • Contains the orthomosaic as a georeferenced .tif file

A text readable log file from the project processing is in the file Station12Feb2021_limited.log

A reverse-engineering of the methods and color palette used by renown Swiss relief painter Eduard Imhof, toward the goal of creating a digital homage for modern cartographers. Links are provided in this Cascade Story Map to an ArcGIS Pro style resource and project package. Cartographers are invited to get the scoop on the aesthetic technique then start cranking out glorious hillshade maps of their own.This story map provides links to an ArcGIS Pro project package with the requisite layers and style ready to go, just pan and zoom around!Happy Mountain Mapping! John Nelson

A 2D Hydraulic model (HEC-RAS) for below Tuttle Creek Reservoir at the confluence of the Kansas River and the Big Blue River near Manhattan, KS is presented. Model geometry is based on United States Geological Survey (USGS) 3DEP data (2015), with underwater bathymetry “burned” in using cross-sections sampled in the field in April of 2023. The model was calibrated based on water surface measured during data collection. The hydraulic simulations correspond to streamflows during which fish monitoring data were collected by researchers at Kansas State University (L. Rowley and K. Gido, to be published). Results from the hydraulic model, coupled with a sediment transport model, will be used to study fish and macroinvertabrate ecological response to streamflow. Methods The following is a summary of data utilized for developing a bathymetric terrain for 2D hydraulic modeling using HEC-RAS. Data used for model calibration and validation is also discussed.

Available Data Cross-section elevation data were collected by the United States Army Corps of Engineers (USACE) Kansas City District at approximately 200-foot to 1000-foot increments at the confluence of the Big Blue River and the Kansas River near Manhattan, Kansas. The following equipment was used by two complete surveying teams: • Ohmex SonarMite single beam echo sounder SFX @ 200khz, • Ohmex SonarMite single beam echo sounder DFX @ 28kHz & 200kHZ, • Trimble R12i 0096 & 0098, • Trimble R8 1984 & 6282

The cross-section elevation data were collected by boat and supplemented by hand-carried, pole-mounted Trimbles on April 10 to 14, 2023. The USGS gage on the Big Blue River near Manhattan, KS (06887000) had an average discharge of 425 cfs during the field collection time period (Figure 1). A USGS gage downstream of the confluence, Kansas River at Wamego, KS (06887500) shows an average discharge of 780 cfs at the same time period (Figure 2).

Figure 1 (Refer to supplemental information file). USGS gage Big Blue R NR Manhattan, KS – 06887000 discharge data for the week of April 11, 2023 – April 15, 2023. The average flow was taken as 425 cfs.

Figure 2 (Refer to supplemental information file). USGS gage Kansas River at Wamego, KS (06887500) discharge data for the week of April 11, 2023 – April 15, 2023. The average flow was taken as 780 cfs. Wamego, KS is downstream of the Big Blue River and Kansas River confluence and represents combined flow for both tributaries.

Figure 3 (Refer to supplemental information file). Map of bathymetric cross-sections collected in April 2023 near Manhattan, KS. Arrows show flow direction. Inset is the data collection location relative to the state of Kansas.

Terrain The field data collection featured 56 cross-sections. HEC-RAS 6.3.1 was utilized to create a bathymetric surface by interpolating 1-D cross-sections, while a 1-m resolution USGS 3DEP terrain (2015) was used for the floodplain and surrounding areas. A more recent USGS 3DEP (2018) data was available but featured higher stream flow than the 2015 data collection and therefore, more of the channel was submerged. Overall, the difference between 2015 and 2018 had a mean deviation of ~0.04 feet, with a majority of the differences in the channel ranging between +/-0.5 feet. Islands in this reach are unvegetated and prone to movement, and therefore the exact channel form is uncertain. However, it is assumed that relative island areas are consistent throughout the reach, and 2015 LiDAR was used to delineate the most island area as possible.

To build the bathymetric terrain, a similar process as what was discussed in Harris et al. (2023), field collected data were imported into ArcGIS Pro 3.0 as a point shapefile. To preserve georeferencing, the point shapefile was segmented into groups of 3-4 cross-sections and these cross-sections were interpolated into mini-surfaces using the Inverse Distance Weighted (IDW) spatial analysis tool. These mini-surfaces were brought into HEC-RAS and cross-sections were drawn to intersect with these field surveyed locations. The 1-D cross-sections were then used to create a TIFF for the entire channel area. The 1D interpolation captures the channel centerline between measured cross-sections but meanders and channel widening may not be covered by the interpolated channel. The channel raster was broken into its component objects or “exploded”, in ArcGIS Pro using the Raster to Point tool. The points were then interpolated using the Inverse-Distance-Weighted interpolation tool (IDW). This creates a terrain that covers meanders and channel expansion while maintaining fidelity to the original channel raster.

Areas where the terrain was inundated at the time of LiDAR data collection are “flat” and referred to as a hydro-flattened surface. The Slope tool in ArcMap was used to delineate these hydro-flattened areas and a shapefile tracing unsubmerged islands was used. The IDW surface was clipped to the hydro-flattened extents and then mosaicked with the original 3DEP terrain to create a seamless bathymetric and topographic surface.

The field data collected in April 2023 (Figure 3) required supplemental information to cover a fish monitoring instance upstream of the bridge at Pillsbury Drive/177. In September 2021, the USACE Kansas City District collected sediment samples with XY-georeference and depth measurements. The LiDAR hydro-flattened surface was used to estimate the energy grade slope from the new cross-section to the recent field monitoring extents. The model scenario or “plan” on the April 2023 extents was run at a similar flow as was occurring in September 2021. The combination of water surface elevation at that flow (780 cfs), the energy grade slope in the 3DEP data and field measured depth in 2021 were used to estimate the elevation at the channel bed.

Land Cover Land cover was delineated using the Multi-Resolution Land Characteristic (MRLC) Consortium’s 2019 National Land Cover Data (NLCD) (MRLC 2016). Fifteen types of landcover were identified for this study area by the NLCD: Hay-Pasture, Shrub-Scrub, Developed Low Intensity, Developed Medium Intensity, Cultivated Crops, Deciduous Forest, Herbaceous, Develop Open Space, Developed High Intensity, Woody Wetlands, Emergent Herbaceous Wetland, Open Water, Mixed Forest, Barren Land, and Evergreen Forest. Manning’s n values were selected based on a range of n values along with a “Suggested Initial n” provided by Krest Engineers (2021) (Table 1). Table 1. A table representing a range of Manning’s n values, a suggested Manning’s n value, and percent imperviousness for each NLCD land cover type. (Krest Engineers, 2021)

Model Settings The 2D HEC-RAS mesh was set to 40-feet square, with breaklines to orient cell edges along areas of steep elevation change or to support model convergence. Boundary conditions were placed at three locations in the 2D flow area: the inflow of the Big Blue River (boundary condition type: flow hydrograph), the upstream end of the Kanas River (flow hydrograph), and the downstream end of the Kanas River (normal depth). An energy grade slope was given as 0.0005 ft/ft for the Big Blue River and 0.0003 ft/ft for the Kansas River. Advanced time step control adjustments were implemented using Courant’s Criterion, with a minimum Courant of 0.75 and a maximum of 3.

Calibration The suggested value from Krest Engineers (2021) was the initial Manning’s n used for each land cover type (Table 1). The hydraulic model was then run, and the Manning’s n was changed to better conform to water surface elevations observed during field data collection. Flows corresponding to the field collection dates were 415 cfs for the Big Blue River and 360 cfs for the Kansas River. These streamflows were determined by cross-referencing the field collection dates (April 10 to 14, 2023) to continuous monitoring data available from USGS at gages Big Blue R NR Manhattan, KS (06887000) and Kansas R at Fort Riley, KS (06879100). The 2D model simulation results were compared to the field-measured water surface elevations at each channel cross-section with the ArcGIS Zonal Statistics as Table tool. Model improvement was determined by calculating the Root Mean Square Error (RMSE) of the simulated water surface elevation to the field observed water surface elevation, and the Manning’s n values resulting in the lowest error were selected. Following calibration, the model has overall RMSE of 0.29 ft for depth. The final Manning’s n values used for all the following simulations are included in Table 2.

Land Cover

Mannings n

Open Water

0.025

Emergent Herbaceous Wetlands

0.05

Woody Wetlands

0.045

Herbaceous

0.025

Mixed Forest

0.08

Evergreen Forest

0.08

Deciduous Forest

0.1

Scrub-Shrub

0.07

Hay-Pasture

0.025

Cultivated Crops

0.02

Baren Land

0.023

Developed, Open Space

0.03

Developed, Low Intensity

0.06

Developed, Medium Intensity

0.08

Developed, High Intensity

0.12

Table 2. The selected Manning’s n per Landcover classification after calibration

Simulations Apart from the calibration simulations, further simulations were conducted to match additional fish data collection from July 17 – 21, 2023 and October 2- 6, 2023. USGS gages, Big Blue R NR Manhattan, KS (06887000) and Kansas R at Fort Riley, KS (06879100), were used to find the discharge rates (in cfs) during those fish sampling periods. While discharge was consistent throughout the weeks for some gages (Figures 4 and 7), others showed differences greater than 10% or 100 cfs (Figures 5 and 6). The gages that showed significant differences were divided into two sub-simulations for the lower and higher flows during that week.

USGS Streamflow Data for July 17 - 21, 2023

HEC RAS Scenario Description River Simulation Flow (cfs)

July_KS_LF July lower flow Big

The documentation below is in reference to this items placement in the NM Supply Chain Data Hub. The documentation is of use to understanding the source of this item, and how to reproduce it for updatesTitle: Soil Survey Geographic Database (SSURGO) DownloaderItem Type: Web Mapping Application URLSummary: Download ready-to-use project packages with over 170 attributes derived from the SSURGO (Soil Survey Geographic Database) dataset.Notes: Prepared by: Uploaded by EMcRae_NMCDCSource: https://nmcdc.maps.arcgis.com/home/item.html?id=cdc49bd63ea54dd2977f3f2853e07fff link to Esri web mapping applicationFeature Service: https://nmcdc.maps.arcgis.com/home/item.html?id=305ef916da574a71877edb15c3f47f08#overviewUID: 26Data Requested: Ag CensusMethod of Acquisition: Esri web mapDate Acquired: 6/16/22Priority rank as Identified in 2022 (scale of 1 being the highest priority, to 11 being the lowest priority): 8Tags: PENDINGDOCUMENTATION FROM DATA SOURCE URL: This application provides quick access to ready-to-use project packages filled with useful soil data derived from the SSURGO dataset.To use this application, navigate to your study area and click the map. A pop-up window will open. Click download and the project package will be copied to your computer. Double click the downloaded package to open it in ArcGIS Pro. Alt + click on the layer in the table of contents to zoom to the subbasin.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.Dataset SummaryThe map packages were created from the October 2021 SSURGO snapshot. The dataset covers the 48 contiguous United States plus Hawaii and portions of Alaska. Map packages are available for Puerto Rico and the US Virgin Islands. A project package for US Island Territories and associated states of the Pacific Ocean can be downloaded by clicking one of the included areas in the map. The Pacific Project Package includes: Guam, the Marshall Islands, the Northern Marianas Islands, Palau, the Federated States of Micronesia, and American Samoa.Not all areas within SSURGO have completed soil surveys and many attributes have areas with no data. The soil data in the packages is also available as a feature layer in the ArcGIS Living Atlas of the World.AttributesKey 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 SymbolMap 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 RatingLegend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project ScaleSurvey 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 VersionMap 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 Map Unit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Map Unit 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 AverageComponent 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 KeyComponent 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 - High ValueTotal Subsidence - Low ValueTotal Subsidence - Representative ValueTotal Subsidence - High ValueCrop Productivity IndexEsri SymbologyThis field was created to provide symbology based on the Taxonomic Order field (taxorder). Because some map units have a null value for soil order, a

Geospatial (GIS) Data on glacial topography derived from LiDAR elevation data. Contains GIS vector data (in ESRI file geodatabases) that characterize the geometry ofglacial landforms created during the last glaciation (12,000 to 14,000 years ago), such as moraines, ice walled lake plains, doubly breached doughnuts and eskers and is supplementedby online LiDAR derived elevation data. For easy data access, an ArcGIS Pro 3.0 project (aprx) file is provided.

Spatial data layers of stream crossing point locations, cross-section polyline, centerline polyline, and bank polyline shapefiles have been developed for selected stream crossings in the Squannacook River basin, Massachusetts. The spatial data and calculated attribute values are model input data for U.S. Army Corps of Engineer’s Hydrologic Engineering Center’s River Analysis System (HEC-RAS) hydraulic models. The stream crossing point locations were derived from the North Atlantic Aquatic Connectivity Collaboration (NAACC) database. The stream channel cross-sections, centerlines, and bank polylines were derived using automated methods in a Geographic Information System (GIS) using ArcGIS Pro and Python programming language. The polyline shapefiles are Z-enabled and have elevation data derived from Light Detection and Ranging (lidar) Digital Elevation Models (DEM) for Z-coordinate vertex values in units of feet. The polyline shapefiles are also M-enabled and have profile stationing values for the M-coordinate vertex values in units of feet. The automated GIS processes delineated a series of stream channel cross-sections along lidar-derived stream centerlines and have stream channel bathymetry estimated from Massachusetts bankfull channel geometry equations (Bent and Waite, 2013). The bankfull equations were also used to derive stream bank polylines. This data release contains the following shapefiles in the Spatial_Data_Layers.zip file: 1. Stream_Crossing_Locations.shp - Esri point shapefile derived from the NAACC stream crossing database. 2. Stream_Crossing_Watersheds.shp - Esri polygon shapefile of lidar-derived watershed boundaries that estimate the upstream drainage area for each stream crossing _location. 3. Model_Cross_Sections.shp - Esri Z- and M-enabled polyline shapefile of the cross-section data used for hydraulic model input. 4. Model_Flowpaths.shp - Esri Z- and M-enabled polyline shapefile of the stream centerline and stream bank line data used for hydraulic model input. References: Bent, G.C., and Waite, A.M., 2013, Equations for estimating bankfull channel geometry and discharge for streams in Massachusetts: U.S. Geological Survey Scientific Investigations Report 2013–5155, 62 p., http://dx.doi.org/10.3133/sir20135155

This layer provides generalized boundaries for the 50 States and the District of Columbia, developed by Esri from US Census Bureau public domain sources and updated as boundaries change.Attribute fields include 2020 total population from the US Census PL94 data.This ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, StoryMaps, custom apps, and mobile apps. The data can also be exported for offline workflows. Cite the 'U.S. Census Bureau' when using this data.

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 thegSSURGO 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 Summary Phenomenon 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 Service Update Frequency:AnnualPublication Date:December 2024 What can you do with this layer?Feature 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.ArcGIS Online 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-upArcGIS Pro Add 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 - Presence Rating 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 -

Soil is essential to human survival. We rely on it for the production of food, fibre, timber and energy crops. Together with climate, the soil determines which crops can be grown, where and how much they will yield. In addition to supporting our agricultural needs, we rely on the soil to regulate the flow of rainwater and to act as a filter for drinking water. With such a tremendously important role, it is imperative that we manage our soils for their long-term productivity, sustainability and health.

The first step in sustainable soil management is ensuring that the soil will support the land use activity. For example, only the better agricultural soils in Manitoba will support grain and vegetable production, while more marginal agricultural soils will support forage and pasture-based production. For this reason, agricultural development should only occur in areas where the soil resource will support the agricultural activity. The only way to do this is to understand the soil resource that is available. Soil survey information is the key to understanding the soil resource.

Soil survey is an inventory of the properties of the soil (such as texture, internal drainage, parent material, depth to groundwater, topography, degree of erosion, stoniness, pH and salinity) and their spatial distribution over a landscape. Soils are grouped into similar types and their boundaries are delineated on a map. Each soil type has a unique set of physical, chemical and mineralogical characteristics and has similar reactions to use and management. The information assembled in a soil survey can be used to predict or estimate the potentials and limitations of the soils’ behaviour under different uses. As such, soil surveys can be used to plan the development of new lands or to evaluate the conversion of land to new uses. Soil surveys also provide insight into the kind and intensity of land management that will be needed.

The survey scale of soils data for Manitoba ranges from 1:5,000 to 1:126,720, as identified in the 'SCALE' column.1:5,000. The survey objective at this scale is to collect high precision field scale data and it is mostly used in research plots and other highly intensive areas. It is also applicable to agricultural production and planning such as precision farming, agriculture capability, engineering, recreation, potato/irrigation suitability and productivity indices. Profile descriptions and samples are collected for all soils. At least one soil inspection exists per delineation and the minimum size delineation is 0.25 acres. The soil taxonomy is generally Phases of Soil Series. The mapping scale is 1:5,000 or 12.7 in/ mile.

This file also contains soils data that has been collected in Manitoba at a survey intensity level of the second order. This includes data collected at a scale of 1:20,000. The survey objective at this scale is to collect field scale data and it is mostly used in agricultural production and planning such as precision farming, agriculture capability, engineering, recreation, potato/irrigation suitability and productivity indices. Soil pits are generally about 200 metres apart and are dug along transects which are about 500 metres apart. This translates to about 32 inspections sites per section (640 acres). The soils in each delineation are identified by field observations and remotely sensed data. Boundaries are verified at closely spaced intervals. Profile descriptions are collected for all major named soils and 10 inspection sites/section and 2 to 3 horizons per site require lab analyses. At least one soil inspection exists in over 90% of delineations and the minimum size delineation is generally about 4 acres at 1:20,000. The soil taxonomy is generally Phases of Soil Series. The mapping scale is 1:20,000 or 3.2 inch/ mile.

This file also contains data that has been collected at the third order. This includes scales of 1:40,000 and 1:50,000. The survey objective at this scale is to collect field scale or regional data. If the topography is relatively uniform, appropriate interpretations include agriculture capability, engineering, recreation, potato/irrigation suitability and productivity indices. Soil pits are generally dug adjacent to section perimeters. This translates to about 16 inspection sites per section (640 acres). Soil boundaries are plotted by observation and remote sensed data. Profile descriptions exist for all major named soils and 2 inspection sites/section and 2 to 3 horizons per site require lab analyses. At least one soil inspection exists in 60-80% of delineations and the minimum size delineation is generally in the 10 to 20 acre range. The soil taxonomy is generally Series or Phases of Soil Series. The mapping scale is 1:40,000 or 2 inch/ mile; 1:50,000 or 1.5 inch/mile.

This file also contains soils data that has been collected at a survey intensity level of the fourth order. This includes scales of 1:63,360, 1:100,000, 1:125,000, and 1:126,720. The survey objective is to collect provincial data and to provide general soil information about land management and land use. The number of soil pits dug averaged to about 6 inspections per section (640 acres). Soil boundaries are plotted by interpretation of remotely sensed data and few inspections exist. Profile descriptions are collected for all major named soils. At least one soil inspection exists in 30-60% of delineations and the minimum size delineation is 40 acres (1:63,360), 100 acres (1:100,000), 156 acres (126,700) and 623 acres (250,000). The soil taxonomy is generally phases of Subgroup or Association.

As of 2022, soil survey field work and reports are still currently being collected in certain areas where detailed information does not exist. This file will be updated as more information becomes available. Typically, this is conducted on an rural municipality basis.

In some areas of Manitoba, more detailed and historical information exists than what is contained in this file. However, at this time, some of this information is only available in a hard copy format. This file will be updated as more of this information is transferred into a GIS format.

This file has an organizational framework similar to the original SoilAID digital files and a portion of this geographic extent was originally available on the Manitoba Land Initiative (MLI) website.

Domains and coded values have also been integrated into the geodatabase files. This allows the user to view attribute information in either an abbreviated or a more descriptive manner. Choosing to display the description of the coded values allows the user to view the expanded information associated with the attribute value (reducing the need to constantly refer to the descriptions within the metadata). To change these settings in ArcCatalog, go to Customize --> ArcCatalog Options --> Tables tab --> check or uncheck 'Display coded value domain and subtype descriptions'. To change these settings in ArcMap, go to Customize --> ArcMapOptions --> Tables tab --> check or uncheck 'Display coded value domain and subtype descriptions'. This setting can also be changed by opening the attribute table, then Table Options (top left) --> Appearance --> check or uncheck 'Display coded value domain and subtype descriptions'. The file also contains field aliases, which can also be turned on or off under Table Options.

The file - "Manitoba Municipal Boundaries" - from Manitoba Community Planning Services was used as one of the base administrative references for the soil polygon layer.

Also used as references were the hydrological features mapped in the 1:20,000 and 1:50,000 NTS topographical layers (National Topographic System of Canada). Typically this would relate to larger hydrological features such as those designated as perennial lakes and perennial rivers.

This same capability is available in ArcGIS Pro.

For more info:

https://www.gov.mb.ca/agriculture/soil/soil-survey/importance-of-soil-survey-mb.html#

River flood hazard zones were developed by 2 different external expert consultants between 2016 and 2021. The layers are derived by advanced models using empirical calculations. Two different models were used to construct the river flood layers: TUFLOW (Water Technology, 2021), InfoWorks (URS, 2016). The reports detailing the methodologies, and risk assessment on the Priority Rivers, can be accessed from the NRC website.Changes made to the 50yr Flood Layer (Regionwide Model)In 111 Black Swamp Road, Mangawhai, Northland, 0975 Area the 50yr Flood was missing The missing area data was provided by Sher (Rivers and Natural Hazard Engineer)Location of the data: W:\ArcGIS Pro\Environmental Services\Rivers and Natural Hazards\RIVERS\Regionwide Model\PROJECTS\03 Regionwide Project Final\Source Data\2021-04-16_FloodMappingResults\WaterTechnology_NRC_RoG_FloodExtents_RiverineOnly.gdb\M08_050yr_FloodExtent 111 Black Swamp Road, Mangawhai, Northland, 0975, NZLThe data was smoothed with the below mentioned details Smoothing Type: PAEK Smoothing Tolerance: 50mThe missing area was extracted from the smoothed area and was appended to the original data brought from the sde Original 50yr data name in sde: nrc_GISADMIN_RFHZ_50yearExtent_RegionwideModels Update 50yr data name in sde : nrc_GISADMIN_RFHZ_50yearExtent_RegionwideModels_Updated2022 This 50yr layer has the flood for property at 111 Black Swamp Road, Mangawhai, Northland, 0975, NZL (Refer Ticket: 18141 for the process)Note: This layer nrc_GISADMIN_RFHZ_50yearExtent_RegionwideModels_Updated2022 has been used in 2 places1. Northland River Flood Hazard Zones - Updated (21st Oct 2022) - Map Image ServiceURL: https://nrcmaps.nrc.govt.nz/imagery/rest/services/Northland_River_Flood_Hazard_Zone_Updated_21st_Oct_2022/MapServerPublished By : Divya S Published on: 21st Oct 20222. Published as Tile layer and has been added to the Natural Hazard ViewerAWS: AGOL Tile ServiceMap Name: River Flood Hazard Zones (Updated - 50yr and 100yr Regionewide - Published Individually) Published By: Divya S Date: 27th Oct 2022

This map package includes the official Tribal areas that NTIA recognizes for their grant programs. The map package includes the following layers. Alaska Native Villages - this layer represents Alaska Native Villages and is created by Census. The layer was downloaded on Jan. 28, 2025, from here: TIGER/Line® Shapefiles.Native Hawaiian Areas - this layer represents Native Hawaiian Areas and is created by Census. The layer was downloaded on Jan. 28, 2025, from here: TIGER/Line® Shapefiles and has been filtered to only include Native Hawaiian Areas. BIA AIAN National LAR - this layer represents American Indian Lands and is created by the BIA. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025. The layer was filtered to only include lands across the continental U.S. BIA AIAN LAR Supplemental - this layer is a supplemental dataset to the LAR. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025.BIA AIAN Tribal Statistical Areas - this layer represents Tribal Statistical Areas located in Oklahoma. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025.This map package was created on Jan. 28, 2025 and was created using ArcGIS Pro 3.4.0. If you have any questions regarding the map package please e-mail NTIAanalytics@ntia.gov.ResourcesCensus DataBIA Open DataBIA Data DisclaimerBy using this product, the user agrees to the below terms and conditions:No warranty is made by the Bureau of Indian Affairs (BIA) for the use of the data for purposes not intended by the BIA. This GIS Dataset may contain errors. There is no impact on the legal status of the land areas depicted herein and no impact on land ownership. No legal inference can or should be made from the information in this GIS Dataset. The GIS Dataset is prepared strictly for illustrative and reference purposes only and should not be used, and is not intended for legal, survey, engineering or navigation purposes. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from source documents and/or the translation of information from source documents to the systems of record continue to exist. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.Census Use RestraintsThe TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions. Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.

Important Note: This item is in mature support as of March 2025 and will be retired in December 2027. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. This application provides quick access to ready-to-use project packages filled with useful soil data derived from the SSURGO dataset.To use this application, navigate to your study area and click the map. A pop-up window will open. Click download and the project package will be copied to your computer. Double click the downloaded package to open it in ArcGIS Pro. Alt + click on the layer in the table of contents to zoom to the subbasin.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.Dataset SummaryThe map packages were created from the October 2023 SSURGO snapshot. The dataset covers the 48 contiguous United States plus Hawaii and portions of Alaska. Map packages are available for Puerto Rico and the US Virgin Islands. A project package for US Island Territories and associated states of the Pacific Ocean can be downloaded by clicking one of the included areas in the map. The Pacific Project Package includes: Guam, the Marshall Islands, the Northern Marianas Islands, Palau, the Federated States of Micronesia, and American Samoa.Not all areas within SSURGO have completed soil surveys and many attributes have areas with no data. The soil data in the packages is also available as a feature layer in the ArcGIS Living Atlas of the World.AttributesKey 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 SymbolMap 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 RatingLegend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project ScaleSurvey 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 VersionMap 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 Map Unit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Map Unit 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 AverageComponent 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 KeyComponent 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 - High ValueTotal Subsidence - Low ValueTotal Subsidence - Representative ValueTotal Subsidence - High ValueCrop Productivity IndexEsri SymbologyThis field was created to provide symbology based on the Taxonomic Order field (taxorder). Because some map units have a null value for soil order, a custom script was used to populate this field using the Component Name (compname) and Map Unit Name (muname) fields. This field was created using the dominant soil order of each map unit.Esri SymbologyHorizon TableEach map unit polygon has one or more components and each component has one or more layers known as horizons. To incorporate this field from the Horizon table into the attributes for this layer, a custom script was used to first calculate the mean value weighted by thickness of the horizon for each component and then a mean value of components weighted by the Component Percentage Representative Value field for each map unit. K-Factor Rock FreeEsri Soil OrderThese fields were calculated from the Component table using a

This downloadable zip file contains an ESRI File Geodatabase (FGDB) that is compatible with most versions of ArcGIS Pro, ArcMap, and AutoCAD Map 3D or Civil 3D. To view the geodatabase’s contents, please download the zip file to a local directory and extract its contents. This zipped geodatabase will require approximately 1.57 GB of disc space (1.73 GB extracted). Due to its size, the zip file may take some time to download. The geodatabase in the download includes the following layers:2 foot contours, Spot Elevations, Breaklines 2015 LiDAR derived 2ft topographic contours for Tallahassee and Leon County, Florida. Topographic contours re-projected from NAD83 State Plane to Web Mercator. Source data vertical datum NAVD88.TLCGIS regularly uses digital orthophotos and planimetric/hydrographic/topographic data to support regulatory functions, land management and acquisition, planning, engineering and habitat restoration projects. This dataset is part of a regularly scheduled update of LiDAR and digital orthophotography products. The dataset was created from source imagery acquired by a Trimble TAC80 natural color digital camera and LAS data acquired by a Optech ALTM HA500 (Pegasus) LIDAR sensor from January 18, 2015 to February 5, 2015.

This downloadable zip file contains an ESRI File Geodatabase that is compatible with most versions of ArcGIS Pro, ArcMap, and AutoCAD Map 3D or Civil 3D. To view the geodatabase’s contents, please download the zip file to a local directory and extract its contents.This content in this file geodatabase consist of planimetric layers identifiable in the orthoimagery collected for Leon County, FL in January, 2021. TLCGIS regularly uses digital orthophotos and planimetric/hydrographic/topographic data to support regulatory functions, land management and acquisition, planning, engineering and habitat restoration projects.This dataset is part of a regularly scheduled update of LiDAR and digital orthophotography products. The dataset was created from source imagery acquired by a Leica ADS100 multispectral aerial mapping camera from January 5-18, 2021. Planimetric Layers:BridgesBuildings - Buildings feature class contains all buildings 100 square feet or greater that are visible in the 2021 orthoimagery. Hydro LinesHydro PolygonsImperv - Impervious Surface includes Airport, Building, Landscape Island, Paved Driveway, Paved Island, Paved Parking, Paved Road, Paved Road Over Bridge, Ruin, Sidewalk, Sidewalk Over Sidewalk, Tennis Court, Unfinished Building, Unpaved Driveway, Unpaved Parking, Unpaved Road, and WaterbodyImpervHydroProjectBoundaryRdedge - Road edges were extracted from the impervious surfaces data from 2021 using paved roads, unpaved roads, paved driveways, and unpaved driveways.

Bowden Harbour Jamaica Elevation/Bathymetry grid tile service.Produced from ESA’s Sentinel-2 A/B imagery, 10 meter resolution Satellite Derive Bathymetry (SDB) is a highly accurate, extremely cost effective bathymetry product that can be produced in clear shallow water regions. The surface in this web scene was calibrated and validated using nautical charts as a survey planning surface to demonstrate shoal points and "no-go" areas.TCarta is a leading global provider of innovative hydrospatial products and Earth observation analysis services. TCarta GIS professionals, hydrographers, and developers provide solutions for onshore and offshore geospatial applications from engineering to environmental monitoring and beyond.TCarta’s primary focus is on providing affordability and accessibility of data and analytics utilizing cutting edge technology and approaches to best serve our clients where traditional methods fail with proven integrity of services and professional practices in a changing and dynamic world.USES: Satellite Derived Bathymetry (SDB) is a lower cost alternative to marine surveys and much higher resolution than ETOPO and GEBCO datasets. Coastal Engineering: Floating Solar Facilities: Suitability Analysis - Location siting using modern and accurate bathymetryWave modeling for construction planningMooring design & Cable routing to shore Offshore Wind Farms:Planning and AppraisalEnvironmental Impact assessmentsMooring design & Cable routingSite characterization Fiber Optic Cable Route Planning:Protecting marine life sanctuariesDecrease distance Aquaculture:Site selectionMonitoringFlow prediction Dredging:Measuring materialMonitoring Water Quality Monitoring:Chlorophyll IndexSediment flowNatural Disasters:Inundation modellingEnvironmental Compliance monitoring.TOOLS: ArcGIS PRO add-in and toolboxDELIVERABLES: GIS ready raster and vector formats, typically as GeoTiff, ASCII data with xyzu(where u represents Uncertainty of Z value) files in map projection coordinates (WGS84) with metadata. Other formats are available upon request like geodatabases, KML/KMZ, HDF, NetCDF

This application provides quick access to ready-to-use project packages filled with useful soil data derived from the SSURGO dataset.To use this application, navigate to your study area and click the map. A pop-up window will open. Click download and the project package will be copied to your computer. Double click the downloaded package to open it in ArcGIS Pro. Alt + click on the layer in the table of contents to zoom to the subbasin.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.Dataset SummaryPhenomenon Mapped: Ready-to-use project packages with over 170 attributes derived from the SSURGO dataset, split up by HUC8s. Geographic Extent: The dataset covers the 48 contiguous United States plus Hawaii and portions of Alaska. Map packages are available for Puerto Rico and the US Virgin Islands. A project package for US Island Territories and associated states of the Pacific Ocean can be downloaded by clicking one of the included areas in the map. The Pacific Project Package includes: Guam, the Marshall Islands, the Northern Marianas Islands, Palau, the Federated States of Micronesia, and American Samoa.Source: Natural Resources Conservation ServiceUpdate Frequency: AnnualPublication Date: December 2024Link to source metadata*Not all areas within SSURGO have completed soil surveys and many attributes have areas with no data.The soil data in the packages is also available as a feature layer in the ArcGIS Living Atlas of the World.AttributesKey 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 SymbolMap 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 RatingLegend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project ScaleSurvey 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 VersionMap 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 Map Unit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Map Unit 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 AverageComponent 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 KeyComponent 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 - High ValueTotal Subsidence - Low ValueTotal Subsidence - Representative ValueTotal Subsidence - High ValueCrop Productivity IndexEsri SymbologyThis field was created to provide symbology based on the Taxonomic Order field (taxorder). Because some map units have a null value for soil order, a custom script was used to populate this field using the Component Name (compname) and Map Unit Name (muname) fields. This field was created using the dominant soil order of each map unit.Esri SymbologyHorizon TableEach map unit polygon has one or more components and each component has one or more layers known as horizons. To incorporate this field from the Horizon table into the attributes for this layer, a custom script was used to first calculate the mean value weighted by thickness of the horizon for each component and then a mean value of components weighted by the Component Percentage Representative Value field for each map unit. K-Factor Rock FreeEsri Soil OrderThese fields were calculated from the Component table using a model that included the Pivot