Vector polygon map data of city limits from Houston, Texas containing 731 features.

City limits GIS (Geographic Information System) data provides valuable information about the boundaries of a city, which is crucial for various planning and decision-making processes. Urban planners and government officials use this data to understand the extent of their jurisdiction and to make informed decisions regarding zoning, land use, and infrastructure development within the city limits.

By overlaying city limits GIS data with other layers such as population density, land parcels, and environmental features, planners can analyze spatial patterns and identify areas for growth, conservation, or redevelopment. This data also aids in emergency management by defining the areas of responsibility for different emergency services, helping to streamline response efforts during crises..

This city limits data is available for viewing and sharing as a map 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.

Contains data from CARTO.CTYLIMIT.Updated as needed.

Polygon features with attributes displaying the corporate limits of Baker, Baton Rouge, Central, and Zachary in East Baton Rouge Parish, Louisiana.Metadata

This data represents the State of Oregon city limit boundaries. Each city limit is defined as a continuous area within the statutory boundary of an incorporated city, which is the smallest subdivision of an annexed area. It is represented as spatial data (polygon with label point).

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's 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 jurisdictions. The boundaries are continuously being revised 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 and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the 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).

This service provides visual representation of North Carolina Municipal Boundaries defined through the 2021-2022 Powell Bill.This service was created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System (GIS). Municipal boundaries are recognized as a base cartographic layer for location analysis. This data is current for the fiscal year 2021 - 2022. Municipal boundaries updated this year were based on towns that reported annexation changes to the NC Office of Secretary of State. This may not be representative of all towns with boundary changes this year.The Municipal Boundaries service is based on the Powell Bill Program maps for the 2021-2022 fiscal year. Municipalities in North Carolina participating in the Powell Bill Program are required to submit to NCDOT on a regular basis. These datasets include incorporated municipalities in North Carolina that participate in the Powell Bill Program. Boundaries of municipalities which do not participate in the Powell Bill Program are also included in this data. Sources for the boundaries vary in scale and format as provided by the individual Municipalities.For more detailed information about the Powell Bill Program: https://connect.ncdot.gov/municipalities/State-Street-Aid/pages/default.aspxThe Spatial Data Operations Group at the North Carolina Department of Information Technology-Transportation, GIS Unit serves as the data steward of this service, on behalf of the North Carolina Department of Transportation, Powell Bill (State Street-Aid) Program Unit. This data is updated annually, first quarter (usually in February).MetadataThe metadata for the contained layer of the NCDOT City Boundaries Service is available through the following link:Municipal BoundariesPoint of ContactNorth Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the City Boundaries data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product Team

This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.

To provide a base for very generalized maps or used as an outline in conjunction with other data layers. Establishes City Limits for City's Standard Boundary Format. This layer was updated on July 22, 2012.

Vector polygon map data of city limits from Fort Worth, Texas containing 15 features.

City limits GIS (Geographic Information System) data provides valuable information about the boundaries of a city, which is crucial for various planning and decision-making processes. Urban planners and government officials use this data to understand the extent of their jurisdiction and to make informed decisions regarding zoning, land use, and infrastructure development within the city limits.

By overlaying city limits GIS data with other layers such as population density, land parcels, and environmental features, planners can analyze spatial patterns and identify areas for growth, conservation, or redevelopment. This data also aids in emergency management by defining the areas of responsibility for different emergency services, helping to streamline response efforts during crises..

This city limits data is available for viewing and sharing as a map 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.

City Boundary

City limits and city annexations for incorporated cities within Jackson County. These data are created annually by using the assessor's tax code polygons. Any error in the city limits should be brought to the attention of the Jackson County Assessor's office for correction of the tax code polygons which are used for the creation of these data. In some cases, a city may have applied for and had an annexation approved which is not reflected in these data. Once the city pays the county to finalize the annexation, the changes should be reflected.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCity 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 Buffers (this dataset)Counties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing excludes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_CITY: CDTFA incorporated city nameCDTFA_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_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or 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

