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

The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Coordinate System: Web Mercator Auxiliary Sphere Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American Samoa Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Resolution/Tolerance: 1 meter/2 meters Number of Features: 3,035,617 flowlines, 473,936 waterbodies, 16,658 sinksFeature Request Limit: 5,000Source: EPA and USGSPublication Date: March 13, 2019ArcGIS Server URL: https://services.arcgis.com/P3ePLMYs2RVChkJx/arcgis/rest/services/NHDPlusV21/FeatureServerPrior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.What can you do with this Feature 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 OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. 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. 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.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map. Use 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 the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.

The Minnesota DNR Toolbox provides a number of convenience geoprocessing tools used regularly by MNDNR staff. Many of these may be useful to the wider public. However, some tools may rely on data that is not available outside of the DNR.

Toolsets included in MNDNR Tools:
- Analysis Tools
- Conversion Tools
- General Tools
- LiDAR and DEM Tools
- Sampling Tools

The application download includes a comprehensive help document, which you can also access separately here: ArcGISPro_MNDNR_Toolbox_Pro_User_Guide.pdf

These toolboxes are provided free of charge and are not warrantied for any specific use. We do not provide support or assistance in downloading or using these tools. We do, however, strive to produce high-quality tools and appreciate comments you have about them.

The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesGeographic Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSUpdate Frequency: AnnualPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not. Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.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 OnlineAdd this layer to a map in the map viewer. 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. 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.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use 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 the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually. The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2025 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on September 2025 from data collected in 2024-2025. Data was processed using Python scripts and ArcGIS Pro for standardization and integration of the data. To learn more about Parcel and CAMA in CT visit our Parcels Page in the Geodata Portal.Coordinate system: This dataset is provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection as it was for 2024. Prior versions were provided at WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Ownership Suppression: The updated dataset includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name was replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with fully suppressed ownership data, please note that no "Suppression" field was included in the submission to confirm these details and this labeling approach was implemented as the solution.New Data Fields:The new dataset introduces the “Property Zip” and “Mailing Zip” fields, which will display the zip codes for the owner and property.Service URL:In 2024, we implemented a stable URL to maintain public access to the most up-to-date data layer. Users are strongly encouraged to transition to the new service as soon as possible to ensure uninterrupted workflows. This URL will remain persistent, providing long-term stability for your applications and integrations. Once you’ve transitioned to the new service, no further URL changes will be necessary.CAMA Notes:The CAMA underwent several steps to standardize and consolidate the information. Python scripts were used to concatenate fields and create a unique identifier for each entry. The resulting dataset contains 1,354,720 entries and information on property assessments and other relevant attributes.CAMA was provided by the towns.Spatial Data Notes:Data processing involved merging the parcels from different municipalities using ArcGIS Pro and Python. The resulting dataset contains 1,282,833 parcels.No alteration has been made to the spatial geometry of the data.Fields that are associated with CAMA data were provided by towns.The data fields that have information from the CAMA were sourced from the towns’ CAMA data.If no field for the parcels was provided for linking back to the CAMA by the town a new field within the original data was selected if it had a match rate above 50%, that joined back to the CAMA.Linking fields were renamed to "Link".All linking fields had a census town code added to the beginning of the value to create a unique identifier per town.Any field that was not town name, Location, Editor, Edit Date, or a field associated back to the CAMA, was not used in the creation of this Dataset.Only the fields related to town name, location, editor, edit date, and link fields associated with the towns’ CAMA were included in the creation of this dataset. Any other field provided in the original data was deleted or not used.Field names for town (Muni, Municipality) were renamed to "Town Name".Attributes included in the data: Town Name OwnerCo-OwnerLinkEditorEdit DateCollection year – year the parcels were submittedLocationProperty ZipMailing AddressMailing CityMailing StateMailing ZipAssessed TotalAssessed LandAssessed BuildingPre-Year Assessed Total Appraised LandAppraised BuildingAppraised OutbuildingConditionModelValuationZoneState UseState Use DescriptionLand Acre Living AreaEffective AreaTotal roomsNumber of bedroomsNumber of BathsNumber of Half-BathsSale PriceSale DateQualifiedOccupancyPrior Sale PricePrior Sale DatePrior Book and PagePlanning RegionFIPS Code *Please note that not all parcels have a link to a CAMA entry.*If any discrepancies are discovered within the data, whether pertaining to geographical inaccuracies or attribute inaccuracy, please directly contact the respective municipalities to request any necessary amendmentsAdditional information about the specifics of data availability and compliance will be coming soon.If you need a WFS service for use in specific applications : Please Click HereContact: opm.giso@ct.gov

