Name: CORE MPO Bikeways

Display Field: Rt_Name

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: This data includes bikeways of various types, whether existing or planned within the CORE MPO Non-motorized Transportation Plan. The various types of bikeways can include bike lanes, shared use paths, cycle tracks, paved shoulders, and shared lanes, among others. Definitions of different types of bikeways are provided in the Non-motorized Transportation Plan, Appendix E: Bikeway Route Notes. See web page at: http://www.thempc.org/Transportation/Non-motorTranspPlan.html. Edited as needed.Use limitations: Available for public use and download via the SAGIS Open Data website DATA DICTIONARIESThe Data Dictionary for a few of the fields are shown below. The Existing or EXIST_CD (Existing Type) fields and the Status_by_Type (Status of Plan) field are the most fundamental ones and they are explained first. The Existing field may be symbolized automatically when this feature class is added to a map. It indicates the current type of facility on each segment of the plan's bikeway network, regardless of what type is recommended in the MPO Non-motorized Transportation Plan. On the other hand, the Status_by_Type field indicates whether a given bikeway segment currently has the type of facility recommended for it in the Non-motorized Transportation Plan. For example, the record for a segment that currently has only shared lanes, but is recommended to have bike lanes, would show the code for "Shared Lane" in the Existing or EXIST_CD fields, and would show the code for "Recommended Bike Lane" in the Status_by_Type field. In short, symbolizing the Existing or EXIST_CD fields shows you current conditions on the network, while symbolizing Status_by_Type field shows you what is recommended and how far along the region is in meeting that vision (e.g. with the latter field, you could use different colors to dinstinguish types and use solid and dotted lines to dinstinguish whether the recommended type already exists or not).Existing or EXIST_CD (Existing Type) field:BL or 101 = Bike Lane CT or 102 = Cycle TrackBP or 103 = Bike Path (i.e. Shared Use Path) PS or 104 = Paved ShoulderNarrow PS or 105 = Narrow Paved ShoulderSL or 106 = Shared LaneWCL or 107 = Wide Curb Lane108 = Unopened. This describes a segment that is either physically or legally untraversable by bicycle in its current state. A few examples are: woods, swamp, canal-side maintenance drives (whether grassy or dirt), old railroad beds, freeways where bicycles are currently prohibited but where a separated facility is recommended in the future, freeways that are recommended to be replaced with slower, local streets. Status_by_Type (Status of Plan) field:0 = Existing Bike Lane1 = Existing Shared Use Path2 = Existing Paved Shoulder3 = Existing Shared Lane4 = Existing Wide Curb Lane5 = Recommended Bike Lane6 = Recommended Shared Use Path7 = Recommended Paved Shoulder8 = Recommended Wide Curb Lane9 = Existing Cycle Track10 = Recommended Cycle Track11 = Existing Narrow Paved Shoulder12 = Recommended Narrow Paved Shoulder13 = Recommended Shared LaneA few other fields are detailed below.History (Plan Year Origin) distinguishes which of the bikeway plan's segments were in the GIS data set for the CORE MPO's Bikeway Plan of 2000 and which ones were added during the udpate that became the CORE MPO Non-motorized Transportation Plan of 2014. Be aware that bikeway plans existed prior to 2000, but that prior history is not currently distinguished in this field. Also note that while most of the 2000 plan was retained in the 2014 plan, a few segments were not. Those segements are not in this data set. Segments that were retained from the 2000 plan do not necessarily have the same recommendations for facility type now that they had in 2000.2000 Plan = retained from the GIS data from the CORE MPO Chatham County Bikeway Plan (adopted in 2000)2014 Plan = added during the update which became the bikeway section of CORE MPO Non-motorized Transportation Plan (adopted in 2014)LOS_Category (Level of Service Category) shows results of a particular kind of analysis that attempts to predict the comfort of bicycling on a given roadway segment, considering factors such as volume of auto and truck traffic, traffic speed, width of lane, and pavement condition. This method is not appropriate for off-road bikeway types (such as shared use paths) and was not appllied to bikeway segments that currently exist as such. The method does not account for conditions at intersections. The method of analysis is explained in an appendix of the CORE MPO Non-motorized Transportation Plan, which includes the assumptions that were employed whenever field data was not readily available. Be aware that this Bicycle LOS is a different type of assessment from the traditional LOS assessments focusing on auto drivers, which instead measures characteristics such as delay and traffic density. In the Bicycle LOS method, numeric scores are grouped into categories as follows:A = Extremely good LOS (score less than or equal to 1.5)B = Very good LOS (score greater than 1.5 and less than or equal to 2.5)C = Moderately good LOS (score greater than 2.5 and less than or equal to 3.5)D = Moderately poor LOS (socre greater than 3.5 and less than or euqual to 4.5)E = Very poor LOS (score greater than 4.5 and less than or equal to 5.5)F = Extremely poor LOS (score greater than 5.5)<Null> or NoData means the segment was not rated with this Bicycle LOS method. These are instances in whcih the bikeway segment is or will be off-road (shared use paths), or is proposed for a street that does not yet exist.

Service Item Id: 802bb6e18b494140a329f0ed3374651f

Copyright Text: Transportation Planner, Chatham County - Savannah Metropolitan Planning Commission, Coastal Region Metropolitan Planning Organization

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 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: 898393.8586860783
YMin: 699580.618201822
XMax: 1066971.4424619973
YMax: 815638.9421870708
Spatial Reference: 102666  (2239)

