Point 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).

Latest Study Effective Date 03/22/2022, Latest LOMR Effective Date 08/29/2024The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA.The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).This layer is derived from NFHL Product ID NFHL_06073C, San Diego County-wide, Latest Study Effective Date and Latest LOMR Effective Date as mentioned at the top of this section in bold-faced type. with the additional County of San Diego, Department of Public Works, Flood Control Engineering-derived attribute FLOODPLAI.

CDFW BIOS GIS Dataset, Contact: Emily Perkins, Description: The FPAs were designed to conserve as much of the Biological Core and Linkage Area (BCLA) as possible, minimize preserve fragmentation, maximize use of existing public lands and open space, and maintain private property rights and economic viability (MHCP Executive Summary 2003). Some areas are designated hardline and some softline. The hardline areas are designated primarily for conservation while the softline areas may be further delineated to development or conservation.

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).

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.

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.

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.

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.

Notice: Data is preliminary and subject to change. This dataset is updated in the evening on a daily basis. There is a delay in the Esri Hub caching process of between 5 - 10 minutes. Download requests will be queued in your browser prior to execution during the caching process and resume once the data cache is rebuilt.COVID-19 Statistics San Diego CountyData source: County of San Diego, Health and Human Services Agency, Public Health Services, Epidemiology and Immunization Services Branch

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/

Locations and health center information was sourced from https://www.fhcsd.org/clinic-location-list/. This list was digitized into a spreadsheet and geolocated using ArcGIS World Geocoding Service. To be hosted by Homelessness Hub at UC San Diego. Data is current to April 2024.

description: This data layer was provided to CSMW by Moffatt Nichol as part of their efforts related to compiling the San Diego Coastal RSM Plan. The data was reportedly collected by Thales Geosolutions, Inc as High Resolution Multibeam acoustic Backscatter and processed by KTU+A for the San Diego Region Nearshore Coastal Zone Program.These data are intended for science researchers, students, policy makers, and the general public. The data can be used with GIS or other software to display the seafloor substrate types of the Nearshore Coastal Zone of the San Diego Region.Dataset was submitted to CSMW by SANDAG as part of the San Diego County Coastal Regional Sediment Management Plan (2009).; abstract: This data layer was provided to CSMW by Moffatt Nichol as part of their efforts related to compiling the San Diego Coastal RSM Plan. The data was reportedly collected by Thales Geosolutions, Inc as High Resolution Multibeam acoustic Backscatter and processed by KTU+A for the San Diego Region Nearshore Coastal Zone Program.These data are intended for science researchers, students, policy makers, and the general public. The data can be used with GIS or other software to display the seafloor substrate types of the Nearshore Coastal Zone of the San Diego Region.Dataset was submitted to CSMW by SANDAG as part of the San Diego County Coastal Regional Sediment Management Plan (2009).

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]

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) downloaded from https://www.sdmts.com/google_transit_files/google_transit.zip and http://www.gonctd.com/google_transit.zip.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.

Public transit stops in San Diego County serviced by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Provided by SANGIS and hosted by H-Hub at UC San Diego. Current to 2024.Bus, commuter and light rail, and trolley stops developed from the General Transit Feed Specification (GTFS) downloaded from https://www.sdmts.com/google_transit_files/google_transit.zip and https://www.goncts.com/google_transit.zip. 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. Stop layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.

The power outages in this layer are pulled directly from the utility public power outage maps and is automatically updated every 15 minutes. This dataset represents only the most recent power outages and does not contain any historical data.

Link to landing page referenced by identifier. Service Protocol: Link to landing page referenced by identifier. Link Function: information-- dc:identifier.

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.

This is a geographic database of public, private, and charter schools in San Antonio and Bexar County. It was compiled from all available sources and rectified (QAQC) as of 2012.

© Bexar County IT eServices GIS