This is a dataset of georeferenced 1917 Sanborn Fire Insurance maps of Knoxville TN, including individual sheets, a sheet index, a seamless mosaic, and a map key. Digital images of the data sheets were downloaded from the University of Tennessee Library https://digital.lib.utk.edu/collections/sanbornmapcollection. Multi-part sheets were clipped into pieces for georeferencing. Chris DeRolph georeferenced each sheet and piece, where possible. There were a few outlying images that were unable to be georeferenced due to lack of recognizable common features between the sheets and reference maps/imagery in the sheet vicinity. The sheet index shapefile includes a field with a hyperlink to the UTK library download page for the sheet. The seamless mosaic was created using the Mosaic to New Raster tool in ArcGIS Pro with all georeferenced sheets/pieces as inputs and the Minimum Mosaic Operator. No attempt was made prior to the mosaicking process to remove sheet numbers, scale bars, north arrows, overlapping labels/annotation, etc. Viewing individual sheets will provide the cleanest look at an area, while the seamless mosaic provides the most comprehensive view of the city at the time the maps were created.

Retirement Notice: This item is in mature support as of February 2023 and will be retired in December 2025. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version.This layer displays change in pixels of the Sentinel-2 10m Land Use/Land Cover product developed by Esri, Impact Observatory, and Microsoft. Available years to compare with 2021 are 2018, 2019 and 2020. By default, the layer shows all comparisons together, in effect showing what changed 2018-2021. But the layer may be changed to show one of three specific pairs of years, 2018-2021, 2019-2021, or 2020-2021.Showing just one pair of years in ArcGIS Online Map Viewer To show just one pair of years in ArcGIS Online Map viewer, create a filter. 1. Click the filter button. 2. Next, click add expression. 3. In the expression dialogue, specify a pair of years with the ProductName attribute. Use the following example in your expression dialogue to show only places that changed between 2020 and 2021:ProductNameis2020-2021 By default, places that do not change appear as a transparent symbol in ArcGIS Pro. But in ArcGIS Online Map Viewer, a transparent symbol may need to be set for these places after a filter is chosen. To do this: 4. Click the styles button.5. Under unique values click style options. 6. Click the symbol next to No Change at the bottom of the legend. 7. Click the slider next to "enable fill" to turn the symbol off. Showing just one pair of years in ArcGIS Pro To show just one pair of years in ArcGIS Pro, choose one of the layer's processing templates to single out a particular pair of years. The processing template applies a definition query that works in ArcGIS Pro. 1. To choose a processing template, right click the layer in the table of contents for ArcGIS Pro and choose properties. 2. In the dialogue that comes up, choose the tab that says processing templates. 3. On the right where it says processing template, choose the pair of years you would like to display. The processing template will stay applied for any analysis you may want to perform as well. How the change layer was created, combining LULC classes from two yearsImpact Observatory, Esri, and Microsoft used artificial intelligence to classify the world in 10 Land Use/Land Cover (LULC) classes for the years 2017-2021. Mosaics serve the following sets of change rasters in a single global layer: Change between 2018 and 2021Change between 2019 and 2021Change between 2020 and 2021To make this change layer, Esri used an arithmetic operation combining the cells from a source year and 2021 to make a change index value. ((from year * 16) + to year) In the example of the change between 2020 and 2021, the from year (2020) was multiplied by 16, then added to the to year (2021). Then the combined number is served as an index in an 8 bit unsigned mosaic with an attribute table which describes what changed or did not change in that timeframe. Variable mapped: Change in land cover between 2018, 2019, or 2020 and 2021 Data Projection: Universal Transverse Mercator (UTM)Mosaic Projection: WGS84Extent: GlobalSource imagery: Sentinel-2Cell Size: 10m (0.00008983152098239751 degrees)Type: ThematicSource: Esri Inc.Publication date: January 2022 What can you do with this layer?Global LULC maps provide information on conservation planning, food security, and hydrologic modeling, among other things. This dataset can be used to visualize land cover anywhere on Earth. This layer can also be used in analyses that require land cover input. For example, the Zonal Statistics tools allow a user to understand the composition of a specified area by reporting the total estimates for each of the classes. Land Cover processingThis map was produced by a deep learning model trained using over 5 billion hand-labeled Sentinel-2 pixels, sampled from over 20,000 sites distributed across all major biomes of the world. The underlying deep learning model uses 6 bands of Sentinel-2 surface reflectance data: visible blue, green, red, near infrared, and two shortwave infrared bands. To create the final map, the model is run on multiple dates of imagery throughout the year, and the outputs are composited into a final representative map. Processing platformSentinel-2 L2A/B data was accessed via Microsoft’s Planetary Computer and scaled using Microsoft Azure Batch. Class definitions1. WaterAreas where water was predominantly present throughout the year; may not cover areas with sporadic or ephemeral water; contains little to no sparse vegetation, no rock outcrop nor built up features like docks; examples: rivers, ponds, lakes, oceans, flooded salt plains.2. TreesAny significant clustering of tall (~15-m or higher) dense vegetation, typically with a closed or dense canopy; examples: wooded vegetation, clusters of dense tall vegetation within savannas, plantations, swamp or mangroves (dense/tall vegetation with ephemeral water or canopy too thick to detect water underneath).4. Flooded vegetationAreas of any type of vegetation with obvious intermixing of water throughout a majority of the year; seasonally flooded area that is a mix of grass/shrub/trees/bare ground; examples: flooded mangroves, emergent vegetation, rice paddies and other heavily irrigated and inundated agriculture.5. CropsHuman planted/plotted cereals, grasses, and crops not at tree height; examples: corn, wheat, soy, fallow plots of structured land.7. Built AreaHuman made structures; major road and rail networks; large homogenous impervious surfaces including parking structures, office buildings and residential housing; examples: houses, dense villages / towns / cities, paved roads, asphalt.8. Bare groundAreas of rock or soil with very sparse to no vegetation for the entire year; large areas of sand and deserts with no to little vegetation; examples: exposed rock or soil, desert and sand dunes, dry salt flats/pans, dried lake beds, mines.9. Snow/IceLarge homogenous areas of permanent snow or ice, typically only in mountain areas or highest latitudes; examples: glaciers, permanent snowpack, snow fields. 10. CloudsNo land cover information due to persistent cloud cover.11. Rangeland Open areas covered in homogenous grasses with little to no taller vegetation; wild cereals and grasses with no obvious human plotting (i.e., not a plotted field); examples: natural meadows and fields with sparse to no tree cover, open savanna with few to no trees, parks/golf courses/lawns, pastures. Mix of small clusters of plants or single plants dispersed on a landscape that shows exposed soil or rock; scrub-filled clearings within dense forests that are clearly not taller than trees; examples: moderate to sparse cover of bushes, shrubs and tufts of grass, savannas with very sparse grasses, trees or other plants.CitationKarra, Kontgis, et al. “Global land use/land cover with Sentinel-2 and deep learning.” IGARSS 2021-2021 IEEE International Geoscience and Remote Sensing Symposium. IEEE, 2021.AcknowledgementsTraining data for this project makes use of the National Geographic Society Dynamic World training dataset, produced for the Dynamic World Project by National Geographic Society in partnership with Google and the World Resources Institute.For questions please email environment@esri.com

