You have been assigned a new project, which you have researched, and you have identified the data that you need.The next step is to gather, organize, and potentially create the data that you need for your project analysis.In this course, you will learn how to gather and organize data using ArcGIS Pro. You will also create a file geodatabase where you will store the data that you import and create.After completing this course, you will be able to perform the following tasks:Create a geodatabase in ArcGIS Pro.Create feature classes in ArcGIS Pro by exporting and importing data.Create a new, empty feature class in ArcGIS Pro.

WSDOT template for Esri file geodatabase polygon feature class. Template has pre-defined attribute schema to help users create data that is more consistent or compliant with agency standards. Metadata has been created using the FGDC metadata style but stored in the ArcGIS format. Content presentation will change upon export to FGDC format.This service is maintained by the WSDOT Transportation Data, GIS & Modeling Office. If you are having trouble viewing the service, please contact Online Map Support at onlinemapsupport@wsdot.wa.gov.

This ESRI featureclass and associated metadata is a template. Attribute schema is pre-defined to help users create data that is more consistent or compliant with agency standards.Metadata has been created using the FGDC metadata style but stored in the ArcGIS Format. Content presentation will change upon export to FGDC format.

Summary This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a _location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point _location. GPS started being used in 1992 when the technology became available. Records from FMIS (Fire Management Information System) were reviewed and compared to refuge records. Polygon data in FMIS only occurs from 2012 to current and many acreage estimates did not match. This dataset includes ALL fires no matter the size. This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a _location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point _location. GPS started being used in 1992 when the technology became available. Data origins include: Data origins include: 1) GPS Polygon-data (Best), 2) GPS Lat/Long or UTM, 3)TRS QS, 4)TRS Point, 6)Hand digitized from topo map, 7) Circle buffer, 8)Screen digitized, 9) FMIS Lat/Long. Started compiling fire history of CMR in 2007. This has been a 10 year process.FMIS doesn't include fires polygons that are less than 10 acres. This dataset has been sent to FMIS for FMIS records to be updated with correct information. The spreadsheet contains 10-15 records without spatial information and weren't included in either feature class. Fire information from 1964 - 1980 came from records Larry Eichhorn, BLM, provided to CMR staff. Mike Granger, CMR Fire Management Officer, tracked fires on an 11x17 legal pad and all this information was brought into Excel and ArcGIS. Frequently, other information about the fires were missing which made it difficult to back track and fill in missing data. Time was spent verifiying locations that were occasionally recorded incorrectly (DMS vs DD) and converting TRS into Lat/Long and/or UTM. CMR is divided into 2 different UTM zones, zone 12 and zone 13. This occasionally caused errors in projecting. Naming conventions caused confusion. Fires are frequently names by _location and there are several "Soda Creek", "Rock Creek", etc fires. Fire numbers were occasionally missing or incorrect. Fires on BLM were included if they were "Assists". Also, fires on satellite refuges and the district were also included. Acreages from GIS were compared to FMIS acres. Please see documentation in ServCat (URL) to see how these were handled.

