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.

In this course, you will learn about some common types of data used for GIS mapping and analysis, and practice adding data to a file geodatabase to support a planned project.Goals Create a file geodatabase. Add data to a file geodatabase. Create an empty geodatabase feature class.

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.

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 feature class is the asset inventory for ADA Ramps within unincorporated King County. This data begins as an event table and edited via the Roads Asset Event Editor application. A nightly process places the events on roadsegment_route feature class to be exported to a feature class in the RoadsGIS geodatabase.

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

WSDOT template for Esri file geodatabase line 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 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.

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.

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.

ESRI line feature class representing City of Somerville, Massachusetts street centerlines. Last updated November 4, 2024.

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.

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 trends in station use. 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.

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 dataset contains the recreation opportunity information that the Forest Service collects through the Recreation Portal and shares with the public on https://www.recreation.gov, the Forest Service World Wide Web pages (https://www.fs.usda.gov/) and the Interactive Visitor Map. This recreation data contains detailed descriptions of recreational sites, areas, activities & facilities. This published dataset consists of one point feature class for recreational areas, one spatial view and three related tables such as activities, facilities & rec area advisories. The purpose of each related table is described belowRECAREAACTIVITIES: This related table contains information about the activities that are associated with the rec area.RECAREAFACILITIES: This related table contains information about the amenities that are associated with the rec area.RECAREAADVISORIES: This table contains events, news, alerts and warnings that are associated with the rec area.RECAREAACTIVITIES_V: This spatial view/feature class is generated by joining the RECAREAACTIVITIES table to the RECREATION OPPORTUNITIES Feature Class. Please note that the RECAREAID is the unique identifier present in point feature class and in the related tables as well. The RECAREAID is used as foreign key to access relate records.This published data is updated nightly from an XML feed maintained by the CIO Rec Portal team. This data is intended for public use and distribution. Metadata

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 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.

This digital dataset was created as part of a U.S. Geological Survey study, done in cooperation with the Monterey County Water Resource Agency, to conduct a hydrologic resource assessment and develop an integrated numerical hydrologic model of the hydrologic system of Salinas Valley, CA. As part of this larger study, the USGS developed this digital dataset of geologic data and three-dimensional hydrogeologic framework models, referred to here as the Salinas Valley Geological Framework (SVGF), that define the elevation, thickness, extent, and lithology-based texture variations of nine hydrogeologic units in Salinas Valley, CA. The digital dataset includes a geospatial database that contains two main elements as GIS feature datasets: (1) input data to the 3D framework and textural models, within a feature dataset called “ModelInput”; and (2) interpolated elevation, thicknesses, and textural variability of the hydrogeologic units stored as arrays of polygonal cells, within a feature dataset called “ModelGrids”. The model input data in this data release include stratigraphic and lithologic information from water, monitoring, and oil and gas wells, as well as data from selected published cross sections, point data derived from geologic maps and geophysical data, and data sampled from parts of previous framework models. Input surface and subsurface data have been reduced to points that define the elevation of the top of each hydrogeologic units at x,y locations; these point data, stored in a GIS feature class named “ModelInputData”, serve as digital input to the framework models. The location of wells used a sources of subsurface stratigraphic and lithologic information are stored within the GIS feature class “ModelInputData”, but are also provided as separate point feature classes in the geospatial database. Faults that offset hydrogeologic units are provided as a separate line feature class. Borehole data are also released as a set of tables, each of which may be joined or related to well location through a unique well identifier present in each table. Tables are in Excel and ascii comma-separated value (CSV) format and include separate but related tables for well location, stratigraphic information of the depths to top and base of hydrogeologic units intercepted downhole, downhole lithologic information reported at 10-foot intervals, and information on how lithologic descriptors were classed as sediment texture. Two types of geologic frameworks were constructed and released within a GIS feature dataset called “ModelGrids”: a hydrostratigraphic framework where the elevation, thickness, and spatial extent of the nine hydrogeologic units were defined based on interpolation of the input data, and (2) a textural model for each hydrogeologic unit based on interpolation of classed downhole lithologic data. Each framework is stored as an array of polygonal cells: essentially a “flattened”, two-dimensional representation of a digital 3D geologic framework. The elevation and thickness of the hydrogeologic units are contained within a single polygon feature class SVGF_3DHFM, which contains a mesh of polygons that represent model cells that have multiple attributes including XY location, elevation and thickness of each hydrogeologic unit. Textural information for each hydrogeologic unit are stored in a second array of polygonal cells called SVGF_TextureModel. The spatial data are accompanied by non-spatial tables that describe the sources of geologic information, a glossary of terms, a description of model units that describes the nine hydrogeologic units modeled in this study. A data dictionary defines the structure of the dataset, defines all fields in all spatial data attributer tables and all columns in all nonspatial tables, and duplicates the Entity and Attribute information contained in the metadata file. Spatial data are also presented as shapefiles. Downhole data from boreholes are released as a set of tables related by a unique well identifier, tables are in Excel and ascii comma-separated value (CSV) format.

Flood and Coastal Risk Management - Incident Management.

Impact cell feature class dataset relates to flood zones and has data for impact cells that are outside flood zone 3 but inside flood zone 2. This is a spatial dataset.