Coordinate system Update:

Notably, this dataset will be provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection, instead of WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857) which is the coordinate system of the 2023 dataset and will remain in Connecticut State Plane moving forward.

Ownership Suppression and Data Access:
The updated dataset now includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name will be replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with suppressed ownership data, users should be aware that there was no "Suppression" field in the submission to verify specific details. This measure was implemented this year to help verify compliance with Suppression.

New Data Fields:
The new dataset introduces the "Land Acres" field, which will display the total acreage for each parcel. This additional field allows for more detailed analysis and better supports planning, zoning, and property valuation tasks. An important new addition is the FIPS code field, which provides the Federal Information Processing Standards (FIPS) code for each parcel’s corresponding block. This allows users to easily identify which block the parcel is in.

Updated Service URL:
The new parcel service URL includes all the updates mentioned above, such as the improved coordinate system, new data fields, and additional geospatial information. Users are strongly encouraged to transition to the new service as soon as possible to ensure that their workflows remain uninterrupted. The URL for this service will remain persistent moving forward. Once you have transitioned to the new service, the URL will remain constant, ensuring long term stability.

For a limited time, the old service will continue to be available, but it will eventually be retired. Users should plan to switch to the new service well before this cutoff to avoid any disruptions in data access.

The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2024 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually.

These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on 10/31/2024 from data collected in 2023-2024. Data was processed using Python scripts and ArcGIS Pro, ensuring standardization and integration of the data.

CAMA Notes:

The CAMA underwent several steps to standardize and consolidate the information. Python scripts were used to concatenate fields and create a unique identifier for each entry. The resulting dataset contains 1,353,595 entries and information on property assessments and other relevant attributes.

• CAMA was provided by the towns.

Spatial Data Notes:

Data processing involved merging the parcels from different municipalities using ArcGIS Pro and Python. The resulting dataset contains 1,290,196 parcels.

• No alteration has been made to the spatial geometry of the data.

• Fields that are associated with CAMA data were provided by towns.

• The data fields that have information from the CAMA were sourced from the towns’ CAMA data.

• If no field for the parcels was provided for linking back to the CAMA by the town a new field within the original data was selected if it had a match rate above 50%, that joined back to the CAMA.

• Linking fields were renamed to "Link".

