This feature service includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations. BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES: additional clarifying information about the action. BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the BOE'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).

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.

Purpose

County 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, coastal buffers are removed, leaving the land-based portions of jurisdictions. 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
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 (this dataset)
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
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

• 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
• Place Name: CDTFA incorporated (city) or county name
• 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.
• Legal 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.
• 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 System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_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.

Accuracy

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. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

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.

Purpose

County 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 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
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 (this dataset)
   • Without Coastal Buffers
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
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

• 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
• Place Name: CDTFA incorporated (city) or county name
• 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.
• Legal 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.
• 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 System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_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.

Accuracy

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. COUNTY = county name; CITY = city name or unincorporated

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.

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

This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.

This map is a compilation of the final set of city and county boundary changes filed with the California State Board of Equalization in accordance with Government Code 54900 for each assessment roll year beginning with the 2021 roll year. Boundary corrections are included in the dataset according to information provided by the city, county, and/or LAFCO. These corrections may or may not have been corrected in the Board of Equalization's records. Each layer is considered FINAL as of June in the year noted by the layer name. The boundaries from 2021 through 2025 are based on the California State Board of Equalization's tax rate area maps and may not align with other sources. For the latest data, please view the "City and County Boundary Line Changes" map.As of April 1, 2024, the maintenance of this map is provided by the California Department of Tax and Fee Administration (CDTFA) for sales and use tax purposes.

Counties in California intended for the NEVI Map.

This is SCAG’s 2019 city boundary data (v.1.0), updated as of July 6, 2021, including the boundaries for each of the 191 cities and 6 county unincorporated areas in the SCAG region. The original city boundary data was obtained from county LAFCOs to reflect the most current updates and annexations to the city boundaries. This data will be further reviewed and updated as SCAG continues to receive feedbacks from LAFCOs, subregions and local jurisdictions.Data-field description:COUNTY: County name COUNTY_ID: County FIPS CodeCITY: City NameCITY_ID: City FIPS CodeACRES: Area in acresSQMI: Area in square milesYEAR: Dataset year

Geospatial data about City of San Francisco, California Zoning Map — Height Districts. Export to CAD, GIS, PDF, CSV and access via API.

Jurisdictional boundaries for all cities and towns within Napa County, California.Jurisdictional boundaries for all cities and towns within Napa County, California.

Item last updated 03-20-2025 10:21

City and town boundaries for the purpose of establishing election divisions within a district. Created April 16, 2021. The districts contained within this dataset only represent districts that conduct an election. This dataset may not contain all districts within San Bernardino County. This dataset should only be used for the purpose of establishing election divisions within a district. It will be removed once the redistricting process has concluded.

This data set of polygon features represents Riverside County's Incorporated City Boundaries. Topology has been run and all gaps and overlaps have been fixed. The data has been adjusted to match Riverside County Parcel Boundaries. The city name field is used to represent the citys' name. Every polygon that represents an incorporated city must have a city name. Maintained by Stella Spadafora, 05/2015

© RCIT GIS, LAFCO

This layer is a component of Administrative Boundaires.

This map shows cases broken down by the county level and city level in Southern California.

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. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally- recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2019, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs, delineated in 20 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

