This resource was created by Esri Canada Education and Research. To browse our full collection of higher-education learning resources, please visit https://hed.esri.ca/resourcefinder/

ArcGIS Field Maps is a mobile app that allows you to view and collect field data using an Android or iOS smartphone or tablet. It is also a web app that allows you to configure web maps for use in the mobile app. The tutorials in this learning path will introduce you to the features of the Field Maps mobile app, how to create and configure web maps in Field Maps Designer that can be used in the Field Maps mobile app in online and offline mode, and how to collect data from a map and in the field with the mobile app.

MRGP NewsIf you already have an ArcGIS named user, join the MRGP Group. Doing so allows you complete the permit requirements under your organization's umbrella. As a group member you get access to the all the MRGP items without having to log-in and log-out. If you don’t have an ArcGIS member account please contact Chad McGann (MRGP Program Lead) at 802-636-7239 or your Regional Planning Commission’s Transportation Planner. April 9, 2025. Conditional logic in webform for the newly published Open Drainage Survey was not calculating properly leading to some records with "Undetermined" status and priority. Records have been rescored and survey was republished with corrective logic. Field App version not impacted.March 11, 2025. The Road Erosion Inventory Survey123 questions for Open Drainage Roads are being streamlined to make assessments faster. Coming April 1st, the survey will be changed to only ask if there is erosion depending on if the corresponding practice type is failing. This aims at using erosion as an indicator to measure the success of each of the four Open Drainage road elements to handle stormwater: crown, berm, drainage, turnout.March 29, 2023. For MRGP permitting, Lyndonville Village (GEOID 5041950) has merged with Lyndonville Town (GEOID 5000541725). 121 segments and 14 outlets have been updated to reflect the administrative change. December 8, 2023. The Open Drainage Road Inventory survey has been updated for the 2024 field season. We added and modified a few notes for clarification and corrected an issue with users submitting incomplete surveys. See FAQ section below for how to delete the old survey and download the new one. The app will notify you there's an update, and execute it, but we've experienced select-one questions with duplicate entries.November 29, 2023. The Closed Drainage Road Inventory survey has been updated for the 2024 field season. There's a new outlet status option called "Not accessible" and conditional follow-up question. This has been added to support MS4 requirements. See FAQ section below for how to delete the old survey and download the new one. The app will notify you there's an update and execute it for you but we've experienced select-one questions with duplicate entries. Reporter for MRGPThe Reporter for MRGP doesn't require you to download any apps to complete an inventory; all you need is an internet connection and web browser. The Reporter includes culverts and bridges from VTCULVERTS, town highways from Vtrans, current status for MRGP segments and outlets and second cycle progress. The Reporter is a great way to submit work completed to meet the MRGP standards. MRGP Fieldworker SolutionStep 1: Download the free mobile appsFor fieldworkers to collect and submit data to VT DEC, two free apps are required: ArcGIS Field Maps and Survey123. ArcGIS Field Maps is used first to locate the segment or outlet for inventory, and Survey123, for completing the Road Erosion Inventory.• You can download ArcGIS Fields Maps and Survey123 from the Google Play Store.• You can download ArcGIS Field Maps and Survey123 from Apple Store.Step 2: Sign into the mobile appYou will need appropriate credentials to access fieldworker solution, Please contact your Regional Planning Commission’s Transportation Planner or Chad McGann (MRGP Program Lead) at 802-636-7239.Open Field Maps, select ‘ArcGIS Online’ as shown below, and enter the user name and password. The credential is saved unless you sign out. Step 3: Open the MRGP Mobile MapIf you’re working in an area that has a reliable data connection (e.g. LTE or 4G), open the map below by selecting it.Step 4: Select a road segment or outlet for inventoryUsing your location, highlighted in red below, select the segment or outlet you need to inventory, and select 'Update Road Segment Status' from the pop-up to launch Survey123.

Step 5: Complete the Road Erosion Inventory and submit inventory to DECSelecting 'Update Road Segment Status' opens Survey123, downloads the relevant survey and pre-populates the REI with important information for reporting to DEC. You will have to enter the same username and password to access the REI forms. The credential is saved unless you sign out of Survey123.Complete the survey using the appropriate supplement below and submit the assessment directly to VT DEC.Paved Roads with Catch Basin SupplementPaved and Gravel Roads with Drainage Ditches Supplement