• All linking fields had a census town code added to the beginning of the value to create a unique identifier per town.

• Any field that was not town name, Location, Editor, Edit Date, or a field associated back to the CAMA, was not used in the creation of this Dataset.

• Only the fields related to town name, location, editor, edit date, and link fields associated with the towns’ CAMA were included in the creation of this dataset. Any other field provided in the original data was deleted or not used.

• Field names for town (Muni, Municipality) were renamed to "Town Name".

The attributes included in the data:

• Town Name

• Owner

• Co-Owner

• Link

• Editor

• Edit Date

• Collection year – year the parcels were submitted

• Location

• Mailing Address

• Mailing City

• Mailing State

• Assessed Total

• Assessed Land

• Assessed Building

• Pre-Year Assessed Total

• Appraised Land

• Appraised Building

• Appraised Outbuilding

• Condition

• <span

The nine-banded Armadillo (Dasypus novemcinctus) is the only species of Armadillo in the United States and alters ecosystems by excavating extensive burrows used by many other wildlife species. Relatively little is known about its habitat use or population densities, particularly in developed areas, which may be key to facilitating its range expansion. We evaluated Armadillo occupancy and density in relation to anthropogenic and landcover variables in the Ozark Mountains of Arkansas along an urban to rural gradient. Armadillo detection probability was best predicted by temperature (positively) and precipitation (negatively). Contrary to expectations, occupancy probability of Armadillos was best predicted by slope (negatively) and elevation (positively) rather than any landcover or anthropogenic variables. Armadillo density varied considerably between sites (ranging from a mean of 4.88 – 46.20 Armadillos per km2) but was not associated with any environmental or anthropogenic variables. Methods Site Selection Our study took place in Northwest Arkansas, USA, in the greater Fayetteville metropolitan area. We deployed trail cameras (Spypoint Force Dark (Spypoint Inc, Victoriaville, Quebec, Canada) and Browning Strikeforce XD cameras (Browning, Morgan, Utah, USA) over the course of two winter seasons, December 2020-March 2021, and November 2021-March 2022. We sampled 10 study sites in year one, and 12 study sites in year two. All study sites were located in the Ozark Mountains ecoregion in Northwest Arkansas. Sites were all Oak Hickory dominated hardwood forests at similar elevation (213.6 – 541 m). Devils Eyebrow and ONSC are public natural areas managed by the Arkansas Natural heritage Commission (ANHC). Devil’s Den and Hobbs are managed by the Arkansas state park system. Markham Woods (Markham), Ninestone Land Trust (Ninestone) and Forbes, are all privately owned, though Markham has a publicly accessible trail system throughout the property. Lake Sequoyah, Mt. Sequoyah Woods, Kessler Mountain, Lake Fayetteville, and Millsaps Mountain are all city parks and managed by the city of Fayetteville. Lastly, both Weddington and White Rock are natural areas within Ozark National Forest and managed by the U.S. Forest Service. We sampled 5 sites in both years of the study including Devils Eyebrow, Markham Hill, Sequoyah Woods, Ozark Natural Science Center (ONSC), and Kessler Mountain. We chose our study sites to represent a gradient of human development, based primarily on Anthropogenic noise values (Buxton et al. 2017, Mennitt and Fristrup 2016). We chose open spaces that were large enough to accommodate camera trap research, as well as representing an array of anthropogenic noise values. Since anthropogenic noise is able to permeate into natural areas within the urban interface, introducing human disturbance that may not be detected by other layers such as impervious surface and housing unit density (Buxton et al. 2017), we used dB values for each site as an indicator of the level of urbanization. Camera Placement We sampled ten study sites in the first winter of the study. At each of the 10 study sites, we deployed anywhere between 5 and 15 cameras. Larger study areas received more cameras than smaller sites because all cameras were deployed a minimum of 150m between one another. We avoided placing cameras on roads, trails, and water sources to artificially bias wildlife detections. We also avoided placing cameras within 15m of trails to avoid detecting humans. At each of the 12 study areas we surveyed in the second winter season, we deployed 12 to 30 cameras. At each study site, we used ArcGIS Pro (Esri Inc, Redlands, CA) to delineate the trail systems and then created a 150m buffer on each side of the trail. We then created random points within these buffered areas to decide where to deploy cameras. Each random point had to occur within the buffered areas and be a minimum of 150m from the next nearest camera point, thus the number of cameras at each site varied based upon site size. We placed all cameras within 50m of the random points to ensure that cameras were deployed on safe topography and with a clear field of view, though cameras were not set in locations that would have increased animal detections (game trails, water sources, burrows etc.). Cameras were rotated between sites after 5 or 10 week intervals to allow us to maximize camera locations with a limited number of trail cameras available to us. Sites with more than 25 cameras were active for 5 consecutive weeks while sites with fewer than 25 cameras were active for 10 consecutive weeks. We placed all cameras on trees or tripods 50cm above ground and at least 15m from trails and roads. We set cameras to take a burst of three photos when triggered. We used Timelapse 2.0 software (Greenberg et al. 2019) to extract metadata (date and time) associated with all animal detections. We manually identified all species occurring in photographs and counted the number of individuals present. Because density estimation requires the calculation of detection rates (number of Armadillo detections divided by the total sampling period), we wanted to reduce double counting individuals. Therefore, we grouped photographs of Armadillos into “episodes” of 5 minutes in length to reduce double counting individuals that repeatedly triggered cameras (DeGregorio et al. 2021, Meek et al. 2014). A 5 min threshold is relatively conservative with evidence that even 1-minute episodes adequately reduces double counting (Meek et al. 2014). Landcover Covariates To evaluate occupancy and density of Armadillos based on environmental and anthropogenic variables, we used ArcGIS Pro to extract variables from 500m buffers placed around each camera (Table 2). This spatial scale has been shown to hold biological meaning for Armadillos and similarly sized species (DeGregorio et al. 2021, Fidino et al. 2016, Gallo et al. 2017, Magle et al. 2016). At each camera, we extracted elevation, slope, and aspect from the base ArcGIS Pro map. We extracted maximum housing unit density (HUD) using the SILVIS housing layer (Radeloff et al. 2018, Table 2). We extracted anthropogenic noise from the layer created by Mennitt and Fristrup (2016, Buxton et al. 2017, Table 2) and used the “L50” anthropogenic sound level estimate, which was calculated by taking the difference between predicted environmental noise and the calculated noise level. Therefore, we assume that higher levels of L50 sound corresponded to higher human presence and activity (i.e. voices, vehicles, and other sources of anthropogenic noise; Mennitt and Fristrup 2016). We derived the area of developed open landcover, forest area, and distance to forest edge from the 2019 National Land Cover Database (NLDC, Dewitz 2021, Table 2). Developed open landcover refers to open spaces with less than 20% impervious surface such as residential lawns, cemeteries, golf courses, and parks and has been shown to be important for medium-sized mammals (Gallo et al. 2017, Poessel et al. 2012). Forest area was calculated by combing all forest types within the NLCD layer (deciduous forest, mixed forest, coniferous forest), and summarizing the total area (km2) within the 500m buffer. Distance to forest edge was derived by creating a 30m buffer on each side of all forest boundaries and calculating the distance from each camera to the nearest forest edge. We calculated distance to water by combining the waterbody and flowline features in the National Hydrogeography Dataset (U.S. Geological Survey) for the state of Arkansas to capture both permanent and ephemeral water sources that may be important to wildlife. We measured the distance to water and distance to forest edge using the geoprocessing tool “near” in ArcGIS Pro which calculates the Euclidean distance between a point and the nearest feature. We extracted Average Daily Traffic (ADT) from the Arkansas Department of Transportation database (Arkansas GIS Office). The maximum value for ADT was calculated using the Summarize Within tool in ArcGIS Pro. We tested for correlation between all covariates using a Spearman correlation matrix and removed any variable with correlation greater than 0.6. Pairwise comparisons between distance to roads and HUD and between distance to forest edge and forest area were both correlated above 0.6; therefore, we dropped distance to roads and distance to forest edge from analyses as we predicted that HUD and forest area would have larger biological impacts on our focal species (Kretser et al. 2008). Occupancy Analysis In order to better understand habitat associations while accounting for imperfect detection of Armadillos, we used occupancy modeling (Mackenzie et al. 2002). We used a single-species, single-season occupancy model (Mackenzie et al. 2002) even though we had two years of survey data at 5 of the study sites. We chose to do this rather than using a multi-season dynamic occupancy model because most sites were not sampled during both years of the study. Even for sites that were sampled in both years, cameras were not placed in the same locations each year. We therefore combined all sampling into one single-season model and created unique site by year combinations as our sampling locations and we used year as a covariate for analysis to explore changes in occupancy associated with the year of study. For each sampling location, we created a detection history with 7 day sampling periods, allowing presence/absence data to be recorded at each site for each week of the study. This allowed for 16 survey periods between 01 December 2020, and 11 March 2021 and 22 survey periods between 01 November 2021 and 24 March 2022. We treated each camera as a unique survey site, resulting in a total of 352 sites. Because not all cameras were deployed at the same time and for the same length of time, we used a staggered entry approach. We used a multi-stage fitting approach in which we

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

*This dataset is authored by ESRI and is being shared as a direct link to the feature service by Pend Oreille County. NHD is a primary hydrologic reference used by our organization.The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesCoordinate System: Web Mercator Auxiliary Sphere Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American Samoa Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not.Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.What can you do with this Feature 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 OnlineAdd this layer to a map in the map viewer. 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. 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.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use 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 the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.

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

The Virginia Geographic Information Network (VGIN) has coordinated and manages the development of a consistent, seamless, statewide digital road centerline file with address, road name, and state route number attribution, as part of the Virginia Base Mapping Program (VBMP). The Road Centerline Program (RCL) leverages the Commonwealth"s investment in the VBMP digital orthophotography and is focused on creating a single statewide, consistent digital road file.The RCL data layer is a dynamic dataset supported and maintained by Virginia"s Local Governments, VDOT, and VGIN. VBMP RCL is extracted and provided back to local governments and state agencies in many geographic data sets every quarter.GDB Version: ArcGIS Pro 3.3Additional Resources:Routable RCL With Network Dataset GDB(ArcGIS Pro 3.2)Shapefile DownloadREST EndpointRoad Centerline Data StandardArcGIS LYR FileHistorical RCL & Ancillary Centerlines -Contact VGIN

Rangelands are regions dominated by grasses and shrubs including savannahs, grasslands, and deserts. Rangelands provide valuable forage for gazing and browsing animals. This layer quantifies annual range production in pounds/acre/year.A raw pixel value in this service represents the number of pounds of range forage expected per acre per year.Dataset SummaryPhenomenon Mapped: Range Forage ProductionUnits: pounds/acre/yearCell Size: 30 meterSource Type: DiscretePixel Type: Unsigned integerData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii)Mosaic Projection: Web Mercator Auxiliary SphereExtent: The western portion of the continental U.S., Florida, a small part of Alaska, and the Island of HawaiiSource: Natural Resources Conservation ServicePublication Date: December 2021ArcGIS Server URL: https://landscape11.arcgis.com/arcgis/Data from the gNATSGO database was used to create the layer for the contiguous United States, Alaska, Puerto Rico, and the U.S. Virgin Islands. The remaining areas were created with the gSSURGO database (Hawaii, Guam, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American Samoa).This layer is derived from the 30m (contiguous U.S.) and 10m rasters (all other regions) produced by the Natural Resources Conservation Service (NRCS). The value for range production is derived from the gSSURGO component table field Range Production - Representative Value (rsprod_r). The value in this layer is the average value for all components of each map unit weighted by component percent (comppct_r).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 "range production" 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 "range production" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions.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.

