Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Description: This raster dataset shows hillshade relief for San Diego County to be used for cartographic purposes.Pixels are 2.5ft x 2.5 ft.This hillshade layer was created from a Merged Digital Elevation Model (DEM) data derived from Quality Level 2 LiDAR (USGS Base Specification) LiDAR acquired through the San Diego regional partnership acquisition projects in 2014 and 2017, and the FEMA acquisition project in 2015. Class 2 (ground) LiDAR points in conjunction with the hydro breaklines were used to create 2.5-foot hydro-flattened raster DEMs from which contour lines were generated.Geographic Extent:San Diego County in southwestern California, covering approximately 4,475 total square miles.This layer is not suitable for analysis purposes.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG, FEMA, County of San Diego, SanGIS
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: This layer depicts communities and neighborhoods as points with their respective names. Communities within the City of San Diego and the unincorporated areas of San Diego County are included. While some communities may have active planning groups, others are simply neighborhoods where people live. Communities within other municipalities are not included.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Department of Public Works, County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: This layer depicts communities and neighborhoods as points with their respective names. Communities within the City of San Diego and the unincorporated areas of San Diego County are included. While some communities may have active planning groups, others are simply neighborhoods where people live. Communities within other municipalities are not included.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Department of Public Works, County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata. A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. ***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a basic county dataset (cnty14_1_basic), a basic state dataset (state14_1), an ocean dataset (ocean14_1), a 3 nautical mile CA coastal buffer (cnty14_1_coastbuff), and country/state datasets (both full and neighbor-only - cntrystate14_1_full and cntrystate14_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. This specific datasetrepresents the full detailed county dataset with all coding (islands, inlets, constructed features, etc). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: This layer depicts communities and neighborhoods as points with their respective names. Communities within the City of San Diego and the unincorporated areas of San Diego County are included. While some communities may have active planning groups, others are simply neighborhoods where people live. Communities within other municipalities are not included.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Department of Public Works, County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata. A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. ***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a basic county dataset (cnty14_1_basic), a basic state dataset (state14_1), an ocean dataset (ocean14_1), a 3 nautical mile CA coastal buffer (cnty14_1_coastbuff), and country/state datasets (both full and neighbor-only - cntrystate14_1_full and cntrystate14_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. This specific datasetrepresents the full detailed county dataset with all coding (islands, inlets, constructed features, etc). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: This layer depicts communities and neighborhoods as points with their respective names. Communities within the City of San Diego and the unincorporated areas of San Diego County are included. While some communities may have active planning groups, others are simply neighborhoods where people live. Communities within other municipalities are not included.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Department of Public Works, County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata. A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. ***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a basic county dataset (cnty14_1_basic), a basic state dataset (state14_1), an ocean dataset (ocean14_1), a 3 nautical mile CA coastal buffer (cnty14_1_coastbuff), and country/state datasets (both full and neighbor-only - cntrystate14_1_full and cntrystate14_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. This specific datasetrepresents the full detailed county dataset with all coding (islands, inlets, constructed features, etc). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Color: [166, 152, 133, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: In 1968, the Board of Supervisors passed Policy I-1, which outlined the creation of community and subregional planning areas. In this policy, the Board directed the Department of Planning and Development Services to create and maintain these areas. The community boundaries reflect commonality of interest, topography, access, and existing district boundaries to the greatest extent possible. If and when the boundaries of community and subregional plan areas are revised, voting precinct boundaries are also to conform to these new boundaries. Each area has a set of locally elected volunteers to hold meetings and organize local citizen participation. Representative planning and sponsor groups were formed within the communities and subregions of the unincorporated area for the purpose of advising and assisting the Director of Planning & Development Services, the Zoning Administrator, the Planning Commission and the Board of Supervisors in the preparation, amendment and implementation of community and subregional plans.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: Randy Yakos, County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: Community plan boundaries for the City of San Diego land use policy plans specific to these geographic areas. Land use policies within jurisdictional boundaries have the ability to create a citywide land use and policy document called the General Plan. Many cities in California are small enough that their General Plans are single volumes. Larger cities, such as San Diego, often subdivide the city into a number of community plans, or "mini" land use policy plans for more specific geographic areas.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: City of San Diego, Planning Department
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Color: [130, 130, 130, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata. A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. ***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a basic county dataset (cnty14_1_basic), a basic state dataset (state14_1), an ocean dataset (ocean14_1), a 3 nautical mile CA coastal buffer (cnty14_1_coastbuff), and country/state datasets (both full and neighbor-only - cntrystate14_1_full and cntrystate14_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. This specific datasetrepresents the full detailed county dataset with all coding (islands, inlets, constructed features, etc). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Color: [166, 152, 133, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: In 1968, the Board of Supervisors passed Policy I-1, which outlined the creation of community and subregional planning areas. In this policy, the Board directed the Department of Planning and Development Services to create and maintain these areas. The community boundaries reflect commonality of interest, topography, access, and existing district boundaries to the greatest extent possible. If and when the boundaries of community and subregional plan areas are revised, voting precinct boundaries are also to conform to these new boundaries. Each area has a set of locally elected volunteers to hold meetings and organize local citizen participation. Representative planning and sponsor groups were formed within the communities and subregions of the unincorporated area for the purpose of advising and assisting the Director of Planning & Development Services, the Zoning Administrator, the Planning Commission and the Board of Supervisors in the preparation, amendment and implementation of community and subregional plans.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: Randy Yakos, County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: Community plan boundaries for the City of San Diego land use policy plans specific to these geographic areas. Land use policies within jurisdictional boundaries have the ability to create a citywide land use and policy document called the General Plan. Many cities in California are small enough that their General Plans are single volumes. Larger cities, such as San Diego, often subdivide the city into a number of community plans, or "mini" land use policy plans for more specific geographic areas.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: City of San Diego, Planning Department
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This dataset contains building outline polygons to support the ongoing development and maintenance of SANDAG's land inventory system (SPACECORE). The SanGIS Parcels feature class and the imagery captured by EagleView/Pictometry during the San Diego regional imagery acquisition partnership project in Spring 2017 were the basis for defining where building outlines were created using EagleView/Pictometry's ChangeFinder methodology. Additional buildings within road rights-of-way were also delineated by the EagleView/Pictometry team. SANDAG will be adding attribution to this dataset as part of our SPACECORE integration process.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata. A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. ***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a basic county dataset (cnty14_1_basic), a basic state dataset (state14_1), an ocean dataset (ocean14_1), a 3 nautical mile CA coastal buffer (cnty14_1_coastbuff), and country/state datasets (both full and neighbor-only - cntrystate14_1_full and cntrystate14_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. This specific datasetrepresents the full detailed county dataset with all coding (islands, inlets, constructed features, etc). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Color: [166, 152, 133, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: This dataset contains building outline polygons to support the ongoing development and maintenance of SANDAG's land inventory system (SPACECORE). The SanGIS Parcels feature class and the imagery captured by EagleView/Pictometry during the San Diego regional imagery acquisition partnership project in Spring 2017 were the basis for defining where building outlines were created using EagleView/Pictometry's ChangeFinder methodology. Additional buildings within road rights-of-way were also delineated by the EagleView/Pictometry team. SANDAG will be adding attribution to this dataset as part of our SPACECORE integration process.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata. A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. ***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a basic county dataset (cnty14_1_basic), a basic state dataset (state14_1), an ocean dataset (ocean14_1), a 3 nautical mile CA coastal buffer (cnty14_1_coastbuff), and country/state datasets (both full and neighbor-only - cntrystate14_1_full and cntrystate14_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. This specific datasetrepresents the full detailed county dataset with all coding (islands, inlets, constructed features, etc). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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.
Color: [168, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerLinePlacementAboveEnd Label Expression: [ABHIADDR] Use Coded Values: true Symbol:
Color: [168, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 152, 133, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [89, 89, 89, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
edit_reason
(
type: esriFieldTypeSmallInteger, alias: Why was it changed?
, Coded Values:
[1: No change needed]
, [2: This place no longer exists]
, [3: This place is named incorrectly]
, ...4 more...
)
Description: Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Routes are developed from the GTFS data available through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS using information provided by the San Diego Metropolitan Transit System (MTS - http://www.sdmts.com/) and the North County Transit District (NCTD - http://www.gonctd.com/) through the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: 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: 3aa3ad1caa49428cb6fac1fa65c99bd5
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: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.
Description: This layer depicts the location of public and private airports, runways, and landing strips throughout the County of San Diego. Private, commercial, and military airport runways and landing strips are included in this layer.Polygon features digitized from 2009 aerial images.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS; County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of rivers as polylines within (clipped to the boundary of) the County of San Diego. This data is generalized and created for use in regional projects. Rivers are classed as major or minor within the dataset. The dataset does not include smaller feeder streams and ditches. Primarily for cartographic purposes.
Description: This dataset contains building outline polygons to support the ongoing development and maintenance of SANDAG's land inventory system (SPACECORE). The SanGIS Parcels feature class and the imagery captured by EagleView/Pictometry during the San Diego regional imagery acquisition partnership project in Spring 2017 were the basis for defining where building outlines were created using EagleView/Pictometry's ChangeFinder methodology. Additional buildings within road rights-of-way were also delineated by the EagleView/Pictometry team. SANDAG will be adding attribution to this dataset as part of our SPACECORE integration process.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: SANDAG’s Land Layers are created for use in the Regional Growth Forecast to distribute projected growth for the San Diego region to suitable subareas. These land layers include existing land use, planned land use, land ownership, land available for development, and lands available for redevelopment and infill. The land layers inventory is updated when new information is available. Many of these data sets are built from the San Diego Geographic Information Source (SanGIS) landbase. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. The land use information was reviewed by each of the local jurisdictions and the County of San Diego to ensure its accuracy. Although this inventory contains more categorical detail and has better positional accuracy than previous land use inventories, users should be aware that this data may be too generalized for some local planning projects. Since each General Plan/Community Plan Land Use Elements have their own individualized way of categorizing their future land use designations, an aggregate planned land use code was devised (PLU). Each General Plan/Community Plan land use designation was cross-walked to a SANDAG PLU code. Adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.The Landuse featureclass was dissolved from SANDAG's Land Layer featureclass ludu2015.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SANDAG Technical Services - GIS, SANDAG Land Layers Inventory
Mapping Source: SanGIS landbase (i.e. parcels), SANDAG, County Assessor's Master Property Records file, Cleveland National Forest, Bureau of Land Management (BLM), State Parks, other public agency contacts, and local agency review.
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata. A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. ***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a basic county dataset (cnty14_1_basic), a basic state dataset (state14_1), an ocean dataset (ocean14_1), a 3 nautical mile CA coastal buffer (cnty14_1_coastbuff), and country/state datasets (both full and neighbor-only - cntrystate14_1_full and cntrystate14_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. This specific datasetrepresents the full detailed county dataset with all coding (islands, inlets, constructed features, etc). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Description: Recorded easements in San Diego County and local jurisdictions. Covers four types of easements - conservation, open space, biological, and recreational. Open space may be either private or public benefit. Recorded easements only as defined by the San Diego County Assessor's Office and shown on official records (as shown on Assessor Parcel Maps). The layer does not include open space areas not designated as recorded easements. Layer is incomplete and does not show all recorded easements.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
San Diego County Assessor's Office, Mapping Division
Description: A summary list of military-owned and leased lands in San Diego County. All major facilities are depicted. Some military-owned housing units are not depicted. Data is current as of the update date. All base names are current. Data is maintained by Land Use and Environment Group for regulatory purposes. Not all property ownership of military lands aligns with actual controlled space of a military facility. Data was derived from an ArcINFO coverage in the 1990's. DPLU staff then updatedthe data with input from the local base facility managers and Geofidelis west. Data derived from Geofidelis West data sources
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service
Description: This dataset consists of polygons representing Indian Reservations in the County of San Diego as documented by the County of San Diego Assessor's Office, Mapping Division. An Indian Reservation is an area of land managed by a native American tribe under the United States Department of the Interior's Bureau of Indian Affairs. The polygons are intedned to represent those lands recogonized as part of the Indian Nation by the Bureau of Indian Affarirs (BIA). The data does not include parcels that may be owned by a Tribe but which are not officially recogonized as reservation lands by BIA.Because tribes possess tribal sovereignty, even though it is limited, laws on tribal lands vary from the surrounding area. These laws can permit legal casinos on reservations for example. The tribal council, not the local or federal government, generally has jurisdiction over reservations. Most Indian reservations were established by the federal government. The name "reservation" comes from the conception of the Indian tribes as independent sovereigns at the time of the U.S. Constitution was ratified.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS
County of San Diego Assessor's Office, Mapping Divsion
Description: This feature class consists of administrative boundaries of the National Forests of Region 5, Pacific Southwest Region. It contains boundaries used for administrative responsibilities within individual forests such as those of ranger districts. These lines are not necessarily the same as ownership lines (Forest Service and Non-Forest Service ownership is a separate GIS layer). Boundaries are based on the PLSS (public land survey system) lines and corners, and on geographical features such as ridgelines. This is a by-product of the Forest Service Automated Lands Program.
Service Item Id: 3aa3ad1caa49428cb6fac1fa65c99bd5
Copyright Text: SanGIS via USDA Forest Service - Pacific Southwest Region - Regional Office
Description: This dataset comprises polygons of Counties and water bodies in the vicinity of San Diego County for cartographic purposes.Data is generalized and created for use in regional projects.
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.