Polygon features representing the COSA Boundary in the city of San Antonio.

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.

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.

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.

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 park boundaries within the City of San Antonio

City, Town, and Village boundary file, digitized from the Oswego County, NY tax maps as originally drawn by Stewart Mapping Services, Inc of San Antonio Texas, but with topology corrected by Oswego County Department of Real Property Tax Services.

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.

City Council adopted new district boundaries that are effective for the May 2023 municipal election for City Council. You can learn more about these district changes at the City’s redistricting website: https://www.sabexarcountmein.org/.

This is a graphical polygon dataset depicting the polygon boundaries of the Historic River Overlay Districts of San Antonio, Texas.

This is a graphical polygon dataset which depicts concentrated downtown retail, service office and mixed uses in the existing downtown business district. Major/regional shopping centers are permitted, but urban design standards are required in order to maintain a neighborhood commercial scale, to promote pedestrian activity and to maintain the unique character of the center.

This is a graphical point dataset depicting the location of the San Antonio City Hall is situated in the center of Military Plaza (Plaza de Armas) established in 1722 by the Spanish settlers of Texas who earlier had established a garrison on San Pedro Creek which runs along the western border of the plaza.

This is a geographical polygon dataset depicting the polygon boundaries of all mandatory detention areas within the City of San Antonio, and Bexar County, Texas.

This is a graphical polygon dataset depicts the new zoning district that restricts the use of outdoor lighting around military installations.

This dataset shows all the boundaries for neighborhood and homeowner associations registered with the City of San Antonio.

Building Climates Zones of California Climate Zone Descriptions for New Buildings - California is divided into 16 climatic boundaries or climate zones, which is incorporated into the Energy Efficiency Standards (Energy Code). Each Climate zone has a unique climatic condition that dictates which minimum efficiency requirements are needed for that specific climate zone. The numbers used in the climate zone map don't have a title or legend. The California climate zones shown in this map are not the same as what we commonly call climate areas such as "desert" or "alpine" climates. The climate zones are based on energy use, temperature, weather and other factors.This is explained in the Title 24 energy efficiency standards glossary section:"The Energy Commission established 16 climate zones that represent a geographic area for which an energy budget is established. These energy budgets are the basis for the standards...." "(An) energy budget is the maximum amount of energy that a building, or portion of a building...can be designed to consume per year.""The Energy Commission originally developed weather data for each climate zone by using unmodified (but error-screened) data for a representative city and weather year (representative months from various years). The Energy Commission analyzed weather data from weather stations selected for (1) reliability of data, (2) currency of data, (3) proximity to population centers, and (4) non-duplication of stations within a climate zone."Using this information, they created representative temperature data for each zone. The remainder of the weather data for each zone is still that of the representative city." The representative city for each climate zone (CZ) is:CZ 1: ArcataCZ 2: Santa RosaCZ 3: OaklandCZ 4: San Jose-ReidCZ 5: Santa MariaCZ 6: TorranceCZ 7: San Diego-LindberghCZ 8: FullertonCZ 9: Burbank-GlendaleCZ10: RiversideCZ11: Red BluffCZ12: SacramentoCZ13: FresnoCZ14: PalmdaleCZ15: Palm Spring-IntlCZ16: Blue Canyon

The administrative boundaries are the product of a Dissolve on the SAFDAreasOfResponsibility Feature Class using the Battalion attribute. These are not still alarm areas for the Battalions.

Established in 1982, Government Code Section 65570 mandates FMMP to report biennially on even numbered years, the conversion of farmland and grazing land, and to provide maps and data to local government and the public. The Important Farmland survey area is based on Natural Resources Conservation Service (NRCS) modern soil surveys covering most non-governmental lands in California; 51 counties are fully or partially surveyed during the 2018 map update. Soil surveys specific to National Forests or other government land units are not surveyed. Beginning in 2002, SSURGO digital soil information was incorporated into the Riverside County Important Farmland data and the 2016 data began to incorporate the new NRCS Gridded Soil Survey (gSSURGO). Data subsequent to 2002 may have acreage and soil line differences due to incorporation of newer NRCS-SSURGO or gSSURGO editions.Prior to the availability of SSURGO or gSSURGO, soil information was hand-transferred from the paper soil surveys. Older versions of the data have not been modified. The land use minimum mapping unit of ten acres has not changed, but digital soil units of less than one acre occur in the gSSURGO-enhanced Important Farmland data. The data between 2002 and 2014 incorporates SSURGO and the interaction of land use and soil components resulted in units of less than ten acres for categories such as Other Land. The 2016 data incorporates gSSURGO and will no longer merge resulting polygons less than one acre for any map category for that and future updates. For more information on gSSURGO, contact the USDA-Natural Resources Conservation Service: https://www.nrcs.usda.govUSDA NRCS soil surveys CA638 (San Diego Area); CA678 (Orange County and Western Part of Riverside County); CA679 (Western Riverside Area); CA680 (Coachella Valley Area); CA681 (Palo Verde Area); AZ656 (Colorado River Indian Reservation, Parts of AZ and CA).Riverside County initial mapping year - 1984.USDA NRCS soil survey CA638 (San Diego Area) was added to the survey area in 2008.Geodetic Model: 1984 to 2012 - North American Datum of 1927; 2014 to 2018 - North American Datum of 1983.2018 county boundaries: California Department of Forestry and Fire Protection, Fire and Resource Assessment Program (FRAP) 2018 version (cnty 18_2) of California Counties GIS data. https://frap.fire.ca.gov2018 Imagery source: USDA Farm Service Agency - National Agricultural Imagery Program (NAIP); Summer 2018; True color; 1 meter resolution. https://www.fsa.usda.govGoogle Incorporated; Various dates; True color; Google Maps and Streetview. https://www.google.com/maps