Florida COVID-19 Cases by Zip Code exported from the Florida Department of Health GIS Layer on date seen in file name. Archived by the University of South Florida Libraries, Digital Heritage and Humanities Collections. Contact: LibraryGIS@usf.edu.Please Cite Our GIS HUB. If you are a researcher or other utilizing our Florida COVID-19 HUB as a tool or accessing and utilizing the data provided herein, please provide an acknowledgement of such in any publication or re-publication. The following citation is suggested: University of South Florida Libraries, Digital Heritage and Humanities Collections. 2020. Florida COVID-19 Hub. Available at https://covid19-usflibrary.hub.arcgis.com/.https://doi.org/10.5038/USF-COVID-19-GISLive FDOH Data Source: https://services1.arcgis.com/CY1LXxl9zlJeBuRZ/arcgis/rest/services/Florida_Cases_Zips_COVID19/FeatureServerFor data 5/10/2020 or after: Archived data was exported directly from the live FDOH layer into the archive. For data prior to 5/10/2020: Data was exported by the University of South Florida - Digital Heritage and Humanities Collection using ArcGIS Pro Software. Data was then converted to shapefile and csv and uploaded into ArcGIS Online archive. For data definitions please visit the following box folder: https://usf.box.com/s/vfjwbczkj73ucj19yvwz53at6v6w614hData definition files names include the relative date they were published. The below information was taken from ancillary documents associated with the original layer from FDOH.Q. How is the zip code assigned to a person or case? Cases are counted in a zip code based on residential or mailing address, or by healthcare provider or lab address if other addresses are missing.Q. Why is the city data and the zip code data different? The zip code data is supplied to a healthcare worker, case manager, or lab technician by each individual during intake when a test is first recorded. When entering a zip code, the system we use automatically produces a list of cities within that zip code for the individual to further specify where they live. Sometimes the individual uses the postal city, which may be Miami, when in reality that person lives outside the City of Miami boundaries in the jurisdiction of Coral Gables. Many zip codes contain multiple city/town jurisdictions, and about 20% of zip codes overlap more than one county. Q: How is the Zip Code data calculated and/or shown? If a COUNTY has five or more cases (total): • In zip codes with fewer than 5 cases, the total number of cases is shown as “<5”. • Zip codes with 0 cases in these counties are “0" or "No cases.” • All values of 5 or greater are shown by the actual number of cases in that zip code. If a COUNTY has fewer than five total cases across all of its zip codes, then ALL of the zip codes within that county show the total number of cases as "Suppressed." Q: My zip code says "SUPPRESSED" under cases. What does that mean? IF Suppressed: This county currently has fewer than five cases across all zip codes in the county. In an effort to protect the privacy of our COVID-19-Positive residents, zip code data is only available in counties where five or more cases have been reported. Q: What about PO Box zip codes, or zip codes with letters, like 334MH? PO Box zip codes are not shown in the map. “Filler” zip codes with letters, like 334MH, are typically areas where no or very few people live – like the Florida Everglades, and are shown on the map like any other zip code. Key Data about Cases by Zip Code: ZIP = The zip code COUNTYNAME = The county for the zip code (multi-part counties have been split) ZIPX = The unique county-zip identifier used to pair the data during updates POName = The postal address name assigned to the zip code place_labels = A list of the municipalities intersecting the zip code boundary c_places = The list of cities cases self-reported as being residents of Cases_1 = The number of cases in each zip code, with conditions*LabelY = A calculated field for map display only. All questions regarding this dataset should be directed to the Florida Department of Health.

