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.

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 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 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.

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.

The Geological Survey of Northern Ireland (GSNI) was commissioned to produce a Northern Ireland wide coastal geological dataset, detailing the bedrock geology.GSNI used the 1;10,000 digital bedrock geology map to create a coastal dataset which extends inland 200 meters and out to a seaward depth of approx. 10 metres, matching the extend of the Northern Ireland 3-Dimensional Coastal Survey. This involved refinement of the existing 1;10,000 map where signification coastal change has occurred since the original survey. Where gaps existed, unpublished datasets were used.

Township and city area boundary 1.................

This line feature layer contains Legal City boundaries within Los Angeles County.

The principal attribute is BDRY_TYPE which represents the boundary feature types. Use its values below for definition queries and layer symbology for your mapping needs.

Coast - This value represents the coastline. This data is carefully maintained by DPW staff, based Los Angeles Region Imagery Acquisition Consortium data.

Land City - This value represents city boundaries on land.

Land County - This value represents the county boundary on land.

Pier - One example is the Santa Monica Pier. Man-made features may be regarded as extensions of the coastline.

Breakwater - Examples include the breakwater barriers that protect the Los Angeles Harbor.

Water - This value is used to separate features representing internal navigable waters and the ocean. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.

Ocean - This value is used to represent ocean boundaries between cities in addition to the seaward boundaries of coastal cities. Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles (a nautical mile is 1852 meters) from the coastline.

Large Scale International Boundaries

Version 11.1 Release Date: August 22, 2022

Overview

The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. These data and their derivatives are the only international boundary lines approved for U.S. Government use. They reflect U.S. Government policy, and not necessarily de facto limits of control. This dataset is a National Geospatial Data Asset.

Details

Sources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery of the data involves 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.

Attributes

