Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose
City boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. 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 Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• CDTFA_COUNTY: 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.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• 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.

A. SUMMARY Maximum speed limits per street segment for the City of San Francisco. Speed limits are indicated primarily for streets that have speeds greater than 25 MPH, unless the speed limit has been changed from a higher speed or a speed survey has been conducted to enforce the de facto speed limit of 25 MPH. 25 MPH is the de fact speed limit for most residential and commercial streets, and apply to streets on this map denoted by a 0 MPH label. Alleys narrower than 25 feet can have de facto speed limits of 15 MPH. B. METHODOLOGY Speed limit legislation information is taken from MTAB legislation and in some cases directives from engineers in the 5212 classification. Speed limit implementation information is taken from SSD Shops Reports and then parsed via python code. Implementation for speed limits will specify when signs are put in stating the new speed limits, and the work order that the sign installation was spec'd in. C. UPDATE FREQUENCY Updated quarterly or on an as need basis by request

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.

A. SUMMARY This data represents the boundaries of City-owned lands maintained in the City's Facility System of Record (FSR). Note: Not all lands are within the City and County proper. The City owns properties outside of its boundaries, including lands managed by SF Recreation and Parks, SF Public Utilities Commission, and other agencies. Certain lands are managed by following agencies which are not directly part of the City and County of San Francisco, but are included here for reference: San Francisco Housing Authority (SFHA), San Francisco Office of Community Investment and Infrastructure (OCII), and City College of San Francisco. B. HOW THE DATASET IS CREATED The Enterprise GIS program in the Department of Technology is the technical custodian of the FSR. This team creates and maintains this dataset in conjunction with the Real Estate Division and the Capital Planning Program of the City Administrator’s Office, who act as the primary business data stewards for this data. C. UPDATE PROCESS There are a handful of events that may trigger changes to this dataset: 1. The sale of a property 2. The leasing of a property 3. The purchase of a property 4. The change in jurisdiction of a property (e.g. from MTA to DPW) 5. The removal or improvement of the property Each of these changes triggers a workflow that updates the FSR. The Real Estate Division and Capital Planning make updates on an ongoing basis. The full dataset is reviewed quarterly to ensure nothing is missing or needs to be corrected. Updates to the data, once approved, are immediately reflected in the internal system and are updated here in the open dataset on a monthly basis. D. HOW TO USE THIS DATASET See here for an interactive map of all the City lands in this dataset. To track the facilities on City lands, join this dataset to the City Facilities dataset using the land_id field. If you see an error in the data, you can submit a change request with the relevant information to dtis.helpdesk@sfgov.org. Please be as specific about the error as you can (including relevant land_id(s)). E. RELATED DATASETS City Facilities

As of July 19, 2015, the PD District boundaries have been updated through a redistricting process. These new boundaries are not reflected in the dataset yet so you cannot compare data from July 19, 2015 onward to official reports from PD with the Police District column. We are working on an update to the dataset to reflect the updated boundaries starting with data entered July 19 onward.

Incidents derived from SFPD Crime Incident Reporting system Updated daily, showing data from 1/1/2003 up until two weeks ago from current date. Please note: San Francisco police have implemented a new system for tracking crime. The dataset included here is still coming from the old system, which is in the process of being retired (a multi-year process). Data included here is no longer the official SFPD data. We will migrate to the new system for DataSF in the upcoming months.

Summary Geographic boundaries for the bay area counties

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

