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

Summary Geographic boundaries for the bay area counties

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.

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)

This layer is sourced from maps.smcgov.org.

A log of dataset alerts open, monitored or resolved on the open data portal. Alerts can include issues as well as deprecation or discontinuation notices.

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. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

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.

Graph and download economic data for Employed Persons in San Francisco County/City, CA (LAUCN060750000000005) from Jan 1990 to Apr 2025 about San Francisco County/City, CA; household survey; employment; persons; and USA.

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

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

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

Analysis of ‘Zoning Map - Zoning Districts’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/28f51f62-ddc4-40c4-8e22-32de984f2745 on 13 February 2022.

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

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.

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

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/d/5gzd-g9ns

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

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 California 2020 TIGER/Line shapefile 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.

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

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.

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.

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 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 Buffers (this dataset)Without 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 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 includes 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