ArcGIS REST Services Directory Login | Get Token
JSON | SOAP

FeatureServices/Trails_CTC (MapServer)

View In:   ArcGIS JavaScript   ArcGIS Online map viewer   Google Earth   ArcMap   ArcGIS Explorer

View Footprint In:   ArcGIS Online map viewer

Service Description: Frederick County, Maryland’s 2018 Approved Bikeways and Trails Plan establishes trails for multi-modal connectivity locally between towns within Frederick County and regionally with connections planned with the C&O Canal and I-270 Corridor Transitway. These multiuse trails take the form of rails to trails, side paths in highway corridors, or along natural corridors, like streams. The following trails have been flagged by Frederick County Planning staff for inclusion in the CTC trail database: City of Frederick to C&O Towpath Connector, Ballenger Creek Trail, H&F Trolley Trails, Frederick Scenic Trail, I-270 Transitway Trail, City of Frederick and Municipal, and Pennsylvania RR Trail. Multiuse trails are specifically designed to accommodate different users, including walkers/hikers and bicyclists, among others, at the same time. This Plan recognizes that multi-use trails can serve both a recreation function and for transportation. The surface material used on multi-use trails includes either a compacted crushed stone, concrete or most typically asphalt. The crushed stone surface is generally cheaper to construct and provides a hard surface which can accommodate most bicycles. An asphalt surface would be suitable for all types of bicycles and can also accommodate in-line skating. The minimum recommended width of a multi-use trail is now 10 ft. though it can vary from 8 ft to 12 ft. depending on any design constraints or in heavy use areas that may warrant a wider trail. Although substandard, an 8 ft width can be adequate for trails through rural areas that are not expected to have heavy traffic. Within the more developed areas, a 12 ft width is desirable. Since many of the trail corridors are proposed along streams and the Monocacy River special consideration will need to be taken to minimize any adverse impacts on the stream or adjoining wetlands. Issues related to the environmental impacts from trails would be addressed as part of more detailed studies of individual trail corridors. The sidepath will function as a multi-use trail that is specifically located along and within the right of way of a parallel roadway. While this type of path may look like a sidewalk they differ in the following respects: a sidepath is able to accommodate two-way bicycle travel as well as pedestrians, a sidepath is wider (typically 8-10 feet) than a sidewalk (typically 4-5 feet), and they will most often will be constructed with an asphalt surface rather than concrete. Sidepaths are typically located along roadways with relatively high volume and high speed vehicle traffic where cycling on the roadway is not safe and may be considered for longer distance connections where there isn’t any other corridor feature that could accommodate a multi-use trail. Full Bikeways and Trails Plan text can be found here: https://www.frederickcountymd.gov/DocumentCenter/View/300816/Bikeways-and-Trail-Plans-2018 Fields: [Name] indicates the planned/existing trail’s name. [Type] differentiates between multi use and natural surface trails [Source] Source of GIS Data [Easement] indicates planned easement status (largely incomplete data) [Surface] differentiates between paved and natural surface trails. [Path Width] in standard US feet measure. [Agency] the jurisdiction responsible for the trail [From-To] describes the end locations of a trail [Status] Differentiates between existing and proposed trails [CTC_Flag] a trail, as identified by Frederick County Planning staff, for inclusion in the CTC trails database.

Map Name: Layers

Legend

All Layers and Tables

Layers: Description: Trails

Copyright Text:

Spatial Reference: 102685  (2248)


Single Fused Map Cache: false

Initial Extent: Full Extent: Units: esriFeet

Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP

Document Info: Supports Dynamic Layers: false

MaxRecordCount: 1000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, AMF, geoJSON

Min Scale: 0

Max Scale: 0



Child Resources:   Info

Supported Operations:   Export Map   Identify   Find   Return Updates   Generate KML