The Boundaries were updated on September 6, 2024 to comply with the Boundary Line Adjustment between Essex and King and Queen Counties ordered by the Circuit Court in Case Number CL24000137-00

County Boundary for Essex County, Virginia.

This dataset represents the spatial boundaries of clean water supply in the Suffolk region served by ESW. This dataset is critical for understanding the division of service areas among different companies within the United Kingdom. 

The political boundary datalayer is a polygon representation of town boundaries created from arcs developed from survey coordinates extracted from the 68-volume Harbor and Lands Commission Town Boundary Atlas for the 351 communities (cities and towns) in Massachusetts. The Atlas was published in the early 1900's and is maintained by the Survey Section of Massachusetts Highway Department. For communities with a coastal boundary, MassGIS has collaborated with Massachusetts Water Resources Authority and the Department of Environmental Protection to complete a 1:12000 scale coastline. The boundary for the coastline was defined as being the upland side of tidal flats and rocky inter-tidal zones. Note that the 351 communities are the official municipal names, not including "villages" or other sections of towns. Note: Complete metadata is available within the downloaded zip file. This metadata can be viewed with ESRI ArcGIS software, and can be exported to FGDC and ISO metadata formats.

This parcels dataset is a spatial representation of tax lots for Essex County, New Jersey that have been extracted from the NJ statewide parcels composite by the NJ Office of Information Technology, Office of GIS (NJOGIS). Parcels at county boundaries have been modified to correspond with the NJ county boundaries and the parcels in adjacent counties.Each parcel contains a field named PAMS_PIN based on a concatenation of the county/municipality code, block number, lot number and qualification code. Using the PAMS_PIN, the dataset can be joined to the MOD-IV database table that contains supplementary attribute information regarding lot ownership and characteristics. Due to irregularities in the data development process, duplicate PAMS_PIN values exist in the parcel records. Users should avoid joining MOD-IV database table records to all parcel records with duplicate PAMS_PINs because of uncertainty regarding whether the MOD-IV records will join to the correct parcel records. There are also parcel records with unique PAMS_PIN values for which there are no corresponding records in the MOD-IV database tables. This is mostly due to the way data are organized in the MOD-IV database.The polygons delineated in the dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such.The MOD-IV system provides for uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of the Division of Taxation. MOD-IV maintains and updates all assessment records and produces all statutorily required tax lists for property tax bills. This list accounts for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel. Tax List records were received as raw data from the Taxation Team of NJOIT which collected source information from municipal tax assessors and created the statewide table. This table was subsequently processed for ease of use with NJ tax parcel spatial data and split into an individual table for each county.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

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

The Electric_service_area feature class contains information about electric utility service areas in the State of Virginia. This data contains a set of polygon features clipped to the Virginia Base Mapping Project (VBMP) state boundary reference layer. The data set includes 2,428 features divided spatially by 30 electric service providers throughout the state. The maps also include hyperlinks to viewable authorization certificates containing a text document that notes the service type (electric, natural gas, water) and the geographic area that the utility has been authorized to serve. The data was created by first georeferencing digitally scanned versions of 1:24,000 USGS quadrangle (quad) maps which contained hand-drawn electric service area boundaries prepared by the SCC. Using heads up digitizing, the georeferenced maps were then cut from the polygon features of a USGS quad index. The data was then clipped to only include Essex County.

Water Boundary Meters (SCADA) System

This dataset consists of the school catchment boundaries for elementary and secondary schools for the Greater Essex County District School Board and the Windsor Essex Catholic District School Board. The files are in shapefile format (.shp) which is intended for GIS (Geographic Information Systems) purposes.

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

Tecumseh Municipal Political Boundary

Link to StatsCan file: https://www150.statcan.gc.ca/n1/en/catalogue/92-179-X

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces/Area Hydrography Relationship File contains a record for each face/area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up the MTS. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces/Area Hydrography Relationship File (facesah.dbf) applies can be determined by linking to the Topological Faces shapefile (faces.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces/Area Hydrography Relationship File applies can be determined by linking to the Area Hydrography shapefile (areawater.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces/Area Hydrography Relationship File contains a record for each face/area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up the MTS. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces/Area Hydrography Relationship File (facesah.dbf) applies can be determined by linking to the Topological Faces shapefile (faces.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces/Area Hydrography Relationship File applies can be determined by linking to the Area Hydrography shapefile (areawater.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces/Area Hydrography Relationship File contains a record for each face/area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up the MTS. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces/Area Hydrography Relationship File (facesah.dbf) applies can be determined by linking to the Topological Faces shapefile (faces.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces/Area Hydrography Relationship File applies can be determined by linking to the Area Hydrography shapefile (areawater.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) contains a record for each face / area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Area Hydrography Shapefile (AREAWATER.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) contains a record for each face / area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Area Hydrography Shapefile (AREAWATER.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

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

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

Information supplied by Essex County Council showing boundaries of Urban Areas/Settlement areas within Thurrock. Upon accessing this Licensed Data you will be deemed to have accepted the terms of the Public Sector End User Licence – INSPIRE