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.

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.

The Washington State Surface Geology Map scale at a scale of 1:24,000 geodatabase was made accessible through the Washington State Department of Natural Resources, Division of Geology and Earth Resources. The data are provided in ESRI ArcGIS 10.0 file geodatabase format (see Read Me file). The projection is in Lambert Conformal Conic, NAD83 HARN datum. Data available for download include:- One ESRI ArcGIS 10.0 geodatabase, consisting of a set of 11 feature classes, 7 relationship classes, and one geodatabase table.- Metadata for each feature class, in both XML and HTML formats (for ease of reading outside of GIS software)- One shapefile depicting the outline of Washington State.- One ArcGIS map document (ending in the .mxd extension), containing specifications for data presentation in ArcMap- One ArcGIS layer file for each feature class (ending in the .lyr extension), containing specifications for data presentation in an ArcGIS viewing application- One Geologic Map Codes document (PDF) defining the symbology used in the map.- The README file These digital data and metadata are provided as is, as available, and with all faults basis. Neither Department of Natural Resources nor any of its officials and employees makes any warranty of any kind for this information, express or implied, including but not limited to any warranties of merchantability or fitness for a particular purpose, nor shall the distribution of this information constitute any warranty. This resource was provided by the Washington State Department of Natural Resources, Division of Geology and Earth Resources and made available for distribution through the National Geothermal Data System.

Ground response--GIS data, June 2010. Downloadable GIS data includes: One ESRI ArcGIS 9.3 geodatabase, consisting of a set of 4 feature classes; Metadata for each feature class, in HTML format (for ease of reading outside of GIS software); One ArcGIS map document (ending in the .mxd extension), containing specifications for data presentation in ArcMap; One ArcGIS layer file for each feature class (ending in the .lyr extension), containing specifications for data presentation in the free ArcGIS Explorer (as well as ArcMap); README file

The data in this map service is updated every weekend.Note: This data includes all activities regardless of whether there is a spatial feature attached.Note: This is a large dataset. Metadata and Downloads are available at: https://data.fs.usda.gov/geodata/edw/datasets.php?xmlKeyword=FACTS+common+attributesTo download FACTS activities layers, search for the activity types you want, such as timber harvest or hazardous fuels treatments. The Forest Service's Natural Resource Manager (NRM) Forest Activity Tracking System (FACTS) is the agency standard for managing information about activities related to fire/fuels, silviculture, and invasive species. This feature class contains the FACTS attributes most commonly needed to describe FACTS activities.This record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService CSV Shapefile GeoJSON KML https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_ActivityFactsCommonAttributes_01/MapServer/0 Geodatabase Download Shapefile Download For complete information, please visit https://data.gov.

This ArcGIS model inserts a file name into a feature class attribute table. The tool allows an user to identify features by a field that reference the name of the original file. It is useful when an user have to merge multiple feature classes and needs to identify which layer the features come from.

The Digital Geologic Units of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina consists of geologic units mapped as area (polygon) features. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). The data were captured, grouped and attributed as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.3.1. (available at: https://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The data layer is available as a feature class in a 9.1 personal geodatabase (grsm_geology.mdb). Attributed geologic contact lines that define the geologic unit polygons are present within the Geologic Contacts (GRSMGLGA) data layer. The Geologic Units (GRSMGLG) GIS data layer is also available as a coverage export (.E00) file (GRSMGLG.E00), and as a shapefile (.SHP) file (GRSMGLG.SHP). Each GIS data format has an ArcGIS 9.1 layer (.LYR) file (GRSMGLG_GDB.LYR (geodatabase feature class), GRSMGLG_COV.LYR (coverage), GRSMGLG_SHP.LYR (shapefile) with map symbology that is included with the GIS data. See the Distribution Information section for additional information on data acquisition. The GIS data projection is NAD83, UTM Zone 17N. That data is within the area of interest of Great Smoky Mountains National Park. This dataset is just one component of the Digital Geologic Map of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina. The data layers (feature classes) that comprise the Digital Geologic Map of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina include: GRSMAML (Alteration and Metamorphic Lines), GRSMATD (Geologic Attitude and Observation Points), GRSMFLD (Folds), GRSMFLT (Faults), GRSMGLG (Geologic Units), GRSMGLGA (Geologic Contacts), GRSMGPT (Point Geologic Features), GRSMGSL (Geologic Sample Localities), GRSMMIN (Mine Point Features), GRSMSEC (Cross Section Lines), GRSMSUR (Surficial Geologic Units), GRSMSURA (Surficial Contacts) and GRSMSYM (Fault Symbology). There are three additional ancillary map components, the Geologic Unit Information (GRSMGLG1) Table, the Source Map Information (GRSMMAP) Table and the Map Help File (GRSM_GEOLOGY.HLP). Refer to the NPS GRE Geology-GIS Geodatabase Data Model v. 1.3.1 (available at: https://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm) for detailed data layer (feature class) and table specifications including attribute field parameters, definitions and domains, and implemented topology rules and relationship classes.The corresponding Integration of Resource Management Applications (IRMA) NPS Data Store reference is Great Smoky Mountains National Park Geology.

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 GIS-usable format employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 16, using North American Datum of 1983 (NAD83). To produce a polygon vector layer for use in ArcGIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcGIS (Version 9.2, © 2006 Environmental Systems Research Institute, Redlands, California). 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 of INDU and immediate environs. 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, link to NVC association and alliance codes), 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 sites, 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.

