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

For the latest Land Use Legend, 2022-DWR-Standard-Land-Use-Legend-Remote-Sensing-Version.pdf, please see the Data and Resources section below.

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

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

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

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

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

IDPR's Idaho Trails App Dataset, Web Map, and Web App have been extensively retooled for 2024.

Feature Service

The new App is served by this Hosted Feature Layer dataset which can be updated more frequently and on-the-fly-- changes will appear on the App and through the feature Service in real time. The newest web presentation technology under AGOL, Experience Builder, served by this dataset, will make possible several extended features to come in future updates to the App. This packaged release replaces the App created with predecessor technology Web App Builder. Web App Builder technology is scheduled to be phased out by Esri by the end of 2024.

Under the hood

Linear routes, closure routes and areas, and boundary area data are ported through a Web Map from the underlying Hosted Feature Service (HFS). In addition to view settings for attributes popups set in the Web Map, additional visibility option not available directly included in the HFS data or controllable in the Web Map will be further processed in the Experience App presentation.

Underlaying Classes in the Dataset:

One single linear class "Idaho Routes" contains all road and trail features (60,000+ route segments):

Routes characterized as recreational in nature include "High Clearance" (previously "Jeep" treated as a road type, now as a full-width "trail" type): High-clearance, Special Vehicle Designation (mostly OHVs >50"), OHVs 50" and under, and single-track (each width class separated by seasonal and not); E-Bike; and, non-motorized and non-mechanized. Routes where vehicles either must be highway-legal (OHVs prohibited; typically paved roads), or routes requiring Restricted plate for legal OHV travel (mostly JURISDICTION = County); combined from previously-separate Layers: Highway-legal, Automobile, Other Roads (each with subcategories for seasonal access restrictions).

(Note: Different route types are no longer kept in separate layers as with the legacy Map Service dataset. Route symbology, and selectable visibility will be filtered based on the value in the SYMBOL attribute from the above linear class within the Web Map and Experience-based App. If dynamically consuming the Feature Service, provisions will need to be made to filter to select visibility by road and trail types based on the value in the SYMBOL field.)

"Points of Interest" (point type data) is comprised of a layer previously titled "Trailheads" and now includes the flexibility of other types of lat/lon point-based information such as links to external maps and "attractions" information such as site seeing destinations not previously included in IDPR's map presentation.
"Emergency Route Closures" contains linear route Closures (overlays any route where a Closure Order applies in web map) "Area Restrictions" is added for areas such as defined by human exclusion Orders (polygon; usually planned annual human or vehicle exclusion areas, but can be emergency closure as well) Multiple "Boundary" polygon classes contain boundary outlines and attributes information for IDPR Regions (3), Counties (44), Wildernesses (42), National Forests and Ranger Districts (39), and BLM District and Field Offices (12), and BLM land units (700+). These separate classes reduce the data footprint of the Routes data and are joined in App popups by geographic Intersection logic.

Bonus Material:

Added to the App are several optional, dynamic layers via publicly-available REST services selectable for visibility:

Idaho Department of Lands- Lands Available for Recreational Use (visible by-default) Idaho Department of Fish & Game Hunting Units boundaries and numbers BLM Surface Management Agency layer for all local, state, and federal agencies which manage public lands (accessible, and not)
US Forest Service Motor Vehicle Use Map, National Dataset (mirrors local MVUM paper and GeoPDF maps, where data available, lags local data when changes are made) National Park Service (NPS) Parks and Monuments areas and boundaries NOAA Snow Depth Other REST Services to be added based on utility in researching recreational access

This dataset is published for the use of the individuals who fund this Program. Organizations wishing to consume this Feature Service into their own application should inquire to IDPR to obtain a use agreement and schema information to aid in development.AGOL Experience App here: https://experience.arcgis.com/experience/97a42a2a73c944ba918042faf518c689

Inquire to maps@idpr.idaho.gov

2023 Updates to the National Incident Feature Service and Event Geodatabase For 2023, there are no schema updates and no major changes to GeoOps or the GISS Workflow! This is a conscious choice and is intended to provide a needed break for both users and administrators. Over the last 5 years, nearly every aspect of the GISS position has seen a major overhaul and while the advancements have been overwhelmingly positive, many of us are experiencing change fatigue. This is not to say there is no room for improvement. Many great suggestions were received throughout the season and in the GISS Survey, and they will be considered for inclusion in 2024. That there are no critical updates necessary also indicates that we have reached a level of maturity with the current state, and that is good news for everyone. Please continue to submit your ideas; they are appreciated and valuable insight, even if the change is not implemented. For information on 2023 AGOL updates please see the NWCG page. There are three smaller changes worth noting this year: Standard Symbology is now the default on the NIFS For most workflows, the update will be seamless. All the Event Standard symbols are now supported in Field Maps and Map Viewer. Most users will now see the same symbols in all print and digital products. However, in AGOL some web apps do not support the complex line symbols. The simplified lines will still be present in the official Editing Apps (Operations, SITL, and GISS), and any custom apps built with the Web App Builder (WAB) interface. Experience Builder can be used for any new app creation. If you must use WAB or another app that cannot display the complex line symbology in the NIFS, please contact wildfireresponse@firenet.gov for guidance. Event Line now has Preconfigured Labels Labels on Event Line have historically been uncommon, but to speed their implementation when necessary, color-coded labels classes have been added to the NIFS and the lyrx files provided in the GIS Folder Structure. They can be disabled or modified as needed, should they interfere with any of your workflows. “Restricted” Folder added to GeoOps Folder Structure At the base level within the 2023_Template, a ‘restricted’ folder is now included. This folder should be used for all data and products that contain sensitive, restricted, or controlled-unclassified information. This will aid the DOCL and any future FOIA liaisons in protecting this information. When using OneDrive, this folder can optionally be password protected. Reminder: Sensitive Data is not allowed to be hosted within the NIFC Org.

This submission offers a link to a web mapping application hosted instance of the Global Oil & Gas Features Database (GOGI), via EDX Spatial. This offers users with the ability to visualize, interact, and create maps with data of their choice, as well as download specific attributes or fields of view from the database. This data can also be downloaded as a File Geodatabse from EDX at https://edx.netl.doe.gov/dataset/global-oil-gas-features-database. Access the technical report describing how this database was produced using the following link: https://edx.netl.doe.gov/dataset/development-of-an-open-global-oil-and-gas-infrastructure-inventory-and-geodatabase” This data was developed using a combination of big data computing, custom search and data integration algorithms, and expert driven search to collect open oil and gas data resources worldwide. This approach identified over 380 data sets and integrated more than 4.8 million features into the GOGI database. Acknowledgements: This work was funded under the Climate and Clean Air Coalition (CCAC) Oil and Gas Methane Science Studies. The studies are managed by United Nations Environment in collaboration with the Office of the Chief Scientist, Steven Hamburg of the Environmental Defense Fund. Funding was provided by the Environmental Defense Fund, OGCI Companies (Shell, BP, ENI, Petrobras, Repsol, Total, Equinor, CNPC, Saudi Aramco, Exxon, Oxy, Chevron, Pemex) and CCAC.

NOTICE TO PROVISIONAL 2023 LAND USE DATA USERS: Please note that on December 6, 2024 the Department of Water Resources (DWR) published the Provisional 2023 Statewide Crop Mapping dataset. The link for the shapefile format of the data mistakenly linked to the wrong dataset. The link was updated with the appropriate data on January 27, 2025 and a notice was posted on the shapefile download site. If you downloaded the Provisional 2023 Statewide Crop Mapping dataset in shapefile format between December 6, 2024 and January 27, we encourage you to redownload the data. The Map Service and Geodatabase formats were correct as posted on December 06, 2024. Thank you for your interest in DWR land use datasets. The California Department of Water Resources (DWR) has been collecting land use data throughout the state and using it to develop agricultural water use estimates for statewide and regional planning purposes, including water use projections, water use efficiency evaluations, groundwater model developments, climate change mitigation and adaptations, and water transfers. These data are essential for regional analysis and decision making, which has become increasingly important as DWR and other state agencies seek to address resource management issues, regulatory compliances, environmental impacts, ecosystem services, urban and economic development, and other issues. Increased availability of digital satellite imagery, aerial photography, and new analytical tools make remote sensing-based land use surveys possible at a field scale that is comparable to that of DWR’s historical on the ground field surveys. Current technologies allow accurate large-scale crop and land use identifications to be performed at desired time increments and make possible more frequent and comprehensive statewide land use information. Responding to this need, DWR sought expertise and support for identifying crop types and other land uses and quantifying crop acreages statewide using remotely sensed imagery and associated analytical techniques. Currently, Statewide Crop Maps are available for the Water Years 2014, 2016, 2018- 2022 and PROVISIONALLY for 2023. Historic County Land Use Surveys spanning 1986 - 2015 may also be accessed using the CADWR Land Use Data Viewer: https://gis.water.ca.gov/app/CADWRLandUseViewer. For Regional Land Use Surveys follow: https://data.cnra.ca.gov/dataset/region-land-use-surveys. For County Land Use Surveys follow: https://data.cnra.ca.gov/dataset/county-land-use-surveys. For a collection of ArcGIS Web Applications that provide information on the DWR Land Use Program and our data products in various formats, visit the DWR Land Use Gallery: https://storymaps.arcgis.com/collections/dd14ceff7d754e85ab9c7ec84fb8790a.

This vector dataset contains polygon features that represent the college campuses or site locations throughout Suffolk County. These features can be linked with some of the features of the CollegePoint feature class by the FACILITYID field. These data are organized for consumption in desktop and web applications.

This data set contains GPS data collected by the FDEP Bureau of Surveying and Mapping (BSM). Data was first imported from the NGS Online Positional User Service (OPUS). On 1/10/2017 the import was performed based on all OPUS submittals performed by Rudolphe Konou of FDEP BSM. The file was imported to a geodatabase. Some of the original fields were dropped from the data set and some maintenance of the other fields was performed to match BSM needs for a web application.Since inception, the file is updated via a Geoform as solutions are returned to FDEP from OPUS. Point of Contact:Bryan Shoaf, FDEP Division of State Lands850-245-2619bryan.shoaf@dep.state.fl.us

BAARI (Bay Area Aquatic Resource Inventory) was established to meet regional needs for wetlands and stream monitoring. One primary objective was to apply standardized monitoring tools to ensure data comparability and consistent, documented quality. These data help agencies and organizations assess the extent and condition of wetlands in local watersheds and identify and prioritize opportunities for ecological restoration and enhancement in a watershed context.BackgroundBAARI data is part of the Wetland and Riparian Area Monitoring Plan (WRAMP), which consists of a 1-2-3 level monitoring framework. This allows assessment of wetlands at two scales: landscape and highly localized. BAARI is Level 1 of this framework, developed for landscape level analyses of wetland extent, distribution and abundance. Geographic information systems (GIS) and remote sensing are used to map and create inventories of existing wetlands (both modern and historical). These inventories quantify the extent of wetland habitats and projects, and are used for landscape profiles of wetlands at the state, regional, watershed, and local scales. Level 2 entails rapid field assessment of wetland health or ecological condition. In California the California Rapid Assessment Method (CRAM) is a diagnostic tool that two or more trained practitioners can use to assess the condition of a wetland or riparian site in one half day or less using visual indicators in the field. Level 3 monitoring entails intensive sampling of ecological function or specific aspects of wetland condition. These assessments are intensive quantitative measurements of condition, stress, or cause-and-effect relationships. A Level 3 assessment is an in-depth study of a particular attribute of wetland health such as water quality, fish habitat, bird populations, vegetative cover and diversity, or physical processes. Level 3 monitoring can describe the performance of specific ecological functions at the site scale. Information on the WRAMP is available at http://www.mywaterquality.ca.gov/eco_health/wetlands/condition/wramp_toolkit.shtmlMore information on BAARI can be found online at: http://www.sfei.org/BAARI. Description of Updates in Version 2Local experts provided advice on and reviewed BAARIâ??s stream, wetland and riparian GIS layers in specific locations to help update the data as conditions in the field changed and/or to increase its accuracy and detail. Improving the accuracy and detail of BAARI improves the base maps for all monitoring and assessment efforts to understand the distribution, amount and ecological condition of Bay Area aquatic resources. The following updates were made to BAARI under this project:The Santa Clara Valley Water District (SCVWD) provided their GIS based stream data for the Guadalupe River Watershed. SFEIâ??s GIS team incorporated parts of the SCVWD dataset into BAARI to improve the accuracy and detail of the BAARI stream layer with the Guadalupe River watershed. Updates included features such as underground connectors between the upper and lower watershed reaches, and enhanced details of portions of the upper watershed. Watershed Sciences developed six hand-drawn maps showing field verified ditch locations circa 2006. Those data were used in developing the sediment TMDL for the watershed. Watershed sciences provided those maps to SFEIâ??s GIS team and worked with them to compare the remotely sensed stream and ditch locations in the BAARI data set (based on 2009 NAIP imagery) to her maps and other data (including Google Earth using multiple image dates). Based on this careful comparative process, about 500 linear updates were made to the BAARI stream layer for the Sonoma Creek watershed with the data source attributed to Laurel Collinsâ?? maps. SFEI staff added stream names for the whole BAARI dataset (Bay Area 9 counties, ocean shoreline, and Tomales Bay - 530 different names applied to more than 24000 stream segments).Additional corrections to wetland and stream presence, extent, and classification were appended to the dataset by SFEI staff where inaccuracies were identified based on local expertise of wetlands in the Bay Area.All BAARI updates were reviewed by a second GIS staff member to ensure that they were acceptable and followed BAARI mapping protocols. Description of Attribute Fields in BAARIBaylandsRestProj: restoration project associated with this wetland. This field has not been updated in version 2. Refer to http://www.EcoAtlas.org for current listings of ecological restoration projects. Source_Dat: source(s) from which the wetland polygon was digitized, or otherwise incorporated into BAARIWetlandTyp: Coded classification of the wetland type. Codes are defined on p5-6 of "BAARI Mapping Standards" Organization: organization that digitized the wetland polygonClickCode: simplification of the 'WetlandTyp' attribute used for map database queries in web mapping applications such as http://www.EcoAtlas.org. Refers to the standardized wetland classification system employed by the California Aquatic Resources Inventory (CARI). More information about CARI is available at http://www.sfei.org/it/gis/cari ClickLabel: verbal description of the ClickCode codeLegCode: further simplification of the 'WetlandTyp' attribute used in the legends of web mapping applications such as http://www.EcoAtlas.orgLegLabel: verbal description of the LegCode codeORIG_FID: unusedOpenWater: Open Water (1) or a wetland (0)TidRip: unusedGlobalID: Unique identifier, if one exists StreamsWetlandTyp: Coded classification of the stream type. Codes are defined on p9-10 of "BAARI Mapping Standards" Bayland: Identifies whether the feature falls within the historical extent of the Baylands (1) or not (0)Strahler: Strahler stream order of the stream segment.ClickCode: simplification of the 'WetlandTyp' attribute used for map database queries in web mapping applications such as http://www.EcoAtlas.orgClickLabel: verbal description of the ClickCode codeLegCode: further simplification of the 'WetlandTyp' attribute used in the legends of web mapping applications such as http://www.EcoAtlas.orgLegLabel: verbal description of the LegCode codeGlobalID: Unique identifier, if one exists (e.g. ReachCode attribute in NHD)IDNum: Numerical version of GlobalIDStreamName: the recognized Geographic Names Information System (GNIS) name of the streamSource_Dat: source(s) from which the segment was digitized, or otherwise incorporated into BAARI.Name_Source: source from which 'StreamName' was identifiedFNode: "From Node" used to determine stream flow directionTNode: "To Node" used to determine stream flow directionLegHeader: legend header used in the legends of web mapping applications such as http://www.EcoAtlas.orgTMDL_DATA: "Yes" value indicates TMDL data is available for this stream segment. Contact SFEI for information about integrating TMDL data with BAARIWetlands (Non-tidal)WetlandTyp: Coded classification of the wetland type. Codes are defined on p6-9 of "BAARI Mapping Standards" SourceData: source(s) from which the wetland polygon was digitized, or otherwise incorporated into BAARIOrganization: organization that digitized the wetland polygonClickCode: simplification of the 'WetlandTyp' attribute used for map database queries in web mapping applications such as http://www.EcoAtlas.orgClickLabel: verbal description of the ClickCode codeLegCode: further simplification of the 'WetlandTyp' attribute used in the legends of web mapping applications such as http://www.EcoAtlas.orgLegLabel: verbal description of the LegCode codeGlobalID: Unique identifier, if one exists

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 public map service contains points and polygons representing information from the Massachusetts Cultural Resource Information System (MACRIS) database and related records on file at the Massachusetts Historical Commission (MHC), including the Inventory of Historic Assets of the Commonwealth, National Register of Historic Places nomination forms, local historic district study reports, local landmark reports, and other materials. The MACRIS database and the layers within the MACRIS Maps web application are updated regularly as new information is submitted and added, and as the accuracy of earlier versions of the datalayer is improved. Three datalayers are being made available to the public: The Inventory Points layer contains the locations of buildings, burial grounds, structures, and objects (e.g. statues, monuments, walls). The points layer is symbolized to indicate the most common historic designation types: 1) National Register of Historic Places, 2) local historic district, 3) both National Register and local historic district, 4) Preservation Restriction, 5) Massachusetts Historic Landmark (MA/HL) and 6) inventoried but not designated with one of the previous designations. Less common designations are not symbolized in MACRIS, but are included in the Designations attribute field.The Inventory Areas polygon layer includes areas and districts symbolized in MACRIS in a similar manner to Inventory Points. Another polygon layer, Towns, possesses a binary “y” or blank field to indicate whether a town has a survey pending digitization. Please note that new and updated information is added to MHC files daily, and that there may be considerable lag time before this information is reflected in MACRIS or in MACRIS Maps. Map information for “completed” towns may not reflect the most current information on file with MHC. For additional information, users may consult the source records, forms and maps that make up the official Inventory of Historic and Archaeological Assets of the Commonwealth, on file at the MHC, Massachusetts Archives Building, 220 Morrissey Boulevard, Boston, during weekday business hours. No appointment is needed. For directions, see https://www.sec.state.ma.us/mhc/.See the metadata for more details.

