This dataset was created by the Transportation Planning and Programming (TPP) Division of the Texas Department of Transportation (TxDOT) for planning and asset inventory purposes, as well as for visualization and general mapping. County boundaries were digitized by TxDOT using USGS quad maps, and converted to line features using the Feature to Line tool. This dataset depicts a generalized coastline.Update Frequency: As NeededSource: Texas General Land OfficeSecurity Level: PublicOwned by TxDOT: FalseRelated LinksData Dictionary PDF [Generated 2025/03/14]

NZ Parcel Boundaries Wireframe provides a map of land, road and other parcel boundaries, and is especially useful for displaying property boundaries.
This map service is for visualisation purposes only and is not intended for download. You can download the full parcels data from the NZ Parcels dataset.
This map service provides a dark outline and transparent fill, making it perfect for overlaying on our basemaps or any map service you choose.
Data for this map service is sourced from the NZ Parcels dataset which is updated weekly with authoritative data direct from LINZ’s Survey and Title system. Refer to the NZ Parcel layer for detailed metadata.
To simplify the visualisation of this data, the map service filters the data from the NZ Parcels layer to display parcels with a status of 'current' only.
This map service has been designed to be integrated into GIS, web and mobile applications via LINZ’s WMTS and XYZ tile services. View the Services tab to access these services.
See the LINZ website for service specifications and help using WMTS and XYZ tile services and more information about this service.

Important Note: This item is in mature support as of November 2021 and will be retired. A NEW VERSION of this item is available for your use. We recommend updating your maps and apps to use the new version.Boundary-Line is a specialist 1:10 000 scale boundaries dataset. It contains all levels of electoral and administrative boundaries, from district, wards and civil parishes (or communities) up to parliamentary, assembly and European constituencies. The currency of this data is 10/2019.

The coverage of the map service is GB. The map projection is British National Grid. The service is appropriate for viewing down to a scale of approximately 1:20,000. Updated by Esri UK: 22/01/2020To download this dataset use the link here.Ever wondered how Boundary-Line data could be used in analysis? Take a look at our police or supermarket story map.

Village (Neighborhood) Boundaries across the Nation

Boundary lines and associated attributes for incorporated cities in the Commonwealth of Kentucky.

This map is a compilation of the final set of city and county boundary changes filed with the California State Board of Equalization in accordance with Government Code 54900 for each assessment roll year beginning with the 2021 roll year. Boundary corrections are included in the dataset according to information provided by the city, county, and/or LAFCO. These corrections may or may not have been corrected in the Board of Equalization's records. Each layer is considered FINAL as of June in the year noted by the layer name. The boundaries from 2021 through 2025 are based on the California State Board of Equalization's tax rate area maps and may not align with other sources. For the latest data, please view the "City and County Boundary Line Changes" map.As of April 1, 2024, the maintenance of this map is provided by the California Department of Tax and Fee Administration (CDTFA) for sales and use tax purposes.

