This dataset comprises polygons of census tracts for San Diego County. A census tract is a geographic region defined for the purpose of taking a census. Usually these coincide with the limits of cities, towns or other administrative areas and several tracts commonly exist within a county. In unincorporated areas, these are often arbitrary, except for coinciding with political lines. Census tracts are subdivided into block groups and census blocks.The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.The Census Tracts dataset is based on the TIGER dataset and may be edited by SANDAG and further edited by SanGIS to reflect local boundary datasets. However, SanGIS edits the CENSUS_BLOCK layer and then derives the CENSUS_TRACT layer from the blocks.

This service displays the Places layer and used used as the basis for the Places search service.

The SanGIS data set includes an extensive collection of GIS maps that are available to the public.

 Application Data Included:

 1. Public Safety: Crime Mapping & Analysis, Computer Aided Dispatch,
 Emergency Response Planning

 2. Planning & Development: Specific Plans, Vegetation Mapping, Zoning,
 Geologic Hazards, Codes Enforcement

 3. Facilities Management: Water and Waste Water Utilities, Street
 Lighting, Storm Drains, Pavement Management

 4. Subdivision Mapping: Basemap Maintenance, Parcel Mapping, Survey
 Control, Orthophotography

 5. Route Management: Water Meter Readers, Trash & Recycling Routes

 6. Decision Support & Analysis: Facility Siting, Airport Noise, Slope
 Analysis, Demographics, Economic Development

 SanGIS was created in July, 1997, as a Joint Powers Agreement (JPA)
 between the City and County of San Diego. After 13 years of working
 together on data and application development, the City and County
 decided to formalize their partnership in GIS by creating the SanGIS
 JPA. Finding that access to correct and current geographic data was
 considered more important than application development to County and
 City departments, SanGIS focuses on ensuring geographic data is
 maintained and accessible.

 SanGIS Mission:

 To maintain and promote the use of a regional geographic data
 warehouse for the San Diego area and to facilitate the development of
 shared geographic data and automated systems which use that data.

 SanGIS Goals:

 1. To ensure geographic data currency and integrity.

 2. To provide cost effective access to geographic data to member
 agencies, subscribers and the public.

 3. To generate revenue from the sale of geographic data products to
 reduce the cost of map maintenance to member agencies.

 Data Collection:

 SanGIS data was created or obtained from several sources. Some of our
 data is licensed; some data was created from tabular digital files;
 some data was digitized from paper maps; and other data was entered
 using coordinate geometry tools.

 Updating the Data:

 Responsibility for the maintenance of the over 200 geographic data
 layers is distributed to City and County departments based on several
 factors such as who has the source documents, who has the greatest
 need for the data, and who is held accountable for this data as part
 of their city-wide or county-wide duties. Most basemap maintenance is
 completed by SanGIS staff. SanGIS is also responsible for coordinating
 with other data maintainers to ensure currency and accuracy for all
 participants.

 Data Coverage:

 All of the SanGIS geographic data is within San Diego County
 only. Much of our data covers the entire County of San Diego but some
 is only for the City of San Diego.

 [Summary provided by SanGIS]

URL from idinfo/citation in CSDGM metadata.

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 assigned a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory interests 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.

​

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

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.

Download Data Dictionary (CSV)This dataset comprises polygons representing current taxable parcels, including some non-taxable parcels, specifically within the city limits of Carlsbad. The data, sourced from SanGIS, contains parcels as shown on the Assessor Parcel Map (APM). It's important to note that parcels shown in this layer may lag behind the official APM by a number of weeks due to the timing of SanGIS being notified of newly created parcels and the publication schedule of the parcel layer. The City of Carlsbad GIS processes parcels monthly, adding another delay in the inclusion of newly created parcels.Point of Contact:For inquiries about land-use details and the implications of a property being within special zones/planning areas, overlay zones, including Coastal Zone, Redevelopment Zone, Beach Overlay Zone, Fire Zone, and Visitor Zone.City of Carlsbad Planning Division1635 Faraday AvenueCarlsbad, California 92008442-339-2610For the latest and most specific tax parcel information represented by parcel polygons, please refer to the SanGIS website or consult the San Diego County Assessor/Recorder/County Clerk (ARCC).SanGIS5510 Overland Avenue, Suite 230San Diego, California 92123858-874-7000

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.

This dataset comprises polygons of public parks in the County of San Diego, including open space parks and preserves. This dataset was created by merging parks datasets from the following sources: County of San Diego, City of San Diego, San Diego Port District, State Parks, SanGIS and 16 other incorporated cities in San Diego County.Please note that this data was published from a SanGIS dataset for use in the San Diego Ocean Planning Partnership, a collaborative pilot project between the California State Lands Commission and the Port of San Diego. For more information about the Partnership, please visit: https://www.sdoceanplanning.org/

