Color: [255, 255, 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: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
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: f1ada56b3d6b4c20975e8aae00bd221f
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: 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.
Color: [230, 152, 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: [62, 97, 138, 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: [0, 102, 51, 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: [56, 168, 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: [78, 78, 78, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps.
Plan_Date
(
type: esriFieldTypeDate, alias: Plan Date, length: 8
)
AB_Date
(
type: esriFieldTypeDate, alias: As Built, length: 8
)
DMP_Status
(
type: esriFieldTypeString, alias: DMP Status, length: 1
, Coded Values:
[1: Included in the Master Drainage Plan]
, [2: Not Included in the Mater Drainage Plan]
)
Node_Type
(
type: esriFieldTypeString, alias: Type, length: 6
, Coded Values:
[Cap: Cap - Used at plug end of pipe]
, [Plug: Plug _ Used to plug end of pipe]
, [Lug: Lug - Connection point of one pipe to another without structure]
, ...4 more...
)
Owner
(
type: esriFieldTypeString, alias: Owner, length: 10
, Coded Values:
[PropOwner: Private Property Owner]
, [City: City of Oceanside]
, [USACE: United States Army Corps of Engineers]
, ...12 more...
)
Status
(
type: esriFieldTypeInteger, alias: Status
, Coded Values:
[1: Active]
, [2: Abandoned]
, [3: Filled and abandoned]
, ...8 more...
)
Description: This data was collected using a Trimble GPS unit or was mapped from land development plans. This data is to be used for inventory of city assets, maintenance information, storm water quality control, and hydrologic studies. The feature attributes include storm drain type, type of pipe material, pipe diameter, invert elevations, slope, Q100, capcity, condition, status, installation date, engineering plan numbers, coordinate data, and owner information.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: City of Oceanside, Engineering Division
Description: This dataset consists of points for the location of Alcoholic Beverage Control Licenses in San Diego County geocoded from address information obtained from the California Department of Alcoholic Beverage Control (https://www.abc.ca.gov/).The dataset was downloaded in .lst format (https://www.abc.ca.gov/datport/DataExport.html), converted to Excel format and the records for San Diego County extracted. The San Diego records were then geocoded using the SANDAG composite locator. Note that a small percentage (circa 5%) of the records could not be geocoded and are included in the dataset without a point location. The dataset was then projected from WGS 1984 Web Mercator (auxillary sphere) into NAD_1983_StatePlane California VI FIPS 0406 (US Feet) and x y coordinate fields added.The dataset is downloaded and geocoded by SanGIS on a monthly basis. More current information may be available from the ABC website.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: California Department of Alcoholic Beverage Control for data. SanGIS for geocoding of San Diego data and presenting in a GIS-compatible format.
Description: This dataset consists of points for the location of Alcoholic Beverage Control Licenses in San Diego County geocoded from address information obtained from the California Department of Alcoholic Beverage Control (https://www.abc.ca.gov/).The dataset was downloaded in .lst format (https://www.abc.ca.gov/datport/DataExport.html), converted to Excel format and the records for San Diego County extracted. The San Diego records were then geocoded using the SANDAG composite locator. Note that a small percentage (circa 5%) of the records could not be geocoded and are included in the dataset without a point location. The dataset was then projected from WGS 1984 Web Mercator (auxillary sphere) into NAD_1983_StatePlane California VI FIPS 0406 (US Feet) and x y coordinate fields added.The dataset is downloaded and geocoded by SanGIS on a monthly basis. More current information may be available from the ABC website.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: California Department of Alcoholic Beverage Control for data. SanGIS for geocoding of San Diego data and presenting in a GIS-compatible format.
Description: This dataset consists of points for the location of Alcoholic Beverage Control Licenses in San Diego County geocoded from address information obtained from the California Department of Alcoholic Beverage Control (https://www.abc.ca.gov/).The dataset was downloaded in .lst format (https://www.abc.ca.gov/datport/DataExport.html), converted to Excel format and the records for San Diego County extracted. The San Diego records were then geocoded using the SANDAG composite locator. Note that a small percentage (circa 5%) of the records could not be geocoded and are included in the dataset without a point location. The dataset was then projected from WGS 1984 Web Mercator (auxillary sphere) into NAD_1983_StatePlane California VI FIPS 0406 (US Feet) and x y coordinate fields added.The dataset is downloaded and geocoded by SanGIS on a monthly basis. More current information may be available from the ABC website.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: California Department of Alcoholic Beverage Control for data. SanGIS for geocoding of San Diego data and presenting in a GIS-compatible format.
Description: This dataset consists of points for the location of Alcoholic Beverage Control Licenses in San Diego County geocoded from address information obtained from the California Department of Alcoholic Beverage Control (https://www.abc.ca.gov/).The dataset was downloaded in .lst format (https://www.abc.ca.gov/datport/DataExport.html), converted to Excel format and the records for San Diego County extracted. The San Diego records were then geocoded using the SANDAG composite locator. Note that a small percentage (circa 5%) of the records could not be geocoded and are included in the dataset without a point location. The dataset was then projected from WGS 1984 Web Mercator (auxillary sphere) into NAD_1983_StatePlane California VI FIPS 0406 (US Feet) and x y coordinate fields added.The dataset is downloaded and geocoded by SanGIS on a monthly basis. More current information may be available from the ABC website.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: California Department of Alcoholic Beverage Control for data. SanGIS for geocoding of San Diego data and presenting in a GIS-compatible format.
Description: This dataset consists of points for the location of Alcoholic Beverage Control Licenses in San Diego County geocoded from address information obtained from the California Department of Alcoholic Beverage Control (https://www.abc.ca.gov/).The dataset was downloaded in .lst format (https://www.abc.ca.gov/datport/DataExport.html), converted to Excel format and the records for San Diego County extracted. The San Diego records were then geocoded using the SANDAG composite locator. Note that a small percentage (circa 5%) of the records could not be geocoded and are included in the dataset without a point location. The dataset was then projected from WGS 1984 Web Mercator (auxillary sphere) into NAD_1983_StatePlane California VI FIPS 0406 (US Feet) and x y coordinate fields added.The dataset is downloaded and geocoded by SanGIS on a monthly basis. More current information may be available from the ABC website.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: California Department of Alcoholic Beverage Control for data. SanGIS for geocoding of San Diego data and presenting in a GIS-compatible format.
Description: The original FEMA layer name was S_BFE_StatePlane. This layer shows theBase flood elevation lines on the printed DFIRM. The layer was downloaded from FEMA DFIRMs on 05-07-2012. The Original data was in UTM coordinate system. The data was converted from UTM to match City data of:
Projected Coordinate System: NAD_1983_StatePlane_California_VI_FIPS_0406_Feet
Projection: Lambert_Conformal_Conic The original data covered the entire San Diego County but was clipped by the City boundy.
Color: [0, 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: 12 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: The original layer name from FEMA ia s_firm_pan. It was projected from NAD27 to NAD 83. This layer shows the Flood Insurance Rate Map pannels. It was down loaded from the FEMA Map Services.
Color: [0, 34, 51, 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: 16 Font Family: Arial Black Font Style: normal Font Weight: normal Font Decoration: none
Description: Parcels represent taxable pieces of property. A parcel is created by the San Diego County Assessor/Recorder/County Clerk (ARCC) to identify a specific portion of real property that is taxed at a certain rate for a certain owner. Tax parcels are typically the same as a legally subdivided lot but are not necessessarily so. For example, a single owner may own a legally subdivided piece of property but there may be two or more tax parcels covering that property. Legal subdivisions are shown in the LOTS layer.Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).The SanGIS parcel layers are “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building in downtown San Diego may have 200 individual condos. Each condo is a separate taxable parcel. All 200 parcels will be associated with the same physical lot on the ground. When the SanGIS parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 200 polygons all stacked on top of each other that represent the taxable parcels and each polygon will have the same physical characteristics (shape, size, area, location) – they are, essentially, copies of each other. However, other associated information (owner, document numbers, etc) will be different for each. In this case, each condo unit will have its own parcel number and there will be no single parcel representing the lot on the ground. Besides condominiums there are two other cases where you will see stacked parcels – possessory interest and mobile homes. Possessory interests have Assessor Parcel Numbers (APNs) that start with 76x. A possessory interest (or PI) parcel represents a taxable interest in the underlying, or parent, parcel but not necessarily ownership. For instance, a private company may have an arrangement with a University to operate a business on campus – a coffee shop or gift shop for example. The private business is taxable and is assinged a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory intestests do not represent ownership on the parcel, only a taxable interest in the underlying parent parcel.Mobile home parcel APNs start with 77x. In a manner similar to the possessory interests, mobile home owners own their home (coach) but not the underlying property on which the house sits. The actual mobile home is a separate taxable parcel associated with the mobile home park parent parcel. These taxable parcels all have the same polygon as the underlying parent parcel and will show as stacked parcels as well.This dataset contains parcels as shown on the Assessor Parcel Maps (APM). However, parcels shown in this layer may lag that of the official APM by a number of weeks due to how SanGIS is notified of the newly created parcel and the timing of publication of the parcel layer.This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in thier Master Property Record (MPR file) and Parcel Assessment Record (PAR file). In addition to the MPR and PAR data assigned by ARCC, SanGIS may add situs address information if it has been provided by the addressing authority in which the parcel is situated. The situs address information provided by SanGIS may not be the same as the SITUS address data in the MPR.This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include:Land use information provided in the NUCLEUS_USE_CD field (225 types with a 3-digit domain). The ASR_LANDUSE field is an older version of this field but comprises more generalized land uses (91 types). Generalized land use zoning information is provided in the NUCLEUS_ZONE_CD field. The ASR_ZONE field is an older version of this field. Land use zoning is generalized comprising 9 zone types. This can provide a useful approximation for parcels that are outside of the San Diego City and County zoning jurisdictions.Please note that land use and zoning fields are not regularly maintained by the Assessor's Office and should only be used as an approximate guide. Updates are only made when there is new construction, or a change in ownership. They are not updated when the County and Local Cities update their zoning data or when permit changes to properties are completed. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data. NOTE: If the name of this layer includes "_NORTH", "_SOUTH", or "_EAST" it represents a subset of the entire San Diego County Parcel Base. That is, the "_NORTH" layer includes only parcels generally in the Northwestern portion of the County. The "_SOUTH" layer includes parcels in the Southwestern portion. And the "_EAST" layer includes parcels in the approximate Eastern half of the County.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: SanGIS using legal recorded data provided by the County Recorders and Assessor's Office. See the County ARCC website at https://arcc.sdcounty.ca.gov/Pages/default.aspx for more information about tax parcels
Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [Basin_Name] CONCAT " GROUND WATER BASIN" Use Coded Values: true Symbol:
Color: [135, 188, 245, 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: 16 Font Family: Arial Rounded MT Bold Font Style: normal Font Weight: normal Font Decoration: none
Description: Public transit stops in San Diego County serviced by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley stops developed from the General Transit Feed Specification (GTFS) data available from the transitland feed registry (and formerly the GTFS Data Exchange). Stops are developed from the GTFS data available through the transitland feed registry (https://transit.land/feed-registry/) and formerly from 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 stops for both MTS and NCTD systems. SanGIS uses built-in ArcGIS tools to develop the stops from the STOPS.txt data file.Stops layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
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 transitland feed registry (https://transit.land/feed-registry/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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 transitland feed registry (formerly from GTFS Data Exchange). Routes are developed from the GTFS data available through the transitland feed registry (https://transit.land/feed-registry/), formerly from the GTFS Data Exchange. 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: f1ada56b3d6b4c20975e8aae00bd221f
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 transitland feed registry (https://transit.land/feed-registry/) and formerly from the GTFS Data Exchange (http://www.gtfs-data-exchange.com/). GTFS data specifications are available at https://developers.google.com/transit/overview.
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: 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 right of way polygons within the County of San Diego. A right of way is defined as a dedicated right for the public to travel unhindered, to access a route regardless of land ownership or any other legality. Rights-of-way are shown whether they are improved (constructed) or unimproved. Not all dedicated rights-of-way may be shown.SanGIS notes that the original source is an SDGE dataset that has been updated on a continual basis by SanGIS since. The dataset is as current and complete as the reference data on hand. The data is updated per recorded Subdivision and Parcel maps received, Record of Surveys, Recorded Documents (Road Opening / Road Closure), Assessor Parcel map cuts, and data received from local jurisdictions including State and Federal entitites. The right-of-way dataset is maintained as part of the SanGIS parcel dataset. The right-of-way parcel subtype is excluded from the published parcel layer and is published separately as this right-of-way layer as requested by the City and County of San Diego. Data schema for this layer does not include attributes from the Master Property Record (MPR) that are added to the published Parcel layers.For details of attributes refer to field definitions under resources.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: SanGIS using legal recorded data provided by the County Recorder and Assessor's 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: f1ada56b3d6b4c20975e8aae00bd221f
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: f1ada56b3d6b4c20975e8aae00bd221f
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: f1ada56b3d6b4c20975e8aae00bd221f
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: f1ada56b3d6b4c20975e8aae00bd221f
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: f1ada56b3d6b4c20975e8aae00bd221f
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: Parcels represent taxable pieces of property. A parcel is created by the San Diego County Assessor/Recorder/County Clerk (ARCC) to identify a specific portion of real property that is taxed at a certain rate for a certain owner. Tax parcels are typically the same as a legally subdivided lot but are not necessessarily so. For example, a single owner may own a legally subdivided piece of property but there may be two or more tax parcels covering that property. Legal subdivisions are shown in the LOTS layer.Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).The SanGIS parcel layers are “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building in downtown San Diego may have 200 individual condos. Each condo is a separate taxable parcel. All 200 parcels will be associated with the same physical lot on the ground. When the SanGIS parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 200 polygons all stacked on top of each other that represent the taxable parcels and each polygon will have the same physical characteristics (shape, size, area, location) – they are, essentially, copies of each other. However, other associated information (owner, document numbers, etc) will be different for each. In this case, each condo unit will have its own parcel number and there will be no single parcel representing the lot on the ground. Besides condominiums there are two other cases where you will see stacked parcels – possessory interest and mobile homes. Possessory interests have Assessor Parcel Numbers (APNs) that start with 76x. A possessory interest (or PI) parcel represents a taxable interest in the underlying, or parent, parcel but not necessarily ownership. For instance, a private company may have an arrangement with a University to operate a business on campus – a coffee shop or gift shop for example. The private business is taxable and is assinged a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory intestests do not represent ownership on the parcel, only a taxable interest in the underlying parent parcel.Mobile home parcel APNs start with 77x. In a manner similar to the possessory interests, mobile home owners own their home (coach) but not the underlying property on which the house sits. The actual mobile home is a separate taxable parcel associated with the mobile home park parent parcel. These taxable parcels all have the same polygon as the underlying parent parcel and will show as stacked parcels as well.This dataset contains parcels as shown on the Assessor Parcel Maps (APM). However, parcels shown in this layer may lag that of the official APM by a number of weeks due to how SanGIS is notified of the newly created parcel and the timing of publication of the parcel layer.This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in thier Master Property Record (MPR file) and Parcel Assessment Record (PAR file). In addition to the MPR and PAR data assigned by ARCC, SanGIS may add situs address information if it has been provided by the addressing authority in which the parcel is situated. The situs address information provided by SanGIS may not be the same as the SITUS address data in the MPR.This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include:Land use information provided in the NUCLEUS_USE_CD field (225 types with a 3-digit domain). The ASR_LANDUSE field is an older version of this field but comprises more generalized land uses (91 types). Generalized land use zoning information is provided in the NUCLEUS_ZONE_CD field. The ASR_ZONE field is an older version of this field. Land use zoning is generalized comprising 9 zone types. This can provide a useful approximation for parcels that are outside of the San Diego City and County zoning jurisdictions.Please note that land use and zoning fields are not regularly maintained by the Assessor's Office and should only be used as an approximate guide. Updates are only made when there is new construction, or a change in ownership. They are not updated when the County and Local Cities update their zoning data or when permit changes to properties are completed. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data. NOTE: If the name of this layer includes "_NORTH", "_SOUTH", or "_EAST" it represents a subset of the entire San Diego County Parcel Base. That is, the "_NORTH" layer includes only parcels generally in the Northwestern portion of the County. The "_SOUTH" layer includes parcels in the Southwestern portion. And the "_EAST" layer includes parcels in the approximate Eastern half of the County.
Service Item Id: f1ada56b3d6b4c20975e8aae00bd221f
Copyright Text: SanGIS using legal recorded data provided by the County Recorders and Assessor's Office. See the County ARCC website at https://arcc.sdcounty.ca.gov/Pages/default.aspx for more information about tax parcels
Color: [0, 169, 230, 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: 11 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 128, 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: [137, 68, 68, 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: 12 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none