This data release contains the analytical results and evaluated source data files of geospatial analyses for identifying areas in Alaska that may be prospective for different types of lode gold deposits, including orogenic, reduced-intrusion-related, epithermal, and gold-bearing porphyry. The spatial analysis is based on queries of statewide source datasets of aeromagnetic surveys, Alaska Geochemical Database (AGDB3), Alaska Resource Data File (ARDF), and Alaska Geologic Map (SIM3340) within areas defined by 12-digit HUCs (subwatersheds) from the National Watershed Boundary dataset. The packages of files available for download are: 1. LodeGold_Results_gdb.zip - The analytical results in geodatabase polygon feature classes which contain the scores for each source dataset layer query, the accumulative score, and a designation for high, medium, or low potential and high, medium, or low certainty for a deposit type within the HUC. The data is described by FGDC metadata. An mxd file, and cartographic feature classes are provided for display of the results in ArcMap. An included README file describes the complete contents of the zip file. 2. LodeGold_Results_shape.zip - Copies of the results from the geodatabase are also provided in shapefile and CSV formats. The included README file describes the complete contents of the zip file. 3. LodeGold_SourceData_gdb.zip - The source datasets in geodatabase and geotiff format. Data layers include aeromagnetic surveys, AGDB3, ARDF, lithology from SIM3340, and HUC subwatersheds. The data is described by FGDC metadata. An mxd file and cartographic feature classes are provided for display of the source data in ArcMap. Also included are the python scripts used to perform the analyses. Users may modify the scripts to design their own analyses. The included README files describe the complete contents of the zip file and explain the usage of the scripts. 4. LodeGold_SourceData_shape.zip - Copies of the geodatabase source dataset derivatives from ARDF and lithology from SIM3340 created for this analysis are also provided in shapefile and CSV formats. The included README file describes the complete contents of the zip file.

The Geopspatial Fabric provides a consistent, documented, and topologically connected set of spatial features that create an abstracted stream/basin network of features useful for hydrologic modeling.The GIS vector features contained in this Geospatial Fabric (GF) data set cover the lower 48 U.S. states, Hawaii, and Puerto Rico. Four GIS feature classes are provided for each Region: 1) the Region outline ("one"), 2) Points of Interest ("POIs"), 3) a routing network ("nsegment"), and 4) Hydrologic Response Units ("nhru"). A graphic showing the boundaries for all Regions is provided at http://dx.doi.org/doi:10.5066/F7542KMD. These Regions are identical to those used to organize the NHDPlus v.1 dataset (US EPA and US Geological Survey, 2005). Although the GF Feature data set has been derived from NHDPlus v.1, it is an entirely new data set that has been designed to generically support regional and national scale applications of hydrologic models. Definition of each type of feature c ...

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 below RECAREAACTIVITIES: 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

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.

