Parent Layer: Transportation

Name: Trails 2050 Core Network

Display Field: ProjectCategory

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: The Trails 2050 Core Network layer shows the high priority facilities that have the potential to improve citywide connectivity to a variety of destinations in Chesapeake's busiest areas. It was adopted on November 19, 2024 as part of the Trails & Connectivity (TConn) Plan. The full network, adopted by City Council on November 19, 2024, along with existing facilities that are part of the network, can be seen in the Trails 2050 layer. The Trails 2050 Core Network layer contains the following attribute information: Project Category - category assigned by Alta during the TConn study (options include: Bridge the Gaps, Complete the System, Connect Neighborhoods, Connect Open Spaces, Improve Blueway Connections, or null)Facility Type - type of trail/path proposed. Options include: Bike Boulevard, Bike Lane, BLueway, Separated Facility, and Shared Use Path/Trail.Bike Boulevards - are streets with additional signage and traffic calming measures; bikes share-the-road with motoristsBike Lanes - have designated on-street areas adjacent to driving lanes; they are marked with lines, symbology, and signage to increase awareness among motorists that cyclists may be present.Blueways - are designated waterways that can be used and accessed by non-motorized watercraft such as kayaks, canoes, paddleboards, etc.Separated Facilities - come in the form of two subcategories: separated bike lanes and side paths. Separated bike lanes are found in the roadway but have physical barriers separating them from driving lanes; they may be separated by curbs, bollards, planters, or other means. Side paths are shared use paths located along a roadway; they may have paved, concrete, or natural surfaces.Shared Use Paths (SUP)/Trails - provide space for walkers, runners, bikers, and other users; typically they do not follow roadways. They may have paved, concrete, or natural surfaces.Symbology Type - the facility types are condensed into the following categories for display purposes. They are: Paved SUP/Trail, Paved SUP/Trail 2050, Separated Facility, Separated Facility 2050, Bike Lane, Bike Lane 2050, Bike Boulevard, Bike Boulevard 2050, and Blueway 2050. The "2050" at the end of the symbology group name indicates that the path does not exist, bit it is part of the adopted Trails & Connectivity Plan.Trail Name - if it has one; many trails are not named.Roadway - name of major roadway the trail follows; off road indicates the trail does not follow a roadway.Start - crossroad where the trail starts. For N/S trails, the northern most street intersection; for E/W trail, the western most street intersection.End - crossroad where the trails ends. For N/S trails, the southernmost street intersection; for E/W trails, the eastern most street intersection.Length (miles) - length of trails

Service Item Id: 98af486085f54f1888458af16e7441e1

Copyright Text: Planning, Trails & Connectivity Study, Alta

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 1.2079478566895887E7
YMin: 3366952.750071317
XMax: 1.2173176852924138E7
YMax: 3478388.6102043986
Spatial Reference: 102747  (2284)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [232, 190, 255, 127]
Width: 8
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: true

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• ProjectCategory ( type: esriFieldTypeString, alias: ProjectCategory, length: 255 )
• FacilityType ( type: esriFieldTypeString, alias: FacilityType, length: 255 )
• Roadway ( type: esriFieldTypeString, alias: Roadway, length: 255 )
• Start ( type: esriFieldTypeString, alias: Start, length: 255 )
• End_ ( type: esriFieldTypeString, alias: End, length: 255 )
• Timeline ( type: esriFieldTypeString, alias: Timeline, length: 255 )
• Notes ( type: esriFieldTypeString, alias: Notes, length: 255 )
• FundedInDevelopment ( type: esriFieldTypeString, alias: FundedInDevelopment, length: 255 )
• Lengthmi ( type: esriFieldTypeDouble, alias: Length (miles) )
• CREATED_USER ( type: esriFieldTypeString, alias: Created User, length: 255 )
• CREATED_DATE ( type: esriFieldTypeDate, alias: Created Date, length: 8 )
• LAST_EDITED_USER ( type: esriFieldTypeString, alias: Last Editor, length: 255 )
• LAST_EDITED_DATE ( type: esriFieldTypeDate, alias: Last Edited Date, length: 8 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata