Description: This dataset represents designed bikeways in the City of San Diego. Geometry includes parallel lines buffered 20 feet from the City's SDW.CITY.STREET_ALLEY_WALKWAY centerline data sourced from ATLAS. Street segments also reflect the SDW.CITY.STREET_ALLEY_WALKWAY data as maintained under the SDW.CITY.STREET feature class in the City's Atlas.sde enterprise geodatabase. The dataset also includes SAP ID and IAMFLOC attributes from the STREET_ALLEY_WALKWAY data to help join this data to the existing data sources in both ATLAS and SAP. The following attribute descriptions were created to interpret the attributes included in the dataset:rd20full (alias Street): Street name derived from STREET_ALLEY_WALKWAY.length_mi (alias Length (Miles)): Street segment length calculated in GIS in the NAD 83 State Plane IV coordinate system.proj_type (alias Project Type): The paving project type in which the bike facilities were originally created. end_dsgn (alias End Design Date): Date on which the designed plans were signed by the multi-modal team in the Traffic Engineering Division. This attributes originates from the TED Designed Bikeways dataset.bike_class_type (alias Bike Class Type): Classifies all bike lanes with a domain (Bike_Class_Type) with the following values:Class1 (alias Class I): Separated bike pathClass2 (alias Class II): Bike laneClass3 (alias Class III): Bike route with sharrows and/or Bike Route signage.Class4 (alias Class IV): Separated bike lane with barrier between cyclist and vehicle traffic.AdvisoryBikeLane (alias Advisory Bike Lane): advisory bike lanes.Needs (alias Needs Class): Reserved for editing purposes.status (alias Status): Utilizes the domain Bike Segment_Status to standardize the naming convention, representing the current state of the data with the following values:Built: Signifies a built bike facility. Designed: Represent bike facilities with signed plans but not built. This is the default status for this dataset.Needs Class: reserved for editing purposes.Planned: Proposed bike lanes derived from the Planning Department's SDW.CITY.BIKE_MASTER_PLAN dataset under the SDW.CITY.LANDUSE feature class in Atlas.xstrt1 (alias Cross Street 1): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.xstrt2 (alias Cross Street 2): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.project_id (alias Project ID): The paving project ID in which the bike facilities were originally created, derived from various City sources. road_buffer (alias Road Buffer (Feet)): Based on the signed plans from TED's Multi-Modal Team, this attribute signifies the buffer distance between the bike lane and vehicle traffic. Values of 0 indicate no buffer.bike_lane_width (alias Bike Lane Width (Feet)): Based on the signed plans from TED's Multi-Modal Team, this attribute signifies the lane width. Values of 0 indicate no lane (Class III sharrow).curb_buffer (alias Curb Buffer Width (Feet)): Based on the signed plans from TED's Multi-Modal Team, this attribute signifies the buffer distance between the bike lane and either the curb or parked cars to the right of the cyclist. Values of 0 indicate no buffer.combined_class (alias Combined Class): Concatenated classification which combines Road Buffer, Bike Lane Width, Curb Buffer, and Bike Class Type.district (alias Council District): City of San Diego Council District calculated from SDW.CITY.COUNCIL data under the SDW.CITY.DISTRICT feature dataset in Atlas.onewaystreet (alias One-Way Street): Relies on the Yes/No domain to indicate whether a bike facility is located on a one-way or two-way street.SAPID (alias SAP ID): The street segment ID as derived from the STREET_ALLEY_WALKWAY dataset. Both SAPID and IAMFLOC are included in this dataset to reflect any updates within the SAP asset management system.START_CONS (alias Start Construction Date): Start date of construction of the paving project in which the bike facilities were originally created, derived from various City sources. END_CONSTR (alias End Construction Date): End date of construction of the paving project in which the bike facilities were originally created, derived from various City sources. title (alias Project Title): Paving project title in which the bike facilities were originally created, derived from various City sources.date_cy (alias Construction End Year): Derived from End Construction Date and used to facilitate mileage-by-year calculations.date_design_year (alias End Design Year): Derived from End Design Date and used to facilitate mileage-by-year calculations.PROJECT_ST (alias Construction Status): Construction status of the paving project in which the bike facilities were originally created, derived from various City sources.
Service Item Id: ebfc098a3fb340c68bd4b254a0f6e8f7
Copyright Text: Traffic Engineering Division of City of San Diego's Transportation Department, along with SANDAG data sourced from the San Diego Regional Bike Network Map (https://icommutesd.com/bike/bikemap.aspx). Contact the TED GIS Analyst for any questions or concerns. Contact the Traffic Engineering Division before public distribution.
Description: This dataset represents the built bikeways in the City of San Diego. Geometry includes parallel lines buffered 20 feet from the City's SDW.CITY.STREET_ALLEY_WALKWAY centerline data sourced from ATLAS. Street segments also reflect the SDW.CITY.STREET_ALLEY_WALKWAY data as maintained under the SDW.CITY.STREET feature class in the City's Atlas.sde enterprise geodatabase. The dataset also includes SAP ID and IAMFLOC attributes from the STREET_ALLEY_WALKWAY data to help join this data to the existing data sources in both ATLAS and SAP. The following attribute descriptions were created to interpret the attributes included in the dataset:rd20full (alias Street): Street name derived from STREET_ALLEY_WALKWAY.length_mi (alias Length (Miles)): Street segment length calculated in GIS in the NAD 83 State Plane IV coordinate system.proj_type (alias Project Type): The paving project type in which the bike facilities were originally created. end_dsgn (alias End Design Date): Date on which the designed plans were signed by the multi-modal team in the Traffic Engineering Division. This attributes originates from the TED Designed Bikeways dataset.bike_class_type (alias Bike Class Type): Classifies all bike lanes with a domain (Bike_Class_Type) with the following values:Class1 (alias Class I): Separated bike pathClass2 (alias Class II): Bike laneClass3 (alias Class III): Bike route with sharrows and/or Bike Route signage.Class4 (alias Class IV): Separated bike lane with barrier between cyclist and vehicle traffic.AdvisoryBikeLane (alias Advisory Bike Lane): advisory bike lanes.Needs (alias Needs Class): Reserved for editing purposes.status (alias Status): Utilizes the domain Bike Segment_Status to standardize the naming convention, representing the current state of the data with the following values:Built: Signifies a built bike facility. This is the default status for this dataset.Designed: Represent bike facilities with signed plans but not builtNeeds Class: reserved for editing purposes.Planned: Proposed bike lanes derived from the Planning Department's SDW.CITY.BIKE_MASTER_PLAN dataset under the SDW.CITY.LANDUSE feature class in Atlas.xstrt1 (alias Cross Street 1): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.xstrt2 (alias Cross Street 2): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.project_id (alias Project ID): The paving project ID in which the bike facilities were originally created, derived from various City sources. road_buffer (alias Road Buffer (Feet)): Based on the signed plans from TED's Multi-Modal Team, this attribute signifies the buffer distance between the bike lane and vehicle traffic. Values of 0 indicate no buffer.bike_lane_width (alias Bike Lane Width (Feet)): Based on the signed plans from TED's Multi-Modal Team, this attribute signifies the lane width. Values of 0 indicate no lane (Class III sharrow).curb_buffer (alias Curb Buffer Width (Feet)): Based on the signed plans from TED's Multi-Modal Team, this attribute signifies the buffer distance between the bike lane and either the curb or parked cars to the right of the cyclist. Values of 0 indicate no buffer.combined_class (alias Combined Class): Concatenated classification which combines Road Buffer, Bike Lane Width, Curb Buffer, and Bike Class Type.district (alias Council District): City of San Diego Council District calculated from SDW.CITY.COUNCIL data under the SDW.CITY.DISTRICT feature dataset in Atlas.onewaystreet (alias One-Way Street): Relies on the Yes/No domain to indicate whether a bike facility is located on a one-way or two-way street.SAPID (alias SAP ID): The street segment ID as derived from the STREET_ALLEY_WALKWAY dataset. Both SAPID and IAMFLOC are included in this dataset to reflect any updates within the SAP asset management system.START_CONS (alias Start Construction Date): Start date of construction of the paving project in which the bike facilities were originally created, derived from various City sources. END_CONSTR (alias End Construction Date): End date of construction of the paving project in which the bike facilities were originally created, derived from various City sources. title (alias Project Title): Paving project title in which the bike facilities were originally created, derived from various City sources.date_cy (alias Construction End Year): Derived from End Construction Date and used to facilitate mileage-by-year calculations.date_design_year (alias End Design Year): Derived from End Design Date and used to facilitate mileage-by-year calculations.PROJECT_ST (alias Construction Status): Construction status of the paving project in which the bike facilities were originally created, derived from various City sources.
Service Item Id: ebfc098a3fb340c68bd4b254a0f6e8f7
Copyright Text: Traffic Engineering Division of City of San Diego's Transportation Department, along with SANDAG data sourced from the San Diego Regional Bike Network Map (https://icommutesd.com/bike/bikemap.aspx). Contact the TED GIS Analyst for any questions or concerns. Contact the Traffic Engineering Division before public distribution.