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.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

This dataset is a collection of the current base zone designations applied to property in the City of San Diego, as per the Official Zoning Map adopted by the City Council on February 28, 2006, and all subsequent updates.Residential Base Zones (RE, RS, RX, RT, RM) https://docs.sandiego.gov/municode/MuniCodeChapter13/Ch13Art01Division04.pdf Areas designated for single and multi-family residences. More information about Residential Base Zone regulations are available from https://www.sandiego.gov/development-services/zoning/zoninginfo/zoninginfo130104 Commercial Base Zones (CN, CR, CO, CV, CP, CC) https://docs.sandiego.gov/municode/MuniCodeChapter13/Ch13Art01Division05.pdf Areas intended for businesses that provide consumer goods and services as well as a wide variety of commercial, retail, office and recreational uses. Industrial Base Zones (IP, IL, IH, IS, IBT) https://docs.sandiego.gov/municode/MuniCodeChapter13/Ch13Art01Division06.pdf Areas intended for research and development, factories, warehousing and other industrial uses. Mixed-Use Base Zones (RMX, EMX) https://docs.sandiego.gov/municode/MuniCodeChapter13/Ch13Art01Division07.pdf

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

Geospatial data about City of San Diego, California Contours. Export to CAD, GIS, PDF, CSV and access via API.

This dataset comprises centerline segments for roads (both active and inactive, public and private, constructed or of record) in San Diego County based on data received from all official jurisdictions within the County (the County and 18 cities).

The TIGER/Line shapefiles and related database files (.dbf) 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 shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This layer is a georeferenced image of the first "road" atlas of California. According to Tom Lennon of Thomas Brothers Map Co. in Los Angeles, this atlas is rare; they have five copies of it in their L.A. office, and he has never seen any other copies. He thinks the original issue was very small. Bancroft has no copies, but does have a copy of Thomas Bros. Atlas of Western Cities and Towns (no date but library note says acquired in 1937) which duplicates some of this atlas's material (smaller S.F. map, larger color Pasadena map) and adds more on cities in adjoining western states. Lennon said this atlas was "a put together thing by George Thomas." He also said there was an Atlas of the San Francisco Bay Area by the company, produced for the World's Fair of 1936. Maps are printed with and without color. Bound with three illustrated promotional pamphlets advertising various scenic areas of California. The original map appears in 'Thomas Bros. Recreational and Statistical Atlas, California.'

2005 Lidar coverage over cities of San Diego, Poway, and Chula Vista. These lidar data are part of a larger project that collected lidar for a number of coastal cities in San Diego County. Data from the same 2005 lidar project may be available for other cities beyond San Diego, Poway, and Chula Vista but those cities should be contacted individually. Lidar data were collected in conjunction with a three-inch resolution imagery collection for San Diego, Poway, and Chula Vista. Lidar products include LAS files and ASCII canopy data at a minimum; Poway adds two foot contours. Point spacing of LAS data is approximately one meter. Data have also been resampled to a one-ninth arc second grid (three meter spacing) and placed within the National Elevation Dataset.