Overview The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.4 (published 24 February 2025). The 11.4 release contains updated boundary lines and data refinements designed to extend the functionality of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control. National Geospatial Data Asset This dataset is a National Geospatial Data Asset (NGDAID 194) managed by the Department of State. It is a part of the International Boundaries Theme created by the Federal Geographic Data Committee. Dataset Source Details Sources for these data include treaties, relevant maps, and data from boundary commissions, as well as national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process includes analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground. Cartographic Visualization The LSIB is a geospatial dataset that, when used for cartographic purposes, requires additional styling. The LSIB download package contains example style files for commonly used software applications. The attribute table also contains embedded information to guide the cartographic representation. Additional discussion of these considerations can be found in the Use of Core Attributes in Cartographic Visualization section below. Additional cartographic information pertaining to the depiction and description of international boundaries or areas of special sovereignty can be found in Guidance Bulletins published by the Office of the Geographer and Global Issues: https://data.geodata.state.gov/guidance/index.html Contact Direct inquiries to internationalboundaries@state.gov. Direct download: https://data.geodata.state.gov/LSIB.zip Attribute Structure The dataset uses the following attributes divided into two categories: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | Core CC1_GENC3 | Extension CC1_WPID | Extension COUNTRY1 | Core CC2 | Core CC2_GENC3 | Extension CC2_WPID | Extension COUNTRY2 | Core RANK | Core LABEL | Core STATUS | Core NOTES | Core LSIB_ID | Extension ANTECIDS | Extension PREVIDS | Extension PARENTID | Extension PARENTSEG | Extension These attributes have external data sources that update separately from the LSIB: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | GENC CC1_GENC3 | GENC CC1_WPID | World Polygons COUNTRY1 | DoS Lists CC2 | GENC CC2_GENC3 | GENC CC2_WPID | World Polygons COUNTRY2 | DoS Lists LSIB_ID | BASE ANTECIDS | BASE PREVIDS | BASE PARENTID | BASE PARENTSEG | BASE The core attributes listed above describe the boundary lines contained within the LSIB dataset. Removal of core attributes from the dataset will change the meaning of the lines. An attribute status of “Extension” represents a field containing data interoperability information. Other attributes not listed above include “FID”, “Shape_length” and “Shape.” These are components of the shapefile format and do not form an intrinsic part of the LSIB. Core Attributes The eight core attributes listed above contain unique information which, when combined with the line geometry, comprise the LSIB dataset. These Core Attributes are further divided into Country Code and Name Fields and Descriptive Fields. County Code and Country Name Fields “CC1” and “CC2” fields are machine readable fields that contain political entity codes. These are two-character codes derived from the Geopolitical Entities, Names, and Codes Standard (GENC), Edition 3 Update 18. “CC1_GENC3” and “CC2_GENC3” fields contain the corresponding three-character GENC codes and are extension attributes discussed below. The codes “Q2” or “QX2” denote a line in the LSIB representing a boundary associated with areas not contained within the GENC standard. The “COUNTRY1” and “COUNTRY2” fields contain the names of corresponding political entities. These fields contain names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the ‘"Independent States in the World" and "Dependencies and Areas of Special Sovereignty" lists maintained by the Department of State. To ensure maximum compatibility, names are presented without diacritics and certain names are rendered using common cartographic abbreviations. Names for lines associated with the code "Q2" are descriptive and not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS denote independent states. Names rendered in normal text represent dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user. Descriptive Fields The following text fields are a part of the core attributes of the LSIB dataset and do not update from external sources. They provide additional information about each of the lines and are as follows: ATTRIBUTE NAME | CONTAINS NULLS RANK | No STATUS | No LABEL | Yes NOTES | Yes Neither the "RANK" nor "STATUS" fields contain null values; the "LABEL" and "NOTES" fields do. The "RANK" field is a numeric expression of the "STATUS" field. Combined with the line geometry, these fields encode the views of the United States Government on the political status of the boundary line. ATTRIBUTE NAME | | VALUE | RANK | 1 | 2 | 3 STATUS | International Boundary | Other Line of International Separation | Special Line A value of “1” in the “RANK” field corresponds to an "International Boundary" value in the “STATUS” field. Values of ”2” and “3” correspond to “Other Line of International Separation” and “Special Line,” respectively. The “LABEL” field contains required text to describe the line segment on all finished cartographic products, including but not limited to print and interactive maps. The “NOTES” field contains an explanation of special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, limitations regarding the purpose of the lines, or the original source of the line. Use of Core Attributes in Cartographic Visualization Several of the Core Attributes provide information required for the proper cartographic representation of the LSIB dataset. The cartographic usage of the LSIB requires a visual differentiation between the three categories of boundary lines. Specifically, this differentiation must be between: International Boundaries (Rank 1); Other Lines of International Separation (Rank 2); and Special Lines (Rank 3). Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary. Please consult the style files in the download package for examples of this depiction. The requirement to incorporate the contents of the "LABEL" field on cartographic products is scale dependent. If a label is legible at the scale of a given static product, a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field contains the preferred description for the three LSIB line types when they are incorporated into a map legend but is otherwise not to be used for labeling. Use of the “CC1,” “CC1_GENC3,” “CC2,” “CC2_GENC3,” “RANK,” or “NOTES” fields for cartographic labeling purposes is prohibited. Extension Attributes Certain elements of the attributes within the LSIB dataset extend data functionality to make the data more interoperable or to provide clearer linkages to other datasets. The fields “CC1_GENC3” and “CC2_GENC” contain the corresponding three-character GENC code to the “CC1” and “CC2” attributes. The code “QX2” is the three-character counterpart of the code “Q2,” which denotes a line in the LSIB representing a boundary associated with a geographic area not contained within the GENC standard. To allow for linkage between individual lines in the LSIB and World Polygons dataset, the “CC1_WPID” and “CC2_WPID” fields contain a Universally Unique Identifier (UUID), version 4, which provides a stable description of each geographic entity in a boundary pair relationship. Each UUID corresponds to a geographic entity listed in the World Polygons dataset. These fields allow for linkage between individual lines in the LSIB and the overall World Polygons dataset. Five additional fields in the LSIB expand on the UUID concept and either describe features that have changed across space and time or indicate relationships between previous versions of the feature. The “LSIB_ID” attribute is a UUID value that defines a specific instance of a feature. Any change to the feature in a lineset requires a new “LSIB_ID.” The “ANTECIDS,” or antecedent ID, is a UUID that references line geometries from which a given line is descended in time. It is used when there is a feature that is entirely new, not when there is a new version of a previous feature. This is generally used to reference countries that have dissolved. The “PREVIDS,” or Previous ID, is a UUID field that contains old versions of a line. This is an additive field, that houses all Previous IDs. A new version of a feature is defined by any change to the