December 11, 2018This layer was edited to reflect an Annexation. See Changes Feature Class for details.=================================================October 24, 2018This layer was edited to reflect an Annexation. See Changes Feature Class for details.=================================================August 27, 2018This layer was edited to reflect an Annexation. See Changes Feature Class for details.=================================================May 1, 2018This layer was edited to reflect some Reorganizations. See Changes Feature Class for details.=================================================April 9, 2018This layer was edited to reflect a Reorganization. See Changes Feature Class for details.=================================================February 2, 2018This layer was edited to reflect a Reorganization. See Changes Feature Class for details.=================================================December 15 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.=================================================December 15 2017The update metadata is now being placed in this Description field so it is more compatible with ArcGIS Pro, and easier to update.=================================================November 17, 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================October 30, 2017This layer was edited to reflect some Adjustments. See Changes Feature Class for details.==================================================September 27, 2017This layer was edited to reflect several Reorganizations. See Changes Feature Class for details.==================================================August 18, 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================June 30, 2017This layer was edited to reflect an Annexation and a Reorganization. See Changes Feature Class for details.==================================================June 12-14, 2017This layer was edited to reflect several Corrections. See Changes Feature Class for details.==================================================April 25, 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================March 16, 2017This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================February 6, 2017This layer was edited to reflect some corrections. See Changes Feature Class for details.==================================================January 19, 2017This layer was edited to reflect a correction. See Changes Feature Class for details.==================================================November 18, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================October 3, 2016This layer was edited to reflect a correction. See Changes Feature Class for details.==================================================September 12, 2016This layer was edited to reflect a reorganization and an annexation. See Changes Feature Class for details.==================================================May 17, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================April 4, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================March 18, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================January 29, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================January 26, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================December 11, 2015This layer was edited to reflect a Correction-Annexation and an Adjustment. See Changes Feature Class for details.==================================================November 13, 2015This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================September 22, 2015This layer was edited to reflect an adjustment. See Changes Feature Class for details.==================================================September 10, 2015This layer was edited to reflect a Reorganization and USA Amendment. See Changes Feature Class for details.==================================================June 12, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================April 2, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================March 19, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================February 19, 2015This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================January 9, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================December 30, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================December 12, 2014This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================October 7, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================Aug 26-29, 2014This layer was edited to reflect some Corrections. See Changes Feature Class for details.==================================================July 7, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================June 30, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================June 12, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================May 23, 2014This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================May 9, 2014This layer was edited to reflect a Reorganization and some Annexations. See Changes Feature Class for details.==================================================March 4, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================February 24, 2014This layer was edited to reflect some Reorganizations. See Changes Feature Class for details.==================================================November 1, 2013This layer was edited to reflect some Reorganizations. See Changes Feature Class for details.==================================================October 7-8, 2013This layer was edited to reflect some changes. See Changes Feature Class for details.==================================================July 15, 2013This layer was edited to reflect an Annexation. See Changes Feature Class for details.==================================================April 29, 2013This layer was edited to reflect several Changes. See Changes Feature Class for details.===================================================March 26-27, 2013This layer was edited to reflect a Correction. See Changes Feature Class for details.===================================================January 17, 2013This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================January 11, 2013This layer was edited to reflect a Correction. See Changes Feature Class for details.===================================================January 8, 2013This layer was edited to reflect some Annexations. See Changes Feature Class for details.===================================================December 18, 2012This layer was edited to reflect an Annexation. See Changes Feature Class for details.===================================================December 3, 2012This layer was edited to reflect an Annexation. See Changes Feature Class for details.===================================================October 30, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================October 3, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================September 26-27, 2012This layer was edited to reflect some Corrections. See Changes Feature Class for details.===================================================August 24, 2012This layer was edited to reflect an Annexation and Reorganization. See Changes Feature Class for details.===================================================June 15, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================March 15, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================Feb 22, 2012This layer was edited to reflect some Corrections. See Changes Feature Class for details.===================================================Jan 17-18, 2012This layer was edited to reflect some Changes. See Changes Feature Class for details.===================================================Oct 26, 2011This

These data were compiled for the use of training natural feature machine learning (GeoAI) detection and delineation. The natural feature classes include the Geographic Names Information System (GNIS) feature types Basins, Bays, Bends, Craters, Gaps, Guts, Islands, Lakes, Ridges and Valleys, and are an areal representation of those GNIS point features. Features were produced using heads-up digitizing from 2018 to 2019 by Dr. Sam Arundel's team at the U.S. Geological Survey, Center of Excellence for Geospatial Information Science, Rolla, Missouri, USA, and Dr. Wenwen Li's team in the School of Geographical Sciences at Arizona State University, Tempe, Arizona, USA.

LouVelo is a docked bikeshare program owned by Louisville Metro Government and operated by Cyclehop since May of 2017. The System includes Approximately 250 bikes, 25 Docked Stations in Louisville, and an additional 3 stations owned and operated by the City of Jeffersonville in Partnership with Cyclehop. These data will be updated on a monthly basis to show monthly trends in ridership along with general patterns of use with pick up and drop off location data. These data are updated and maintained for use in the Louisville Metro Open Data Portal LouVelo Dashboard to show ridership for the entirety of the program. Some stations have been relocated since the programs founding. For up to date information on dock locations please view the system map on the LouVelo website. This dashboard is maintained by Louisville Metro Public Works.For any questions please contact:James GrahamMobility CoordinatorLouisville Metro Public WorksDivision of Transportation444 S. 5th, St, Suite 400Louisville, KY 40202(502) 574-6473james.graham@louisvilleky.govFor more information about the LouVelo bikeshare program please visit their website.

