MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
The California State Water Resources Control Board (State Water Board) and the nine Regional Water Quality Control Boards (Regional Water Boards), collectively known as the California Water Boards (Water Boards), are dedicated to a single vision: abundant clean water for human uses and environmental protection to sustain California’s future. Under the federal Clean Water Act (CWA) and the state’s pioneering Porter-Cologne Water Quality Control Act, the State and Regional Water Boards have regulatory responsibility for protecting the water quality of nearly 1.6 million acres of lakes, 1.3 million acres of bays and estuaries, 211,000 miles of rivers and streams, and about 1,100 miles of California coastline.The State Water Board is located in Sacramento. There are nine Regional Water Boards, the boundaries of which are generally based on watersheds, also known as hydrologic areas. The nine Regional Water Boards are referred to by specific names, which are: (1) North Coast, (2) San Francisco Bay, (3) Central Coast, (4) Los Angeles, (5) Central Valley, (6) Lahontan, (7) Colorado River Basin, (8) Santa Ana, and (9) San Diego. Due to their size, and/or geographic spread, the Central Valley Board has three offices and the Lahontan Board has two offices. In addition, the Drinking Water Program has fourteen District offices spread throughout the state.This map service shows the jurisdictional boundaries of the nine Regional Water Boards and the locations of their administrative offices. The official legal definitions of Regional Water Quality Control Board jurisdictions may be found in the Section 13200 of the California Water Code.For more information, please visit the California Water Boards website at https://www.waterboards.ca.gov.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
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.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year
This EnviroAtlas dataset shows the San Diego, CA EnviroAtlas community boundary. It represents the outside edge of all the block groups included in the EnviroAtlas Community. This dataset was produced the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).
Historical districts contain multiple properties and/or objects that share historical significance. The City’s Historical Resources Board can establish a district if the contributing resources meet one of six criteria. For more information, read the nomination guidelines.
This dataset comprises road centerlines for all roads in San Diego County. Road centerline information is collected from recorded documents (subdivision and parcel maps) and information provided by local jurisidictions (Cities in San Diego County, County of San Diego). Road names and address ranges are as designated by the official address coordinator for each jurisidcition. Jurisdictional information is created from spatial overlays with other data layers (e.g. Jurisdiction, Census Tract).The layer contains both public and private roads. Not all roads are shown on official, recorded documents. Centerlines may be included for dedicated public roads even if they have not been constructed. Public road names are the official names as maintained by the addressing authority for the jurisdiction in which the road is located. Official road names may not match the common or local name used to identify the road (e.g. State Route 94 is the official name of certain road segments commonly referred to as Campo Road).Private roads are either named or unnamed. Named private roads are as shown on official recorded documents or as directed by the addressing authority for the jurisdiction in which the road is located. Unnamed private roads are included where requested by the local jurisidiction or by SanGIS JPA members (primarily emergency response dispatch agencies). Roads are comprised of road segments that are individually identified by a unique, and persistent, ID (ROADSEGID). Roads segments are terminated where they intersect with each other, at jurisdictional boundaries (i.e. city limits), certain census tract and law beat boundaries, at locations where road names change, and at other locations as required by SanGIS JPA members. Each road segment terminates at an intersection point that can be found in the ROADS_INTERSECTION layer.Road centerlines do not necessarily follow the centerline of dedicated rights-of-way (ROW). Centerlines are adjusted as needed to fit the actual, constructed roadway. However, many road centerline segments are created intially based on record documents prior to construction and may not have been updated to meet as-built locations. Please notify SanGIS if the actual location differs from that shown. See the SanGIS website for contact information and reporting problems (http://www.sangis.org/contact/problem.html).Note, the road speeds in this layer are based on road segment class and were published as part of an agreement between San Diego Fire-Rescue, the San Diego County Sheriff's Department, and SanGIS. The average speed is based on heavy fire vehicles and may not represent the posted speed limit.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty boundaries boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal Buffers (this dataset)Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.
This is a subset of a hosted web service provided and managed by USGS. The data only includes features within the San Diego region. For more information, visit the USGS Watershed Boundary Dataset resource pageThis dataset contains the 10-digit Hydrologic Unit polygon boundaries for the San Diego region, representing watersheds in the USGS hierarchy.
Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information
This is a graphical polygon dataset depicting the polygon boundaries of the ten City of San Antonio City Council Districts. 2012 Redistricting Plan precleared by D.O.J. under Section 5 of the Voting Rights Act 11/27/2012. Updated per Limited Purpose Annexation Ordinance 2014-11-06-0861, of 36.266 Acres. Ordinance 2014-01-09-0001 of Areas 1 - 4.Updated per Ordinance 2015-01-15-0020, Boundary Adjustment of approx. 1,906.12 Acres (Government Cayon)
Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Analysis of ‘Vegetation - Canada de San Vicente - San Diego County [ds770]’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/d85bfd39-93f3-48f9-b13d-0974baab3a0e on 26 January 2022.
--- Dataset description provided by original source is as follows ---
The Vegetation Map of Cañada de San Vicente (CSV), San Diego County, was created by the California Department of Fish and Game (DFG) Vegetation and Mapping Program (VegCAMP). CSV, formerly known as Monte Vista Ranch, was acquired in April 2009 by DFG and is currently not open to the public as the management plan is not complete. The map study area boundary is based on the DFG Lands layer that was published in April, 2011 and includes 4888 acres of land. This includes 115 acres of private land located in the northeast corner of the map that was considered an area of interest (AOI) before purchase by DFG. The map is based on field data from 38 vegetation Rapid Assessment surveys (RAs), 111 reconnaissance points, and 118 verification points that were conducted between April 2009 and January 2012. The rapid assessment surveys were collected as part of a comprehensive effort to create the Vegetation Classification Manual for Western San Diego County (Sproul et al., 2011). A total of 1265 RAs and 18 relevés were conducted for this larger project, all of which were analyzed together using cluster analysis to develop the final vegetation classification. The CSV area was delineated by vegetation type and each polygon contains attributes for hardwood tree, shrub and herb cover, roadedness, development, clearing, and heterogeneity. Of 545 woodland and shrubland polygons that were delineated, 516 were mapped to the association level and 29 to the alliance level (due to uncertainty in the association). Of 46 herbaceous polygons that were delineated, 36 were mapped to the group or macrogroup level and 8 were mapped to association. Four polygons were mapped as urban or agriculture. The classification and map follow the National Vegetation Classification Standard (NVCS) and Federal Geographic Data Committee (FGDC) standard and State of California Vegetation and Mapping Standards. The minimum mapping area unit (MMU) is one acre, though occasionally, vegetation is mapped below MMU for special types including wetland, riparian, and native herbaceous and when it was possible to delineate smaller stands with a high degree of certainty (e.g., with available field data). In total, about 45 % of the polygons were supported by field data points and 55% were based on photointerpretation.
--- Original source retains full ownership of the source dataset ---
This is a geographic database of park boundaries within the City of San Antonio
Vector polygon map data of property parcels from the City of San Antonio, Texas containing 629,531 features.
Parcel map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.
Parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.
Attributes for this data layer include: Shape_area, GlobalID, Shape_len, Shape, ModifiedDate, ParcelKey, and ModifiedUID.
Available for viewing and sharing in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
This is a geographic database of the extraterritorial jurisdiction of the cities that are within Bexar County (San Antonio excluded)Updated previously per Resolution No 2012-007-R From the City of Somerset which effected the ETJ as well.Updated per ordinance 2013-05-09-0318 (Helotes ETJ ONLY release)
Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information
This geodatabase includes the boundaries of the California Natural Resource Agency’s State Conservancies. The collection of the State Conservancies boundaries was initiated in January 2012 by the Sierra Nevada Conservancy, and the geodatabase was updated in 2022 to include Sierra Nevada Conservancy boundary expansion. The geodatabase was constructed from GIS data requested from each of the State Conservancies. The following documentation describes the contacts who provided data, and where available, the type of spatial information provided. Baldwin Hills Conservancy: A shapefile of the Baldwin Hills Conservancy boundary was requested and received from Amanda Recinos, amanda@greeninfo.org, of GreenInfo Network on behalf of the Executive Officer of the Baldwin Hills Conservancy, David McNeill, on 10 January 2012. This boundary has not been modified from the original boundary provided. California State Coastal Conservancy: The California State Coastal Conservancy was updated by San Jenniches, sjenniches@scc.ca.gov, of the Coastal Conservancy in Fiscal Year 2014-2015. The SNC did not receive the boundary directly from the Coastal Conservancy; the feature class was provided by Nickolas Perez, Nickolas.Perez@water.ca.gov, of the California Natural Resources Agency to the SNC on 30 April 2015. Coachella Valley Mountains Conservancy: A shapefile of the Coachella Valley Mountains Conservancy boundary was requested and received fromKerrie Godrey, kgodfrey@cvmc.ca.gov, of the Coachella Valley Mountains Conservancy on 10 January 2012. This boundary has not been modified from the original boundary provided. Delta Conservancy: A shapefile of the legal Delta and Suisun Marsh boundaries were provided by Elisa Sabatina with the Delta Conservancy, Elisa.Sabatini@deltaconservancy.ca.gov, on 10 January 2012. This boundary has not been modified from the original boundary provided. Rivers and Mountains Conservancy (San Gabriel/Lower LA): A shapefile of the Rivers and Mountains Conservancy was provided by Luz Torres, ltorres@rmc.ca.gov, of the Rivers and Mountains Conservancy on 10 January 2012. This boundary has not been modified from the original boundary provided. San Diego River Conservancy: Michael Nelson, mnelson@sdrc.ca.gov, the Executive Officer of the San Diego River Conservancy reported via email on 11 January 2012 that no prior GIS boundary existed for the Conservancy. Mr. Nelson provided written consent to the SNC, via an email dated 11 January 2012, to develop the San Diego River Conservancy GIS boundary from a PDF document supplied by Mr. Nelson that showed the general location of the San Diego River Conservancy’s boundary as occupying a one half mile buffer from the San Diego River. This boundary has not been modified from the original boundary provided. San Joaquin River Conservancy: The San Joaquin River Conservancy boundary was created from using both the legislation description of the boundary and a pdf version of the San Joaquin River Conservancy boundary provided by Marile Colindres, marile.colindres@sjrc.ca.gov, of the San Joaquin Conservancy on 24 February 2012. This boundary has not been modified from the since the creation of the boundary from the legal description in 2012. Santa Monica Mountains Conservancy: The SNC was not able to acquire GIS data from the Santa Monica Mountains Conservancy staff; therefore, the SNC created a boundary to represent the Santa Moninca Mountains Conservancy by using the description of the Conservancy from their website. Specifically, the SNC used the text from their website to select watersheds for GIS boundary: “the Santa Monica Mountains Conservancy zone covers an area from the edge of the Mojave Desert to the Pacific Ocean. The zone encompasses the whole of the Santa Monica Mountains, the Simi Hills, the Verdugo Mountains and significant portions of the Santa Susana and San Gabriel Mountains. In addition, the Mountains Recreation and Conservation Authority also owns or manages thousands of acres in the Sierra Pelona Mountains and in the Whittier-Puente Hills. From north to south, these areas drain into the Santa Clara River, Calleguas Creek, numerous smaller coastal watersheds in the Santa Monica Mountains, and the Los Angeles River and Rio Hondo.The Sierra Nevada Conservancy (SNC) 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 Tahoe Conservancy boundary was created by using the Tahoe Regional Planning Agency (TRPA) boundary received from the Tahoe Conservancy staff and clipping the TRPA boundary to the State of California boundary, using the Teale Albers projection. The TRPA boundary was received by the SNC from the Tahoe Conservancy staff in 2011, and the Tahoe Conservancy boundary was created by the SNC in 2012. Notes:Some conservancy boundaries overlap.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Tax rate area boundaries and related data based on changes filed with the Board of Equalization per Government Code 54900 for the specified assessment roll year. The data included in this map is maintained by the California State Board of Equalization and may differ slightly from the data published by other agencies. BOE_TRA layer = tax rate area boundaries and the assigned TRA number for the specified assessment roll year; BOE_Changes layer = boundary changes filed with the Board of Equalization for the specified assessment roll year; Data Table (C##_YYYY) = tax rate area numbers and related districts for the specified assessment roll year