The APCW map legend is symbolized by the APCW_R field of the Forests to Faucets 2.0 dataset, and supports web maps associated with the Forests to Faucets 2.0 Data Explorer app and Forests to Faucets 2.0 Reports app.

The Wildfire Threat map legend uses the WFP_IMP_R field of the Forests to Faucets 2.0 dataset, and supports web maps associated with the Forests to Faucets 2.0 Data Explorer app and Forests to Faucets 2.0 Reports app.

Cotton root rot is a century-old cotton disease that now can be effectively controlled with Topguard Terra fungicide. Because this disease tends to occur in the same general areas within fields in recurring years, site-specific application of the fungicide only to infested areas can be as effective as and considerably more economical than uniform application. The overall objective of this research was to demonstrate how site-specific fungicide application could be implemented based on historical remote sensing imagery and using variable-rate technology. Procedures were developed for creating binary prescription maps from historical airborne and high-resolution satellite imagery. Two different variable-rate liquid control systems were adapted to two existing cotton planters, respectively, for site-specific fungicide application at planting. One system was used for site-specific application on multiple fields in 2015 and 2016 near Edroy, Texas, and the other system was used on multiple fields in both years near San Angelo, Texas. Airborne multispectral imagery taken during the two growing seasons was used to monitor the performance of the site-specific treatments. Results based on prescription maps derived from historical airborne and satellite imagery of two fields in 2015 and one field in 2016 are reported in this article. Two years of field experiments showed that the prescription maps and the variable-rate systems performed well and that site-specific fungicide treatments effectively controlled cotton root rot. Reduction in fungicide use was 41%, 43%, and 63% for the three fields, respectively. The methodologies and results of this research will provide cotton growers, crop consultants, and agricultural dealers with practical guidelines for implementing site-specific fungicide application using historical imagery and variable-rate technology for effective management of cotton root rot. Resources in this dataset: Resource Title: A ground picture of cotton root rot File Name: IMG_0124.JPG Resource Description: A cotton root rot-infested area in a cotton field near Edroy, TX. Resource Title: An aerial image of a cotton field File Name: Color-infrared image of a field.jpg Resource Description: Aerial color-infrared (CIR) image of a cotton field infested with cotton root rot. Resource Title: As-applied fungicide application data File Name: Jim Ermis-Farm 1-Field 11 Fungicide Application.csv Resource Description: As-applied fungicide application rates for variable rate application of Topguard to a cotton field infested with cotton rot

