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.

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, 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 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 Buffers (this dataset)Place 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.

Geospatial data about City of San Antonio, Texas Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

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) 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, odsdataservices@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 items, or others, from the shoreline

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

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 service displays the County Supervisor, City Council, School District and Fire Protection district boundaries within the San Diego region. The Council and Supervisor District services include links to each District website. Layers can be downloaded from the Regional GIS Data Warehouse under the District category.

© Planning and Community Development Department, Comprehensive Division Updated per Ordinance 2015-01-15-0020, Boundary Adjustment of approx. 1,906.12 Acres (Government Cayon) Updated per Ordinance 2014-11-06-0861, Boundary Adjustment of approx. 36.266 Acres. Updated per Ordinance 2014-09-04-0658 Boundary Adjustment of approx. 1.73 Acres from the City of Live Oak to the City of San Antonio. Updated per Ordinance 2014-09-04-0657 Boundary Adjustment of approx. 31.81 acres from the City of Shavano park to the City of San Antonio and approx. 6.24 acres from the City of San Antonio to Shavano Park.

This layer is sourced from qagis.sanantonio.gov.

This shapefile contains tax rate area (TRA) boundaries in San Diego County for the specified assessment roll year. Boundary alignment is based on the 2014 county parcel map. A tax rate area (TRA) is a geographic area within the jurisdiction of a unique combination of cities, schools, and revenue districts that utilize the regular city or county assessment roll, per Government Code 54900. Each TRA is assigned a six-digit numeric identifier, referred to as a TRA number. TRA = tax rate area number