NEW!: Use the new Business Account Number lookup tool. SUMMARYThis dataset includes the locations of businesses that pay taxes to the City and County of San Francisco. Each registered business may have multiple locations and each location is a single row. The Treasurer & Tax Collector’s Office collects this data through business registration applications, account update/closure forms, and taxpayer filings. Business locations marked as “Administratively Closed” have not filed or communicated with TTX for 3 years, or were marked as closed following a notification from another City and County Department. The data is collected to help enforce the Business and Tax Regulations Code including, but not limited to: Article 6, Article 12, Article 12-A, and Article 12-A-1. http://sftreasurer.org/registration.HOW TO USE THIS DATASETSystem migration in 2014: When the City transitioned to a new system in 2014, only active business accounts were migrated. As a result, any businesses that had already closed by that point were not included in the current dataset.2018 account cleanup: In 2018, TTX did a major cleanup of dormant and unresponsive accounts and closed approximately 40,000 inactive businesses.To learn more about using this dataset watch this video.To update your listing or look up your BAN see this FAQ: Registered Business Locations ExplainerData pushed to ArcGIS Online on November 6, 2025 at 6:14 AM by SFGIS.Data from: https://data.sfgov.org/d/g8m3-pdisDescription of dataset columns:

 UniqueID
 Unique formula: @Value(ttxid)-@Value(certificate_number)


 Business Account Number
 Seven digit number assigned to registered business accounts


 Location Id
 Location identifier


 Ownership Name
 Business owner(s) name


 DBA Name
 Doing Business As Name or Location Name


 Street Address
 Business location street address


 City
 Business location city


 State
 Business location state


 Source Zipcode
 Business location zip code


 Business Start Date
 Start date of the business


 Business End Date
 End date of the business


 Location Start Date
 Start date at the location


 Location End Date
 End date at the location, if closed


 Administratively Closed
 Business locations marked as “Administratively Closed” have not filed or communicated with TTX for 3 years, or were marked as closed following a notification from another City and County Department.


 Mail Address
 Address for mailing


 Mail City
 Mailing address city



 Mail State
 Mailing address state



 Mail Zipcode
 Mailing address zipcode


 NAICS Code
 The North American Industry Classification System (NAICS) is a standard used by Federal statistical agencies for the purpose of collecting, analyzing and publishing statistical data related to the U.S. business economy. A subset of these are options on the business registration form used in the administration of the City and County's tax code. The registrant indicates the business activity on the City and County's tax registration forms.

See NAICS Codes tab in the attached data dictionary under About > Attachments.

 NAICS Code Description
 The Business Activity that the NAICS code maps on to ("Multiple" if there are multiple codes indicated for the business).


 NAICS Code Descriptions List
 A list of all NAICS code descriptions separated by semi-colon


 LIC Code
 The LIC code of the business, if multiple, separated by spaces


 LIC Code Description
 The LIC code description ("Multiple" if there are multiple codes for a business)


 LIC Code Descriptions List
 A list of all LIC code descriptions separated by semi-colon


 Parking Tax
 Whether or not this business pays the parking tax


 Transient Occupancy Tax
 Whether or not this business pays the transient occupancy tax


 Business Location
 The latitude and longitude of the business location for mapping purposes.


 Business Corridor
 The Business Corridor in which the the business location falls, if it is in one. Not all business locations are in a corridor.

Boundary reference: https://data.sfgov.org/d/h7xa-2xwk

 Neighborhoods - Analysis Boundaries
 The Analysis Neighborhood in which the business location falls. Not applicable outside of San Francisco.

Boundary reference: https://data.sfgov.org/d/p5b7-5n3h

 Supervisor District
 The Supervisor District in which the business location falls. Not applicable outside of San Francisco. Boundary reference: https://data.sfgov.org/d/xz9b-wyfc


 Community Benefit District
 The Community Benefit District in which the business location falls. Not applicable outside of San Francisco. Boundary reference: https://data.sfgov.org/d/c28a-f6gs


 data_as_of
 Timestamp the data was updated in the source system


 data_loaded_at
 Timestamp the data was loaded here (open data portal)


 SF Find Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'SF Find Neighborhoods' (6qbp-sg9q) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Police Districts
 This column was automatically created in order to record in what polygon from the dataset 'Current Police Districts' (qgnn-b9vv) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Supervisor Districts
 This column was automatically created in order to record in what polygon from the dataset 'Current Supervisor Districts' (26cr-cadq) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Analysis Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'Analysis Neighborhoods' (ajp5-b2md) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods' (jwn9-ihcz) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