Supplemental Areas covered by an Airport Land Use Compatibility Plan, such as Critical Airspace Protection Zones, that are line layers. Please click here to see the Los Angeles County Airport Land Use Commission portion of our website for maps and documents. SOURCE: Brackett Field Land Use Compatibility Plan (adopted 12/9/15).All airport layers can be seen and interacted with together in our A-NET GIS web mapping application - click here.NEED MORE FUNCTIONALITY? If you are looking for more layers or advanced tools and functionality, then try our suite of GIS Web Mapping Applications.

This feature class is updated every business day using Python scripts and the Permit database. Please disregard the "Date Updated" field as it does not keep in sync with DWR's internal enterprise geodatabase updates. This dataset contains the places of use (POU) for water rights based on the polygon ID. A POU is the location (area) where permitted water is used. Since there can be multiple permits on the same POU site, this dataset contains duplicate area features where several permits may be stacked on top of each other spatially. The advantage to using this dataset is that all permits in NDWR’s Permit database are available. Use a filter or definition query to restrict the permits needed. If the permit does not have a polygon ID, the area feature for the permit will not be available in this dataset.Background:While NDWR’s Permit Database was created in 1992, water rights mapping started in August 2007. Water right places of use are mapped from the description or map included with the permit application. If township-range-section and quarter-quarter descriptions are provided, boundary lines are traced from the Public Land Survey System (PLSS) dataset provided by the Bureau of Land Management (BLM). County parcel maps may also be used to trace boundaries of water use. If the POU does not follow PLSS or county parcel boundaries, the application map is georeferenced and the area is plotted from the boundary on the map. The Water Rights Section of NDWR is responsible for reviewing and approving water rights applications, for new appropriations and for changes to existing water rights, as well as evaluating and responding to protests of applications, approving subdivision dedications for water quantity, evaluating domestic well credits and relinquishments, issuing certificates for permitted water rights, conducting field investigations, and processing requests for extensions of time for filing proofs of completion and proofs of beneficial use.Please note that this POU feature class may not contain all water right information on a site or permit. POUs with boundaries for an entire basin or county are not drawn as the large area makes it difficult to see other POUs. POUs for stockwater permits were not consistently mapped before 2021. The GIS Team is working to map active permits that may have been previously skipped. The GIS datasets do not replace the need to review the Permit database and hard copy permit files and are intended for convenience in sharing information on a map, finding a location, seeing spatial patterns, and planning.Code Descriptions:app_status app_status_nameABN ABANDONED (inactive)ABR ABROGATED (inactive)APP APPLICATION (pending)CAN CANCELLED (inactive)CER CERTIFICATE (active)CUR CURTAILED (inactive)DEC DECREED (active)DEN DENIED (inactive)EXP EXPIRED (inactive)FOR FORFEITED (inactive)PER PERMIT (active)REJ REJECTED (inactive)REL RELINQUISHED (inactive)RES RESERVED (pending)RFA READY FOR ACTION (pending)RFP READY FOR ACTION PROTESTED (pending)RLP RELINQUISH A PORTION (active)RSC RESCINDED (inactive)RVK REVOKED (inactive)RVP REVOCABLE PERMIT (active)SUP SUPERSEDED (inactive)SUS SUSPENDED (inactive)VST VESTED RIGHT (pending)WDR WITHDRAWN (inactive)manner of use (mou) use_nameCOM COMMERCIALCON CONSTRUCTIONDEC AS DECREEDDOM DOMESTICDWR DEWATERINGENV ENVIRONMENTALIND INDUSTRIALIRC IRRIGATION-CAREY ACTIRD IRRIGATION-DLEIRR IRRIGATIONMM MINING AND MILLINGMUN MUNICIPALOTH OTHERPWR POWERQM QUASI-MUNICIPALREC RECREATIONALSTK STOCKWATERINGSTO STORAGEUKN UNKNOWNWLD WILDLIFEMMD MINING, MILLING AND DEWATERINGEVP EVAPORATIONsource source_nameEFF EFFLUENTGEO GEOTHERMALLAK LAKEOGW OTHER GROUND WATEROSW OTHER SURFACE WATERRES RESERVOIRSPR SPRINGSTO STORAGESTR STREAMUG UNDERGROUNDDate Field Descriptions:Permit Date—Date the permit was issued.File Date—Date application was filed at the Division.Sent for Publication—Date the notice that the application was filed was sent to the newspaper of record for publication.Last Publication—The last date of publication of said notice in the paper; 30 days from this date is the last day for filing a protest to an application.POC Filed Date—When a Proof of Completion of Work is accepted by this office, it becomes “filed” rather than just received. The filed date is the same as the received date.