Sept 5, 2018This layer was edited to reflect some Reorganizations. See Changes Feature Class for details.=================================================May 1, 2018This layer was edited to reflect some Reorganizations. See Changes Feature Class for details.=================================================April 9, 2018This layer was edited to reflect a Reorganization. See Changes Feature Class for details.=================================================February 2, 2018This layer was edited to reflect a Reorganization. See Changes Feature Class for details.=================================================December 15 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.=================================================December 15 2017The update metadata is now being placed in this Description field so it is more compatible with ArcGIS Pro, and easier to update.=================================================November 17, 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================October 30, 2017This layer was edited to reflect some Adjustments. See Changes Feature Class for details.==================================================September 27, 2017This layer was edited to reflect several Reorganizations. See Changes Feature Class for details.==================================================August 18, 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================June 30, 2017This layer was edited to reflect an Annexation and a Reorganization. See Changes Feature Class for details.==================================================June 12-14, 2017This layer was edited to reflect several Corrections. See Changes Feature Class for details.==================================================April 25, 2017This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================March 16, 2017This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================February 6, 2017This layer was edited to reflect some corrections. See Changes Feature Class for details.==================================================January 19, 2017This layer was edited to reflect a correction. See Changes Feature Class for details.==================================================November 18, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================October 3, 2016This layer was edited to reflect a correction. See Changes Feature Class for details.==================================================September 12, 2016This layer was edited to reflect a reorganization and an annexation. See Changes Feature Class for details.==================================================May 17, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================April 4, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================March 18, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================January 29, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================January 26, 2016This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================December 11, 2015This layer was edited to reflect a Correction-Annexation and an Adjustment. See Changes Feature Class for details.==================================================November 13, 2015This layer was edited to reflect a reorganization. See Changes Feature Class for details.==================================================September 22, 2015This layer was edited to reflect an adjustment. See Changes Feature Class for details.==================================================September 10, 2015This layer was edited to reflect a Reorganization and USA Amendment. See Changes Feature Class for details.==================================================June 12, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================April 2, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================March 19, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================February 19, 2015This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================January 9, 2015This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================December 30, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================December 12, 2014This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================October 7, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================Aug 26-29, 2014This layer was edited to reflect some Corrections. See Changes Feature Class for details.==================================================July 7, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================June 30, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================June 12, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================May 23, 2014This layer was edited to reflect a Correction. See Changes Feature Class for details.==================================================May 9, 2014This layer was edited to reflect a Reorganization and some Annexations. See Changes Feature Class for details.==================================================March 4, 2014This layer was edited to reflect a Reorganization. See Changes Feature Class for details.==================================================February 24, 2014This layer was edited to reflect some Reorganizations. See Changes Feature Class for details.==================================================November 1, 2013This layer was edited to reflect some Reorganizations. See Changes Feature Class for details.==================================================October 7-8, 2013This layer was edited to reflect some changes. See Changes Feature Class for details.==================================================July 15, 2013This layer was edited to reflect an Annexation. See Changes Feature Class for details.==================================================April 29, 2013This layer was edited to reflect several Changes. See Changes Feature Class for details.===================================================March 26-27, 2013This layer was edited to reflect a Correction. See Changes Feature Class for details.===================================================January 17, 2013This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================January 11, 2013This layer was edited to reflect a Correction. See Changes Feature Class for details.===================================================January 8, 2013This layer was edited to reflect some Annexations. See Changes Feature Class for details.===================================================December 18, 2012This layer was edited to reflect an Annexation. See Changes Feature Class for details.===================================================December 3, 2012This layer was edited to reflect an Annexation. See Changes Feature Class for details.===================================================October 30, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================October 3, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================September 26-27, 2012This layer was edited to reflect some Corrections. See Changes Feature Class for details.===================================================August 24, 2012This layer was edited to reflect an Annexation and Reorganization. See Changes Feature Class for details.===================================================June 15, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================March 15, 2012This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================Feb 22, 2012This layer was edited to reflect some Corrections. See Changes Feature Class for details.===================================================Jan 17-18, 2012This layer was edited to reflect some Changes. See Changes Feature Class for details.===================================================Oct 26, 2011This layer was edited to reflect a Reorganization. See Changes Feature Class for details.===================================================Oct 20, 2011This layer was edited to reflect some Corrections. See Changes Feature Class for details.===================================================Oct 14, 2011This