The dataset uses the following attributes: Attribute Name Explanation Country Code Country-level codes are from the Geopolitical Entities, Names, and Codes Standard (GENC). The Q2 code denotes a line representing a boundary associated with an area not in GENC. Country Names Names approved by the U.S. Board on Geographic Names (BGN). Names for lines associated with a Q2 code are descriptive and are not necessarily BGN-approved. Label Required text label for the line segment where scale permits Rank/Status Rank 1: International Boundary Rank 2: Other Line of International Separation Rank 3: Special Line Notes Explanation of any applicable special circumstances Cartographic Usage Depiction of the LSIB requires a visual differentiation between the three categories of boundaries: 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. Additional cartographic information can be found in Guidance Bulletins (https://hiu.state.gov/data/cartographic_guidance_bulletins/) published by the Office of the Geographer and Global Issues. Please direct inquiries to internationalboundaries@state.gov.

Credits

The lines in the LSIB dataset are the product of decades of collaboration between geographers at the Department of State and the National Geospatial-Intelligence Agency with contributions from the Central Intelligence Agency and the UK Defence Geographic Centre. Attribution is welcome: U.S. Department of State, Office of the Geographer and Global Issues.

Changes from Prior Release

This version of the LSIB contains changes and accuracy refinements for the following line segments. These changes reflect improvements in spatial accuracy derived from newly available source materials, an ongoing review process, or the publication of new treaties or agreements. Changes to lines include: • Akrotiri (UK) / Cyprus • Albania / Montenegro • Albania / Greece • Albania / North Macedonia • Armenia / Turkey • Austria / Czechia • Austria / Slovakia • Austria / Hungary • Austria / Slovenia • Austria / Germany • Austria / Italy • Austria / Switzerland • Azerbaijan / Turkey • Azerbaijan / Iran • Belarus / Latvia • Belarus / Russia • Belarus / Ukraine • Belarus / Poland • Bhutan / India • Bhutan / China • Bulgaria / Turkey • Bulgaria / Romania • Bulgaria / Serbia • Bulgaria / Romania • China / Tajikistan • China / India • Croatia / Slovenia • Croatia / Hungary • Croatia / Serbia • Croatia / Montenegro • Czechia / Slovakia • Czechia / Poland • Czechia / Germany • Finland / Russia • Finland / Norway • Finland / Sweden • France / Italy • Georgia / Turkey • Germany / Poland • Germany / Switzerland • Greece / North Macedonia • Guyana / Suriname • Hungary / Slovenia • Hungary / Serbia • Hungary / Romania • Hungary / Ukraine • Iran / Turkey • Iraq / Turkey • Italy / Slovenia • Italy / Switzerland • Italy / Vatican City • Italy / San Marino • Kazakhstan / Russia • Kazakhstan / Uzbekistan • Kosovo / north Macedonia • Kosovo / Serbia • Kyrgyzstan / Tajikistan • Kyrgyzstan / Uzbekistan • Latvia / Russia • Latvia / Lithuania • Lithuania / Poland • Lithuania / Russia • Moldova / Ukraine • Moldova / Romania • Norway / Russia • Norway / Sweden • Poland / Russia • Poland / Ukraine • Poland / Slovakia • Romania / Ukraine • Romania / Serbia • Russia / Ukraine • Syria / Turkey • Tajikistan / Uzbekistan

This release also contains topology fixes, land boundary terminus refinements, and tripoint adjustments.

Copyright Notice and Disclaimer

While U.S. Government works prepared by employees of the U.S. Government as part of their official duties are not subject to Federal copyright protection (see 17 U.S.C. § 105), copyrighted material incorporated in U.S. Government works retains its copyright protection. The works on or made available through download from the U.S. Department of State’s website may not be used in any manner that infringes any intellectual property rights or other proprietary rights held by any third party. Use of any copyrighted material beyond what is allowed by fair use or other exemptions may require appropriate permission from the relevant rightsholder. With respect to works on or made available through download from the U.S. Department of State’s website, neither the U.S. Government nor any of its agencies, employees, agents, or contractors make any representations or warranties—express, implied, or statutory—as to the validity, accuracy, completeness, or fitness for a particular purpose; nor represent that use of such works would not infringe privately owned rights; nor assume any liability resulting from use of such works; and shall in no way be liable for any costs, expenses, claims, or demands arising out of use of such works.

COB_ARC: This theme shows line representation of the jurisdictional and cartographic county perimeters for Oregon and Washington.

Coastal Area & Boundary Polygon:

The Coastal Area layer is a 1:24,000-scale, polygon feature-based layer that includes the land and waters that lie within the Coastal Area as defined by Connecticut General Statute (C.G.S.) 22a-94(a). Activities and actions conducted within the coastal area by Federal and State Agencies (i.e., U.S. Army Corps of Engineers (USACOE), DEP regulatory programs, and state plans and actions) must be consistent with all of the applicable standards and criteria contained in the Connecticut Coastal Management Act (C.G.S. 22a-90 to 22a-113). A subset of the Coastal Area, the Coastal Boundary, represents an area within which activities regulated or conducted by coastal municipalities must be consistent with the Coastal Management Act. As defined in this section of the statutes, the Coastal Area includes the land and water within the area delineated by the following: the westerly, southerly and easterly limits of the state's jurisdiction in Long Island Sound; the towns of Greenwich, Stamford, Darien, Norwalk, Westport, Fairfield, Bridgeport, Stratford, Shelton, Milford, Orange, West Haven, New Haven, Hamden, North Haven, East Haven, Branford, Guilford, Madison, Clinton, Westbrook, Deep River, Chester, Essex, Old Saybrook, Lyme, Old Lyme, East Lyme, Waterford, New London, Montville, Norwich, Preston, Ledyard, Groton and Stonington. This layer includes a single polygon feature defined by the boundaries described above. Attribute information is comprised of an Av_Legend to denote the coastal area. Data is compiled at 1:24,000 scale. This data is not updated.

The Coastal Boundary layer is a 1:24,000-scale, polygon feature-based layer of the legal mylar-based maps adopted by the Commissioner of the Department of Environmental Protection (DEP) (i.e., maps were adopted on a town by town basis) showing the extent of lands and coastal waters as defined by Connecticut General Statute (C.G.S.) 22a-93(5)) within Connecticut's coastal area (defined by C.G.S. 22a-94(c)). The coastal boundary is a hybrid of the original 1:24,000 version maps prepared by DEP consistent with C.G.S. 22a-94(d) (Coastal Area) and the revised boundary mapping undertaken by twenty-two coastal towns prepared pursuant to C.G.S. 22a-94(f). This layer therefore does not replace the legal maps and may not be used for legal determinations. The Coastal Boundary layer includes a single polygon feature that represents the coastal boundary. No other features are included in this layer. Data is compiled at 1:24,000 scale. Attribute information is comprised of an Av_Legend attribute and a CoastB_Flg attribute to denote the coastal boundary. Other attributes include automatically calculated Shape_Length and Shape_Area fields. This data is not updated. Any regulated activity conducted within the coastal boundary by a municipal agency (i.e., plans of development, zoning regulations, municipal coastal programs and coastal site plan review (i.e., site plans submitted to zoning commission, subdivision or resubdivision plans submitted to planning commission, application for special permit or exception to the zoning or planning commissions or zoning board of appeals, variance submitted to zoning board of appeals and a referral of a municipal project)) must be conducted in a manner consistent with the requirements of the Connecticut Coastal Management Act (CMA; C.G.S. 22a-90 to 22a-113). As the Coastal Boundary is a hybrid of the Coastal Area, all state and federal agency activities must be consistent with the requirements of the CMA. As defined in C.G.S. 22a-94(b) the coastal boundary is a "continuous line delineated on the landward side by the interior contour elevation of the one hundred year frequency coastal flood zone, as defined and determined by the National Flood Insurance Act, as amended (USC 42 Section 4101, P.L. 93-234), or a one thousand foot linear setback measured from the mean high water mark in coastal waters, or a one thousand foot linear setback measured from the inland boundary of tidal wetlands mapped under section 22a-20, whichever is farthest inland; and shall be delineated on the seaward side by the seaward extent of the jurisdiction of the state." The original boundary maps were created in 1979 on stable mylar overlay using the 1:24,000-scale US Geological Survey topographic quadrangle maps (mylar film format). The source for tidal wetland maps were the legal 1:24,000 maps (mylar format) adopted by the Commissioner of DEP and transformed to 1:24,000 mylar-scale maps by the Office of Policy and Management (OPM) using an accurate pantograph. OPM similarly converted FEMA's flood insurance maps (various scales) to a 1:24,000 mylar overlay. The inland extent of coastal waters was plotted on 1:24,000 USGS topographic maps following the procedures and sources described in The Boundary Between Saltwater and Freshwater in Connecticut, December 1978 prepared by the State of Connecticut, Department of Environmental Protection, Coastal Area Management Program. The following twenty-two towns have adopted municipal coastal boundaries: Chester, Clinton, Darien, Deep River, East Haven, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Madison, Milford, New Haven, New London, North Haven, Norwalk, Old Lyme, Old Saybrook, Stamford and Waterford. The coastal boundary maps for these towns may be at different scales than the original DEP draft maps and may contain minor adjustments to the boundary as permitted in C.G.S. 22a-94(f).