The California Senate Bill 743 (SB 743) (Steinberg, 2013) VMT maps provide an estimate of personal vehicle travel by residents and employees within the San Diego region. The California Office of Planning and Research released a Technical Advisory on Evaluating Transportation Impacts in CEQA (https://opr.ca.gov/ceqa/sb-743/) and the maps provided by SANDAG are an interpretation of the guidelines provided as a resource to the jurisdictions in our region to use as they see fit. The estimated data in these maps are an analysis of travel using SANDAG’s ABM. The currently approved ABM version (14.2.2) used for the 2021 Regional Plan is ABM2+ with the Series 14 Growth Forecast version 38. The historic version of the ABM (14.1.1) was used for the 2019 Regional Transportation Plan with the Series 14 Growth Forecast version 17. These maps and data are subject to change as new estimates are produced using updated inputs and methodologies. Local jurisdictions are under no obligation to use the data in their development approval processes or transportation analyses under SB 743. Users of the data should exercise their professional judgment in reviewing, evaluating, and analyzing VMT reduction estimate results from the tool. Each agency should consult with California Environmental Quality Act (CEQA) experts and legal counsel regarding their own CEQA practices and updates to local policies. The estimated data are provided at four geographic scales: City, City/County CPA, Census Tract, and Traffic Analysis. For each geography SANDAG provides the VMT data per capita and per employee. VMT per capita represents the average amount of personal, non-commercial, vehicle travel made on an average weekday by each resident who lives within that geographic boundary. VMT per employee represents the average amount of personal, non-commercial, vehicle travel made on an average weekday by each resident employee whose employment/work location is within that geographic boundary. When downloading and viewing this layer in GIS or tabular formats, all records will be displayed by default. In order to limit the records to a specific VMT category, a query or filter on [version], [geo], [year], and [vmt_type] fields will need to be applied. For example, when using the query in GIS you can set the definition query to: [version] = "ABM2+ / 2021 RP" AND [geo] = "Census Tract" AND [year] = 2016 AND [vmt_type] = "Residents" - this query will display only records for census tracts with 2016 VMT estimates by residents. An example in Excel would consist of setting the filter (checkbox) [version] = "ABM2+ / 2021 RP", [geo] = "Census Tract", [year] = 2016, and [vmt_type] = "Residents" to display records for census tracts with 2016 VMT estimates by residents.

This shapefile contains tax rate area (TRA) boundaries in San Diego County for the specified assessment roll year. Boundary alignment is based on the 2014 county parcel map. A tax rate area (TRA) is a geographic area within the jurisdiction of a unique combination of cities, schools, and revenue districts that utilize the regular city or county assessment roll, per Government Code 54900. Each TRA is assigned a six-digit numeric identifier, referred to as a TRA number. TRA = tax rate area number

This is a graphical polygon dataset depicting the polygon boundaries of Cities within Bexar County Texas and Surrounding Counties. (excluding San Antonio)Updated per Ordinance No. 564, No. 565, and No. 567 on April 9, 2015 extending the Helotes City limits with the annexation of four parcels of vacant property known as Bricewood Subdivision. Updated previously per Resolution No 2012-007-R From the City of Somerset .Updated per ordinance 2014-09-04-0657 (Savano Park ETJ ONLY release)Updated per ordinance 2014-09-04-0658 (Live Oak City Limit release)Updated per ordinance 2014-08-21-0614 (Fair Oaks Ranch ETJ ONLY release.

Layer extracted from the SANDAG Bike Map: https://www.sandag.org/projects-and-programs/bikeways-and-walkways/bike-map. Website Description on the dataset: "Over 1,800 miles of bikeway connect the San Diego region, making it easy to walk, bike, or roll wherever you want to go. The San Diego Regional Bike Map can help you plan your trip.The bike map also serves as an inventory for existing and planned bikeways in the region. This helps transportation planners and modelers identify where gaps in our bikeway network exist and how to fix them. We continually update our data to reflect feedback from local cities and the County of San Diego."

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]

This layer is sourced from qagis.sanantonio.gov.

© Planning and Community Development Department, Comprehensive Division Updated per Ordinance 2015-01-15-0020, Boundary Adjustment of approx. 1,906.12 Acres (Government Cayon) Updated per Ordinance 2014-11-06-0861, Boundary Adjustment of approx. 36.266 Acres. Updated per Ordinance 2014-09-04-0658 Boundary Adjustment of approx. 1.73 Acres from the City of Live Oak to the City of San Antonio. Updated per Ordinance 2014-09-04-0657 Boundary Adjustment of approx. 31.81 acres from the City of Shavano park to the City of San Antonio and approx. 6.24 acres from the City of San Antonio to Shavano Park.

This layer is sourced from qagis.sanantonio.gov.

Vector polygon map data of property parcels from the City of San Antonio, Texas containing 629,531 features.

Parcel map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

Parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

Attributes for this data layer include: Shape_area, GlobalID, Shape_len, Shape, ModifiedDate, ParcelKey, and ModifiedUID.

Available for viewing and sharing in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

This layer is sourced from qagis.sanantonio.gov.

Geospatial data about Bexar County, Texas City Blocks (1896). Export to CAD, GIS, PDF, CSV and access via API.