Facebook
TwitterThe 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.
Facebook
TwitterCDFW BIOS GIS Dataset, Contact: Eric Zahn, Description: This dataset represents a summary of SDTT data collected from 1996-2006. Any track or sign identified from 15 target animals was recorded. Surveys consisted of transects of approximately one mile in length and 30 feet in width along designated dirt trails and roads throughout open space lands in San Diego County.
Facebook
TwitterThis resource is a member of a series. 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) System (MTS). The MTS 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. The All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.
Facebook
TwitterThis 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.
Facebook
TwitterThis 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).
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The California Department of Fish and Wildlife Vegetation Classification and Mapping Program (VegCAMP) created a fine-scale vegetation classification and map of the Department's Oak Grove property, San Diego County, California following FGDC and National Vegetation Classification Standards. The vegetation classification was derived from floristic field survey data collected in the field in May 2010 and was based on previously described Alliances and Associations. The map was produced using true-color 2009 1-meter National Agricultural Imagery Program (NAIP) imagery as the base. Supplemental imagery including 2005 1-meter California Color Infrared (CIR) and true-color 1-foot aerial imagery available through GlobeXplorer ImageConnect were also used. The minimum mapping unit (MMU) is one acre, with the exception of wetland types, which were sometimes mapped to ½ acre. Field verification of 45 percent of the mapped polygons was conducted in June 2011; in combination with the 2010 sampling effort, 83 percent of the polygons were verified in the field.
Facebook
TwitterDownload 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
Facebook
TwitterVector 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.
Facebook
TwitterPoint feature layer of City of San Diego library locations with associated website and contact information, created by the County of San Diego Department of Public Works GIS, in conjunction with San Diego County Library (SDCL).
Facebook
TwitterThese parcels are symbolized by SCAG land use codes for San Diego County. The work was done for a GIS Practicum project at Claremont Graduate University, Spring 2023.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
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
Facebook
TwitterPublic 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.Please note that this data was reprojected 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/
Facebook
TwitterPublic transit stops and stations covering the County of San Diego. Bus, commuter and light rail, and trolley stops managed by the San Diego County Metropolitan Transit System (SDMTS) and the North County Transit District (NCTD). Data is developed from the General Transit Feed Specification (GTFS) data available from the GTFS Data Exchange. Layer is updated quarterly and may not reflect most current route information.
Facebook
Twitter4" and 9" tiled imagery mosaic for the San Diego County region. Web Mercator Auxiliary Sphere. See metadata:
Facebook
TwitterWARNING: 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.
Facebook
TwitterPlease note that the included metadata applies to the full set of data provided by the San Francisco Estuary Institute. This layer represents historical habitats and does not include historical creeks and distributaries. Please see https://www.sfei.org/content/northern-san-diego-county-lagoons-historical-ecology-gis-data#sthash.U9l5NJNt.SGa2tbKs.dpbs for additional information.Original metdata as provided by the San Francisco Estuary Institute:OverviewThis geodatabase contains several feature classes representing a reconstruction of the historical ecological conditons of six northern San Diego County lagoons (Buena Vista Lagoon, Agua Hedionda Lagoon, Batiquitos Lagoon, San Elijo Lagoon, San Dieguito Lagoon, and Los Peñasquitos Lagoon) prior to Euro-American modification. This dataset integrates many sources of data describing the historical features of the estuaries.Extensive supporting information, including bibliographic references, analyses, and research methods, can be found in the accompanying report:Beller EE, Baumgarten SA, Grossinger RM, Longcore TR, Stein ED, Dark SJ, Dusterhoff SR. 2014. Northern San Diego County Lagoons Historical Ecology Investigation: Regional Patterns, Local Diversity, and Landscape Trajectories. Prepared for the State Coastal Conservancy. SFEI Publication #722, San Francisco Estuary Institute, Richmond, CA.The report and GIS data area available at the project website: http://www.sfei.org/HE_San_Diego_Lagoons.A geographic information system was used to collect, catalog, and analyze the spatial components of the study area. Historical maps and aerial photography were georeferenced, allowing us to compare historical layers to each other and to contemporary aerial photography and maps. Additionally, the georeferenced maps were used as a means to geographically locate information gathered from surveyor notes, early explorers' journals, travelers' accounts, and newspaper articles. Using the various georeferenced maps and photographs combined with narrative sources we constructed a series of synthesis layers representing historical ecological conditions for the six estuaries. The polygon and line layers making up the historical habitat map include Historical_Habitats, Historical_Creeks, and Historical_Distributaries.Habitat types used in the Historical_Habitats layer include Salt Marsh, Salt Flat (Seasonally Flooded), Open Water / Mud Flat, Freshwater / Brackish Wetland, Beach, and Dune. See the Northern San Diego County Lagoons Historical Ecology Investigation for a detailed description of the historical habitat types and the methods that were used to map them.Historical creeks and their distributaries were mapped as polyline features in two distinct layers. Distributary channels mark the endpoints of historically discontinuous channels.--Historical_Habitats Attribute Table Fields:Habitat_Type: The historical habitat type classification.Interp_Cert: coded H (high): feature definitely present before Euro-American modification; M (medium): feature probably present before Euro-American modification; or L (low): feature possibly present before Euro-American modification. Shape_Cert: coded H (high): mapped feature expected to be 90%-110% of actual feature size; M (medium): expected to be 50%-200% of actual size; L (low): expected to be 25%-400% of actual size. Loc_Cert: coded H (high): expected maximum horizontal displacement less than 50 m; M (medium): less than 150 m; L (low): less than 500 m.Notes: Additional documentation about the feature.S_Digitize: Source data used to digitize a feature. S_Interp1: Interpretation Source 1 - Primary data used to interpret a mapped feature if other than the digitizing source – often the earliest historical documentation/evidence found.S_Interp2: Interpretation Source 2 - Data used to support mapping of a feature – additional documentation/evidence other than Interpretation Source 1.Name: The name of the lagoon/wetland complex.Source_Quotes: Excerpt(s) from historical textual data sources used to support mapping of a feature.Source_Quotes2: Excerpt(s) from historical textual data sources used to support mapping of a feature.Notes2: Additional documentation about the feature.Shape.area: Area of the feature in square meters.Shape.len: Length of the feature in meters.--Historical_Creeks Attribute Table Fields:Interp_Cert: coded H (high): feature definitely present before Euro-American modification; M (medium): feature probably present before Euro-American modification; or L (low): feature possibly present before Euro-American modification. Shape_Cert: coded H (high): mapped feature expected to be 90%-110% of actual feature size; M (medium): expected to be 50%-200% of actual size; L (low): expected to be 25%-400% of actual size. Loc_Cert: coded H (high): expected maximum horizontal displacement less than 50 m; M (medium): less than 150 m; L (low): less than 500 m.Notes: Additional documentation about the feature.S_Digitize: Source data used to digitize a feature. S_Interp1: Interpretation Source 1 - Primary data used to interpret a mapped feature if other than the digitizing source – often the earliest historical documentation/evidence found.S_Interp2: Interpretation Source 2 - Data used to support mapping of a feature – additional documentation/evidence other than Interpretation Source 1.Marsh_Comp: Lagoon/marsh complex into which the channel drains.SHAPE.len: Length of the channel feature in meters.Flow: Channel type (Perennial, Intermittent, Unknown).--(Attribute table information not provided for Historical_Distributary layer)--Additional Bibliographic Information:For a full list of works cited in this study, please consult the References section of the Northern San Diego County Lagoons Historical Ecology Investigation. Additional information about sources cited in the GIS layers is provided below:USGS Digital Raster Graphics (DRG) for the study area were created/revised between 1975 and 1983, and are cited as USGS 1975-1983.Historical aerial photographs are cited as San Diego County 1928. In some cases, the citation is followed by a number in parentheses specifying the particular image consulted.Abbreviated source institution names and accession numbers are provided for additional photographs cited in the GIS layers. Source institutions include:Carlsbad Pub Library = Carlsbad City Library Carlsbad History RoomScripps = Scripps Institution of Oceanography Archives, UC San DiegoSDHC = San Diego History CenterSpence Air Photos = Benjamin and Gladys Thomas Air Photo Archives, UCLA Department of GeographyAdditional sources not cited in the report include:Alexander WE. n.d. Plat book of San Diego County, California. Township 13 S., R. 3 W. Township 13 S., R. 4 W. Los Angeles, CA: Pacific Plat Book Company. Courtesy of The Bancroft Library, UC Berkeley.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year
Facebook
TwitterThis is a single polygon that depicts all of Bexar County and the Extra-Territorial Jurisdiction (ETJ) areas for the City of San Antonio. This is the minimum coverage area needed by the City for aerial imagery.
This data is being used as reference for the Aerial Imagery Service Request for Proposals (RFP).
Facebook
TwitterThe 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.