Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>A geographic representation of the municipal boundaries updated by SanGIS when notified by LAFCO of a recorded annexation or detachment. The revised layer is published as needed once changes are made and verified. Adjustments are also made to this dataset from ongoing landbase maintenance activities.</SPAN></P><P><SPAN>SanGIS will add individual polygons for annexations to a municipal jurisdiction but will not maintain a separate polygon for the agency losing territory. That is, a polygon will be created for the "gain" but the "loss" will be reflected only by modifying the existing boundary. </SPAN></P><P><SPAN>On an annual basis, SanGIS will reconcile the JUR_MUNICIPAL layer with the JUR_MUNICIPAL_ASR layer developed by the Assessor. This will happen when the Assessor publishes the annual TRA updates. SanGIS will accept the Assessor layer as is and use it as the basis for new annexations/detachments going forward. Individual polygons that have been created in the past year will be incorporated into the municipal boundary as shown on the Assessor's TRA updates. </SPAN></P><P><SPAN>NOTE: The County Assessor's Office JUR_MUNICIPAL_ASR layer is the official Municipal Boundary layer; however, it is created for tax purposes and is only updated on an annual basis as required by state law.</SPAN></P></DIV></DIV></DIV>
Copyright Text: County Assessor, SanGIS, San Diego Local Agency Formation Commission (LAFCO)
Description: This dataset comprises road centerlines for all roads in San Diego County. Road centerline information is collected from recorded documents (subdivision and parcel maps) and information provided by local jurisidictions (Cities in San Diego County, County of San Diego). Road names and address ranges are as designated by the official address coordinator for each jurisidcition. Jurisdictional information is created from spatial overlays with other data layers (e.g. Jurisdiction, Census Tract).The layer contains both public and private roads. Not all roads are shown on official, recorded documents. Centerlines may be included for dedicated public roads even if they have not been constructed. Public road names are the official names as maintained by the addressing authority for the jurisdiction in which the road is located. Official road names may not match the common or local name used to identify the road (e.g. State Route 94 is the official name of certain road segments commonly referred to as Campo Road).Private roads are either named or unnamed. Named private roads are as shown on official recorded documents or as directed by the addressing authority for the jurisdiction in which the road is located. Unnamed private roads are included where requested by the local jurisidiction or by SanGIS JPA members (primarily emergency response dispatch agencies). Roads are comprised of road segments that are individually identified by a unique, and persistent, ID (ROADSEGID). Roads segments are terminated where they intersect with each other, at jurisdictional boundaries (i.e. city limits), certain census tract and law beat boundaries, at locations where road names change, and at other locations as required by SanGIS JPA members. Each road segment terminates at an intersection point that can be found in the ROADS_INTERSECTION layer.Road centerlines do not necessarily follow the centerline of dedicated rights-of-way (ROW). Centerlines are adjusted as needed to fit the actual, constructed roadway. However, many road centerline segments are created intially based on record documents prior to construction and may not have been updated to meet as-built locations. Please notify SanGIS if the actual location differs from that shown. See the SanGIS website for contact information and reporting problems (http://www.sangis.org/contact/problem.html).Note, the road speeds in this layer are based on road segment class and were published as part of an agreement between San Diego Fire-Rescue, the San Diego County Sheriff's Department, and SanGIS. The average speed is based on heavy fire vehicles and may not represent the posted speed limit.
Service Item Id: 61f0a85f49414a11986616eb926fb189
Copyright Text: SanGIS using information from documents recorded with the County of San Diego and the addressing authorities in the 18 cities in San Diego County.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This dataset comprises road centerlines for all roads in San Diego County. Road centerline information is collected from recorded documents (subdivision and parcel maps) and information provided by local jurisidictions (Cities in San Diego County, County of San Diego). Road names and address ranges are as designated by the official address coordinator for each jurisidcition. Jurisdictional information is created from spatial overlays with other data layers (e.g. Jurisdiction, Census Tract).</SPAN></P><P><SPAN /><SPAN>The layer contains both public and private roads. Not all roads are shown on official, recorded documents. Centerlines may be included for dedicated public roads even if they have not been constructed. Public road names are the official names as maintained by the addressing authority for the jurisdiction in which the road is located. Official road names may not match the common or local name used to identify the road (e.g. State Route 94 is the official name of certain road segments commonly referred to as Campo Road).</SPAN><SPAN /></P><P><SPAN>Private roads are either named or unnamed. Named private roads are as shown on official recorded documents or as directed by the addressing authority for the jurisdiction in which the road is located. Unnamed private roads are included where requested by the local jurisidiction or by SanGIS JPA members (primarily emergency response dispatch agencies). </SPAN></P><P><SPAN>Roads are comprised of road segments that are individually identified by a unique, and persistent, ID (ROADSEGID). Roads segments are terminated where they intersect with each other, at jurisdictional boundaries (i.e. city limits), certain census tract and law beat boundaries, at locations where road names change, and at other locations as required by SanGIS JPA members. Each road segment terminates at an intersection point that can be found in the ROADS_INTERSECTION layer.</SPAN></P><P><SPAN>Road centerlines do not necessarily follow the centerline of dedicated rights-of-way (ROW). Centerlines are adjusted as needed to fit the actual, constructed roadway. However, many road centerline segments are created intially based on record documents prior to construction and may not have been updated to meet as-built locations. Please notify SanGIS if the actual location differs from that shown. See the SanGIS website for contact information and reporting problems (http://www.sangis.org/contact/problem.html).</SPAN></P><P><SPAN>Note, the road speeds in this layer are based on road segment class and were published as part of an agreement between San Diego Fire-Rescue, the San Diego County Sheriff's Department, and SanGIS. The average speed is based on heavy fire vehicles and may not represent the posted speed limit.</SPAN></P></DIV></DIV></DIV>
Copyright Text: SanGIS using information from documents recorded with the County of San Diego and the addressing authorities in the 18 cities in San Diego County.
Description: <DIV STYLE="text-align:Left;"><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>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. </SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>The following attribute descriptions were created to interpret the attributes included in the dataset:</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>rd20full (alias Street): Street name derived from STREET_ALLEY_WALKWAY.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>length_mi (alias Length (Miles)): Street segment length calculated in GIS in the NAD 83 State Plane IV coordinate system.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>proj_type (alias Project Type): The paving project type in which the bike facilities were originally created. </SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>bike_class_type (alias Bike Class Type): Classifies all bike lanes with a domain (Bike_Class_Type) with the following values:</SPAN></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Class1 (alias Class I): Separated bike path</SPAN></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Class2 (alias Class II): Bike lane</SPAN></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Class3 (alias Class III): Bike route with sharrows and/or Bike Route signage.</SPAN></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Class4 (alias Class IV): Separated bike lane with barrier between cyclist and vehicle traffic.</SPAN></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>AdvisoryBikeLane (alias Advisory Bike Lane): advisory bike lanes.</SPAN></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Needs (alias Needs Class): Reserved for editing purposes.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN>Built: Signifies a built bike facility. </SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Designed: Represent bike facilities with signed plans but not built. </SPAN></SPAN><SPAN>This is the default status for this dataset.</SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Needs Class: reserved for editing purposes.</SPAN></SPAN></P><P STYLE="text-indent:20;margin:0 0 0 0;"><SPAN><SPAN>Planned: Proposed bike lanes derived from the Planning Department's SDW.CITY.BIKE_MASTER_PLAN dataset under the </SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>SDW.CITY.LANDUSE feature class in Atlas.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>xstrt1 (alias Cross Street 1): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>xstrt2 (alias Cross Street 2): Cross street data derived from the STREET_ALLEY_WALKWAY dataset.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>project_id (alias Project ID): The paving project ID in which the bike facilities were originally created, derived from various City sources. </SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>combined_class (alias Combined Class): Concatenated classification which combines Road Buffer, Bike Lane Width, Curb Buffer, and Bike Class Type.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>title (alias Project Title): Paving project title in which the bike facilities were originally created, derived from various City sources.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>date_cy (alias Construction End Year): Derived from End Construction Date and used to facilitate mileage-by-year calculations.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>date_design_year (alias End Design Year): Derived from End Design Date and used to facilitate mileage-by-year calculations.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><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></SPAN></P><DIV><P><SPAN /></P></DIV></DIV>
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: <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>
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: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The City of San Diego Bicycle Master Plan update to the City’s 2002 plan. Adopted in January, 2014</SPAN></P></DIV></DIV></DIV>