UAB "Sangis" financial data: profit, annual turnover, paid taxes, sales revenue, equity, assets (long-term and short-term), profitability indicators.

A geographic representation of the municipal boundaries updated by SanGIS when notified by LAFCO of a recorded annexation or detachment. The revised layer is published as needed once changes are made and verified. Adjustments are also made to this dataset from ongoing landbase maintenance activities.SanGIS will add individual polygons for annexations to a municipal jurisdiction but will not maintain a separate polygon for the agency losing territory. That is, a polygon will be created for the "gain" but the "loss" will be reflected only by modifying the existing boundary. On an annual basis, SanGIS will reconcile the JUR_MUNICIPAL layer with the JUR_MUNICIPAL_ASR layer developed by the Assessor. This will happen when the Assessor publishes the annual TRA updates. SanGIS will accept the Assessor layer as is and use it as the basis for new annexations/detachments going forward. Individual polygons that have been created in the past year will be incorporated into the municipal boundary as shown on the Assessor's TRA updates. NOTE: The County Assessor's Office JUR_MUNICIPAL_ASR layer is the official Municipal Boundary layer; however, it is created for tax purposes and is only updated on an annual basis as required by state law.

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.

Approximate areas covered by each US Postal Service (USPS) Zip Code in San Diego County. Areas are approximate boundaries only as determined by SanGIS and SanGIS JPA member users and associates. Does not represent an official depiction of USPS Zip Code boundaries. Does not represent all zip codes that may be used in the County. Certain Zip Codes are assigned for post office boxes only and cannot be represented by polygons. Note that the USPS does not define a Zip Code as an area. USPS defines a zip code as the identifier for the post office that mail will be delivered from. SanGIS Zip Code boundaries are approximated from situs addresses and information received from SanGIS JPA members and associates.

Data from BLM Geocommunicator were merged with Indian Reservations of San Diego County (SanGIS) and a dataset associated with Phase 2A RETI documents. The product contains lands in California that are of very small size. Last update: September 4, 2009.

This dataset comprises polygons of census tracts for San Diego County. A census tract is a geographic region defined for the purpose of taking a census. Usually these coincide with the limits of cities, towns or other administrative areas and several tracts commonly exist within a county. In unincorporated areas, these are often arbitrary, except for coinciding with political lines. Census tracts are subdivided into block groups and census blocks.The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.The Census Tracts dataset is based on the TIGER dataset and may be edited by SANDAG and further edited by SanGIS to reflect local boundary datasets. However, SanGIS edits the CENSUS_BLOCK layer and then derives the CENSUS_TRACT layer from the blocks.

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.

School site addresses maintained by California Department of Education (CDE) were geocoded to the SanGIS parcels and street centerlines. Using aerial imagery, online research, site visits, and over-the-phone/email verification, attributes were corrected and/or polygons were adjusted to best represent the portion of the parcel in active use for school-related activities. This layer includes active schools.

SANDAG performs an annual land use and housing unit inventory in the interest of maintaining a robust and accurate catalog of the existing conditions for any given year. This catalog of snapshots are the land use data on which the regional forecast is based every four years. Prior to performing our annual inventory, the polygon geometry for the regionwide layer is updated with a snapshot of parcels from SanGIS representative of January first of the given year. The land use information has been updated continuously since 2000 using aerial photography, the County Assessor Master Property Records file, and other ancillary information. To make the Landuse 2018 feature class, adjacent parcel polygons with the same land use have been aggregated (dissolved) into a single feature.

The types of data in this feature class are school names, spatial locations, addresses, and additional school details (e.g. status of operation, whether the facility is private or public,etc.). School addresses were sourced from the California Department of Education (CDE) and were geocoded using the SanGIS parcels and street centerlines. The attributes from previous School iterations were also updated using aerial imagery, online research, site visits, and over-the-phone/email verification. Certain points were manually relocated to school buildings.

Polygons of public and private school sites. Includes elementary, middle, and high schools. Intended use is mapping and general analysis purposes. Provided by SANGIS and hosted by H-Hub at UC San Diego. School site addresses maintained by California Department of Education (CDE) were geocoded to the SanGIS parcels and street centerlines. Using aerial imagery, online research, site visits, and/or over-the-phone verification, attributes were corrected and/or polygons were adjusted to best represent the portion of the parcel in active use for school-related activities. This layer includes active schools.