City-owned and leased facilities maintained in the City's Facility System of Record (FSR). Does not include the following agencies which are not part of the City and County of San Francisco: SFHA, OCII and City College. This dataset was developed through a process involving some of the primary stewards for the facility data and their stakeholders. It is meant to be a living reference and will be maintained and updated through established workflows and processes over time. You can access the attached User Guide for more detail by clicking the red About button and scrolling to attachments.Data pushed to ArcGIS Online on November 7, 2025 at 3:15 AM by SFGIS.Data from: https://data.sfgov.org/d/nc68-ngbrDescription of dataset columns:

 facility_id
 System generated unique facility identifier


 common_name
 Commonly known/used facility name


 address
 Address or location description of facility


 city
 City where facility is located.


 zip_code
 ZIP Code where facility is located.


 block_lot
 The block and lot number, also known as the Assessor Parcel Number or APN. For facilities with multiple APNs associated, the lowest numbered APN is used. This will blank if in the facility is the right-of-way or outside of San Francisco county.


 owned_leased
 Indicates if the facility is owned or leased by the City.


 dept_id_for_jurisdiction
 Department ID of the City department with jurisdiction over the facility.


 jurisdiction
 Jurisdiction: department name of the City department with jurisdiction over the facility.


 gross_sq_ft
 Gross square footage of facility (original source: FRRM). Note: Incomplete data, updating as values are determined.


 longitude
 The longitude of the facility's location.


 latitude
 The latitude of the facility's location.


 supervisor_district
 Board of Supervisors District in which the facility is located, if applicable. Note: there are city facilities that are outside the boundaries of the City and County of San Francisco.


 city_tenants
 City departments that are tenants of the facility, separated by a semi-colon.


 land_id
 Foreign key to City Lands table.


 geom
 The geometry/location column which allows the facility to be mapped in Socrata.


 data_last_updated
 Timestamp when the record (row) was last updated in the source system


 data_as_of
 Timestamp when the record (row) was last refreshed in the source system


 data_loaded_at
 Timestamp when the record (row) was was last updated here (in the data portal)


 Analysis Neighborhoods



 DELETE - Neighborhoods_from_fyvs_ahh9



 DELETE - Supervisor Districts



 DELETE - Current Police Districts



 DELETE - Fire Prevention Districts



 DELETE - Zip Codes



 Neighborhoods



 SF Find Neighborhoods



 Current Police Districts



 Current Supervisor Districts

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

A. SUMMARY This dataset contains San Francisco Board of Supervisor district boundaries approved by the San Francisco Redistricting Task Force in April 2022 following redistricting based on the 2020 Decennial Census.

B. HOW THE DATASET IS CREATED The dataset was created from the final map submitted by the San Francisco Redistricting Task Force. Boundaries in this map were decided using data from the 2020 Census on the number of people living in each census block in the City and County. This data includes the number of individuals incarcerated in facilities under the control of the Department of Corrections and Rehabilitation based on their last known residential address. This information is made available by the Statewide Database based on U.S. Census Bureau Census Redistricting Data (P.L. 94-171).

These map boundaries were trimmed to align with the city and county's physical boundaries for greater usability. This trimming mainly consisted of excluding the water around the City and County from the boundaries.

C. UPDATE PROCESS Supervisor District boundaries are updated every 10 years following the federal decennial census. The Supervisor District boundaries reflected in this dataset will remain unchanged. A new dataset will be created after the next decennial census and redistricting process are completed.

The dataset is manually updated as new members of the Board of Supervisors take office. The most recent manual update date is reflected in the 'data_as_of' field.

Once the redistricting process is completed after the next decennial census and a new dataset is published, this dataset will become static and will no longer be updated.

D. HOW TO USE THIS DATASET This dataset can be joined to other datasets for analysis and reporting at the Supervisor District level.

If you are building an automated reporting pipeline using Socrata API access, we recommend using this dataset if you'd like your boundaries to remain static. If you would like the boundaries to automatically update after each decennial census to reflect the most recent Supervisor District boundaries, see the Current Supervisor Districts dataset or the Current Supervisor Districts (trimmed to remove water and other non-populated City territories) dataset.

E. RELATED DATASETS Supervisor Districts (2012) Current Supervisor Districts Current Supervisor Districts (trimmed to remove water and non-populated areas)

