43 datasets found
  1. D

    San Francisco Mid-Block Points

    • data.sfgov.org
    Updated Mar 27, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    SFGIS (2025). San Francisco Mid-Block Points [Dataset]. https://data.sfgov.org/Geographic-Locations-and-Boundaries/San-Francisco-Mid-Block-Points/iqyu-pwpr
    Explore at:
    csv, application/rssxml, application/rdfxml, tsv, application/geo+json, kml, kmz, xmlAvailable download formats
    Dataset updated
    Mar 27, 2025
    Dataset authored and provided by
    SFGIS
    License

    ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
    License information was derived automatically

    Area covered
    San Francisco
    Description

    A. SUMMARY This is a dataset containing points representing the midpoint of each block in the City of San Francisco. This dataset is used for geomasking (e.g. removing an exact address and replacing it with a nearby anonymized point) and other anonymization tasks.

    B. HOW THE DATASET IS CREATED This dataset was created by calculating the midpoint of each the street segment in the city (see Streets - Active and Retired) then returning the latitude and longitude of that midpoint. A street segment is a line between two intersections. Street midpoints are calculated for each side of the block.

    C. UPDATE PROCESS This dataset is updated weekly.

    D. HOW TO USE THIS DATASET Use this dataset for geomasking and other anonymization workflows.

    E. RELATED DATASETS - Streets - Active and Retired

  2. c

    California Overlapping Cities and Counties and Identifiers with Coastal...

    • gis.data.ca.gov
    • data.ca.gov
    • +1more
    Updated Oct 25, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2024). California Overlapping Cities and Counties and Identifiers with Coastal Buffers [Dataset]. https://gis.data.ca.gov/datasets/california-overlapping-cities-and-counties-and-identifiers-with-coastal-buffers
    Explore at:
    Dataset updated
    Oct 25, 2024
    Dataset authored and provided by
    California Department of Technology
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    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.

  3. San Francisco Bay Region Incorporated Cities and Towns (clipped)

    • opendata-mtc.opendata.arcgis.com
    • opendata.mtc.ca.gov
    • +1more
    Updated Nov 3, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MTC/ABAG (2021). San Francisco Bay Region Incorporated Cities and Towns (clipped) [Dataset]. https://opendata-mtc.opendata.arcgis.com/datasets/san-francisco-bay-region-incorporated-cities-and-towns-clipped-1
    Explore at:
    Dataset updated
    Nov 3, 2021
    Dataset provided by
    Metropolitan Transportation Commission
    Authors
    MTC/ABAG
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    Incorporated Places (cities and towns) are those reported to the Census Bureau as legally in existence as of May 28, 2021, under the laws of their respective states. Features were extracted from, and clipped using, California 2020 TIGER/Line shapefiles by the Metropolitan Transportation Commission. An incorporated place provides governmental functions for a concentration of people, as opposed to a minor civil division, which generally provides services or administers an area without regard, necessarily, to population. Places may extend across county and county subdivision boundaries, but never across state boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions.

  4. San Francisco Bay Region Spheres of Influence

    • opendata.mtc.ca.gov
    • hub.arcgis.com
    • +1more
    Updated Aug 23, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MTC/ABAG (2019). San Francisco Bay Region Spheres of Influence [Dataset]. https://opendata.mtc.ca.gov/datasets/e9accd91e02f47bd83edea4781eeb187
    Explore at:
    Dataset updated
    Aug 23, 2019
    Dataset provided by
    Association of Bay Area Governmentshttps://abag.ca.gov/
    Metropolitan Transportation Commission
    Authors
    MTC/ABAG
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    The California Association Local Agency Formation Commissions defines a sphere of influence (SOI) as "a planning boundary outside of an agency’s legal boundary (such as the city limit line) that designates the agency’s probable future boundary and service area." This feature set represents the SOIs of the incorporated jurisdictions for the San Francisco Bay Region.The Metropolitan Transportation Commission (MTC) updated the feature set in late 2019 as part of the jurisdiction review process for the BASIS data gathering project. Changes were made to the growth boundaries of the following jurisdictions based on BASIS feedback and associated work: Antioch, Brentwood, Campbell, Daly City, Dublin, Fremont, Hayward, Los Gatos, Monte Sereno, Newark, Oakland, Oakley, Pacifica, Petaluma, Pittsburg, Pleasanton, San Bruno, San Francisco (added to reflect other jurisdictions whose SOI is the same as their jurisdiction boundary), San Jose, San Leandro, Santa Clara, Saratoga, and Sunnyvale.Notes: With the exception of San Mateo and Solano Counties, counties included jurisdiction (city/town) areas as part of their SOI boundary data. San Mateo County and Solano County only provided polygons representing the SOI areas outside the jurisdiction areas. To create a consistent, regional feature set, the Metropolitan Transportation Commission (MTC) added the jurisdiction areas to the original, SOI-only features and dissolved the features by name.Because of differences in base data used by the counties and the MTC, edits were made to the San Mateo County and Solano County SOI features that should have been adjacent to their jurisdiction boundary so the dissolve function would create a minimum number of features.Original sphere of influence boundary acquisitions:Alameda County - CityLimits_SOI.shp received as e-mail attachment from Alameda County Community Development Agency on 30 August 2019Contra Costa County - BND_LAFCO_Cities_SOI.zip downloaded from https://gis.cccounty.us/Downloads/Planning/ on 15 August 2019Marin County - 'Sphere of Influence - City' feature service data downloaded from Marin GeoHub on 15 August 2019Napa County - city_soi.zip downloaded from their GIS Data Catalog on 15 August 2019City and County of San Francisco - does not have a sphere of influenceSan Mateo County - 'Sphere of Influence' feature service data downloaded from San Mateo County GIS open data on 15 August 2019Santa Clara County - 'City Spheres of Influence' feature service data downloaded from Santa Clara County Planning Office GIS Data on 15 August 2019Solano County - SphereOfInfluence feature service data downloaded from Solano GeoHub on 15 August 2019Sonoma County - 'SoCo PRMD GIS Spheres Influence.zip' downloaded from County of Sonoma on 15 August 2019

  5. D

    Streets – Active and Retired

    • data.sfgov.org
    Updated Mar 25, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City and County of San Francisco (2025). Streets – Active and Retired [Dataset]. https://data.sfgov.org/Geographic-Locations-and-Boundaries/Streets-Active-and-Retired/3psu-pn9h
    Explore at:
    csv, tsv, xml, application/rdfxml, application/rssxml, kmz, kml, application/geo+jsonAvailable download formats
    Dataset updated
    Mar 25, 2025
    Dataset authored and provided by
    City and County of San Francisco
    License

    ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
    License information was derived automatically

    Description

    A. SUMMARY A list of street centerlines, including both active and retired streets. These centerlines are identified by their Centerline Network Number ("CNN").

    B. HOW THE DATASET IS CREATED This data is extracted from the Department of Public Works Basemap. Supervisor District and Analysis Neighborhood are added during the loading process. These boundaries utilize the centroid (middle) of the line to determine the district or neighborhood.

    C. UPDATE PROCESS This dataset refreshes daily, though the data may not change every day.

    D. HOW TO USE THIS DATASET Note 1: The Class Code field is used for symbolization: 1 = Freeway 2 = Major street/Highway 3 = Arterial street 4 = Collector Street 5 = Residential Street 6 = Freeway Ramp 0 = Other (private streets, paper street, etc.)

    E. RELATED DATASETS

  6. Understanding street-level data

  • a

    California County Boundaries and Identifiers

    • hub.arcgis.com
    • gis.data.ca.gov
    Updated Sep 16, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2024). California County Boundaries and Identifiers [Dataset]. https://hub.arcgis.com/datasets/60b7e0f3d33b4064a4b43bf14589bfe3
    Explore at:
    Dataset updated
    Sep 16, 2024
    Dataset authored and provided by
    California Department of Technology
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Area covered
    Description

    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 boundaries 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. 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, coastal buffers are removed, leaving 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 Buffers (this dataset)Cities 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 BuffersWithout 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".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.

  • w

    Presidio Boundary

    • data.wu.ac.at
    • data.sfgov.org
    • +1more
    csv, json, kml, kmz +1
    Updated Aug 28, 2016
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of San Francisco (2016). Presidio Boundary [Dataset]. https://data.wu.ac.at/schema/data_gov/N2EwNmM1NWYtZWNmYy00MjA0LWJiYzgtNGNjODMzM2MwM2Ey
    Explore at:
    kml, csv, kmz, zip, jsonAvailable download formats
    Dataset updated
    Aug 28, 2016
    Dataset provided by
    City of San Francisco
    Description

    Boundary of the Presidio. A separate jurisdiction from the City of San Francisco. Layer created from Block 1300, Lot 001 of the City Lots layer. Learn more about the unique national park at http://www.presidio.gov/

  • a

    City Boundaries

    • santa-clara-cwpp-sccfc.hub.arcgis.com
    Updated Jul 6, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    sccfc2020 (2023). City Boundaries [Dataset]. https://santa-clara-cwpp-sccfc.hub.arcgis.com/datasets/837a316a50c14d099b72ab480a752b53
    Explore at:
    Dataset updated
    Jul 6, 2023
    Dataset authored and provided by
    sccfc2020
    Area covered
    Description

    Complete accounting of all incorporated cities, including the boundary and name of each individual city. From 2009 to 2022 CAL FIRE maintained this dataset by processing and digitally capturing annexations sent by the state Board of Equalization (BOE). In 2022 CAL FIRE began sourcing data directly from BOE, in order to allow the authoritative department to provide data directly. This data is then adjusted so it resembles the previous formats.Processing includes:Clipping the dataset to traditional state boundariesErasing areas that span the San Francisco Bay (derived from calw221.gdb)Querying for incorporated areas onlyDissolving each incorporated polygon into a single featureCalculating the COUNTY field to remove the word 'County'Version 22_1 is based on BOE_CityCounty_20220225, and includes all annexations present in BOE_CityAnx2022_20220225 and BOE_CityAnx2023_20220223.Note: The Board of Equalization represents incorporated city boundaries as extending significantly into waterways, including beyond coastal boundaries. To see the representation in its original form please reference the datasets listed above.

  • D

    Department of Public Works Active Parcel History

    • data.sfgov.org
    application/rdfxml +5
    Updated Mar 26, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2025). Department of Public Works Active Parcel History [Dataset]. https://data.sfgov.org/Geographic-Locations-and-Boundaries/Department-of-Public-Works-Active-Parcel-History/6df5-4k8u
    Explore at:
    application/rdfxml, tsv, xml, application/rssxml, json, csvAvailable download formats
    Dataset updated
    Mar 26, 2025
    License

    ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
    License information was derived automatically

    Description

    Note: These are the Department of Public Works Basemap Parcels, not the Assessor-Recorder's Taxable Parcels. See "How to use this dataset" for more information.

    A. SUMMARY Parcels are defined areas of land, demarcated by boundaries to visualize distinct and legal parcels of real property. Occasionally, parcels are divided or combined, and a new parcel can be created. This dataset connects current parcels in San Francisco to historical parcels that are associated with it.

    B. HOW THE DATASET IS CREATED This dataset utilizes the parcel change log to find associated parcels through an iterative process.

    C. UPDATE PROCESS This dataset will be refreshed daily, though the data may not change every day.

    D. HOW TO USE THIS DATASET The City and County of San Francisco has two related but distinct parcel databases. The first is managed by the Department of Public Works, is created by surveyors, and is used in the Department of Public Works basemap. Public Works parcels are used to identify very precisely where private properties end and where public City property begins (e.g. sidewalks, roads, rights of way, etc.). The second is managed by the Assessor-Recorder's Office. Assessor parcels are defined by Revenue and Taxation code and Property Tax law. The Assessor-Recorder uses official maps defined under Revenue and Taxation code section 325 in the creation of assessor parcels and are used to identify taxable property. Each of the Assessor's parcels have an Assessor's Parcel Number (APN) which is used by other departments including but not limited to Tax Collector for tax collection, DBI for permitting, and other use cases.

    Though most parcels are the same between Public Works and the Assessor’s Office, they are not a perfect match. APN's are retired and activated within the timeline parameters of tax years (July – June) based on tax roll state requirements, which means there can be a lag between the Public Works parcel changing and the associated APN being updated. Public Works’ City Basemap identifies legal parcels defined by California Code Subdivision Map Act and Assessor-Recorder’s parcels identify taxable parcel boundaries defined by Revenue and Taxation Code.

    Use this dataset to identify historical parcels from the Public Works Basemap that are associated with an active Public Works basemap parcel. This dataset is not a history of the Assessor-Recorder's Parcels.

    E. RELATED DATASETS

  • Parcel Change Log
  • Parcels - Active and Retired

  • s

    Cities, California, 2015

    • searchworks.stanford.edu
    zip
    Updated Oct 11, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2019). Cities, California, 2015 [Dataset]. https://searchworks.stanford.edu/view/zd071bk4213
    Explore at:
    zipAvailable download formats
    Dataset updated
    Oct 11, 2019
    Area covered
    California City
    Description

    This dataset is intended for researchers, students, and policy makers for reference and mapping purposes, and may be used for basic applications such as viewing, querying, and map output production, or to provide a basemap to support graphical overlays and analysis with other spatial data.

  • D

    Zoning Map - Zoning Districts

    • data.sfgov.org
    Updated Mar 26, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City and County of San Francisco Planning Department (2025). Zoning Map - Zoning Districts [Dataset]. https://data.sfgov.org/Geographic-Locations-and-Boundaries/Zoning-Map-Zoning-Districts/3i4a-hu95
    Explore at:
    tsv, csv, application/rssxml, xml, application/rdfxml, kml, application/geo+json, kmzAvailable download formats
    Dataset updated
    Mar 26, 2025
    Dataset authored and provided by
    City and County of San Francisco Planning Department
    License

    https://www.usa.gov/government-workshttps://www.usa.gov/government-works

    Description

    The Zoning Districts are a component of the Zoning Map which in turn is a key component of the San Francisco Planning Code. More information can be found here: https://sfplanning.org/zoning

  • D

    Zoning Map - Height and Bulk Districts

    • data.sfgov.org
    Updated Mar 26, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City and County of San Francisco Planning Department (2025). Zoning Map - Height and Bulk Districts [Dataset]. https://data.sfgov.org/Geographic-Locations-and-Boundaries/Zoning-Map-Height-and-Bulk-Districts/h9wh-cg3m
    Explore at:
    csv, application/rssxml, tsv, application/rdfxml, xml, kmz, application/geo+json, kmlAvailable download formats
    Dataset updated
    Mar 26, 2025
    Dataset authored and provided by
    City and County of San Francisco Planning Department
    License

    https://www.usa.gov/government-workshttps://www.usa.gov/government-works

    Description

    The Height and Bulk Districts are a component of the Zoning Map which in turn is a key component of the San Francisco Planning Code. A PDF poster of this data is available from here: https://sfplanning.org/resource/zoning-height-and-bulk-districts

  • w

    Census 2000: Blocks for San Francisco (no water)

    • data.wu.ac.at
    csv, json, kml, kmz +1
    Updated Aug 28, 2016
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of San Francisco (2016). Census 2000: Blocks for San Francisco (no water) [Dataset]. https://data.wu.ac.at/odso/data_gov/MGFhM2YyODctZGY5Ny00N2QxLWFjYWItNmRiNGQwMjc4ZmMx
    Explore at:
    kml, zip, kmz, json, csvAvailable download formats
    Dataset updated
    Aug 28, 2016
    Dataset provided by
    City of San Francisco
    Description

    US Census 2000 Block Geography modified to conform with SFGIS Library Geography (Streets, Lakes, et al.). Water areas have been clipped from this layer. Please refer to the Federal Census for the latest data, these boundaries provided as a convenience.

  • A

    ‘Census 2010: Blocks for San Francisco’ analyzed by Analyst-2

    • analyst-2.ai
    Updated Aug 5, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com) (2020). ‘Census 2010: Blocks for San Francisco’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/data-gov-census-2010-blocks-for-san-francisco-35b7/dabc22b5/?iid=002-921&v=presentation
    Explore at:
    Dataset updated
    Aug 5, 2020
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    San Francisco
    Description

    Analysis of ‘Census 2010: Blocks for San Francisco’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/de8736a8-5535-44e1-aa25-55fb91ad2818 on 12 February 2022.

    --- Dataset description provided by original source is as follows ---

    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 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas.

    --- Original source retains full ownership of the source dataset ---

  • Census Designated Places

    • data.smcgov.org
    • data.wu.ac.at
    application/rdfxml +5
    Updated Apr 27, 2016
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    United States Census Bureau (2016). Census Designated Places [Dataset]. https://data.smcgov.org/w/3knn-9sv3/dsrg-gg5p?cur=BFIOEHUd_NW&from=root
    Explore at:
    application/rdfxml, csv, application/rssxml, tsv, json, xmlAvailable download formats
    Dataset updated
    Apr 27, 2016
    Dataset authored and provided by
    United States Census Bureauhttp://census.gov/
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Description

    Boundaries of 2014 Census Designated Places in San Mateo County. This data includes boundaries for: Atherton, Belmont, Brisbane, Broadmoor, Burlingame, Colma, Daly City, East Palo Alto, El Granada, Emerald Lake Hills, Foster City, Half Moon Bay, Highlands-Baywood Park, Hillsborough, Ladera, La Honda, Loma Mar, Menlo Park, Millbrae, Montara, Moss Beach, North Fair Oaks, Pacifica, Pescadero, Portola Valley, Redwood City, San Bruno, San Carlos, San Mateo, South San Francisco, West Menlo Park, and Woodside.

    More information about Census Designated Places can be found on the US Census site: https://www.census.gov/geo/reference/gtc/gtc_place.html

  • Travel Model Super Districts

    • opendata.mtc.ca.gov
    • hub.arcgis.com
    Updated Mar 19, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MTC/ABAG (2018). Travel Model Super Districts [Dataset]. https://opendata.mtc.ca.gov/datasets/travel-model-super-districts
    Explore at:
    Dataset updated
    Mar 19, 2018
    Dataset provided by
    Metropolitan Transportation Commission
    Authors
    MTC/ABAG
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    Descriptions of Metropolitan Transportation Commission's 34 Super DistrictsSuper District #1 - Greater Downtown San Francisco: This area, the northeastern quadrant of the city, is bounded by Van Ness Avenue on the west, 11th Street on the southwest, and Townsend Street on the south. This Super District includes the following neighborhoods and districts: Financial District, Union Square, Tenderloin, Civic Center, South of Market, South Park, Rincon Hill, Chinatown, Jackson Square, Telegraph Hill, North Beach, Nob Hill, Russian Hill, Polk Gulch and Fisherman's Wharf. Treasure Island and Yerba Buena Island are also part of Super District #1.Super District #2 - Richmond District: This area, the northwestern quadrant of the city, is bounded by Van Ness Avenue on the east, Market Street on the southeast, and 17th Street, Stanyan Street, and Lincoln Way on the south. Super District #2 includes the following neighborhoods and districts: the Presidio, the Western Addition District, the Marina, Cow Hollow, Pacific Heights, Cathedral Hill, Japantown, Hayes Valley, Duboce Triangle, the Haight-Ashbury, the Richmond District, Inner Richmond, Outer Richmond, Laurel Heights, Sea Cliff, and the Golden Gate Park.Super District #3 - Mission District: This area, the southeastern quadrant of the city, is bounded by Townsend Street, 11th Street, Market Street, 17th Street, Stanyan Street, and Lincoln Way on the northern boundary; 7th Avenue, Laguna Honda, Woodside Avenue, O'Shaughnessy Boulevard and other smaller streets (Juanita, Casita, El Verano, Ashton, Orizaba) on the western boundary; and by the San Mateo County line on the southern boundary. Super District #3 includes the following neighborhoods and districts: China Basin, Potrero Hill, Inner Mission, Outer Mission, Twin Peaks, Parnassus Heights, Dolores Heights, Castro, Eureka Valley, Noe Valley, Bernal Heights, Glen Park, Ingleside, Ocean View, the Excelsior, Crocker-Amazon, Visitacion Valley, Portola, Bayview, and Hunters Point.Super District #4 - Sunset District: This area, the southwestern quadrant of the city, is bounded by Lincoln Way (Golden Gate Park) on the north; 7th Avenue, Laguna Honda, Woodside Avenue, O'Shaughnessy Boulevard and other smaller streets (Juanita, Casita, El Verano, Ashton, Orizaba) on the eastern boundary; and by the San Mateo County line on the southern boundary. Super District #4 includes the following neighborhoods and districts: Inner Sunset, the Sunset District, Sunset Heights, Parkside, Lake Merced District, Park-Merced, Ingleside Heights, West Portal and St. Francis Wood.Super District #5 - Daly City/San Bruno: This northern San Mateo County Super District includes the communities of Daly City, Colma, Brisbane, South San Francisco, Pacifica, San Bruno, Millbrae, and the north part of Burlingame. The boundary between Super District #5 and Super District #6 is Broadway, Carmelita Avenue, El Camino Real, Easton Drive, the Hillsborough / Burlingame city limits, Interstate 280, Skyline Boulevard, the Pacifica city limits, and the Montara Mountain ridgeline extending to Devil's Slide on the coast.Super District #6 - San Mateo/Burlingame: The central San Mateo County Super District includes the communities of Hillsborough, San Mateo, Foster City, Belmont, the southern part of Burlingame, and the coastside communities of Montara, Moss Beach, El Granada, and Half Moon Bay. The southern boundary of Super District #6 is the Foster City city limits, the Belmont/San Carlos city limits, Interstate 280, Kings Mountain, Lobitos Creek extending to Martins Beach on the coast.Super District #7 - Redwood City/Menlo Park: The southern San Mateo County Super District includes the communities of San Carlos, Redwood Shores, Redwood City, Atherton, Menlo Park, East Palo Alto, Woodside, Portola Valley, and the coastside communities of San Gregorio and Pescadero.Super District #8 - Palo Alto/Los Altos: This Santa Clara County Super District includes the communities of Palo Alto, Los Altos, Los Altos Hills, and the western part of Mountain View. Boundaries include the San Mateo County line, US-101 on the north, and Cal-85 (Stevens Creek Freeway) and Stevens Creek on the east.Super District #9 - Sunnyvale/Mountain View: This is the "Silicon Valley" Super District and includes the communities of Mountain View (eastern part and shoreline), Sunnyvale, Santa Clara (northern part), Alviso, and San Jose (northern part). Also included in this Super District is the "Golden Triangle" district. Super District #9 is bounded by US-101, Cal-85, Stevens Creek on the western boundary; Homestead Road on the southern boundary; Pierce Street, Civic Center Drive and the SP tracks in Santa Clara City; and Interstate 880 as the eastern boundary.Super District #10 - Cupertino/Saratoga: This Super District is located in south central Santa Clara County and includes the communities of Cupertino, Saratoga, Santa Clara City (southern part), Campbell (western part), San Jose (western part), Monte Sereno, Los Gatos and Redwood Estates. This area is bounded by Stevens Creek and the Santa Cruz Mountains on the west, Homestead Road on the north, Interstate 880/California Route 17 on the east; Union Avenue, Camden Avenue and Hicks Road (San Jose) also on the eastern boundary; and the Santa Clara/Santa Cruz county line on the south.Super District #11 - Central San Jose: This central Santa Clara County Super District is comprised of San Jose (central area), Santa Clara City (downtown area), and Campbell (east of Cal-17). The general boundaries of Super District #11 are Interstate 880/California Route 17 on the west; US-101 on the east; and the Capitol Expressway, Hillsdale Avenue, Camden Avenue, and Union Avenue on the south boundary.Super District #12 - Milpitas/East San Jose: This eastern Santa Clara County Super District includes the City of Milpitas, and the East San Jose communities of Berryessa, Alum Rock, and Evergreen. Boundaries include Interstate 880 and US-101 freeways on the west; San Jose City limits (Evergreen) on the south; and the mountains on the east.Super District #13 - South San Jose: This south-central Santa Clara County Super District includes the southern part of San Jose including the Almaden and Santa Teresa neighborhoods. Super District #13 is surrounded by Super District #10 on the west; Super District #11 on the north; Super District #12 on the northeast; and Super District #14 on the south at Metcalf Road (Coyote).Super District #14 - Gilroy/Morgan Hill: This area of Santa Clara County is also known as "South County" and includes the communities of Gilroy, Morgan Hill, San Martin and the Coyote Valley. Also included in this Super District are Loma Prieta (western boundary of the Super District) and Mount Hamilton in the northeastern, rural portion of Santa Clara County. This area is bounded by Santa Cruz and San Benito Counties on the south, and Merced and Stanislaus Counties on the eastern border.Super District #15 - Livermore/Pleasanton: This is the eastern Alameda County Super District including the Livermore and Amador Valley communities of Livermore, Pleasanton, Dublin, San Ramon Village, and Sunol. This Super District includes all of eastern Alameda County east of Pleasanton Ridge and Dublin Canyon.Super District #16 - Fremont/Union City: The southern Alameda County Super District includes the communities of Fremont, Newark and Union City. The boundaries for this Super District are the Hayward/Union City city limits on the north side; the hills to the immediate east; the Santa Clara/Alameda County line on the south; and the San Francisco Bay on the west.Super District #17 - Hayward/San Leandro: This southern Alameda County Super District includes the communities of Hayward, San Lorenzo, San Leandro, Castro Valley, Cherryland, and Ashland. The northern border is the San Leandro/Oakland city limits.Super District #18 - Oakland/Alameda: This northern Alameda County Super District includes the island city of Alameda, Oakland, and Piedmont. The Oakland neighborhoods of North Oakland and Rockridge are in the adjacent Super District #19. The border between Super Districts #18 and #19 are the Oakland/Emeryville city limits; 52nd and 51st Streets; Broadway; and Old Tunnel Road.Super District #19 - Berkeley/Albany: This northern Alameda County Super District includes all of Emeryville, Berkeley, and Albany, and the Oakland neighborhoods in North Oakland and Rockridge. The Super District is surrounded by the Alameda/Contra Costa County lines; the San Francisco Bay; and the Oakland Super District.Super District #20 - Richmond/El Cerrito: This is the western Contra Costa Super District. It includes the communities of Richmond, El Cerrito, Kensington, Richmond Heights, San Pablo, El Sobrante, Pinole, Hercules, Rodeo, Crockett, and Port Costa. The eastern boundary to Super District #20 is defined as the Carquinez Scenic Drive (east of Port Costa); McEwen Road; California Route 4; Alhambra Valley Road; Briones Road through the Regional Park; Bear Creek Road; and Wildcat Canyon Road to the Alameda/Contra Costa County line.Super District #21 - Concord/Martinez: This is one of three central Contra Costa County Super Districts. Super District #21 includes the communities of Concord, Martinez, Pleasant Hill, Clayton, and Pacheco. This area is bounded by Suisun Bay on the north; Willow Pass and Marsh Creek on the east; Mt Diablo on the southeast; and Cowell Road, Treat Boulevard, Oak Grove Road, Minert Road, Bancroft Road, Oak Park Boulevard, Putnam Boulevard, Geary Road, and Pleasant Hill Road on the south; and Briones Park, Alhambra Valley Road and Cal-4 on the west.Super District #22 - Walnut Creek: This central Contra Costa County Super District includes the communities of Walnut Creek, Lafayette, Moraga and Orinda. The latter three communities are more popularly known as Lamorinda. The border with Super District #23 generally follows the southern city limits of Walnut Creek.Super

  • T

    Vital Signs: Population – by metro (2022)

    • data.bayareametro.gov
    application/rdfxml +5
    Updated Jul 8, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2022). Vital Signs: Population – by metro (2022) [Dataset]. https://data.bayareametro.gov/dataset/Vital-Signs-Population-by-metro-2022-/gbn2-y2wk
    Explore at:
    json, csv, xml, application/rssxml, application/rdfxml, tsvAvailable download formats
    Dataset updated
    Jul 8, 2022
    Description

    VITAL SIGNS INDICATOR Population (LU1)

    FULL MEASURE NAME
    Population estimates

    LAST UPDATED
    February 2023

    DESCRIPTION
    Population is a measurement of the number of residents that live in a given geographical area, be it a neighborhood, city, county or region.

    DATA SOURCE
    California Department of Finance: Population and Housing Estimates - http://www.dof.ca.gov/Forecasting/Demographics/Estimates/
    Table E-6: County Population Estimates (1960-1970)
    Table E-4: Population Estimates for Counties and State (1970-2021)
    Table E-8: Historical Population and Housing Estimates (1990-2010)
    Table E-5: Population and Housing Estimates (2010-2021)

    Bay Area Jurisdiction Centroids (2020) - https://data.bayareametro.gov/Boundaries/Bay-Area-Jurisdiction-Centroids-2020-/56ar-t6bs
    Computed using 2020 US Census TIGER boundaries

    U.S. Census Bureau: Decennial Census Population Estimates - http://www.s4.brown.edu/us2010/index.htm- via Longitudinal Tract Database Spatial Structures in the Social Sciences, Brown University
    1970-2020

    U.S. Census Bureau: American Community Survey (5-year rolling average; tract) - https://data.census.gov/
    2011-2021
    Form B01003

    Priority Development Areas (Plan Bay Area 2050) - https://opendata.mtc.ca.gov/datasets/MTC::priority-development-areas-plan-bay-area-2050/about

    CONTACT INFORMATION
    vitalsigns.info@bayareametro.gov

    METHODOLOGY NOTES (across all datasets for this indicator)
    All historical data reported for Census geographies (metropolitan areas, county, city and tract) use current legal boundaries and names. A Priority Development Area (PDA) is a locally-designated area with frequent transit service, where a jurisdiction has decided to concentrate most of its housing and jobs growth for development in the foreseeable future. PDA boundaries are current as of December 2022.

    Population estimates for Bay Area counties and cities are from the California Department of Finance, which are as of January 1st of each year. Population estimates for non-Bay Area regions are from the U.S. Census Bureau. Decennial Census years reflect population as of April 1st of each year whereas population estimates for intercensal estimates are as of July 1st of each year. Population estimates for Bay Area tracts are from the decennial Census (1970-2020) and the American Community Survey (2011-2021 5-year rolling average). Estimates of population density for tracts use gross acres as the denominator.

    Population estimates for Bay Area tracts and PDAs are from the decennial Census (1970-2020) and the American Community Survey (2011-2021 5-year rolling average). Population estimates for PDAs are allocated from tract-level Census population counts using an area ratio. For example, if a quarter of a Census tract lies with in a PDA, a quarter of its population will be allocated to that PDA. Estimates of population density for PDAs use gross acres as the denominator. Note that the population densities between PDAs reported in previous iterations of Vital Signs are mostly not comparable due to minor differences and an updated set of PDAs (previous iterations reported Plan Bay Area 2040 PDAs, whereas current iterations report Plan Bay Area 2050 PDAs).

    The following is a list of cities and towns by geographical area:

    Big Three: San Jose, San Francisco, Oakland

    Bayside: Alameda, Albany, Atherton, Belmont, Belvedere, Berkeley, Brisbane, Burlingame, Campbell, Colma, Corte Madera, Cupertino, Daly City, East Palo Alto, El Cerrito, Emeryville, Fairfax, Foster City, Fremont, Hayward, Hercules, Hillsborough, Larkspur, Los Altos, Los Altos Hills, Los Gatos, Menlo Park, Mill Valley, Millbrae, Milpitas, Monte Sereno, Mountain View, Newark, Pacifica, Palo Alto, Piedmont, Pinole, Portola Valley, Redwood City, Richmond, Ross, San Anselmo, San Bruno, San Carlos, San Leandro, San Mateo, San Pablo, San Rafael, Santa Clara, Saratoga, Sausalito, South San Francisco, Sunnyvale, Tiburon, Union City, Vallejo, Woodside

    Inland, Delta and Coastal: American Canyon, Antioch, Benicia, Brentwood, Calistoga, Clayton, Cloverdale, Concord, Cotati, Danville, Dixon, Dublin, Fairfield, Gilroy, Half Moon Bay, Healdsburg, Lafayette, Livermore, Martinez, Moraga, Morgan Hill, Napa, Novato, Oakley, Orinda, Petaluma, Pittsburg, Pleasant Hill, Pleasanton, Rio Vista, Rohnert Park, San Ramon, Santa Rosa, Sebastopol, Sonoma, St. Helena, Suisun City, Vacaville, Walnut Creek, Windsor, Yountville

    Unincorporated: all unincorporated towns

  • Growth Boundaries (2019)

    • opendata.mtc.ca.gov
    • hub.arcgis.com
    • +1more
    Updated Feb 5, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MTC/ABAG (2020). Growth Boundaries (2019) [Dataset]. https://opendata.mtc.ca.gov/datasets/cee518ed990947de8d2290416306461f
    Explore at:
    Dataset updated
    Feb 5, 2020
    Dataset provided by
    Metropolitan Transportation Commission
    Authors
    MTC/ABAG
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    This data set contains features representing growth boundaries in the San Francisco Bay Region. The data set was developed by Greenbelt Alliance as part of their open space preservation mission. The Metropolitan Transportation Commission (MTC) updated the feature set in late 2019 as part of the jurisdiction review process for the BASIS data gathering project. Changes were made to the growth boundaries of the following jurisdictions based on their BASIS feedback: Antioch, Fremont, Livermore, Marin County, Pittsburg, Pleasanton, and San Ramon.The original features were created by referencing the local measures adopted by voters, city councils/boards of supervisors, or both and map images developed by local government. Web links to the measures and images are included in the attribute table. Greenbelt Alliance is responsible for updating the links to that information if their links change or the documents are taken offline. MTC's updates were made to a limited set of features using shapefiles downloaded from jurisdiction websites, hand editing features by referencing map images provided by jurisdictions, and erasing feature areas using base data features where one jurisdiction's growth boundary overlapped another jurisdiction's city limit. The MTC edits were limited, or related, to features receiving comments from jurisdiction reviewers.While commonly known as either Urban Growth Boundaries (UGBs) or Urban Limit Lines (ULLs), there are no standard designations so they are referred to by a number of designations in the attribute table (name). A couple of the alternative designations include Rural Urban Boundary and City Centered Corridor. Regardless of the designation used, growth boundaries are intended to control where development should be encouraged and discouraged. In this case, the polygons represent the areas where development should occur, and development outside the boundary is discouraged. Development proposed for areas outside the boundary is usually allowed based on special review and approval processes designated by the adopting jurisdiction.Jurisdictions are not required to adopt growth boundaries so the development restrictions imposed by them only apply to the cities and counties that create them. In the case of growth boundaries adopted by counties, they are usually developed with the consent and agreement of the cities adjacent to the county growth boundary.

  • c

    BOE TRA 2023 co38

    • gis.data.ca.gov
    • hub.arcgis.com
    Updated May 16, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Tax and Fee Administration (2023). BOE TRA 2023 co38 [Dataset]. https://gis.data.ca.gov/maps/CDTFA::boe-tra-2023-co38-1/about
    Explore at:
    Dataset updated
    May 16, 2023
    Dataset authored and provided by
    California Department of Tax and Fee Administration
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    This shapefile contains tax rate area (TRA) boundaries in San Francisco 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

  • D

    Analysis Neighborhoods

    • data.sfgov.org
    Updated Oct 17, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2023). Analysis Neighborhoods [Dataset]. https://data.sfgov.org/-/Analysis-Neighborhoods/j2bu-swwd?defaultRender=table
    Explore at:
    csv, application/rssxml, xml, application/geo+json, tsv, kml, application/rdfxml, kmzAvailable download formats
    Dataset updated
    Oct 17, 2023
    License

    ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
    License information was derived automatically

    Description

    A. SUMMARY The Department of Public Health and the Mayor’s Office of Housing and Community Development, with support from the Planning Department, created these 41 neighborhoods by grouping 2010 Census tracts, using common real estate and residents’ definitions for the purpose of providing consistency in the analysis and reporting of socio-economic, demographic, and environmental data, and data on City-funded programs and services. These neighborhoods are not codified in Planning Code nor Administrative Code, although this map is referenced in Planning Code Section 415 as the “American Community Survey Neighborhood Profile Boundaries Map. Note: These are NOT statistical boundaries as they are not controlled for population size. This is also NOT an official map of neighborhood boundaries in SF but an aggregation of Census tracts and should be used in conjunction with other spatial boundaries for decision making. B. HOW THE DATASET IS CREATED This dataset is produced by assigning Census tracts to neighborhoods based on existing neighborhood definitions used by Planning and MOHCD. A qualitative assessment is made to identify the appropriate neighborhood for a given tract based on understanding of population distribution and significant landmarks. Once all tracts have been assigned a neighborhood, the tracts are dissolved to produce this dataset, Analysis Neighborhoods. C. UPDATE PROCESS This dataset is static. Changes to the analysis neighborhood boundaries will be evaluated as needed by the Analysis Neighborhood working group led by DataSF and the Planning department and includes staff from various other city departments. Contact us for any questions. D. HOW TO USE THIS DATASET Downloading this dataset and opening it in Excel may cause some of the data values to be lost or not display properly (particularly the Analysis Neighborhood column). For a simple list of Analysis Neighborhoods without geographic coordinates, click here: https://data.sfgov.org/resource/xfcw-9evu.csv?$select=nhood E. RELATED DATASETS 2020 Census tracts assigned a neighborhood 2010 Census tracts assigned a neighborhood

    • Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    SFGIS (2025). San Francisco Mid-Block Points [Dataset]. https://data.sfgov.org/Geographic-Locations-and-Boundaries/San-Francisco-Mid-Block-Points/iqyu-pwpr

    San Francisco Mid-Block Points

    Explore at:
    csv, application/rssxml, application/rdfxml, tsv, application/geo+json, kml, kmz, xmlAvailable download formats
    Dataset updated
    Mar 27, 2025
    Dataset authored and provided by
    SFGIS
    License

    ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
    License information was derived automatically

    Area covered
    San Francisco
    Description

    A. SUMMARY This is a dataset containing points representing the midpoint of each block in the City of San Francisco. This dataset is used for geomasking (e.g. removing an exact address and replacing it with a nearby anonymized point) and other anonymization tasks.

    B. HOW THE DATASET IS CREATED This dataset was created by calculating the midpoint of each the street segment in the city (see Streets - Active and Retired) then returning the latitude and longitude of that midpoint. A street segment is a line between two intersections. Street midpoints are calculated for each side of the block.

    C. UPDATE PROCESS This dataset is updated weekly.

    D. HOW TO USE THIS DATASET Use this dataset for geomasking and other anonymization workflows.

    E. RELATED DATASETS - Streets - Active and Retired

    Search
    Clear search
    Close search
    Google apps
    Main menu