The Geodatabase to Shapefile Warning Tool examines feature classes in input file geodatabases for characteristics and data that would be lost or altered if it were transformed into a shapefile. Checks include:
1) large files (feature classes with more than 255 fields or over 2GB), 2) field names longer than 10 characters
string fields longer than 254 characters, 3) date fields with time values 4) NULL values, 5) BLOB, guid, global id, and raster field types, 6) attribute domains or subtypes, and 7) annotation or topology

The results of this inspection are written to a text file ("warning_report_[geodatabase_name]") in the directory where the geodatabase is located. A section at the top provides a list of feature classes and information about the geodatabase as a whole. The report has a section for each valid feature class that returned a warning, with a summary of possible warnings and then more details about issues found.

The tool can process multiple file geodatabases at once. A separate text file report will be created for each geodatabase. The toolbox was created using ArcGIS Pro 3.7.11.

For more information about this and other related tools, explore the Geospatial Data Curation toolkit

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

WSDOT template for Esri file geodatabase point feature class. Template has pre-defined attribute schema to help users create data that is more consistent or compliant with agency standards. Metadata has been created using the FGDC metadata style but stored in the ArcGIS format. Content presentation will change upon export to FGDC format.This service is maintained by the WSDOT Transportation Data, GIS & Modeling Office. If you are having trouble viewing the service, please contact Online Map Support at onlinemapsupport@wsdot.wa.gov.

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.

The Digital Shoreline Analysis System (DSAS) is a freely available software application that works within the Environmental Systems Research Institute (ESRI) Geographic Information System (ArcGIS) software. DSAS computes rate-of-change statistics for a time series of shoreline vector data. Additionally, the DSAS application is useful for computing rates of change for any boundary-change problem that incorporates a clearly-identified feature position at discrete times, such as glacier limits, river banks, or land use/cover boundaries. The "bias feature" is a shapefile representation the proxy-datum bias (PDB) data previously published in tabular format (Himmelstoss and others 2010, Himmelstoss and others 2018). These PDB data are used to shift older proxy-based shorelines so that they can be directly compared to newer datum-based shorelines and accurate rates can be calculated.

The Watershed Condition Classification feature class represents data on Watershed Condition on Forest Service lands in HUC12 (from the Watershed Boundary Dataset) watersheds that contain more than 5% USFS ownership. The feature class also includes data on high priority watersheds identified in the Watershed Condition Framework (WCF) process. The WCF data identifies priority watersheds, rationale for their designation as such, and information on Watershed Restoration Action Plans. The data are compiled from the NRM Watershed Condition Assesment and Tracking Tool (WCATT) application. Metadata

SLIDO-4.4 is an Esri ArcGIS version 10.7.1 file geodatabase. The geodatabase contains two feature datasets (a group of datasets within the geodatabase) containing six feature classes total and five individual feature classes. SLIDO-4.4 includes 55,736 landslide polygons in the Deposits feature class dataset and 14,985 historic landslide points locations compiled from 365 studies. The original studies vary widely in scale, scope and focus which is reflected in the wide range of accuracy, detail, and completeness with which landslides are mapped. In the future, we propose a continuous update of SLIDO. These updates should take place: 1) each time DOGAMI publishes a new GIS dataset that contains landslide inventory or susceptibility data or 2) at the end of each winter season, a common time for landslide occurrences in Oregon, which will include recent historic landslide point data. In order to keep track of the updates, we will use a primary release number such as Release 4.0 along with a decimal number identifying the update such as 4.1.

Railroad Lines dataset current as of 2001. This is an ESRI feature class of Railroads within Rock County, Wisconsin..

Personal Geodatabase Esri format, Arcgis v 10. 4, corresponding to the geological map of Figure 1.2. The personal geodatabase contains one feature dataset 'Geology', which in turn contains a polygon feature class 'Surface' and a polyline feature class 'Line'.

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.

This Quarter Section feature class depicts PLSS Second Divisions . PLSS townships are subdivided in a spatial hierarchy of first, second, and third division. These divisions are typically aliquot parts ranging in size from 640 acres to 160 to 40 acres, and subsequently all the way down to 2.5 acres. The data in this feature class was translated from the PLSSSecondDiv feature class in the original production data model, which defined the second division for a specific parcel of land. Metadata

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.