The CAWD GIS was built using local Geographic Information Systems (GIS) and Global Positioning Systems (GPS). Information provided may be used with the consent of the Carmel Area Wastewater District (CAWD). The map is distributed "AS - IS" without any warranties of any kind. This map is intended as a graphical representation of field conditions; the actual location of features in the field may differ from the depiction on the maps.

Soil is a key natural resource that provides the foundation of basic ecosystem services. Soil determines the types of farms and forests that can grow on a landscape. Soil filters water. Soil helps regulate the Earth's climate by storing large amounts of carbon. Activities that degrade soils reduce the value of the ecosystem services that soil provides. For example, since 1850 35% of human caused green house gas emissions are linked to land use change. The Soil Science Society of America is a good source of of additional information.Many hydrologic processes are affected by the properties of the soil. The amount and timing or run off from a storm is related to how fast soil absorbs water. and the physical structure of the soil affects the amount of water that can be stored in the ground.Dataset SummaryThis layer provides access to a 30 arc-second (roughly 1 km) cell-sized raster with attributes related to soil hydrology derived from the Harmonized World Soil Database v 1.2. The values in this layer are for the dominant soil in each mapping unit (sequence field = 1).Fields are available for each of these attributes related to hydrology:Drainage ClassAvailable Water Storage Capacity - mm/mImpermeable Layer Depth - only in the European Soil DatabaseSoil Water Regime - only in the European Soil DatabaseThe layer is symbolized with the Drainage Class field.The document Harmonized World Soil Database Version 1.2 provides more detail on the attributes related to soil hydrology contained in this layer.Other attributes contained in this layer include:Soil Mapping Unit Name - the name of the spatially dominant major soil groupSoil Mapping Unit Symbol - a two letter code for labeling the spatially dominant major soil group in thematic mapsData Source - the HWSD is an aggregation of datasets. The data sources are the European Soil Database (ESDB), the 1:1 million soil map of China (CHINA), the Soil and Terrain Database Program (SOTWIS), and the Digital Soil Map of the World (DSMW).Percentage of Mapping Unit covered by dominant componentMore information on the Harmonized World Soil Database is available here.Other layers created from the Harmonized World Soil Database are available on ArcGIS Online:World Soils Harmonized World Soil Database - Bulk DensityWorld Soils Harmonized World Soil Database – ChemistryWorld Soils Harmonized World Soil Database - Exchange CapacityWorld Soils Harmonized World Soil Database – GeneralWorld Soils Harmonized World Soil Database – TextureThe authors of this data set request that projects using these data include the following citation:FAO/IIASA/ISRIC/ISSCAS/JRC, 2012. Harmonized World Soil Database (version 1.2). FAO, Rome, Italy and IIASA, Laxenburg, Austria.What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop.This layer has query, identify, and export image services available. This layer is restricted to a maximum area of 16,000 x 16,000 pixels - an area 4,000 kilometers on a side or an area approximately the size of Europe. The source data for this layer are available here.This layer is part of a larger collection of landscape layers that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about landscape layers and the Living Atlas of the World. To get started follow these links:Living Atlas Discussion GroupSoil Data Discussion GroupThe Esri Insider Blog provides an introduction to the Ecophysiographic Mapping project.

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