Step 6: Repeat!Go back to the ArcGIS Field Maps and select the next segment for inventory and repeat steps 1-5.

If you have question related to inventory protocol reach out to Chad McGann, MRGP Program Lead, at chad.mcgann@vermont.gov, 802-636-7396.If you have questions about implementing the mobile data collection piece please contact Ryan Knox, ADS-ANR IT, at ryan.knox@vermont.gov, (802) 793-0297

How do I update a survey when a new one is available?While the Survey123 app will notify you and update it for you, we've experienced some select-one questions having duplicate choices. It's a best practice to delete the old survey and download the new one. See this document for step-by-step instructions.I already have an ArcGIS member account with my organization, can I use it to complete MRGP inventories?Yes! The MRGP solution is shared within an ArcGIS Group that allows outside organizations. Click "join this group" and send an request to the ANR GIS team. This will allow you complete MRGP requirements for the REI and stay logged into your organization. Win-win situation for us both!AGOL Group: https://www.arcgis.com/home/group.html?id=027e1696b97a48c4bc50cbb931de992d#overviewThe location where I'm doing inventory does not have data coverage (LTE or 4G). What can I do?ArcGIS Field Maps allows you take map areas offline when you think there will be spotty or no data coverage. I made a video to demonstrate the steps for taking map areas offline - https://youtu.be/ScpQnenDp7wSurvey123 operates offline by default but you need to download the survey. My recommendation is to test the fieldworker solution (Steps 1-5) before you go into the field but don't submit the test survey.How do remove an offline area and create a new one? Check out this how-to document for instructions. Delete and Download Offline AreaWhere can I download the Road Erosion Scoring shown on the the Atlas? You can download the scoring for both outlets and road segments through the VT Open Geodata Portal.https://geodata.vermont.gov/search?q=mrgpHow do I use my own map for launching the official MRGP REI survey form? You can use the following custom url for launching Survey123, open the REI and prepopulate answers in the form. More information is here. TIP: add what's below directly in the HTML view of the popup not the link as described in the post I provided.

Segments (lines):Update Road Segment StatusOutlets (points):Update Outlet Status

How do I save my name and organization information used in subsequent surveys? Watch this short video or execute the steps below:

Open Survey123 and open a blank REI form (Collect button) Note: it's important to open a blank form so you don't save the same segment id for all your surveys Fill-in your 'Name' and 'Organization' and clear the 'Date of Assessment field' (x button). Using the favorites menu in the top-right corner you can use the current state of your survey to 'Set as favorite answers.' Close survey and 'Save this survey in Drafts.' Use Collector to launch survey from selected feature (segment or outlet). Using the favorites menu again, 'Paste answers from favorite.

What if the map doesn't have the outlet or road segment I need to inventory for the MRGP? Go Directly to Survey123 and complete the appropriate Road Erosion Inventory and submit the data to DEC. The survey includes a Geopoint (location) that we can use to determine where you completed the inventory.

Where can I view the Road Erosion Inventories completed with Survey123? Use the web map below to view second cycle inventories completed with Survey123. The first cycle inventories can be downloaded below. First cycle inventories are those collected 2018-2022.Web map - Completed Road Erosion Inventories for MRGPWhere can I download the 2020-2022 data collected with Survey123?Road Segments (lines) - https://anrmaps.vermont.gov/websites/MRGP/MRGP2020_segments.zipOutlets (points) - https://anrmaps.vermont.gov/websites/MRGP/MRGP2020_outlets.zipWhere can I download the 2019 data collected with Survey123?

Road Segments (lines) -

From presentations and reports to stories and field work, maps make everything better.GoalsExplore the suite of ArcGIS maps and apps available to your organization.Create and configure a web map using ArcGIS Online.Share your web maps with anyone, at any time, on any device.

This tutorial will teach you how to take time-series data from many field sites and create a shareable online map, where clicking on a field location brings you to a page with interactive graph(s).

The tutorial can be completed with a sample dataset (provided via a Google Drive link within the document) or with your own time-series data from multiple field sites.

Part 1 covers how to make interactive graphs in Google Data Studio and Part 2 covers how to link data pages to an interactive map with ArcGIS Online. The tutorial will take 1-2 hours to complete.

An example interactive map and data portal can be found at: https://temple.maps.arcgis.com/apps/View/index.html?appid=a259e4ec88c94ddfbf3528dc8a5d77e8