This is a graphical polygon dataset depicting the polygon boundaries of Cities within Bexar County Texas and Surrounding Counties. (excluding San Antonio)Updated per Ordinance No. 564, No. 565, and No. 567 on April 9, 2015 extending the Helotes City limits with the annexation of four parcels of vacant property known as Bricewood Subdivision. Updated previously per Resolution No 2012-007-R From the City of Somerset .Updated per ordinance 2014-09-04-0657 (Savano Park ETJ ONLY release)Updated per ordinance 2014-09-04-0658 (Live Oak City Limit release)Updated per ordinance 2014-08-21-0614 (Fair Oaks Ranch ETJ ONLY release.

This service displays the County Supervisor, City Council, School District and Fire Protection district boundaries within the San Diego region. The Council and Supervisor District services include links to each District website. Layers can be downloaded from the Regional GIS Data Warehouse under the District category.

TIGER blocks were adjusted to better align with local administrative geography, specifically 2020 jurisdictional boundaries and 2020 Community Planning Area boundaries for both the City of San Diego and the County of San Diego. Please note: SANDAG consolidated some blocks with adjacent blocks in cases where there was no visible population. This was done prior to the release of the redistricting tables. The ocean blocks were also removed.

The SanGIS data set includes an extensive collection of GIS maps that are available to the public.

 Application Data Included:

 1. Public Safety: Crime Mapping & Analysis, Computer Aided Dispatch,
 Emergency Response Planning

 2. Planning & Development: Specific Plans, Vegetation Mapping, Zoning,
 Geologic Hazards, Codes Enforcement

 3. Facilities Management: Water and Waste Water Utilities, Street
 Lighting, Storm Drains, Pavement Management

 4. Subdivision Mapping: Basemap Maintenance, Parcel Mapping, Survey
 Control, Orthophotography

 5. Route Management: Water Meter Readers, Trash & Recycling Routes

 6. Decision Support & Analysis: Facility Siting, Airport Noise, Slope
 Analysis, Demographics, Economic Development

 SanGIS was created in July, 1997, as a Joint Powers Agreement (JPA)
 between the City and County of San Diego. After 13 years of working
 together on data and application development, the City and County
 decided to formalize their partnership in GIS by creating the SanGIS
 JPA. Finding that access to correct and current geographic data was
 considered more important than application development to County and
 City departments, SanGIS focuses on ensuring geographic data is
 maintained and accessible.

 SanGIS Mission:

 To maintain and promote the use of a regional geographic data
 warehouse for the San Diego area and to facilitate the development of
 shared geographic data and automated systems which use that data.

 SanGIS Goals:

 1. To ensure geographic data currency and integrity.

 2. To provide cost effective access to geographic data to member
 agencies, subscribers and the public.

 3. To generate revenue from the sale of geographic data products to
 reduce the cost of map maintenance to member agencies.

 Data Collection:

 SanGIS data was created or obtained from several sources. Some of our
 data is licensed; some data was created from tabular digital files;
 some data was digitized from paper maps; and other data was entered
 using coordinate geometry tools.

 Updating the Data:

 Responsibility for the maintenance of the over 200 geographic data
 layers is distributed to City and County departments based on several
 factors such as who has the source documents, who has the greatest
 need for the data, and who is held accountable for this data as part
 of their city-wide or county-wide duties. Most basemap maintenance is
 completed by SanGIS staff. SanGIS is also responsible for coordinating
 with other data maintainers to ensure currency and accuracy for all
 participants.

 Data Coverage:

 All of the SanGIS geographic data is within San Diego County
 only. Much of our data covers the entire County of San Diego but some
 is only for the City of San Diego.

 [Summary provided by SanGIS]

The physical location covered by an interagency, dispatch center for the effective coordination, mobilization and demobilization of emergency management resources. A dispatch center actively supports incidents within its boundaries and the resources assigned to those incidents. 1/11/2023 - Tabular and geospatial changes. USMTBFAC (Blackfeet Reservation) merged into USMTGDC (Great Falls Interagency Dispatch Center). USMTBFAC remains as 4th Tier Dispatch. USMTFHA (Flathead Reservation) merged into USMTMDC (Missoula Interagency Dispatch Center). USMTFHA remains as 4th Tier Dispatch. Changes made by Kat Sorenson, R1 Asst Aircraft Coordinator, and Kara Stringer, IRWIN Business Lead. Edits by JKuenzi. 1/10/2023 - Tabular and geospatial changes. Two islands on west edge of John Day Dispatch area (USORJDCC) absorbed into USORCOC Dispatch per direction from Kaleigh Johnson (Asst Ctr Mgr), Jada Altman (Central Oregon Center Mgr), and Jerry Messinger (Air Tactical Group Supervisor). Update made to Dispatch and Initial Attack Frequency Zone boundaries. Edits by JKuenzi, 11/08/2022 - Tabular and geospatial changes. Update made to Dispatch and Initial Attack Frequency Zone boundaries between Miles City Interagency Dispatch Center (USMTMCC) and Billings Interagency Dispatch Center (USMTBDC), along Big Horn and Rosebud County line near Little Wolf Mountains, per Kat Sorenson, R1 Asst Aircraft Coordinator, and Kelsey Pluhar, DNRC Asst. Center Manager at Miles City Interagency Dispatch Center. Area in Big Horn County is dispatched by MTMCC. Edits by JKuenzi, 09/06/2022-09/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada. Boundary modified between CAOVCC (Owens Valley Interagency Communications Center) and NVSFC (Sierra Front Interagency Dispatch Center), specifically between Queen Valley and Mono Valley. The team making the change is made up of Southern Calif (JTomaselli) and Great Basin (GDingman) GACCs, with input from Ian Mills and Lance Rosen (BLM). Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of Initial Attack Frequency Zone boundaries and GACC boundaries in the area described. Initial edits provided by Ian Mills and Daniel Yarborough. Final edits by JKuenzi, USFS. A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area. Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270. East through Bodie to the CA/NV state line. Follows the CA/NV State Line south to HWY CA 167/NV 359. East on NV359 to where the HWY intersects the corner of FS/BLM land. Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary. 09/22/2022 - Tabular changes only. The DispLocation value of "Prineville, OR", was updated to "Redmond, OR", and the ContactPhone value was updated for Central Oregon Interagency Dispatch Ctr (USORCOC) per direction from Desraye Assali, Supervisory GIS Specialist in Region 6. The original correction had been made 9/30/2020, in the National Dispatch Office Location dataset, but had been missed in the National Dispatch Boundary dataset. Edits by JKuenzi, USFS. 09/07/2022 - 09/08/2022 - Tabular and geospatial changes. Multiple boundaries modified in Northern Rockies GACC to bring lines closer in accordance with State boundaries. Information provided by Don Copple, State Fire Planning & Intelligence Program Manager for Montana Dept of Natural Resources & Conservation (DNRC), Kathy Pipkin, Northern Rockies GACC Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi, USFS. The following changes were made:Boundary changes made to the following: Bitterroot Interagency Dispatch Ctr (USMTBDC), Dillon Interagency Dispatch Ctr (USMTDDC), Flathead Dispatch (USMTFHA), Great Falls Interagency Dispatch Ctr (USMTGDC), Helena Interagency Dispatch Ctr (USMTHDC), Kalispell Interagency Dispatch Ctr (USMTKIC), Lewistown Interagency Dispatch Ctr (USMTLEC), and Missoula Interagency Dispatch Ctr (USMTMDC).9/7/2022 - Tabular and geospatial changes. Completed change of Dispatch Boundary started 4/4/2022, USMTBZC (Bozeman Interagency Dispatch) was absorbed into USMTBDC (Billings Dispatch Center). This information for use in 2023. Change to the Initial Attack Frequency Zone Boundary will be dependent on FAA and frequency manager input which will be given by 2/28/2023. Information provided by Kathy Pipkin, Northern Rockies Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi. 07/08/2022 - Tabular change only. DispName corrected from "Columbia Cascades Communication Center" to "Columbia Cascade Communication Center" , per Desraye Assali, R6 Fire and Aviation GIS Coordinator. Edits by JKuenzi, USFS. 04/04/2022 - Tabular changes only. USCAMVIC (Monte Vista Interagency Center) changed to USCASDIC (San Diego Interagency Center). Information provided by James Tomaselli, R5 GACC Center Mgr, and Kara Stringer, Wildland Fire Data Management Business Operations Lead. Edits by JKuenzi. Tabular change only. Following discussion between NRCC (Northern Rockies Geographic Area Coordination Center), USMTBZC in Bozeman, MT, and USMTBDC in Billings, MT, plans to merge Bozeman into Billings anticipated to start 4/18/2022, but will transition throughout 2022 year and be finalized on or near January 2023. The Dispatch Boundary between USMTBZC (Bozeman Interagency Dispatch) and USMTBDC in Billings, MT, will remain in place on the map until January 2023. Tabular change made to show that MTBDC was doing dispatch duty for MTMCC. Information provided by Kathy Pipkin, Northern Rockies Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi. 03/24/2022 - Geospatial and tabular changes. Update made to 2 small polygons along the Rio Grande near a National Recreation Area and the Amistad Reservoir, which were changed from USNMADC to USTXTIC as a result of 2022 GACC Boundary change per Calvin Miller, Southern Area Coordination Center Deputy Manager, and Kenan Jaycox, Southwest Coordination Center Manager 01/05/2022 - Geospatial and tabular changes. USMTFPAC (Fort Peck Dispatch) was found to have been closed/stopped as of 03/09/2020 per WFMI (Wildland Fire Management Information) application. USMTFPAC polygon was merged into USMTLEC per USMTLEC Center Manager. Edits by JKuenzi, USFS.10/27/2021 - Geospatial and tabular changes. The area of USWASAC is merged into USWANEC per Ted Pierce, Deputy Northwest Geographic Area Coordination Center Manager, and Jill Jones, Interagency Dispatch Center Manager NE Washington Interagency Communications Center. Edits by JKuenzi, USFS.10/15/2021 - Geospatial and tabular changes. Boundary alignments for the Duck Valley Reservation in southern Idaho along the Nevada border. Changes impacting USIDBDC and USNVEIC. The Duck Valley Reservation remains under the Dispatch authority of USNVEIC. The only change was to the alignment of the physical boundary surrounding the Reservation in accordance with the boundary shown on the 7.5 minute quadrangle maps and data supplied by CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Manager. Edits by JKuenzi, USFS.9/30/2021 - Geospatial and tabular changes. Boundary alignments for Idaho on Hwy 95 NE of Weiser between Boise Dispatch Center and Payette Interagency Dispatch Center - per CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Manager. Edits by JKuenzi, USFS. Boundary changes at: Weiser (T11N R5W Sec 32), (T11N, R5W, Sec 3), (T12N R5W, Sec 25), and Midvale.9/21/2021 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southwestern and Southern GACCs where a portion of Texas, formerly under Southwestern GACC direction was moved to the Southern GACC. Changes to Dispatch Boundary include the following: Lake Meredith National Recreation Area changed from TXLAP to NMABC.Buffalo Lake NWR changed from TXBFR to NMABC.Amarillo BLM changed from TXAMD to NMABC.Muleshoe NWR changed from TXMLR to NMABC.Optima NWR changed from TXOPR to NMABC.Big Bend National Park changed from TXBBP to NMADC.Chamizal National Memorial changed from TXCHP to NMADC.Fort Davis Historic Site changed from TXFDP to NMADC.Amistad National Recreation Area changed from TXAMP to NMADC.All changes proposed for implementation starting 1/10/2022. Edits by JKuenzi, USFS. See also data sets for Geographic Area Coordination Centers (GACC), and Initial Attack Frequency Zones Federal for related changes.3/30/2021 - Geospatial and tabular changes. Boundary changes for Washington, Columbia Cascades Communication Center per Ted Pierce, acting NW GACC Deputy Center Mgr, and Justin Ashton-Sharpe, Fire Planner on the Gifford Pinchot and Mt Hood National Forests. North edge of USWACCC modified to include Mt Ranier National Park. West edge modified slightly to include more of Washington (Burke Island, Bachelor Island, Martin Island, Mt Pleasant, Green Mtn, and the eastern three quarters of Silver Lake. No changes made to Oregon side of USWACCC. Edits by JKuenzi, USFS. 2/19/2021 - Geospatial and tabular changes. Boundary changes for Alaska. Fairbanks Area Forestry Dispatch, Delta Area Forestry Dispatch, and Tok Area Forestry Dispatch merged into Northern Forestry Dispatch Center (USAKNFDC) per Jennifer L Jenkins - BLM GIS Specialist, and Ray Crowe - BLM Alaska Interagency Coordination Center (AICC) Center Manager, Dan Labarre - DNR, and Gabriella Branson - DNR. Edits by JKuenzi, USFS. 2/18/2021 - Geospatial and tabular changes. Boundary changes for Idaho originally submitted in 2016 but never completed in entirety. Changes between Boise Dispatch Center and Payette Interagency Dispatch Center - per

This dataset comprises polygons of census tracts for San Diego County. A census tract is a geographic region defined for the purpose of taking a census. Usually these coincide with the limits of cities, towns or other administrative areas and several tracts commonly exist within a county. In unincorporated areas, these are often arbitrary, except for coinciding with political lines. Census tracts are subdivided into block groups and census blocks.The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.The Census Tracts dataset is based on the TIGER dataset and may be edited by SANDAG and further edited by SanGIS to reflect local boundary datasets. However, SanGIS edits the CENSUS_BLOCK layer and then derives the CENSUS_TRACT layer from the blocks.

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)

The Geographic Information Systems (GIS) Unit falls under the purview of the County of Santa Cruz Information Services Department. The GIS Unit serves all County departments and external customers and provides data on land, features and people of Santa Cruz County. Santa Cruz County encompasses 4 cities and approximately 265,000 people. This coverage can be used for basic applications such as viewing, querying and map output production, or to provide a basemap to support graphical overlays and analyses of geospatial data.

The Geographic Information Systems (GIS) Unit falls under the purview of the County of Santa Cruz Information Services Department. The GIS Unit serves all County departments and external customers and provides data on land, features and people of Santa Cruz County. Santa Cruz County encompasses 4 cities and approximately 265,000 people. This coverage can be used for basic applications such as viewing, querying and map output production, or to provide a basemap to support graphical overlays and analyses of geospatial data.