This feature layer is derived from the standard Ball Ground City Limit layer and is displayed as a line feature, rather than a polygon feature. This feature is merely used for cartographic purposes, allowing the boundary of Ball Ground to be displayed at larger scales without the user seeing a pop-up displayed for the city limits when clicking in the map.For instance, at a smaller scale (e.g. zoomed out to see whole city at once) when a user clicks inside the city limits, a pop-up appears with relevant information about the City of Ball Ground. When viewing at a larger scale (e.g. zoomed in to a neighborhood), normally the user would still see a pop-up for the city limits displayed when clicking around within the map frame. However, at a predetermined transition scale, the polygon feature layer is turned off and the line feature layer is turned on. In doing so, the user will see a pop-up with information about the City of Ball Ground at scales where displaying that information would be appropriate. But at scales where it is not appropriate to see such information, the pop-up will not be displayed unless the user specifically clicks on the border (as opposed to anywhere within the border).

City limits (corporate) boundary lines for municipalities within Wyandotte County, Kansas, including cities of Kansas City, KS, Bonner Springs, Ks, Edwardsville, KS, that portion of City of Lake Quivira within Wyandotte County, and unincorporated remnant of Delaware Township. This dataset also contains city boundaries for Bonner Springs, KS and Lake Quivira, KS, that continue across Wyandotte Co. corporate boundary and into neighboring Johnson and Leavenworth Counties. GIS polygon feature layer dataset derived from source document legal boundary and annexation documents using reference map information at 1:1200 scale. Represents present-day boundary.By using this dataset you acknowledge the following:Kansas Open Records Act StatementThe Kansas Open Records Act provides in K.S.A. 45-230 that "no person shall knowingly sell, give or receive, for the purpose of selling or offering for sale, any property or service to persons listed therein, any list of names and addresses contained in, or derived from public records..." Violation of this law may subject the violator to a civil penalty of $500.00 for each violation. Violators will be reported for prosecution.By accessing this site, the user makes the following certification pursuant to K.S.A. 45-220(c)(2): "The requester does not intend to, and will not: (A) Use any list of names or addresses contained in or derived from the records or information for the purpose of selling or offering for sale any property or service to any person listed or to any person who resides at any address listed; or (B) sell, give or otherwise make available to any person any list of names or addresses contained in or derived from the records or information for the purpose of allowing that person to sell or offer for sale any property or service to any person listed or to any person who resides at any address listed."

© 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 is the official City Limits feature class (layer) for the City of Santa Rosa, CA. This feature class is maintained by the City's GIS team. Features that have a value of "POCKET" in the "LAYER" field are not part of the City. These are pockets of unincorporated county land surrounded by the City.

This map service is provided by NC Department of Transportation and represents Municipal Boundaries defined through the Powell Bill 2023.This data was created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System. Municipal boundaries are recognized as a base cartographic layer for location analysis. The data are current for fiscal year 2023.These Municipal Boundaries data are based on the Powell Bill Program maps for the 2023 fiscal year. Municipalities in North Carolina that participate in the Powell Bill Program are required to submit to NCDOT on a regular basis. These data include incorporated municipalities in North Carolina that participate in the Powell Bill Program. Boundaries of municipalities which do not participate in the Powell Bill Program are also included in this data. Sources for the boundaries vary in scale and format as provided by the Municipalities.Additional metadata: GIS Data Layers (ncdot.gov)

This layer represents the jurisdiction and regulatory boundaries of the City of Austin.

© Acknowledgment of the City of Austin GIS Division would be appreciated in products derived from these data This layer is a component of FloodPro_Webapp_Map.

Feature layer containing the authoritative city limit polygon for Sioux Falls, South Dakota and non-authoritative city limit polygons in the surrounding area.

San Bernardino County City Limits current as of December 17, 2024.City limit boundaries are maintained through maps of annexations and detachments by the County of San Bernardino Surveyor's Office. City Limits GIS data stores non-contiguous city polygons as individual polygons. For questions about this dataset, please email opendata@isd.sbcounty.gov.This feature service will be retired soon and will no longer be updated with the latest changes. To ensure you always get the latest updates, please instead point your maps and apps to use the Cities and Towns (Incorporated Areas) feature layer.