Population by age groups, race and gender, and the poverty by race is attached to the split tract geography to create this split tract with population and poverty data. Split tract data is the product of 2020 census tracts split by 2023 incorporated city boundaries and unincorporated community/countywide statistical areas (CSA) boundaries as of July 1, 2023. The census tract boundaries have been altered and aligned where necessary with legal city boundaries and unincorporated areas, including shoreline/coastal areas. Census Tract:Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau (https://www.census.gov/)released 2020 geographic boundaries data including census tracts for the analysis and mapping of demographic information across the United States. City Boundary:City Boundary data is the base map information for the County of Los Angeles. These City Boundaries are based on the Los Angeles County Seamless Cadastral Landbase. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works (DPW). This layer represents current city boundaries within Los Angeles County. The DPW provides the most current shapefiles representing city boundaries and city annexations. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California.Countywide Statistical Areas (CSA): The countywide Statistical Area (CSA) was defined to provide a common geographic boundary for reporting departmental statistics for unincorporated areas and incorporated Los Angeles city to the Board of Supervisors. The CSA boundary and CSA names are established by the CIO and the LA County Enterprise GIS group worked with the Los Angeles County Board of Supervisors Unincorporated Area and Field Deputies that reflect as best as possible the general name preferences of residents and historical names of areas. This data is primarily focused on broad statistics and reporting, not mapping of communities. This data is not designed to perfectly represent communities, nor jurisdictional boundaries such as Angeles National Forest. CSA represent board approved geographies comprised of Census block groups split by cities.Data Fields:CT20: 2020 Census tractFIP22: 2023 City FIP CodeCITY: City name for incorporated cities and “Unincorporated” for unincorporated areas (as of July 1, 2023) CSA: Countywide Statistical Area (CSA) - Unincorporated area community names and LA City neighborhood names.CT20FIP23CSA: 2020 census tract with 2023 city FIPs for incorporated cities and unincorporated areas and LA neighborhoods. SPA22: 2022 Service Planning Area (SPA) number.SPA_NAME: Service Planning Area name.HD22: 2022 Health District (HD) number: HD_NAME: Health District name.POP23_AGE_0_4: 2023 population 0 to 4 years oldPOP23_AGE_5_9: 2023 population 5 to 9 years old POP23_AGE_10_14: 2023 population 10 to 14 years old POP23_AGE_15_17: 2022 population 15 to 17 years old POP23_AGE_18_19: 2023 population 18 to 19 years old POP23_AGE_20_44: 2023 population 20 to 24 years old POP23_AGE_25_29: 2023 population 25 to 29 years old POP23_AGE_30_34: 2023 population 30 to 34 years old POP23_AGE_35_44: 2023 population 35 to 44 years old POP23_AGE_45_54: 2023 population 45 to 54 years old POP23_AGE_55_64: 2023 population 55 to 64 years old POP23_AGE_65_74: 2023 population 65 to 74 years old POP23_AGE_75_84: 2023 population 75 to 84 years old POP23_AGE_85_100: 2023 population 85 years and older POP23_WHITE: 2023 Non-Hispanic White POP23_BLACK: 2023 Non-Hispanic African AmericanPOP23_AIAN: 2023 Non-Hispanic American Indian or Alaska NativePOP23_ASIAN: 2023 Non-Hispanic Asian POP23_HNPI: 2023 Non-Hispanic Hawaiian Native or Pacific IslanderPOP23_HISPANIC: 2023 HispanicPOP23_MALE: 2023 Male POP23_FEMALE: 2023 Female POV23_WHITE: 2023 Non-Hispanic White below 100% Federal Poverty Level POV23_BLACK: 2023 Non-Hispanic African American below 100% Federal Poverty Level POV23_AIAN: 2023 Non-Hispanic American Indian or Alaska Native below 100% Federal Poverty Level POV23_ASIAN: 2023 Non-Hispanic Asian below 100% Federal Poverty Level POV23_HNPI: 2023 Non-Hispanic Hawaiian Native or Pacific Islander below 100% Federal Poverty Level POV23_HISPANIC: 2023 Hispanic below 100% Federal Poverty Level POV23_TOTAL: 2023 Total population below 100% Federal Poverty Level POP23_TOTAL: 2023 Total PopulationAREA_SQMil: Area in square mile.POP23_DENSITY: 2023 Population per square mile.POV23_PERCENT: 2023 Poverty rate/percentage.How this data created?Population by age groups, ethnic groups and gender, and the poverty by ethnic groups is attributed to the split tract geography to create this data. Split tract polygon data is created by intersecting 2020 census tract polygons, LA Country City Boundary polygons and Countywide Statistical Areas (CSA) polygon data. The resulting polygon boundary aligned and matched with the legal city boundary whenever possible. Notes:1. Population and poverty data estimated as of July 1, 2023. 2. 2010 Census tract and 2020 census tracts are not the same. Similarly, city and community boundaries are as of July 1, 2023.

This data set of line features represent Riverside County's recorded street centerlines.This data set was designed to carry out functions of the Transportation department and is not a true street network layer. Centerlines do not have complete "connectivity" due to the fact that this layer is primarily roads that have been recorded but does not necessarily contain all roads. OBJECTID - Internal feature number. STNAME - Recorded name of the centerline. TYPE - Used to classify roads, primarily by surface type. Description of the codes found in the attribute "TYPE" TYPE DESCRIPTION C01 Federal Aid Interstate C02 State Highways C03 F.A.U. Maintained C04 F.A.S. Maintained C05 Paved Surface Maintained C06 Paved Surface (Traveled) C07 Graveled Surface Maintained C08 Graveled Surface (Traveled) C09 Dirt Surface Maintained C10 Dirt Surface (Traveled) C11 Accepted For Public Use C12 Non-County/Accepted for P.U. C13 Non-County road C14 Vacated C15 Abandon C16 Maintained F.A.U./Non-County C17 Maintained F.A.S./Non-County C18 Maintained Paved/Accepted C19 Maintained Paved/Non-County C20 Maintained Paved/Vacated C21 Maintained Gravel/Accepted C22 Maintained Gravel/Non-County C23 Maintained Gravel/Vacated C24 Maintained Dirt/Accepted C25 Maintained Dirt/Non-County C26 Maintained Dirt/Vacated C27 Accepted/Vacated C28 Maintained Under Contract C29 City Road C30 Paved Maintained/Dirt Maintained C31 Dedicated and Accepted/CFD Maintained W01 Maintained for City W02 Maintained for City/Non-County W03 Maintained for City/Non-County (Reversed) W04 Maintained for City/Accepted W05 F.A.U. Maintained/Maintained for City W06 Dirt Surface Maintained/Maintained for City W07 Paved Surface Maintained/Maintained for City W08 Graveled Surface Maintained/Maintained for City Z01 Traffic Division Modeling Connectivity Use Only (The "W" series within the TYPE field were initially created for the City of Wildomar, but have had their application expanded to include any Centerline where the County maintains the road for a City - typically for a limited period after a City's incorporation. The "W" will continue as a convention to make it easy to distinguish such roads from roads normally maintained by the County, even though it is understood that the "W" will lose its initial association with the City of Wildomar over time.). GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. Description of the codes found in the attribute "GENPLANTYPE" GENPLANTYPE SYMBOL DESCRIPTION 01 101 FREEWAY 02 201 EXPRESSWAY 03 301 URBAN ARTERIAL 04 304 URBAN ARTERIAL (PROPOSED) 05 401 ARTERIAL 06 404 ARTERIAL (PROPOSED) 07 501 MOUNTAIN ARTERIAL 08 504 MOUNTAIN ARTERIAL (PROPOSED) 09 13 MAJOR 10 16 MAJOR (PROPOSED) 11 21 SECONDARY 12 24 SECONDARY (PROPOSED) 13 801 SPECIFIC PLAN ROAD 14 804 SPECIFIC PLAN ROAD (PROPOSED) 15 25 SCENIC ROUTE 16 28 SCENIC ROUTE (PROPOSED) 17 0 COLLECTOR(PROPOSED) indicates that the road is part of the "General PLan Alignment" but does not currently exist as a legal centerline. This type of centerline will be stored in the CENTERLINEREF data set. DIRECTION - Represents the direction of traffic flow. Presently not supported. NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. FLAG - Indicates whether or not an arc will be used in a street network data set. Presently not used because there is no street network data set. L_F_ADD - The starting address for the left side of the street. L_T_ADD - The ending address for the left side of the street. R_F_ADD - The starting address for the right side of the street. R_T_ADD - The ending address for the right side of the street. PRE_DIR - The street direction prefix. Example: 'E' for east. STREET_NAME - The base legal street name of the centerline. Example: "MAIN". STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. Valid values for the STREET_TYPE field are: ' ' - ' ' (No Type is a space) AVE - AVENUE BLVD - BOULEVARD CIR - CIRCLE CT - COURT CV - COVE DR - DRIVE EXPY - EXPRESSWAY FWY - FREEWAY HWY - HIGHWAY LN - LANE LOOP - LOOP PATH - PATH PKWY - PARKWAY PL - PLACE PT - POINT RD - ROAD SQ - SQUARE ST- STREET TER - TERRACE TRL - TRAIL WALK - WALK WAY - WAY SUF_DIR - The street direction suffix. Example: "N' for north. TRACT - The tract map number in which the centerline can be found. MODIFIED - Modified Date CREATED - Created Date SOURCE_NOTES - References to legal documentation related to the Centerline found during research, including such things as recordation histroy, name change history, and acceptance for or termination of maintenance information, FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME Valid values for AREA_PLAN_ABBREVIATION are: DESCN - Desert Center ECDES - East County/Desert ECVAP - Eastern Coachella Valley Plan ELSIN - Lake Elsinore EVALE - Eastvale HIGHG - Highgrove HVWIN - Harvest Valley/Winchester JURUP - Jurupa LAKEV - Lakeview/Nuevo LMATH - Lake Mathews MARCH - March MEADV - Mead Valley PASS - Pass Area PVERD - Palo Verde Valley RECHE - Reche Canyon REMAP - REMAP (Riverside Extended Mountain Area Plan) RIVER - Riverside/Corona/Norco SANJA - San Jacinto Valley SBCO - San Bernardino County SUNCI - Sun City/Menifee Valley SWAP - Southwest Area Plan TEMES - Temescal Valley WCVAP - Western Coachella Valley Area Plan SUBROUTE - Optional Identifier used to build ROUTE_NAME to separate branches or distiguish discontinuous portions of a street within an area plan that are unlikely to ever form a continuous route. ROUTE_NAME - Primary field used to construct a Linear Referencing derivative of the Centerlines layer. THis values is a component of ROUTE_ALT1 and ROUTE_ALT2 and is overriden by those fields when they have values. ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. Valuid values for BUILD_PRIORITY are: UL - Upper Left (Default) LL - Lower Left UR - Upper Right LR - Lower Right LINE_LINK - Geometric ID of Centerline arc. Made up of the From X/Y coordinate, the To X/Y coordinate and the Length. Used to detect geometric changes to an existing Centerline. CL_ID - Duplicate of OBJECTID. USed for detecting newly added segments to the network each week or to relate and join exported versions of CENTERLINES back to the original CENTERLINE feature class.FROM_X_COORDINATE, FROM_Y_COORDINATE, TO_X_COORDINATE and TO_Y_COORDINATE: The coordinate data for the end points of the line in numeric format.ROUTE_ORIENTED: Indicates if the line is drawn in the direction that corresponds to the Routes created based on the ROUTE_NAME fields.TRAVEL_DIRECTIONS: Indicates whether the road can be driven and in what directions. Values include "Both Ways", "From-To", "To-From" and "No Ways".CA_ROAD_SYSTEM_PAGE: The map page location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_ROAD_SYSTEM_INDEX: The map index grid location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_FUNCTIONAL_CLASS: The California Functional Classification of the Roadway per the CRS maps. Only classifications between 1 and 5 may qualify for state and federal funds. Classifications include:1 - Interstate2 - Other Freeway or Expressway3 - Other Principal Arterial4 - Minor Arterial5 - Major Collector6 - Minor Collector7 - LocalFEDERAL_ROUTE and FEDERAL_ROUTE_TYPE: The number of the Federal Interstate or U.S. Highway and the operational type of the facility, where applicable.STATE_ROUTE and STATE_ROUTE_TYPE: The number of the State Route or Highway and the operational type of the facility, where applicable.COUNTY_ROUTE: The number of a County Route.CITY_LEFT or CITY_RIGHT: The City or Community name to the left or right of the Centerline. Used for address geolocators.STATE: CA for Califonia. For geolocators that use the State field.ZIP_LEFT or ZIP_RIGHT: The ZIP code to the left or right of the Centerline. Used for address geolocators.FULL_NAME_MIXED_CASE: The full street name in mixed Upper and Lower case letters, sometimes also called Title case. May be used for labeling and geolocators.

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.

This layer is sourced from maps.smcgov.org.

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