The Atlas of Canada National Scale Data 1:5,000,000 Series consists of boundary, coast, island, place name, railway, river, road, road ferry and waterbody data sets that were compiled to be used for atlas medium scale (1:5,000,000 to 1:15,000,000) mapping. These data sets have been integrated so that their relative positions are cartographically correct. Any data outside of Canada included in the data sets is strictly to complete the context of the data.

This dataset provides information about the number of properties, residents, and average property values for Boundary Line Road cross streets in Bridgewater, ME.

The Coastal Boundary layer is a 1:24,000-scale, polygon feature-based layer of the legal mylar-based maps adopted by the Commissioner of the Department of Environmental Protection (DEP) (i.e., maps were adopted on a town by town basis) showing the extent of lands and coastal waters as defined by Connecticut General Statute (C.G.S.) 22a-93(5)) within Connecticut's coastal area (defined by C.G.S. 22a-94(c)). The coastal boundary is a hybrid of the original 1:24,000 version maps prepared by DEP consistent with C.G.S. 22a-94(d) (Coastal Area) and the revised boundary mapping undertaken by twenty-two coastal towns prepared pursuant to C.G.S. 22a-94(f). This layer therefore does not replace the legal maps and may not be used for legal determinations. The Coastal Boundary layer includes a single polygon feature that represents the coastal boundary. No other features are included in this layer. Data is compiled at 1:24,000 scale. Attribute information is comprised of an Av_Legend attribute and a CoastB_Flg attribute to denote the coastal boundary. Other attributes include automatically calculated Shape_Length and Shape_Area fields. This data is not updated. Any regulated activity conducted within the coastal boundary by a municipal agency (i.e., plans of development, zoning regulations, municipal coastal programs and coastal site plan review (i.e., site plans submitted to zoning commission, subdivision or resubdivision plans submitted to planning commission, application for special permit or exception to the zoning or planning commissions or zoning board of appeals, variance submitted to zoning board of appeals and a referral of a municipal project)) must be conducted in a manner consistent with the requirements of the Connecticut Coastal Management Act (CMA; C.G.S. 22a-90 to 22a-113). As the Coastal Boundary is a hybrid of the Coastal Area, all state and federal agency activities must be consistent with the requirements of the CMA. As defined in C.G.S. 22a-94(b) the coastal boundary is a "continuous line delineated on the landward side by the interior contour elevation of the one hundred year frequency coastal flood zone, as defined and determined by the National Flood Insurance Act, as amended (USC 42 Section 4101, P.L. 93-234), or a one thousand foot linear setback measured from the mean high water mark in coastal waters, or a one thousand foot linear setback measured from the inland boundary of tidal wetlands mapped under section 22a-20, whichever is farthest inland; and shall be delineated on the seaward side by the seaward extent of the jurisdiction of the state." The original boundary maps were created in 1979 on stable mylar overlay using the 1:24,000-scale US Geological Survey topographic quadrangle maps (mylar film format). The source for tidal wetland maps were the legal 1:24,000 maps (mylar format) adopted by the Commissioner of DEP and transformed to 1:24,000 mylar-scale maps by the Office of Policy and Management (OPM) using an accurate pantograph. OPM similarly converted FEMA's flood insurance maps (various scales) to a 1:24,000 mylar overlay. The inland extent of coastal waters was plotted on 1:24,000 USGS topographic maps following the procedures and sources described in The Boundary Between Saltwater and Freshwater in Connecticut, December 1978 prepared by the State of Connecticut, Department of Environmental Protection, Coastal Area Management Program. The following twenty-two towns have adopted municipal coastal boundaries: Chester, Clinton, Darien, Deep River, East Haven, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Madison, Milford, New Haven, New London, North Haven, Norwalk, Old Lyme, Old Saybrook, Stamford and Waterford. The coastal boundary maps for these towns may be at different scales than the original DEP draft maps and may contain minor adjustments to the boundary as permitted in C.G.S. 22a-94(f).

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 information is represented as vector digital data. The boundary information is updated twice a year, in May and October. The May release contains the boundaries that have become live in the first week of May, in the year of release. The October release contains the May boundaries plus additional information. Boundary-Line files and sub-levels includes: County - The named county, district, district ward, civil parish, county electoral division (ED); European constituencies - The named European region; Greater London Authority - The Greater London Authority, Greater London Authority Assembly constituency, London borough, London borough ward; Metropolitan districts - The named metropolitan district, metropolitan district ward, civil parish where appropriate; Scottish parliamentary electoral region - The named Scottish Parliamentary electoral region, Scottish parliamentary constituency; Unitary authorities- The named unitary authority, unitary authority ward or unitary authority ED as appropriate, civil parish where appropriate, together with community in Wales; Welsh Assembly Electoral Region - The named Welsh Assembly electoral region, Welsh assembly constituency; Westminster constituencies - The named Westminster constituency; Extent of the realm - Low water mark or seaward boundary extension. Other attribution includes: High water mark; Unique identifiers - For administrative areas, polygons and links; Area measurements; Definitive names; Census codes