Drawing Info:

Renderer:
Unique Value Renderer:
Field 1: EXIST_CD
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
Style: esriSLSSolid
Color: [130, 130, 130, 255]
Width: 1
Default Label:
UniqueValueInfos:
• Value: 101
  Label: Bike Lane
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [97, 163, 59, 255]
  Width: 1
• Value: 102
  Label: Cycle Track
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [122, 45, 145, 255]
  Width: 1
• Value: 103
  Label: Bike Path
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [156, 47, 37, 255]
  Width: 1
• Value: 104
  Label: Paved Shoulder
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [75, 135, 156, 255]
  Width: 1
• Value: 105
  Label: Narrow Paved Shoulder
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [171, 139, 63, 255]
  Width: 1
• Value: 106
  Label: Shared Lane
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [133, 45, 82, 255]
  Width: 1
• Value: 107
  Label: Wide Curb Lane
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [28, 68, 133, 255]
  Width: 1
• Value: 108
  Label: Unopened
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [85, 173, 135, 255]
  Width: 1
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

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: EXIST_CD

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• RtA ( type: esriFieldTypeSmallInteger, alias: Route A )
• RtB ( type: esriFieldTypeSmallInteger, alias: Route B )
• RtC ( type: esriFieldTypeSmallInteger, alias: Route C )
• SegA ( type: esriFieldTypeDouble, alias: Segment on A )
• SegB ( type: esriFieldTypeDouble, alias: Segment on B )
• SegC ( type: esriFieldTypeDouble, alias: Segment on C )
• Route_Nums ( type: esriFieldTypeString, alias: Route Numbers, length: 20 )
• Rt_Name ( type: esriFieldTypeString, alias: Route Name, length: 30 )
• St_Name ( type: esriFieldTypeString, alias: Street Name, length: 30 )
• Existing ( type: esriFieldTypeString, alias: Existing Type, length: 10 )
• Signed_Rt ( type: esriFieldTypeString, alias: On a Signed Route, length: 10 )
• Class ( type: esriFieldTypeString, alias: Class Recommended, length: 38 )
• Type ( type: esriFieldTypeString, alias: Type Recommended, length: 18 )
• Status_Type ( type: esriFieldTypeInteger, alias: Status of Plan , Coded Values: [0: Existing Bike Lane] , [1: Existing Shared Use Path] , [2: Existing Paved Shoulder] , ...11 more... )
• History ( type: esriFieldTypeString, alias: Plan Year Origin, length: 24 )
• Avg_Daily_Traffic ( type: esriFieldTypeInteger, alias: Average Daily Traffic )
• Directional_Factor ( type: esriFieldTypeDouble, alias: Directional Factor )
• Peak_to_Daily_Factor ( type: esriFieldTypeDouble, alias: Peak to Daily Factor )
• Peak_Hr_Factor ( type: esriFieldTypeDouble, alias: Peak Hour Factor )
• Peak_15_Min ( type: esriFieldTypeInteger, alias: Directional Traffic per 15 Min )
• Total_Directional_Thru_Lanes ( type: esriFieldTypeSmallInteger, alias: Num Directional Thru Lanes )
• Speed_Posted ( type: esriFieldTypeSmallInteger, alias: Speed Posted )
• Speed_Effective ( type: esriFieldTypeDouble, alias: Speed Effective )
• Heavy_Veh_Percent ( type: esriFieldTypeDouble, alias: Heavy Vehicle Percent )
• Pave_Rating_FHWA ( type: esriFieldTypeSmallInteger, alias: Pavement Rating FHWA )
• Total_Width_Outlane_Shldr ( type: esriFieldTypeSmallInteger, alias: Width Outside Lane and Shoulder )
• Occ_On_St_Park ( type: esriFieldTypeDouble, alias: Occupied On-street Parking Percent )
• Width_Pave_Outstripe_to_Edge ( type: esriFieldTypeSmallInteger, alias: Width Between Outside Line and Edge )
• Width_On_St_Park ( type: esriFieldTypeSmallInteger, alias: Width Striped On-street Parking )
• Width_Function_of_Vol ( type: esriFieldTypeSmallInteger, alias: Effective Lane Width Function of Volume )
• St_Undivided_Unstriped ( type: esriFieldTypeSmallInteger, alias: Street Undivided, No Centerline )
• Ln_Width_Avg_Effective ( type: esriFieldTypeSmallInteger, alias: Average Effective Lane Width )
• LOS_Score ( type: esriFieldTypeDouble, alias: Level of Service Score )
• LOS_Category ( type: esriFieldTypeString, alias: Level of Service Category, length: 6 )
• EXIST_CD ( type: esriFieldTypeInteger, alias: Existing Type , Coded Values: [101: Bike Lane] , [102: Cylce Track] , [104: Paved Shoulder] , ...5 more... )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• SHAPE.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )

Types:

ID: 101
Name: Bike Lane
Domains:

---

ID: 102
Name: Cycle Track
Domains:

---

ID: 103
Name: Bike Path
Domains:

---

ID: 104
Name: Paved Shoulder
Domains:

---

ID: 105
Name: Narrow Paved Shoulder
Domains:

---

ID: 106
Name: Shared Lane
Domains:

---

ID: 107
Name: Wide Curb Lane
Domains:

---

ID: 108
Name: Unopened
Domains:

---

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

  Iteminfo   Thumbnail   Metadata