Soil is a key natural resource that provides the foundation of basic ecosystem services. Soil determines the types of farms and forests that can grow on a landscape. Soil filters water. Soil helps regulate the Earth's climate by storing large amounts of carbon. Activities that degrade soils reduce the value of the ecosystem services that soil provides. For example, since 1850 35% of human caused green house gas emissions are linked to land use change. The Soil Science Society of America is a good source of of additional information.Dataset SummaryThis layer provides access to a 30 arc-second (roughly 1 km) cell-sized raster with attributes describing the basic properties of soil derived from the Harmonized World Soil Database v 1.2. The values in this layer are for the dominant soil in each mapping unit (sequence field = 1).Attributes in this layer include:Soil Phase 1 and Soil Phase 2 - Phases identify characteristics of soils important for land use or management. Soils may have up to 2 phases with phase 1 being more important than phase 2.Other Properties - provides additional information important for agriculture.Additionally, 3 class description fields were added by Esri based on the document Harmonized World Soil Database Version 1.2 for use in web map pop-ups:Soil Phase 1 DescriptionSoil Phase 2 DescriptionOther Properties DescriptionThe layer is symbolized with the Soil Unit Name field.The document Harmonized World Soil Database Version 1.2 provides more detail on the soil properties attributes contained in this layer.Other attributes contained in this layer include:Soil Mapping Unit Name - the name of the spatially dominant major soil groupSoil Mapping Unit Symbol - a two letter code for labeling the spatially dominant major soil group in thematic mapsData Source - the HWSD is an aggregation of datasets. The data sources are the European Soil Database (ESDB), the 1:1 million soil map of China (CHINA), the Soil and Terrain Database Program (SOTWIS), and the Digital Soil Map of the World (DSMW).Percentage of Mapping Unit covered by dominant componentMore information on the Harmonized World Soil Database is available here.Other layers created from the Harmonized World Soil Database are available on ArcGIS Online:World Soils Harmonized World Soil Database - Bulk DensityWorld Soils Harmonized World Soil Database – ChemistryWorld Soils Harmonized World Soil Database - Exchange CapacityWorld Soils Harmonized World Soil Database – HydricWorld Soils Harmonized World Soil Database – TextureThe authors of this data set request that projects using these data include the following citation:FAO/IIASA/ISRIC/ISSCAS/JRC, 2012. Harmonized World Soil Database (version 1.2). FAO, Rome, Italy and IIASA, Laxenburg, Austria.What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop.This layer has query, identify, and export image services available. This layer is restricted to a maximum area of 16,000 x 16,000 pixels - an area 4,000 kilometers on a side or an area approximately the size of Europe. The source data for this layer are available here.This layer is part of a larger collection of landscape layers that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about landscape layers and the Living Atlas of the World. To get started follow these links:Living Atlas Discussion GroupSoil Data Discussion GroupThe Esri Insider Blog provides an introduction to the Ecophysiographic Mapping project.

