County boundaries within TRPA jurisdiction. It was derived from the U.S. Geological Survey State Boundaries, which were derived from Digital Line Graph (DLG) files representing the 1:2,000,000-scale map in the National Atlas of the United States.

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

TRPA Boundary: Tahoe Regional Planning Agencies jurisdictional boundary
Town Centers: Town centers contain most of the Region’s non-residential services and have been identified as a significant source of sediments and other contaminants that continue to enter Lake Tahoe. Town centers are targeted for redevelopment in a manner that improves environmental conditions, creates a more sustainable and less auto-dependent development pattern and provides economic opportunities in the Region.
Special Planning Districts: Relates to the 2012 Regional Plan Update Special District Boundaries and other related information.
Area Plan, CP, and PAS boundaries: Indicates plan area boundaries, special area boundaries, preliminary community plan boundaries, redevelopment and master plan boundaries, hydrologic related area boundaries, and other related information
Special Areas
Final Land Use
Recreation Facility: Recreation areas and facilities
Scenic Shoreline: Indicates location of scenic shore units around Lake Tahoe
Scenic Shoreline points: Indicates location of scenic shoreline points around Lake Tahoe
Scenic Roads: Indicates location of scenic road corridors around Lake Tahoe
Schools: This layer shows all the currently operational schools in the Tahoe Region. This layer is used to determine monitoring sites, safe route to school needs, and other land-use and transportation planning efforts.
City of South Lake Tahoe: City of South Lake Tahoe boundaries (city limit)
County Boundaries: County boundaries within TRPA jurisdiction. It was derived from the U.S. Geological Survey State Boundaries, which were derived from Digital Line Graph (DLG) files representing the 1:2,000,000-scale map in the National Atlas of the United States.
Peaks: Major mountain peaks in the Lake Tahoe Basin
Contours - 40 ft
Contours - 200 ft
Cities
Fire Districts
Basic Ownership

This dataset comprises various jurisdiction and planning geospatial layers for the Tahoe Basin, including the TRPA Boundary, urban areas, town centers, special planning districts, wildland urban interface (WUI), eastside-westside forest types boundary, area plan, CP and PAS boundaries, special areas, regional land use, scenic corridor, scenic viewpoints, schools, City of South Lake Tahoe, county boundaries, peaks, cities, improvement and utility districts, water service area boundaries, fire districts, forest management zones, transfer ratio, town center with buffer, flyover zone, bonus unit boundary, districts, and areas zoned for multi-family use.Spatial Reference: NAD83 / UTM zone 10N (26910)Area Covered: Tahoe Basin, Nevada, California

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.This dataset is regularly 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)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The 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, gis@state.ca.gov Field 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 San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these

This dataset comprises various jurisdiction and planning geospatial layers for the Tahoe Basin, including the TRPA Boundary, urban areas, town centers, special planning districts, wildland urban interface (WUI), eastside-westside forest types boundary, area plan, CP and PAS boundaries, special areas, regional land use, scenic corridor, scenic viewpoints, schools, City of South Lake Tahoe, county boundaries, peaks, cities, improvement and utility districts, water service area boundaries, fire districts, forest management zones, transfer ratio, town center with buffer, flyover zone, bonus unit boundary, districts, and areas zoned for multi-family use.Spatial Reference: NAD83 / UTM zone 10N (26910)Area Covered: Tahoe Basin, Nevada, California

TRPA Boundary: Tahoe Regional Planning Agencies jurisdictional boundary
Town Centers: Town centers contain most of the Region’s non-residential services and have been identified as a significant source of sediments and other contaminants that continue to enter Lake Tahoe. Town centers are targeted for redevelopment in a manner that improves environmental conditions, creates a more sustainable and less auto-dependent development pattern and provides economic opportunities in the Region.
Special Planning Districts: Relates to the 2012 Regional Plan Update Special District Boundaries and other related information.
Area Plan, CP, and PAS boundaries: Indicates plan area boundaries, special area boundaries, preliminary community plan boundaries, redevelopment and master plan boundaries, hydrologic related area boundaries, and other related information
Special Areas
Final Land Use
Recreation Facility: Recreation areas and facilities
Scenic Shoreline: Indicates location of scenic shore units around Lake Tahoe
Scenic Shoreline points: Indicates location of scenic shoreline points around Lake Tahoe
Scenic Roads: Indicates location of scenic road corridors around Lake Tahoe
Schools: This layer shows all the currently operational schools in the Tahoe Region. This layer is used to determine monitoring sites, safe route to school needs, and other land-use and transportation planning efforts.
City of South Lake Tahoe: City of South Lake Tahoe boundaries (city limit)
County Boundaries: County boundaries within TRPA jurisdiction. It was derived from the U.S. Geological Survey State Boundaries, which were derived from Digital Line Graph (DLG) files representing the 1:2,000,000-scale map in the National Atlas of the United States.
Peaks: Major mountain peaks in the Lake Tahoe Basin
Contours - 40 ft
Contours - 200 ft
Cities
Fire Districts
Basic Ownership