This boundary dataset complements 13 other datasets as part of a study that compared ancient settlement patterns with modern environmental conditions in the Jazira region of Syria. This study examined settlement distribution and density patterns over the past five millennia using archaeological survey reports and French 1930s 1:200,000 scale maps to locate and map archaeological sites. An archaeological site dataset was created and compared to and modelled with soil, geology, terrain (contour), surface and subsurface hydrology and normal and dry year precipitation pattern datasets; there are also three spreadsheet datasets providing 1963 precipitation and temperature readings collected at three locations in the region. The environmental datasets were created to account for ancient and modern population subsistence activities, which comprise barley and wheat farming and livestock grazing. These environmental datasets were subsequently modelled with the archaeological site dataset, as well as, land use and population density datasets for the Jazira region. Ancient trade routes were also mapped and factored into the model, and a comparison was made to ascertain if there was a correlation between ancient and modern settlement patterns and environmental conditions; the latter influencing subsistence activities. This boundary dataset was generated to define the extent of the study area, which comprises the border between Syria and Turkey, Syria and Iraq, the River Tigris and the River Euphrates. All related data collected was confined within this boundary dataset with the exception of the archaeological dataset. Archaeological sites were identified and mapped along both banks of the River Euphrates. Also, the town of Dayr az-Zawr, where the 1963 precipitation and temperature monthly values were collected for one of the datasets, falls outside the Jazira Region. Derived from 1:200,000 French Levant Map Series (Further Information element in this metadata record provides list of sheets).The boundary line dataset was captured from 11 map sheets, which were based on the French Levant surveys conducted in Syria during the 1930s and mapped at a scale of 1:200,000. The size of each map measures 69 x 59 cm. The boundary line on each sheet was traced to mylar. Subsequently, each mylar sheet was photocopied and reduced in size to an 11 x 17 inch sheet. These sheets were merged to form the contiguous area comprising the full extent of the boundary for the study area. This was then traced again to another mylar sheet and subsequently scanned and cleaned for further processing and use in a GIS as a polygon coverage. Thesis M 2001 MATH, Ohio University Mathys, Antone J 'A GIS comparative analysis of bronze age settlement patterns and the contemporary physical landscape in the Jazira Region of Syria'., French Levant Map Series (1:200,000) for Syrie (Syria). Projected to Lambert grid. These are colour maps measuring to 69 x 59 cm in size. The dataset was created from the following sheet numbers and titles: 1) NI-37 XVII, Abou Kemal 2) NI-37 XVIII, Ana 3) NI-37 XXI, Ressafe 4) NI-37 XXII, Raqqa 5) NI-37 XXIII, Deir ez Zoir 6) NI-37 XXIV, Bouara 7) NI-37-III, Djerablous 8) NJ-37 IV, Toual Aaba 9) NJ-37 V, Hassetche 10) NJ-37 VI, Qamishliye-Sinjar 11) (No sheet number), Qaratchok-Darh Dressepar la Service Geographique des F.F.L. en 1945 Reimprime par l'Institut Geographique National en 1950 (Originally produced by this Geographic Service of the F.F.L. (Forces Francaises Libres) in 1945 and reprinted by the National Geographic Institute in 1950). Paris: France. Institut Geographique National, 1945-1950. Original map series might be traced to Beirut: Bureau Topographique des Troupes francaises du Levant, 1933-1938. GIS vector data. This dataset was first accessioned in the EDINA ShareGeo Open repository on 2010-06-09 and migrated to Edinburgh DataShare on 2017-02-21.

COB_ARC:

This theme shows line representation of the jurisdictional and cartographic county perimeters for Oregon and Washington.

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.

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