This is a vector polyline file showing trails at Great Smoky Mountains National Park (GRSM). The data was collected using a Trimble Pro XR GPS receiver with a Trimble Compact Dome Antenna and a Trimble Asset Surveyor hand held data logger. The trail system a Great Smoky Mountains National Park is one of the most important man-made recreational features of the Park. This dataset represents the most comprehensive inventory of both locational and attribute information about the trails systems to date and is considered on of the most important base data layers for the Park. As such GRSM staff will strive to the both spatial and attribute information stored within this dataset up to date in order to best reflect the current status of the trails system at the Park Only Trails that are shown on the official park visitor map and/or listed in the park maintenance system are contained in this dataset. Other trails, while known to the park to exist and clearly used for access to permanent features (e.g. cemeteries, overlooks), are not contained in this dataset due to the parks desire to ensure safety of visitors on park trails. These data are formatted for use by park staff in the park 1:24,000-scale topographic map series, and are classified using the "FCSubtype" field, which classifies a trail segment based on primary use.

This is a vector polyline file showing trails at Great Smoky Mountains National Park (GRSM). The data was collected using a Trimble Pro XR GPS receiver with a Trimble Compact Dome Antenna and a Trimble Asset Surveyor hand held data logger. The trail system a Great Smoky Mountains National Park is one of the most important man-made recreational features of the Park. This dataset represents the most comprehensive inventory of both locational and attribute information about the trails systems to date and is considered on of the most important base data layers for the Park. As such GRSM staff will strive to the both spatial and attribute information stored within this dataset up to date in order to best reflect the current status of the trails system at the Park Only Trails that are shown on the official park visitor map and/or listed in the park maintenance system are contained in this dataset. Other trails, while known to the park to exist and clearly used for access to permanent features (e.g. cemeteries, overlooks), are not contained in this dataset due to the parks desire to ensure safety of visitors on park trails. These data are formatted for use by park staff in the park 1:24,000-scale topographic map series, and are classified using the "FCSubtype" field, which classifies a trail segment based on primary use.

A feature class depicting geographic locations of park trail heads which intersect public roads.

This is a vector point file showing Parking Areas at Great Smoky Mountains National Park (GRSM). Data were collected with GPS and/or aerial photography. The intended use of all data in the park's GIS library is to support diverse park activities including planning, management, maintenance, research, and interpretation.

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.

This is a vector polygon file showing the historic range forest types at Great Smoky Mountains National Park. The data was collected from a historic map drawn by Frank Miller, Assistant Forester, in 1938. The map was scanned using a Vidar color scanner and the digital images were brought into ArcMap. The map was originally divided into 4 separate panels, thus there were 4 separate image files. Each image was Georectified, Clipped and then the Mosaic tool was employed to create one large map image. Two feature classes, one a point feature class and the other a polyline feature class, were then created. The polyline class was used to digitize the boundary of each area of vegetation and a point containing the attributes of each area was placed within. After digitizing, the polyline layer was converted to a polygon feature class and the attribute table from the point layer was joined to the corresponding polygon within the feature class.

This database includes all data related to long-term vegetation monitoring performed by GRSM I&M staff from 2003-2009. Data collection methods follow Jenkins 2008 protocol, and are generally referred to as the GRSM Vegetation Monitoring plots. This program ended in 2009 and was replaced with the Vital Signs program, however, this database will still occasionally be updated as research partners revisit plots.

The National Register of Historic Places is the official list of the Nation's historic places worthy of preservation. Authorized by the National Historic Preservation Act of 1966, the National Park Service's National Register of Historic Places is part of a national program to coordinate and support public and private efforts to identify, evaluate, and protect America's historic and archeological resources

These data depict Road Segment Centerlines and attributes for roads that are managed and maintained by the National Park Service. Road data are used for many purposes including planning and management, mapping and condition assessment, routing and navigation, public information, emergency response, and research. A current, accurate representation of park roads is needed for national reporting and a variety of mapping requirements at all levels of the National Park Service and the general public. A National-level dataset allows the NPS to communicate a consistent and high-quality roads database to NPS staff, partners, visitors, and entities that produce maps and location-based services of park units. The collection, storage, and management of road-related data are important components of everyday business activities in many Federal and State land-managing agencies, road organizations, and businesses. From a management perspective, road data must often mesh closely with other types of infrastructure, resource, and facility enterprise data. For the public using paper maps, the internet, GPS or other instrumentation, standard data formats enable users to consistently and predictably identify specific trails and a core set of corresponding information. Today, digital road data are a necessity throughout a road data management life-cycle, from road planning through design, construction, operation, and maintenance. Automating, sharing, and leveraging road data through this widely accepted standard can provide a variety of important benefits: Efficiency – creating and gathering road data that are standardized and readily usable. Compatibility – compiling data from one project or discipline that can be compatible with other applications; Consistency – using the same standards, meshing data produced by one organization with that developed by another; Speed – hastening the availability of data through a reduction in duplicative efforts and lowered production costs (Applications can be developed more quickly and with more interoperability by using existing standards-compliant data); Conflict resolution – resolving conflicting road data more easily if compliant to the same standards; Reliability – improving the quality of shared road data by increasing the number of individuals who find and correct errors; and Reusability – allow maximum reuse across agencies and support objectives of EGovernment (E-Gov) initiatives and enterprise architecture.

These data depict Road Segment Centerlines and attributes for roads that are managed and maintained by the National Park Service. Road data are used for many purposes including planning and management, mapping and condition assessment, routing and navigation, public information, emergency response, and research. A current, accurate representation of park roads is needed for national reporting and a variety of mapping requirements at all levels of the National Park Service and the general public. A National-level dataset allows the NPS to communicate a consistent and high-quality roads database to NPS staff, partners, visitors, and entities that produce maps and location-based services of park units. The collection, storage, and management of road-related data are important components of everyday business activities in many Federal and State land-managing agencies, road organizations, and businesses. From a management perspective, road data must often mesh closely with other types of infrastructure, resource, and facility enterprise data. For the public using paper maps, the internet, GPS or other instrumentation, standard data formats enable users to consistently and predictably identify specific trails and a core set of corresponding information. Today, digital road data are a necessity throughout a road data management life-cycle, from road planning through design, construction, operation, and maintenance. Automating, sharing, and leveraging road data through this widely accepted standard can provide a variety of important benefits: Efficiency – creating and gathering road data that are standardized and readily usable. Compatibility – compiling data from one project or discipline that can be compatible with other applications; Consistency – using the same standards, meshing data produced by one organization with that developed by another; Speed – hastening the availability of data through a reduction in duplicative efforts and lowered production costs (Applications can be developed more quickly and with more interoperability by using existing standards-compliant data); Conflict resolution – resolving conflicting road data more easily if compliant to the same standards; Reliability – improving the quality of shared road data by increasing the number of individuals who find and correct errors; and Reusability – allow maximum reuse across agencies and support objectives of EGovernment (E-Gov) initiatives and enterprise architecture.