Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.
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.
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.
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
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
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.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Hydrography dataset current as of 2000. Polygon feature class in ESRI format.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
TransportationThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau, displays primary roads, secondary roads, local roads and railroads in the United States. According to the USCB, "This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways."Interstates 20 and 635Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (TIGERweb/Transportation) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 155 (Series Information for All Roads County-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Transportation - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Census Feature Class Codes (CFCC)For feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
TransportationThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau, displays primary roads, secondary roads, local roads and railroads in the United States. According to the USCB, "This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways."Interstates 20 and 635Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (TIGERweb/Transportation) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 155 (Series Information for All Roads County-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Transportation - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Census Feature Class Codes (CFCC)For feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets
description: County and Parish Boundaries dataset current as of 1990. Townships - polygon feature class in ESRI format.; abstract: County and Parish Boundaries dataset current as of 1990. Townships - polygon feature class in ESRI 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.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.
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.
description: Fire and EMS Districts dataset current as of 2000. Polygon feature class in ESRI format.; abstract: Fire and EMS Districts dataset current as of 2000. Polygon feature class in ESRI format.
This packaged data collection contains two sets of two additional model runs that used the same inputs and parameters as our primary model, with the exception being we implemented a "maximum corridor length" constraint that allowed us to identify and visualize the corridors as being well-connected (≤15km) or moderately connected (≤45km). This is based on an assumption that corridors longer than 45km are too long to sufficiently accommodate dispersal. One of these sets is based on a maximum corridor length that uses Euclidean (straight-line) distance, while the other set is based on a maximum corridor length that uses cost-weighted distance. These two sets of corridors can be compared against the full set of corridors from our primary model to identify the remaining corridors, which could be considered poorly connected. This package includes the following data layers: Corridors classified as well connected (≤15km) based on Cost-weighted Distance Corridors classified as moderately connected (≤45km) based on Cost-weighted Distance Corridors classified as well connected (≤15km) based on Euclidean Distance Corridors classified as moderately connected (≤45km) based on Euclidean Distance Please refer to the embedded metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in raster GeoTIFF (.tif) format.
ESRI line feature class representing City of Somerville, Massachusetts street centerlines. Last updated November 4, 2024.
Laatste update: 07 december 2023
This dataset contains 50-ft contours for the Hot Springs shallowest unit of the Ouachita Mountains aquifer system potentiometric-surface map. The potentiometric-surface shows altitude at which the water level would have risen in tightly-cased wells and represents synoptic conditions during the summer of 2017. Contours were constructed from 59 water-level measurements measured in selected wells (locations in the well point dataset). Major streams and creeks were selected in the study area from the USGS National Hydrography Dataset (U.S. Geological Survey, 2017), and the spring point dataset with 18 spring altitudes calculated from 10-meter digital elevation model (DEM) data (U.S. Geological Survey, 2015; U.S. Geological Survey, 2016). After collecting, processing, and plotting the data, a potentiometric surface was generated using the interpolation method Topo to Raster in ArcMap 10.5 (Esri, 2017a). This tool is specifically designed for the creation of digital elevation models and imposes constraints that ensure a connected drainage structure and a correct representation of the surface from the provided contour data (Esri, 2017a). Once the raster surface was created, 50-ft contour interval were generated using Contour (Spatial Analyst), a spatial analyst tool (available through ArcGIS 3D Analyst toolbox) that creates a line-feature class of contours (isolines) from the raster surface (Esri, 2017b). The Topo to Raster and contouring done by ArcMap 10.5 is a rapid way to interpolate data, but computer programs do not account for hydrologic connections between groundwater and surface water. For this reason, some contours were manually adjusted based on topographical influence, a comparison with the potentiometric surface of Kresse and Hays (2009), and data-point water-level altitudes to more accurately represent the potentiometric surface. Select References: Esri, 2017a, How Topo to Raster works—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/how-topo-to-raster-works.htm. Esri, 2017b, Contour—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro Raster Surface toolset at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/contour.htm. Kresse, T.M., and Hays, P.D., 2009, Geochemistry, Comparative Analysis, and Physical and Chemical Characteristics of the Thermal Waters East of Hot Springs National Park, Arkansas, 2006-09: U.S. Geological Survey 2009–5263, 48 p., accessed November 28, 2017, at https://pubs.usgs.gov/sir/2009/5263/. U.S. Geological Survey, 2015, USGS NED 1 arc-second n35w094 1 x 1 degree ArcGrid 2015, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html. U.S. Geological Survey, 2016, USGS NED 1 arc-second n35w093 1 x 1 degree ArcGrid 2016, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html.
Geodetic Networks dataset current as of 1994. Point feature class in ESRI format.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.