Geoform is a configurable app template for form based data editing of a Feature Service. This application allows users to enter data through a form instead of a map's pop-up while leveraging the power of the Web Map and editable Feature Services. This app geo-enables data and workflows by lowering the barrier of entry for completing simple tasks. Use CasesProvides a form-based experience for entering data through a form instead of a map pop-up. This is a good choice for users who find forms a more intuitive format than pop-ups for entering data.Useful to collect new point data from a large audience of non technical staff or members of the community.Configurable OptionsGeoform has an interactive builder used to configure the app in a step-by-step process. Use Geoform to collect new point data and configure it using the following options:Choose a web map and the editable layer(s) to be used for collection.Provide a title, logo image, and form instructions/details.Control and choose what attribute fields will be present in the form. Customize how they appear in the form, the order they appear in, and add hint text.Select from over 15 different layout themes.Choose the display field that will be used for sorting when viewing submitted entries.Enable offline support, social media sharing, default map extent, locate on load, and a basemap toggle button.Choose which locate methods are available in the form, including: current location, search, latitude and longitude, USNG coordinates, MGRS coordinates, and UTM coordinates.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

Contents: This is an ArcGIS Pro zip file that you can download and use for creating map books based on United States National Grid (USNG). It contains a geodatabase, layouts, and tasks designed to teach you how to create a basic map book.Version 1.0.0 Uploaded on May 24th and created with ArcGIS Pro 2.1.3 - Please see the README below before getting started!Updated to 1.1.0 on August 20thUpdated to 1.2.0 on September 7thUpdated to 2.0.0 on October 12thUpdate to 2.1.0 on December 29thBack to 1.2.0 due to breaking changes in the templateBack to 1.0.0 due to breaking changes in the template as of June 11th 2019Updated to 2.1.1 on October 8th 2019Audience: GIS Professionals and new users of ArcGIS Pro who support Public Safety agencies with map books. If you are looking for apps that can be used by any public safety professional, see the USNG Lookup Viewer.Purpose: To teach you how to make a map book with critical infrastructure and a basemap, based on USNG. You NEED to follow the steps in the task and not try to take shortcuts the first time you use this task in order to receive the full benefits. Background: This ArcGIS Pro template is meant to be a starting point for your map book projects and is based on best practices by the USNG National Implementation Center (TUNIC) at Delta State University and is hosted by the NAPSG Foundation. This does not replace previous templates created in ArcMap, but is a new experimental approach to making map books. We will continue to refine this template and work with other organizations to make improvements over time. So please send us your feedback admin@publicsafetygis.org and comments below. Instructions: Download the zip file by clicking on the thumbnail or the Download button.Unzip the file to an appropriate location on your computer (C:\Users\YourUsername\Documents\ArcGIS\Projects is a common location for ArcGIS Pro Projects).Open the USNG Map book Project File (APRX).If the Task is not already open by default, navigate to Catalog > Tasks > and open 'Create a US National Grid Map Book' Follow the instructions! This task will have some automated processes and models that run in the background but you should pay close attention to the instructions so you also learn all of the steps. This will allow you to innovate and customize the template for your own use.FAQsWhat is US National Grid? The US National Grid (USNG) is a point and area reference system that provides for actionable location information in a uniform format. Its use helps achieve consistent situational awareness across all levels of government, disciplines, and threats & hazards – regardless of your role in an incident.One of the key resources NAPSG makes available to support emergency responders is a basic USNG situational awareness application. See the NAPSG Foundation and USNG Center websites for more information.What is an ArcGIS Pro Task? A task is a set of preconfigured steps that guide you and others through a workflow or business process. A task can be used to implement a best-practice workflow, improve the efficiency of a workflow, or create a series of interactive tutorial steps. See "What is a Task?" for more information.Do I need to be proficient in ArcGIS Pro to use this template? We feel that this is a good starting point if you have already taken the ArcGIS Pro QuickStart Tutorials. While the task will automate many steps, you will want to get comfortable with the map layouts and other new features in ArcGIS Pro.Is this template free? This resources is provided at no-cost, but also with no guarantees of quality assurance or support at this time. Can't I just use ArcMap? Ok - here you go. USNG 1:24K Map Template for ArcMapKnown Limitations and BugsZoom To: It appears there may be a bug or limitation with automatically zooming the map to the proper extent, so get comfortable with navigation or zoom to feature via the attribute table.FGDC Compliance: We are seeking feedback from experts in the field to make sure that this meets minimum requirements. At this point in time we do not claim to have any official endorsement of standardization. File Size: Highly detailed basemaps can really add up and contribute to your overall file size, especially over a large area / many pages. Consider making a simple "Basemap" of street centerlines and building footprints.We will do the best we can to address limitations and are very open to feedback!

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.

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