This line feature layer displays the official boundary line for Leon County, Florida as maintained by the Leon County Property Appraiser's Office. This layer is updated on an as needed basis.

From Parliamentary constituencies to council wards, Boundary-Line™ maps every administrative boundary in detail for you. And what's more, it's completely free to download and use. Bring statistics to life For academics or policy-makers, Boundary-Line brings the statistics in your reports to life. It lets you show differences between regions or councils using easy-to-read shaded maps. A robust framework Monitoring outcomes by area is key for public bodies. Boundary-Line gives you a robust analytical framework to ensure the right communities get the right resources. Individual properties When you're consulting on updating boundaries to take account of population change, Boundary-Line lets you show on a map where the line's being drawn, right down to the level of individual properties.

This line-based spatial data represents the Boundary Lines that exist in the Digital Tax Map Collection. • Updates: Data is extracted from DOF’s internal system on the last Friday of each month and refreshed on ArcGIS Online on the 1st. The online map always shows the most recent version. • Accessing the Data: • Digital Tax Map on NYC Open Data: See the complete collection. • Individual layers: Downloadable from the Digital Tax Map Feature Server. • Complete source: Available through the Digital Tax Map service, which always points to the latest monthly release. Note: To ensure reliability, the Tax Map alternates between Set A and Set B each month. If one set has issues, the previous month’s copy remains online. Both sets are kept about a month apart and are available for download: • Set A link • Set B link • Digital Alteration Book (DAB): The DAB is the official log of map changes—such as new lots, merges, or boundary shifts—providing a clear record of how the Tax Map evolves. It is available through the Property Information Portal. Disclaimer: This dataset reflects formal applications submitted to DOF but may not reflect the latest changes in other City systems (e.g., exemptions or buildings data). It is provided for informational purposes only and is not guaranteed to be accurate as of today’s date.

This service provides vector polygon dataset defining the official boundaries of the 100 counties within North Carolina as well as the boundaries between North Carolina and the states which border North Carolina.The North Carolina county polygon boundary service provides location information for North Carolina State and County Boundary lines derived from the best available survey and/or Geographic Information System (GIS) data. Sources for information are the North Carolina Geodetic Survey (NCGS), NC Department of Transportation (NCDOT), United States Geological Survey (USGS), and field surveys conducted by licensed surveyors in North Carolina and neighboring states that have been approved and recorded in their respective counties. Some boundaries cannot be surveyed in cases where boundaries are coincident with river centers. North Carolina Geodetic Survey assists counties on a cooperative basis (NC General Statute 153A-18) in defining and monumenting the location of uncertain or disputed boundaries as established by law. Some counties have completed boundary surveys for at least a portion of their county boundary. However, the majority of county boundaries have not been surveyed and are represented by the best currently available data from GIS sources, including NCDOT county maps (which originally came from the USGS) and updated county parcel maps.This data is updated annually, first quarter (usually in February).MetadataThe metadata for the contained layer of the NCDOT County Boundaries Service is available through the following link:County Boundaries PolygonPoint of Contact North 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 County 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 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 map layer contains hydrologic unit boundaries and codes for the United States, Puerto Rico, and the U.S. Virgin Islands. It was revised for inclusion in the National Atlas of the United States of America, and updated to match the streams file created by the USGS National Mapping Division (NMD) for the National Atlas of the United States of America. This is a revised version of the November 2002 map layer.

This dataset contains the Commonwealth of Kentucky Boundary. The State boundary along Ohio River has been updated to reflect the Supreme Court Case regarding a boundary dispute between Kentucky, Indiana and Ohio in 1980 (Ohio v. Kentucky, 444 U.S. 335 (1980)).Online Linkage: https://ky.box.com/v/kymartian-ky-state-polygon

This layer provides the latest bearing (direction) and/or distance for cadastral boundaries.

When a cadastral survey is undertaken the relationship between boundary and non-boundary marks is ascertained or measured. • This commonly is in the form or a vector (bearing and distance), but occasionally just one component. • Some relationships are defined as arcs. In this data layer, the arc length is recorded in the distance field and a separate record holds the chord.

Only observations that have been captured in Landonline are available. This includes vectors that were re-captured in the Survey Capture Areas from survey plans lodged prior to Landonline and all survey observations since.