Statewide Download (FGDB) (SHP)Users can also download smaller geographic areas of this feature service in ArcGIS Pro using the Copy Features geoprocessing tool. The address service contains statewide address points and related landmark name alias table and street name alias table.The New Jersey Office of Information Technology, Office of GIS (NJOGIS), in partnership with several local GIS and public safety agencies, has built a comprehensive statewide NG9-1-1 database meeting and exceeding the requirements of the National Emergency Number Association (NENA) 2018 NG9-1-1 GIS Data Standard (NENA-STA-006.1-2018). The existing New Jersey Statewide Address Point data last published in 2016 has been transformed in the NENA data model to create this new address point data.The initial address points were processed from statewide parcel records joined with the statewide Tax Assessor's (MOD-IV) database in 2015. Address points supplied by Monmouth County, Sussex County, Morris County and Montgomery Township in Somerset County were incorporated into the statewide address points using customized Extract, Transform and Load (ETL) procedures.The previous version of the address points was loaded into New Jersey's version of the NENA NG9-1-1 data model using Extract, Transform and Load (ETL) procedures created with Esri's Data Interoperability Extension. Subsequent manual and bulk processing corrections and additions have been made, and are ongoing.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

Florida COVID-19 Cases by Zip Code exported from the Florida Department of Health GIS Layer on date seen in file name. Archived by the University of South Florida Libraries, Digital Heritage and Humanities Collections. Contact: LibraryGIS@usf.edu.Please Cite Our GIS HUB. If you are a researcher or other utilizing our Florida COVID-19 HUB as a tool or accessing and utilizing the data provided herein, please provide an acknowledgement of such in any publication or re-publication. The following citation is suggested: University of South Florida Libraries, Digital Heritage and Humanities Collections. 2020. Florida COVID-19 Hub. Available at https://covid19-usflibrary.hub.arcgis.com/.https://doi.org/10.5038/USF-COVID-19-GISLive FDOH Data Source: https://services1.arcgis.com/CY1LXxl9zlJeBuRZ/arcgis/rest/services/Florida_Cases_Zips_COVID19/FeatureServerFor data 5/10/2020 or after: Archived data was exported directly from the live FDOH layer into the archive. For data prior to 5/10/2020: Data was exported by the University of South Florida - Digital Heritage and Humanities Collection using ArcGIS Pro Software. Data was then converted to shapefile and csv and uploaded into ArcGIS Online archive. For data definitions please visit the following box folder: https://usf.box.com/s/vfjwbczkj73ucj19yvwz53at6v6w614hData definition files names include the relative date they were published. The below information was taken from ancillary documents associated with the original layer from FDOH.Q. How is the zip code assigned to a person or case? Cases are counted in a zip code based on residential or mailing address, or by healthcare provider or lab address if other addresses are missing.Q. Why is the city data and the zip code data different? The zip code data is supplied to a healthcare worker, case manager, or lab technician by each individual during intake when a test is first recorded. When entering a zip code, the system we use automatically produces a list of cities within that zip code for the individual to further specify where they live. Sometimes the individual uses the postal city, which may be Miami, when in reality that person lives outside the City of Miami boundaries in the jurisdiction of Coral Gables. Many zip codes contain multiple city/town jurisdictions, and about 20% of zip codes overlap more than one county. Q: How is the Zip Code data calculated and/or shown? If a COUNTY has five or more cases (total): • In zip codes with fewer than 5 cases, the total number of cases is shown as “<5”. • Zip codes with 0 cases in these counties are “0" or "No cases.” • All values of 5 or greater are shown by the actual number of cases in that zip code. If a COUNTY has fewer than five total cases across all of its zip codes, then ALL of the zip codes within that county show the total number of cases as "Suppressed." Q: My zip code says "SUPPRESSED" under cases. What does that mean? IF Suppressed: This county currently has fewer than five cases across all zip codes in the county. In an effort to protect the privacy of our COVID-19-Positive residents, zip code data is only available in counties where five or more cases have been reported. Q: What about PO Box zip codes, or zip codes with letters, like 334MH? PO Box zip codes are not shown in the map. “Filler” zip codes with letters, like 334MH, are typically areas where no or very few people live – like the Florida Everglades, and are shown on the map like any other zip code. Key Data about Cases by Zip Code: ZIP = The zip code COUNTYNAME = The county for the zip code (multi-part counties have been split) ZIPX = The unique county-zip identifier used to pair the data during updates POName = The postal address name assigned to the zip code place_labels = A list of the municipalities intersecting the zip code boundary c_places = The list of cities cases self-reported as being residents of Cases_1 = The number of cases in each zip code, with conditions*LabelY = A calculated field for map display only. All questions regarding this dataset should be directed to the Florida Department of Health.