To create this app:

This data release contains the GIS data supporting U.S. Geological Survey Open-File Report (OFR) 2005-1252, "The Geologic Map of Seattle—A Progress Report," published in 2005 by Kathy Goetz Troost, Derek B. Booth, Aaron P. Wisher, and Scott A. Shimel (https://doi.org/10.3133/ofr20051252). The OFR was prepared for the 2005 Washington Hydrogeology Symposium and describes the status of geologic mapping for Seattle, Washington, at the time. The map is the result of field mapping and compilation of subsurface geologic data during the years 1999–2004 and was funded by the City of Seattle and the U.S. Geological Survey. Data from more than 36,000 exploration points, geotechnical borings, monitoring wells, excavations, and outcrops were used in making the map. The northern part of the 2005 OFR and the supporting GIS data were subsequently published as two geologic maps: Booth, D.B., Troost, K.G., and Shimel, S.A., 2005, Geologic map of northwestern Seattle (part of the Seattle North 7.5’ X 15’ Quadrangle), King County, Washington: U.S. Geological Survey Scientific Investigations Map 2903, https://doi.org/10.3133/sim2903. Booth, D.B., Troost, K.G., and Shimel, S.A., 2009, Geologic map of northeastern Seattle (part of the Seattle North 7.5' x 15' quadrangle), King County, Washington: U.S. Geological Survey Scientific Investigations Map 3065, https://doi.org/10.3133/sim3065. The southern part of the 2005 OFR and the supporting GIS data were not subsequently published for various reasons. With the original authors' permission, the GIS data used to create the map shown in OFR 2005-1252 are being released here to best meet modern open-data standards and to allow for use in future studies and mapping. The data included in this data release are only those components necessary to create the map shown in OFR 2005-1252. The following map features were not available and are not included in this data release: bedding point data, faults, anticlines, and contact lines. OFR_2005-1252.gdb is an Esri geodatabase containing the following feature classes: ofr_2005_1252_geology_poly (1,068 features); ofr_2005_1252_fill_poly (424 features); ofr_2005_1252_seattle_fault_zone_poly (1 feature); ofr_2005_1252_wastage_landslide_deposits_poly (188 features); ofr_2005_1252_beds_line (6 features); and ofr_2005_1252_scarp_line (351 features). Metadata records associated with each of these elements contain more detailed descriptions of their purposes, constituent entities, and attributes. A shapefile (non-geodatabase) version of the dataset is also included, although due to character limits, some field names and text cells in the attribute tables were truncated relative to the equivalent values in the geodatabase. The authors ask that users of the geologic map data cite both the open-file report and the GIS data release: Open-File Report: Troost, K.G., Booth, D.B., Wisher, A.P., and Shimel, S.A., 2005, The geologic map of Seattle—a progress report: U.S. Geological Survey Open-File Report 2005-1252, https://doi.org/10.3133/ofr20051252. GIS data: Troost, K.G., Booth, D.B., Wisher, A.P., and Shimel, S.A., 2024, GIS data for U.S. Geological Survey OFR 2005-1252, The geologic map of Seattle—a progress report: U.S. Geological Survey data release, https://doi.org/10.5066/P93L6SPS.

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

Thank you for your interest in DWR land use datasets.

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

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

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

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

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

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

Crowdsource Polling is a configurable app template that can be used for collecting feedback and assessing public sentiment for a series of proposals, plans, or events. Users are presented with a map and list of features containing the details of each proposal, plan, or event including any attached documents. These users can then submit their feedback in the form of votes and comments. Crowdsource Polling can be accessed anonymously and by authenticating via Twitter.Use CasesCrowdsource Polling can be configured to present information such as:proposed land use changesenvironmental impact pollingpublic comment on capital projectspublic comment on proposed rights of way for transmission systemsevents permit reviewConfigurable OptionsConfigure Crowdsource Polling to present content from any web map and personalize the app by modifying the following options: Display a custom title and logo in the application headerUse a custom color schemeChoose which layer contains the features for which feedback is being solicitedProvide custom instruction on the use of the app, contact information, credits, etc. in a highly configurable help windowSupported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Crowdsource Polling requires a web map with at least one feature layer. In addition, the following requirements must be met to expose full app functionality:To enable votes, this layer must have a numeric field for storing the number of votes on each featureTo collect comments, the feature layer must have a related tableTo capture the names of authenticated users, the layer must have a text field for storing this valueGet Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.Learn MoreFor release notes and more information on configuring this app, see the Crowdsource Polling documentation.

Information Lookup is a configurable web application template that can be used to provide the general public, internal staff and other interested parties with information about a location. If no features are found at that location, a general message is displayed. Optionally, the location entered can be stored in a point layer.Configurable OptionsThe template can be configured using the following options:Lookup Layers: One or more polygon layers queried by the location specified. The pop-up defined in these layers combined into a single pop-up and displayed to the user. The layers can either be a feature service layer or a layer that is part of a dynamic map service. Use a vertical bar or pipe (|) to separate this list of layers. It is recommended that these layers visibility is turned off.Pop-up Title: The title of the pop-up when results are returned from one or more of the Lookup Layers.Pop-up Width: The width of the pop-up. pop-up Max Height: The maximum height title of the pop-up.Unavailable pop-up Title: The title of the pop-up when no results are returned from the Lookup Layers.Unavailable pop-up Message: The message to display in the pop-up when no results are returned from the Lookup Layers.Zoom Level for Location: The scale to set the map at when a location is specified.Store Location: Option to store the location specified in a point layer, if checked on, fill out the remaining parameters.Application Title: Enter a custom title for the application.Storage Layer Name: Name of the point feature service layer in the map to store the location. Editing must be enabled on this layer.Storage Layer Field: Field in the Storage Layer to store a value if a result was returned from the Lookup Layers.Yes Value: The value to store in the Storage Layer Field specified above when a result is returned from the Lookup Layers.No Value: The value to store in the Storage Layer Field specified above when no results are returned from the Lookup Layers.Display Splash Screen on Startup: Option to show a splash screen when the app loads.Splash Screen message: The message to display in the splash screen.Splash Screen Theme: The color scheme for the splash screen.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

This service is available to all ArcGIS Online users with organizational accounts. For more information on this service, including the terms of use, visit us online at https://goto.arcgisonline.com/landscape11/USA_Soils_Map_Units.Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations.Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals.Dataset SummaryPhenomenon Mapped: Soils of the United States and associated territoriesCoordinate System: Web Mercator Auxiliary SphereExtent: The 50 United States, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaVisible Scale: 1:144,000 to 1:1,000Resolution/Tolerance: 1 meter/2 metersNumber of Features: 36,543,233Feature Request Limit: 10,000Source: USDA Natural Resources Conservation ServicePublication Date: October 1, 2019ArcGIS Server URL: https://landscape11.arcgis.com/arcgis/rest/servicesData 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).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 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 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 mapunits have a null value for soil order, a custom script was used to populate this field using the Component Name (compname) and Mapunit Name (muname) fields. This field was created using the dominant soil order of each mapunit.Esri SymbologyHorizon TableEach map unit polygon has one or more components and each component has one or more layers known as horizons. To incorporate this field from the Horizon table into the attributes for this layer, a custom script was used to first calculate the mean value weighted by thickness of the horizon for each component and then a mean value of components weighted by the Component Percentage Representative Value field for each map unit. K-Factor Rock FreeEsri Soil OrderThese fields were calculated from the Component table using a model that included the Pivot Table Tool, the Summarize Tool and a custom script. The first 11 fields provide the sum of Component Percentage Representative Value for each soil order for each map unit. The Soil Order Dominant Condition field was calculated by selecting the highest value in the

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.Geographic 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 SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior 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 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.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.

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 map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations.Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals.Dataset SummaryPhenomenon Mapped: Soils of the United States and associated territoriesCoordinate System: Web Mercator Auxiliary SphereExtent: The 50 United States, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaVisible Scale: 1:144,000 to 1:1,000Number of Features: 36,569,286Source: USDA Natural Resources Conservation ServicePublication Date: December 2021Data from the gSSURGO database was used to create this layer.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 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 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 mapunits have a null value for soil order, a custom script was used to populate this field using the Component Name (compname) and Mapunit Name (muname) fields. This field was created using the dominant soil order of each mapunit.Esri SymbologyHorizon TableEach map unit polygon has one or more components and each component has one or more layers known as horizons. To incorporate this field from the Horizon table into the attributes for this layer, a custom script was used to first calculate the mean value weighted by thickness of the horizon for each component and then a mean value of components weighted by the Component Percentage Representative Value field for each map unit. K-Factor Rock FreeEsri Soil OrderThese fields were calculated from the Component table using a model that included the Pivot Table Tool, the Summarize Tool and a custom script. The first 11 fields provide the sum of Component Percentage Representative Value for each soil order for each map unit. The Soil Order Dominant Condition field was calculated by selecting the highest value in the preceding 11 soil order fields. In the case of tied values the component with the lowest average slope value (slope_r) was selected. If both soil order and slope were tied the first value in the table was selected.Percent AlfisolsPercent AndisolsPercent AridisolsPercent EntisolsPercent GelisolsPercent HistosolsPercent InceptisolsPercent MollisolsPercent SpodosolsPercent UltisolsPercent VertisolsSoil Order - Dominant ConditionEsri Popup StringThis field contains a text string calculated by Esri that is used to create a basic pop-up using some of the more popular SSURGO attributes.Map Unit KeyThe Mapunit key field is found

This rating indicates the percentage of map units that meets the criteria for hydric soils. Map units are composed of one or more map unit components or soil types, each of which is rated as hydric soil or not hydric. Map units that are made up dominantly of hydric soils may have small areas of minor nonhydric components in the higher positions on the landform, and map units that are made up dominantly of nonhydric soils may have small areas of minor hydric components in the lower positions on the landform. Each map unit is rated based on its respective components and the percentage of each component within the map unit. The thematic map is color coded based on the composition of hydric components. The five color classes are separated as 100 percent hydric components, 66 to 99 percent hydric components, 33 to 65 percent hydric components, 1 to 32 percent hydric components, and less than one percent hydric components.In Web Soil Survey, the Summary by Map Unit table that is displayed below the map pane contains a column named 'Rating'.In this column the percentage of each map unit that is classified as hydric is displayed.Hydric soils are defined by the National Technical Committee for Hydric Soils (NTCHS) as soils that formed under conditions of saturation, flooding, or ponding long enough during the growing season to develop anaerobic conditions in the upper part (Federal Register, 1994). Under natural conditions, these soils are either saturated or inundated long enough during the growing season to support the growth and reproduction of hydrophytic vegetation. The NTCHS definition identifies general soil properties that are associated with wetness. In order to determine whether a specific soil is a hydric soil or nonhydric soil, however, more specific information, such as information about the depth and duration of the water table, is needed. Thus, criteria that identify those estimated soil properties unique to hydric soils have been established (Federal Register, 2002). These criteria are used to identify map unit components that normally are associated with wetlands. The criteria used are selected estimated soil properties that are described in "Soil Taxonomy" (Soil Survey Staff, 1999) and "Keys to Soil Taxonomy" (Soil Survey Staff, 2006) and in the "Soil Survey Manual" (Soil Survey Division Staff, 1993). If soils are wet enough for a long enough period of time to be considered hydric, they should exhibit certain properties that can be easily observed in the field. These visible properties are indicators of hydric soils. The indicators used to make onsite determinations of hydric soils are specified in "Field Indicators of Hydric Soils in the United States" (Hurt and Vasilas, 2006).

Water system network including diameter and material. No warranty is expressed or implied as to the accuracy of the information provided. Data is provided for general reference only and is NOT spatially accurate for construction purposes nor does it replace the need for a field locate survey.About the Division The mission of the Division of Water is to provide its customers with reliable drinking water that meets or exceeds Ohio Environmental Protection Agency (OEPA) standards. We strive to provide the best customer service, manage our infrastructure to meet present and future needs, and make every attempt to minimize economic impact to our water customers The Division of Water is divided in to two groups: Distribution and Treatment. Distribution The primary areas of responsibility for distribution include the maintenance and replacement of the following infrastructure: Fire HydrantsValvesWater MainsOther infrastructure including our reservoir and pump stationThis infrastructure is made up of 120 miles of water lines ranging in sizes from ¾” up to 36” in diameter. This department replaces outdated water lines through out the city while maintaining existing facilities.