Last Update: August 2020This dataset contains point locations for preschool and K-12 schools in the state of Utah -- updated for the 2019-2020 school year. Higher education and adult vocational training are not included in the dataset.The Schools Pre K to 12 dataset was built in collaboration with Wasatch Front Regional Council(WFRC), the Utah State Board of Education(USBE), and the Automated Geographic Reference Center(AGRC). The dataset includes public and private K-12 school locations with enrollment and demographics info by grade for public schools (charter and traditional) reported to the USBE. While some preschools are included, this is not a comprehensive statewide dataset for preschools.Schools marked as 'closed' have not been included in this data. More information regarding schools in Utah can be found on the Utah State Board of Education website.The Schools Pre K to 12 will be updated annually in conjunction with USBE’s annual report cycle.MethodologyTabular DataThe tabular portion of the data was downloaded from USBE's data page. The list of fields and the data in this dataset were generated by joining the following USBE reports.2019-2020 School ListFall 2019-2020 Enrollment by Demographics and Grade LevelsGeographic DataPoint locations (geometry) were generated from USBE's school list using the AGRC Geocoding Web APIwhich utilizes address point and street centerline reference data. These were then compared to the previous 2016-2017 school layer’s locations with the best position chosen. Unmatched addresses were hand placed with assistance from publicly available, commercial mapping and search web apps.Fields Worth NotingSchoolType:Residential TreatmentAdult HighVocationalSpecial EducationRegular EducationYIC - Youth-In-CustodyAlternativeSchoolLevel:MID - Junior / Middle SchoolHIGH - High SchoolK12 - Kindergarten through 12th GradePREK - Pre KindergartenELEM - Elementary SchoolAcronyms and Abbreviations in the DataLEA: Local Educational Agency (i.e., school district)LEANameLEANumberLEAIDNESS: Necessarily Existent Small Schools funding