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.

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

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.

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.

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

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

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

Cemetery mapping was a follow on to GRSM trail mapping and was initiated as trail mapping was winding down on 3/8/2001. The objective was to GPS map every cemetery in GRSM. The GRSM Resource Management & Science - Cultural Resource Branch provided a photocopy of a cemetery locations map that was derived from a "1934 Preliminary Base Map Smoky Mountains National Park" which depicted cemetery locations and identification numbers. Cemetery maintenance log sheets were also provided, which included location descriptions of GRSM cemeteries along with identification numbers, names and other information. There were approximately 145 cemeteries identified in these documents. Because of inconsistencies between the map and maintenance logs, there was never an exact count of identified cemeteries. Additionally, other cemeteries existed, that were not described by these documents, but shown on the topographic maps. Many inaccuracies with the base map data and maintenance logs resulted in difficulty in locating the cemeteries. Many cemeteries were located and mapped with the aid of GRSM maintenance personnel and local citizens (old timers). This dataset represents the most up to date and accurate location and identification (cemetery identification) information available to Park resource managers. As such it should be used as the authoritative source or inventory of such information.