ArcGIS REST Services Directory Login
JSON

Layer: Existing Bike Facilities (as of 10/11) (ID: 9)

Name: Existing Bike Facilities (as of 10/11)

Display Field: rd20full

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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. </SPAN></P><P><SPAN>The following attribute descriptions were created to interpret the attributes included in the dataset:</SPAN></P><P><SPAN>rd20full (alias Street): Street name derived from STREET_ALLEY_WALKWAY.</SPAN></P><P><SPAN>length_mi (alias Length (Miles)): Street segment length calculated in GIS in the NAD 83 State Plane IV coordinate system.</SPAN></P><P><SPAN>proj_type (alias Project Type): The paving project type in which the bike facilities were originally created. </SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>bike_class_type (alias Bike Class Type): Classifies all bike lanes with a domain (Bike_Class_Type) with the following values:</SPAN></P><P STYLE="text-indent:20;"><SPAN>Class1 (alias Class I): Separated bike path</SPAN></P><P STYLE="text-indent:20;"><SPAN>Class2 (alias Class II): Bike lane</SPAN></P><P STYLE="text-indent:20;"><SPAN>Class3 (alias Class III): Bike route with sharrows and/or Bike Route signage.</SPAN></P><P STYLE="text-indent:20;"><SPAN>Class4 (alias Class IV): Separated bike lane with barrier between cyclist and vehicle traffic.</SPAN></P><P STYLE="text-indent:20;"><SPAN>AdvisoryBikeLane (alias Advisory Bike Lane): advisory bike lanes.</SPAN></P><P STYLE="text-indent:20;"><SPAN>Needs (alias Needs Class): Reserved for editing purposes.</SPAN></P><P><SPAN>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:</SPAN></P><P STYLE="text-indent:20;"><SPAN>Built: Signifies a built bike facility. This is the default status for this dataset.</SPAN></P><P STYLE="text-indent:20;"><SPAN>Designed: Represent bike facilities with signed plans but not built</SPAN></P><P STYLE="text-indent:20;"><SPAN>Needs Class: reserved for editing purposes.</SPAN></P><P STYLE="text-indent:20;"><SPAN>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.</SPAN></P><P><SPAN>xstrt1 (alias Cross Street 1): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.</SPAN></P><P><SPAN>xstrt2 (alias Cross Street 2): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.</SPAN></P><P><SPAN>project_id (alias Project ID): The paving project ID in which the bike facilities were originally created, derived from various City sources. </SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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).</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>combined_class (alias Combined Class): Concatenated classification which combines Road Buffer, Bike Lane Width, Curb Buffer, and Bike Class Type.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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. </SPAN></P><P><SPAN>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. </SPAN></P><P><SPAN>title (alias Project Title): Paving project title in which the bike facilities were originally created, derived from various City sources.</SPAN></P><P><SPAN>date_cy (alias Construction End Year): Derived from End Construction Date and used to facilitate mileage-by-year calculations.</SPAN></P><P><SPAN>date_design_year (alias End Design Year): Derived from End Design Date and used to facilitate mileage-by-year calculations.</SPAN></P><P><SPAN>PROJECT_ST (alias Construction Status): Construction status of the paving project in which the bike facilities were originally created, derived from various City sources. </SPAN></P></DIV></DIV></DIV>

Service Item Id: 61f0a85f49414a11986616eb926fb189

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.

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 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:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

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

  Iteminfo   Thumbnail   Metadata