Zoning Districts City and County of San Francisco Planning Department. The Zoning Districts are the main component of the Zoning Map. The Zoning Map comprises: - Zoning Districts - Height and Bulk Districts - Special Use Districts - Preservation Districts - Coastal Zone Area - Special Sign Districts The official Zoning Map can be found in the San Francisco Planning Code: http://library.municode.com/index.aspx?clientId=14145&stateId=5&stateName=California (click on the links under ZONING MAPS on the left navigation column). Summaries of the Zoning District codes can be found here: http://www.sf-planning.org/index.aspx?page=1580 Section 105 of the Planning Code states: "The designations, locations and boundaries of the districts established by this Code shall be shown upon the "Zoning Map of the City and County of San Francisco," which shall consist of a series of numbered sectional maps. Wherever any uncertainty exists as to the boundary of any district as shown on said sectional maps, the following rules shall apply: (a) Where boundary lines are indicated as following streets and alleys within the right-of-way, they shall be construed as following the centerlines of such streets and alleys; (b) Where boundary lines are indicated as approximately following lot lines, such lot lines shall be construed to be such boundaries; (c) Where a boundary line divides a lot or crosses unsubdivided property; the location of such boundary shall be as indicated upon the Zoning Map using the scale appearing on such map; (d) Where further uncertainty exists, the City Planning Commission upon written application, or on its own motion, shall by resolution determine the location of a disputed boundary giving due consideration to the apparent indicated location thereof and the scale of the Zoning Map and the express purposes of this Code; (e) Wherever any property is not under these rules specifically included in any use district shown on the Zoning Map, such property is hereby declared to be in an RH-1(D) District, except that all property owned on the effective date of this amendment by the United States of America, State of California, City and County of San Francisco, or other governmental agency and within the City and County of San Francisco but not within the area covered by Sectional Maps Nos. 1 through 13 of the Zoning Map is hereby declared to be in a P (Public Use) District unless reclassified in accordance with the provisions of this Code; (f) Wherever any property is not under these rules specifically included in any height and bulk district shown on the Zoning Map, such property is hereby declared to be in a 40-X height and bulk district, except that all property owned on the effective date of this amendment by the United States of America, State of California, City and County of San Francisco, or other governmental agency and within the City and County of San Francisco but not within the area covered by Sectional Maps Nos. 1H through 13H of the Zoning Map is hereby declared to be in an OS (Open Space) District unless reclassified in accordance with the provisions of this Code, with the exception of Yerba Buena Island and Treasure Island which are hereby declared to be in a 40-X height and bulk district."Updated quarterly.

Statistics on speeding rates and exceedance of speed limit along selected street segments throughout San Francisco. The dataset was prepared as part of the SF Indicators project and covers from 2004 through 2009. http://www.sfindicatorproject.org/indicators/view/49

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 March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.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 along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. 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 BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing excludes the coastal buffers for cities and counties that have them in the 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 OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_COUNTY: 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.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_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.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.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.Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections. Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor.CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information.CDTFA'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. 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

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.

Neighborhood notification boundaries created by the Department of City Planning. These boundaries are designed solely for the Planning Department's neighborhood notifications where neighborhood groups are notified about certain types of developments in their area. An Excel spreadsheet of Neighborhood Groups contact details can be downloaded from this page: http://sf-planning.org/index.aspx?page=1654 There are alternative neighborhood boundaries available (which include a larger number of neighborhoods) here (Mayors Office): https://data.sfgov.org/d/pty2-tcw4 and here (Realtors): https://data.sfgov.org/Geography/SF-Realtor-Neighborhoods/wwis-y924

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 2019 Contra 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 2019 City and County of San Francisco - does not have a sphere of influence San Mateo County - 'Sphere of Influence' feature service data downloaded from San Mateo County GIS open data on 15 August 2019 Santa Clara County - 'City Spheres of Influence' feature service data downloaded from Santa Clara County Planning Office GIS Data on 15 August 2019 Solano County - SphereOfInfluence feature service data downloaded from Solano GeoHub on 15 August 2019 Sonoma County - 'SoCo PRMD GIS Spheres Influence.zip' downloaded from County of Sonoma on 15 August 2019

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/

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.