Florida COVID-19 Cases by Zip Code exported from the Florida Department of Health GIS Layer on date seen in file name. Archived by the University of South Florida Libraries, Digital Heritage and Humanities Collections. Contact: LibraryGIS@usf.edu.Please Cite Our GIS HUB. If you are a researcher or other utilizing our Florida COVID-19 HUB as a tool or accessing and utilizing the data provided herein, please provide an acknowledgement of such in any publication or re-publication. The following citation is suggested: University of South Florida Libraries, Digital Heritage and Humanities Collections. 2020. Florida COVID-19 Hub. Available at https://covid19-usflibrary.hub.arcgis.com/.https://doi.org/10.5038/USF-COVID-19-GISLive FDOH Data Source: https://services1.arcgis.com/CY1LXxl9zlJeBuRZ/arcgis/rest/services/Florida_Cases_Zips_COVID19/FeatureServerFor data 5/10/2020 or after: Archived data was exported directly from the live FDOH layer into the archive. For data prior to 5/10/2020: Data was exported by the University of South Florida - Digital Heritage and Humanities Collection using ArcGIS Pro Software. Data was then converted to shapefile and csv and uploaded into ArcGIS Online archive. For data definitions please visit the following box folder: https://usf.box.com/s/vfjwbczkj73ucj19yvwz53at6v6w614hData definition files names include the relative date they were published. The below information was taken from ancillary documents associated with the original layer from FDOH.Q. How is the zip code assigned to a person or case? Cases are counted in a zip code based on residential or mailing address, or by healthcare provider or lab address if other addresses are missing.Q. Why is the city data and the zip code data different? The zip code data is supplied to a healthcare worker, case manager, or lab technician by each individual during intake when a test is first recorded. When entering a zip code, the system we use automatically produces a list of cities within that zip code for the individual to further specify where they live. Sometimes the individual uses the postal city, which may be Miami, when in reality that person lives outside the City of Miami boundaries in the jurisdiction of Coral Gables. Many zip codes contain multiple city/town jurisdictions, and about 20% of zip codes overlap more than one county. Q: How is the Zip Code data calculated and/or shown? If a COUNTY has five or more cases (total): • In zip codes with fewer than 5 cases, the total number of cases is shown as “<5”. • Zip codes with 0 cases in these counties are “0" or "No cases.” • All values of 5 or greater are shown by the actual number of cases in that zip code. If a COUNTY has fewer than five total cases across all of its zip codes, then ALL of the zip codes within that county show the total number of cases as "Suppressed." Q: My zip code says "SUPPRESSED" under cases. What does that mean? IF Suppressed: This county currently has fewer than five cases across all zip codes in the county. In an effort to protect the privacy of our COVID-19-Positive residents, zip code data is only available in counties where five or more cases have been reported. Q: What about PO Box zip codes, or zip codes with letters, like 334MH? PO Box zip codes are not shown in the map. “Filler” zip codes with letters, like 334MH, are typically areas where no or very few people live – like the Florida Everglades, and are shown on the map like any other zip code. Key Data about Cases by Zip Code: ZIP = The zip code COUNTYNAME = The county for the zip code (multi-part counties have been split) ZIPX = The unique county-zip identifier used to pair the data during updates POName = The postal address name assigned to the zip code place_labels = A list of the municipalities intersecting the zip code boundary c_places = The list of cities cases self-reported as being residents of Cases_1 = The number of cases in each zip code, with conditions*LabelY = A calculated field for map display only. All questions regarding this dataset should be directed to the Florida Department of Health.