These are Rights-of-Ways (ROW) on Idaho BLM land (and some other Federal agency land) as shown on Bureau of Land Management (BLM) Master Title Plats (MTP). Every GIS ROW feature has a "CASEFILE" value, also known as the serial number of the ROW. This corresponds to the LR2000 database, which is a national BLM database for federal lands information. This GIS ROW feature class can be joined or related to exported information from LR2000 using the "CASEFILE" (GIS) and "SERIAL_NR_FULL" (LR2000) fields. NOTE: the LR2000 information is only available to internal BLM users and is not available to the public as it contains sensitive information. This ROW data for any given area may not be complete due to new ROW activity or because of missed or coincident ROW features during the initial data creation. It is recommended that a thorough inventory of all ROWs in a specific project area be obtained (an LR2000 report can provide this) and the GIS ROW data be checked before using this data for projects needing utmost ROW accuracy. The ROW data that was digitized is what was present on the MTP at the time of the digitizing done for that township. The project was performed over several years. Therefore, the "early" townships digitized are more out of date regarding ROWs compared to the ones more recently digitized. Unfortunately, there is no attribute that indicates the digitizing sequence. Any updates to this ROW feature class should be sent to the BLM Idaho State Office GIS staff for incorporation into the statewide GIS ROW feature classes for improvement over time. For more information contact us at blm_id_stateoffice@blm.gov.

This is a MD iMAP hosted service. Find more information on http://imap.maryland.gov. The MD_Surface_Waters Feature Dataset includes 7 feature classes that geospatially depict the surface water bodies of Maryland. These feature classes are being provided so that data from the 2012 Integrated Report of Surface Water Quality can be displayed in geographic form for users of all levels. These different feature classes represent the different assessment unit scales utilized on the 2012 IR - some of which overlap in space. In addition - provided in the attribute tables for the Impoundments - Rivers_Streams - and Tidal_Waters feature classes is the use class designation as specified in COMAR Section 26.08.02.08. More information about these feature classes is contained in the metadata for each feature class. Map Service Link: http://mdewin64.mde.state.md.us/arcgis/rest/services/ MDE_Water_Quality/MD_IntegratedReportSurfaceWaterQuality_2013/MapServer ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

The Trails Layer is designed to provide information about National Forest System trail locations and characteristics to the public. When fully realized, it will describe trail locations, basic characteristics of the trail, and where and when various trail uses are prohibited, allowed and encouraged. Because the data readiness varies between Forests, each Forest will approve which level of attribute subset are published for that forest. Forests can provide no information or one of three attribute subsets describing trails. The attribute subsets include TrailNFS_Centerline which includes the location and trail name and number; TrailNFS_Basic which adds information about basic trail characteristics; and TrailNFS_Mgmt which adds information about where and when users are prohibited, allowed, and encouraged. When a Forest chooses to provide the highest attribute subset, TrailNFS_Mgmt, these attributes must be consistent with the Forest's published Motorized Vehicle Use Map (MVUM). Metadata for the individual Forest feature classes used to compile this feature class are available at data.fs.usda.gov/geodata/edw/dir_trails.php. Metadata

The National Center for Education Statistics' (NCES) Education Demographic and Geographic Estimate (EDGE) program develops annually updated point locations (latitude and longitude) for public elementary and secondary schools included in the NCES Common Core of Data (CCD). The CCD program annually collects administrative and fiscal data about all public schools, school districts, and state education agencies in the United States. The data are supplied by state education agency officials and include basic directory and contact information for schools and school districts, as well as characteristics about student demographics, number of teachers, school grade span, and various other administrative conditions. CCD school and agency point locations are derived from reported information about the physical location of schools and agency administrative offices. The point locations and administrative attributes in this data layer were developed from the 2020-2021 CCD collection. For more information about NCES school point data, see: https://nces.ed.gov/programs/edge/Geographic/SchoolLocations. For more information about these CCD attributes, as well as additional attributes not included, see: https://nces.ed.gov/ccd/files.asp.Notes: -1 or M Indicates that the data are missing. -2 or N Indicates that the data are not applicable. -9 Indicates that the data do not meet NCES data quality standards. All information contained in this file is in the public domain. Data users are advised to review NCES program documentation and feature class metadata to understand the limitations and appropriate use of these data.