VITAL SIGNS INDICATOR Population (LU1)

FULL MEASURE NAME Population estimates

LAST UPDATED October 2019

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 SOURCES U.S Census Bureau: Decennial Census No link available (1960-1990) http://factfinder.census.gov (2000-2010)

California Department of Finance: Population and Housing Estimates Table E-6: County Population Estimates (1961-1969) Table E-4: Population Estimates for Counties and State (1971-1989) Table E-8: Historical Population and Housing Estimates (2001-2018) Table E-5: Population and Housing Estimates (2011-2019) http://www.dof.ca.gov/Forecasting/Demographics/Estimates/

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

U.S. Census Bureau: American Community Survey 5-Year Population Estimates (2011-2017) http://factfinder.census.gov

U.S. Census Bureau: Intercensal Estimates Estimates of the Intercensal Population of Counties (1970-1979) Intercensal Estimates of the Resident Population (1980-1989) Population Estimates (1990-1999) Annual Estimates of the Population (2000-2009) Annual Estimates of the Population (2010-2017) No link available (1970-1989) http://www.census.gov/popest/data/metro/totals/1990s/tables/MA-99-03b.txt http://www.census.gov/popest/data/historical/2000s/vintage_2009/metro.html https://www.census.gov/data/datasets/time-series/demo/popest/2010s-total-metro-and-micro-statistical-areas.html

CONTACT INFORMATION vitalsigns.info@bayareametro.gov

METHODOLOGY NOTES (across all datasets for this indicator) All legal boundaries and names for Census geography (metropolitan statistical area, county, city, and tract) are as of January 1, 2010, released beginning November 30, 2010, by the U.S. Census Bureau. 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 August 2019. For more information on PDA designation see http://gis.abag.ca.gov/website/PDAShowcase/.

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 -2010) and the American Community Survey (2008-2012 5-year rolling average; 2010-2014 5-year rolling average; 2013-2017 5-year rolling average). Estimates of population density for tracts use gross acres as the denominator.

Population estimates for Bay Area PDAs are from the decennial Census (1970 - 2010) and the American Community Survey (2006-2010 5 year rolling average; 2010-2014 5-year rolling average; 2013-2017 5-year rolling average). Population estimates for PDAs are derived from Census population counts at the tract level for 1970-1990 and at the block group level for 2000-2017. Population from either tracts or block groups are allocated to a PDA using an area ratio. For example, if a quarter of a Census block group lies with in a PDA, a quarter of its population will be allocated to that PDA. Tract-to-PDA and block group-to-PDA area ratios are calculated using gross acres. Estimates of population density for PDAs use gross acres as the denominator.

Annual population estimates for metropolitan areas outside the Bay Area are from the Census and are benchmarked to each decennial Census. The annual estimates in the 1990s were not updated to match the 2000 benchmark.

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

Special Use Districts City and County of San Francisco Planning Department. The Special Use Districts are a component of the Zoning Map. The Zoning - Map comprises: - Zoning Districts - Height and Bulk Districts - Special Use Districts - Preservation Districts - Coastal Zone Area - Sprcial Sign Districts The official Zoning Map can be found in the San Francisco Planning Code: http://library.municode.com/index.aspx?clientId=14145&stateId=5&stateName=California (click on the links under ZONING MAPS on the left navigation column). Sec 235 of the Planning Code states: "In addition to the use districts that are established by Section 201 of this Code, there shall also be in the City such special use districts as are established in this Section and Sections 236 through 249.5, in order to carry out further the purposes of this Code. The designations, locations and boundaries of these special use districts shall be as provided in Sections 236 through 249.5, and as shown on the Zoning Map referred to in Section 105 of this Code, subject to the provisions of Section 105. The original of the numbered sectional maps of the Zoning Map for Special Use Districts referred to in Sections 236 through 249.5 is on file with the Clerk of the Board of Supervisors under File No. 191-67-2. and No. 273.80. In any special use district the provisions of the applicable use district established by Section 201 shall prevail, except as specifically provided in Sections 236 through 249.5."