This dataset is refreshed on a weekly basis from the datasets the team works on daily.Last update date: 20 November 2025.National Highways Operational Highway Boundary (RedLine) maps out the land belonging to the highway for the whole Strategic Road Network (SRN). It comprises two layers; one being the an outline and another showing the registration status / category of land of land that makes up the boundary. Due to the process involved in creating junctions with local highway authority (LHA) roads, land in this dataset may represent LHA highway (owned by National Highways but the responsibility of the LHA to maintain). Surplus land or land held for future projects does not form part of this dataset.The highway boundary is derived from:Ordnance Survey Mastermap Topography,HM Land Registry National Polygon Service (National Highway titles only), andplots researched and digitised during the course of the RedLine Boundary Project.The boundary is split into categories describing the decisions made for particular plots of land. These categories are as follows:Auto-RedLine category is for plots created from an automated process using Ordnance Survey MasterMap Topography as a base. Land is not registered under National Highways' name. For example, but not limited to, unregistered ‘ancient’ highway vested in Highways England, or bridge carrying highways over a rail line.NH Title within RedLine category is for plots created from Land Registry Cadastral parcels whose proprietor is National Highways or a predecessor. Land in this category is within the highway boundary (audited) or meets a certain threshold by the algorithm.NH Title outside RedLine category is for plots created in the same way as above but these areas are thought to be outside the highway boundary. Where the Confidence is Low, land in this category is yet to be audited. Where the Confidence is High, land in this category has been reviewed and audited as outside our operational boundary.National Highways (Technician) Data category is for plots created by National Highways, digitised land parcels relating to highway land that is not registered, not yet registered or un-registerable.Road in Tunnel category, created using tunnel outlines from Ordnance Survey MasterMap Topography data. These represent tunnels on Highways England’s network. Land is not registered under National Highways' name, but land above the tunnel may be in National Highways’ title. Please refer to the definitive land ownership records held at HM Land Registry.The process attribute details how the decision was made for the particular plot of land. These are as follows:Automated category denotes data produced by an automated process. These areas are yet to be audited by the company.Audited category denotes data that has been audited by the company.Technician Data (Awaiting Audit) category denotes data that was created by National Highways but is yet to be audited and confirmed as final.The confidence attribute details how confident you can be in the decision. This attribute is derived from both the decisions made during the building of the underlying automated dataset as well as whether the section has been researched and/or audited by National Highways staff. These are as follows:High category denotes land that has a high probability of being within the RedLine boundary. These areas typically are audited or are features that are close to or on the highway.Moderate category denotes land that is likely to be within the highway boundary but is subject to change once the area has been audited.Low category denotes land that is less likely to be within the highway boundary. These plots typically represent Highways England registered land that the automated process has marked as outside the highway boundary.Please note that this dataset is indicative only. For queries about this dataset please contact the GIS and Research Team.

This point shapefile represents municipality and city boundary lines in Serbia. Boundaries of administrative units are collected from different sources (cadastral maps, basic state map and topographic maps of various scales). Positional accuracy has value between 1m to 300m based on source for data collecting. Global Map Serbia version 2.1 Drainage, Population center and Transportation layers were created using the Topographic map 1:300 000. Updating the data using The vector national database (scale 1:1 000 000) and orthophoto images. Digital Terrain Model with 30m grid is produced using terrain elevation data obtained under "Production of digital orthophoto maps for the Republic of Serbia". In order to satisfied Global Map Specification data resampling is done to 1km resolution. Global Map Serbia version 2.0 Land Cover was created using the vector data from European Environment Agency (EEA) - The data were collected and processed using remote sensing satellite images.

This dataset contains existing and approved residential boundaries in Cary, NC. For additional information on properties check out our website. This dataset is updated as residential boundaries are changed.

This hosted feature layer has been published in RI State Plane Feet NAD 83Water Type Boundary lines describe those points along a coastline where one water use type changes to another. Each mapped boundary is coded by number with verbal descriptions found in the Maps of Water Use Categories in the Coastal Resources Management Plan https://www.crmc.ri.gov/regulations/RICRMP.pdf. Except where otherwise noted, the water use classifications along any shoreline reach and between two boundary line designations run parallel to the general coastal trend and extend 500 feet seaward from the mean high water mark.

This point shapefile represents municipality boundary lines in Albania. The Global Map Albania version 2 was developed based on Global Map Specifications version 2.2. The source data of vector layers were a Digital Map 1:25000 and Orthophoto, map image made in 1985 and orthophoto made in 2008. The data source of Elevation layer was developed using orthophoto 2000 year. The data source of Land Use and Vegetation layer were developed using orthophoto 2012 year. IRS, SPOT and RapidEye satellite images, dual coverage, orthophotos (2012), topographic maps for making Land Cover.