TRPA Boundary: Tahoe Regional Planning Agencies jurisdictional boundary
Town Centers: Town centers contain most of the Region’s non-residential services and have been identified as a significant source of sediments and other contaminants that continue to enter Lake Tahoe. Town centers are targeted for redevelopment in a manner that improves environmental conditions, creates a more sustainable and less auto-dependent development pattern and provides economic opportunities in the Region.
Special Planning Districts: Relates to the 2012 Regional Plan Update Special District Boundaries and other related information.
Area Plan, CP, and PAS boundaries: Indicates plan area boundaries, special area boundaries, preliminary community plan boundaries, redevelopment and master plan boundaries, hydrologic related area boundaries, and other related information
Special Areas
Final Land Use
Recreation Facility: Recreation areas and facilities
Scenic Shoreline: Indicates location of scenic shore units around Lake Tahoe
Scenic Shoreline points: Indicates location of scenic shoreline points around Lake Tahoe
Scenic Roads: Indicates location of scenic road corridors around Lake Tahoe
Schools: This layer shows all the currently operational schools in the Tahoe Region. This layer is used to determine monitoring sites, safe route to school needs, and other land-use and transportation planning efforts.
City of South Lake Tahoe: City of South Lake Tahoe boundaries (city limit)
County Boundaries: County boundaries within TRPA jurisdiction. It was derived from the U.S. Geological Survey State Boundaries, which were derived from Digital Line Graph (DLG) files representing the 1:2,000,000-scale map in the National Atlas of the United States.
Peaks: Major mountain peaks in the Lake Tahoe Basin
Contours - 40 ft
Contours - 200 ft
Cities
Fire Districts
Basic Ownership

Major Highways - Used to analyze transportation needs and alternatives for the Lake Tahoe Region.County Roads - Used to analyze transportation needs and alternatives for the Lake Tahoe Region.Streets - Geocoded streets (The best available streets layer for the Lake Tahoe region).Existing Active Transportation Facilities - Bikeway class designation.Existing Active Transportation Facilities - 75ft buffer - A 75 foot buffer around existing active transportation network segments. Proposed Active Transportation Facilities - Proposed Bikeway class designation.Proposed Active Transportation Facilities - 75ft buffer - A 75 foot buffer around proposed active transportation network segments. Tahoe Transit Routes (Consolidated) - Transit routes throughout the Lake Tahoe Region.Microtransit Service Areas - Area of service covered by Lake Link and TART Connect.2020 Regional Transportation Plan Projects - Plan Projects (link to plan)Traffic Analysis Zones (TAZ) - The purpose for these boundaries is to provide zones to analyze transportation needs and alternatives for the Lake Tahoe Region to meet the Tahoe Regional Planning Agency thresholds, as well as conform to local, state, and federal regulations.Tahoe Bus Stops - Transit stops throughout the Lake Tahoe Region.Traffic Volumes – Crashes as reported by CalTrans and NDOT. Measured by average annual daily traffic (AADT).Tahoe Crashes - Collision data reported by CalTrans and NDOT.

Spatial Reference: NAD83 / UTM zone 10N (26910) Area Covered: Tahoe Basin, Nevada, California

PurposeBoundary is derived from the California Department of Tax and Fee Administration (CDTFA). Their county boundaries are the most-up to date 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.CDT GIS attached a GEOID attribute with the value ‘06’ to identify California and create ease of joins with other Census-based datasets. Finally, this layer removes the coastal buffer polygons and does not cut out the bay area water region. 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 BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts (this dataset) Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCENSUS_GEOID: numeric geographic identifiers from the US Census Bureau Boundary AccuracyState boundary is created from county boundaries that 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. 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. 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 (derived from the California County Boundaries and Identifiers): 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. 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.

Sierra Nevada Conservancy (SNC) boundary. The boundary was mapped to correspond with statute AB 2600 (2004) and as re-defined in SB 208 (2022). Work on the boundary was completed by CalFire, GreenInfo Network, and the California Department of Fish and Game. Meets and bounds description of the area as defined in statute: PRC Section 33302 (f) defines the Sierra Nevada Region as the area lying within the Counties of Alpine, Amador, Butte, Calaveras, El Dorado, Fresno, Inyo, Kern, Lassen, Madera, Mariposa, Modoc, Mono, Nevada, Placer, Plumas, Shasta, Sierra, Siskiyou, Tehama, Trinity, Tulare, Tuolumne, and Yuba, described as the area bounded as follows: On the east by the eastern boundary of the State of California; the crest of the White/Inyo ranges; and State Routes 395 and 14 south of Olancha; on the south by State Route 58, Tehachapi Creek, and Caliente Creek; on the west by the line of 1,250 feet above sea level from Caliente Creek to the Kern/Tulare County line; the lower level of the western slope’s blue oak woodland, from the Kern/Tulare County line to the Sacramento River near the mouth of Seven-Mile Creek north of Red Bluff; the Sacramento River from Seven-Mile Creek north to Cow Creek below Redding; Cow Creek, Little Cow Creek, Dry Creek, and up to the southern boundary of the Pit River watershed where Bear Creek Mountain Road and Dry Creek Road intersect; the southern boundary of the Pit River watershed; the western boundary of the upper Trinity watershed in the County of Trinity; on the north by the boundary of the upper Trinity watershed in the County of Trinity and the upper Sacramento, McCloud, and Pit River watersheds in the County of Siskiyou; and within the County of Modoc, the easterly boundary of the Klamath River watershed; and on the north in the County of Modoc by the northern boundary of the State of California; excluding both of the following: (1) The Lake Tahoe Region, as described in Section 6605.5 of the Government Code, where it is defined as "region" (2) The San Joaquin River Parkway, as described in Section 32510.

According to GreenInfo Network and the California Department of Fish and Game, the blue oak woodland used to define a portion of the Sierra Nevada Conservancy's western boundary was delineated using referenced vegetation and imagery data.

The project lead for the collection of this data in California was Terri Weist. She, along with Danielle Walsh, Shelly Blair, and other personnel, captured 30 adult female mule deer from July 2012 to November 2014, equipping the deer with Iridium satellite collars manufactured by Lotek. The data was collected from the interstate Carson River herd, where a portion of the population spends the summer months in the Sierra range of California and the winter months in western Nevada. An additional 57 deer were collared in Nevada and provided by Cody Schroeder of the Nevada Department of Wildlife. Summer range is mostly within Alpine County, California, but also extends into El Dorado County and Mono County. Winter range is confined to the California-Nevada border area in Alpine County, CA. and Douglas County, NV. GPS location data was collected between February 2012 to July 2019. Between 2 and 12 location fixes were recorded per day, with a maximum of a fix taken every 2 hours during migration sequences. To improve the quality of the data set as per Bjørneraas et al. (2010), the GPS data were filtered prior to analysis to remove locations which were: i) further from either the previous point or subsequent point than an individual deer is able to travel in the elapsed time, ii) forming spikes in the movement trajectory based on outgoing and incoming speeds and turning angles sharper than a predefined threshold , or iii) fixed in 2D space and visually assessed as a bad fix by the analyst. The methodology used for this migration analysis allowed for the mapping of winter ranges and the identification and prioritization of migration corridors in a single deer population. Brownian Bridge Movement Models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 45 deer, including location, date, time, and average location error as inputs in Migration Mapper. Due to the large study area and a concentration of deer movement east of Lake Tahoe in the Carson Range, the population was split into two distinct sub-herds. Twenty deer contributing 52 migration sequences were used in the modeling analysis for the Carson Range. Twenty-five deer contributing 58 migration sequences were used from the rest of the population surrounding the Carson Valley. Corridors and stopovers were prioritized based on the number of animals moving through a particular area. BBMMs were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Winter range analyses were based on data from 48 individual deer and 92 wintering sequences using a fixed motion variance of 1000. Winter range designations for this herd would likely expand with a larger sample, filling in some of the gaps between winter range polygons in the map. Large water bodies were clipped from the final outputs.Corridors are visualized based on deer use per cell, with greater than or equal to 1 deer, greater than or equal to 2 deer (10% of the sample), and greater than or equal to 4 deer (20% of the sample) from the Carson Range dataset and greater than or equal to 1 deer, greater than or equal to 3 deer (10% of the sample), and greater than or equal to 5 deer (20% of the sample) from the Carson Valley dataset representing migration corridors, moderate use, and high use corridors, respectively. Stopovers were calculated as the top 10 percent of the population level utilization distribution during migrations and can be interpreted as high use areas. Winter range is visualized as the 50thpercentile contour of the winter range utilization distribution.