Internal feature number.

ESRI

Land Class - Distinguishes land from water. This dataset includes a large water polygon feature that may impact polygon drawing performance. To improve drawing performance, exclude all water features by using the following expression in a layer definition query: LAND_CLASS = "Land"

State of Connecticut, Department of Environmental Protection

Connecticut Legend - Classifies features to highlight and differentiate Connecticut from other states.

State of Connecticut, Department of Environmental Protection

State Code

State of Connecticut, Department of Environmental Protection

State Name

State of Connecticut, Department of Environmental Protection

Label Flag - Identifies polygons considered to be large and significant enough in size to be labeled on a map with State names. Polygons designated for labeling are assigned LABEL_FLAG values equal to "True", whereas small island polygons along coast, not typically labeled with State names, are assigned LABEL_FLAG values equal to "False". Label selected features with the MAP_LABEL attribute.

State of Connecticut, Department of Environmental Protection

Map Label Text - Text values from the STATE_NAME field used for map labeling purposes. Use the LABEL_FLAG field to query for polygon features to label with this field.

State of Connecticut, Department of Environmental Protection

Connecticut Map Label - Map label text for Connecticut. Use this field to label Connecticut without using the LABEL_FLAG field to query for the appropriate features to label, which is a slower technique.

State of Connecticut, Department of Environmental Protection

Not Connecticut Map Label - Map label text for all but the State of Connecticut. Use this field to label all states but Connecticut without using the LABEL_FLAG field to query for the appropriate features to label, which is a slower technique.

State of Connecticut, Department of Environmental Protection

Feature geometry.

ESRI

The USGS is the collector of the data (compiler). The State of Connecticut, Department of Environmental Protection is the creator and maintainer of the data layer (editor) and producer (publisher) of this information for use. The 2005 Edition essentially includes the same set of geographic features published in 1994. However, the 2005 Edition differs from information published in 1994 primarily as a result of minor corrections and improvements to feature geometry and feature attribute information. Some feature attribute information (data fields) have been slightly modified and made easier to use. This layer includes information that is relatively static and does not change over time. Data is not updated. Data compiled at 1:24,000 scale.

Town is a 1:24,000-scale, polygon and line feature-based layer that includes state, county and town (municipal) boundary features depicted on the U.S. Geological Survey (USGS) 7.5 minute topographic quadrangle maps for the State of Connecticut. This layer only includes information for Connecticut. Line features include State, county, and town (municipal) boundaries. Polygon features depict the geographic areas for individual towns (municipalities). Data is in ArcInfo coverage format in the Connecticut State Plane Coordinate System of 1983 (NAD 83). Map units are in feet.

Publication dates of the USGS 7.5 minute topographic quadrangle maps for the State of Connecticut through 1984.

METWP24 depicts political boundaries, common town names, and geocodes for Maine at 1:24,000 scale. The coverage was created from USGS, 7.5 minute map series, town boundaries. The Maine GIS base layer COAST, which contains Maine's coastal Mean High Water (MHW) mark and Maine islands, was used in the development of METWP24. Polygon data was originally obtained in ESRI Shapefile format in Universal Transverse Mercator 1983, Zone 19, map units meters. The name of the shapefile is metwp24p_06302005.shp.

source dates

The political boundary datalayer is a 1:25,000 scale datalayer containing the boundaries of the 351 communities (cities and towns) in Massachusetts. The seaward boundary of coastal communities has been defined at mean high water in this datalayer. Data is in ArcInfo coverage format in the Massachusetts State Plane Coordinate System of 1983 (NAD 83). Map units are in meters.

publication date

None

The New Hampshire Political Boundaries (PB) coverage provides a digital representation of corporate boundaries at the town, county, and state level. It was derived from the 1:24,000-scale USGS Digital Line Graphs (DLGs). Data is in ArcInfo coverage format in the New Hampshire State Plane Coordinate System of 1983 (NAD 83). Map units are in feet.

publication date

Municipal boundaries in New Jersey were gathered from USGS topoquads and other sources in 1987. Since that time, updates to the data have been limited to noting consolidations of boundaries. The scale of the original data varies, relying primarily on 1:24,000 topoquads. Polygon feature data is in ESRI Shapefile format in the State Plane Coordinate System, North American Datum of 1983 (NAD 83), Zone 2900. Map units are in feet.

ground condition

The GIS program for Westchester County, New York provided this data file in response to an inquiry for a 1:24,000-scale town boundary layer for the State of New York. No metadata included with the nysmun.e00 data source. Includes state, county, city, town, and village political boundaries. Data is assumed to be 1:24,000-scale. The SWIS Code identitified polygon features down to the village level. Data is in ArcInfo coverage format in the New York State Plane Coordinate System of 1983 (NAD 83), Zone 4801. Map units are in feet. 

Unknown

State, county, city,and town political boundarie for Rhode Island with name and id coded attributes and city and town name annotation.  Data is in ArcInfo coverage format in the Rhode Island State Plane Coordinate System of 1983 (NAD 83), Zone 5176. Map units are in feet.

publication date

The BNDHASH data layer depicts Vermont villages, towns, counties, Regional Planning Commissions (RPC), State administrative, and LEPC (Local Emergency Planning Committee) boundaries. It is a mosaic of generally 'best available' boundaries from various data sources. Data is in ArcInfo coverage format in the Vermont State Plane Coordinate System of 1983 (NAD 83). Map units are in meters. BNDHASH includes the ArcInfo coverage region subclasses. The REGION.TOWNS subclass includes Vermont towns and was used as the data source for Vermont.

publication date

NORTHEASTM is a 1:24,000-scale, polygon and line feature-based layer that includes state, county, town (municipal), and some village boundary features for the States of Connecticut, Massachusetts, Maine, New Hampshire, New Jersey, New York, Rhode Island, and Vermont. Line features include state, county, town (municipal), and village  boundaries (primarily for New York). Polygon features are intended to depict the geographic areas for individual towns (municipalities) so that they can be aggregated up and combined to form county and state polygon features in derived data sets. Data is in ArcInfo coverage format in the Connecticut State Plane Coordinate System of 1983 (NAD 83). Map units are in feet. This information does not depict official state, county and town boundaries established by the respective state and municipal governments.

publication date

NORTHEASTSTAT is a 1:24,000-scale, polygon and line feature-based layer that includes state boundary features for the States of Connecticut, Massachusetts, Maine, New Hampshire, New Jersey, New York, Rhode Island, and Vermont. Line features include state boundaries. Polygon features are intended to depict the geographic areas and state boundaries for display as background information on a map or in an interactive mapping application. Data is in ArcInfo coverage format in the Connecticut State Plane Coordinate System of 1983 (NAD 83). Map units are in feet. This information does not depict official state boundaries established by the respective state governments.

publication date

Northeast_State_Poly.shp is a 1:24,000-scale polygon feature-based layer that includes state boundary information for the States of Connecticut, Massachusetts, Maine, New Hampshire, New Jersey, New York, Rhode Island, and Vermont. Polygon features are intended to depict the geographic areas for individual states. Northeast_State_Poly.shp is in Shapefile format.

publication date

Northeast_State_Poly is a 1:24,000-scale polygon feature-based layer that includes state boundary information for the States of Connecticut, Massachusetts, Maine, New Hampshire, New Jersey, New York, Rhode Island, and Vermont. Polygon features are intended to depict the geographic areas for individual states. Northeast_State_Poly is in GeoDatabase Feature Class format.

publication date

Create NORTHEASTM (Northeast United States Political Boundary Master) - The following steps describe how an ArcInfo Coverage named NORTHEASTM was created using data sources from the states of Connecticut, Maine, Massachusetts, New York, New Jersey, Rhode Island and Vermont. All data sources were downloaded directly from State GIS Web sites with the exception of data for the State of New York, which was provide by the GIS Program for Westchester County, New York. Each data source included town (municipal or township) boundary line features compiled at 1:24,000 scale (1 inch = 2,000 feet) with the exception of data from Massachusetts, which was compiled at 1:25,000 scale. Enclosing town polygon features along the shoreline, coastline features were connected to town boundary line features in each state data source.

1.  Convert Data Sources to Connecticut State Coordinate System - All data sources were converted to ArcInfo Coverage format, if necessary. Each state data source was subsequently projected to the Connecticut State Plane Coordinate System, North American Datum of 1983 (NAD 83), with map units set to feet. Following the projection, polygon and line ArcInfo Coverage feature topology was created for each state data source using the ArcInfo BUILD command. When necessary to successfully complete the ArcInfo Coverage BUILD process, the ArcInfo CLEAN command was used with DANGLE and FUZZY tolerances of 10 and 4 feet, respectively.

2. Edit Geometry of State Data Source Line Features - Line features from each state data source were copied to a separate ArcInfo Coverage for each state. Line feature geometry in each line feature state data source was visually inspected and political boundary line features extending into the waters of the Atlantic Ocean, Long Island Sound, and Gulf of Maine were deleted. Coastline features that enclosed towns along the coast and offshore islands were retained. The compiler observed inconsistencies between the individual state data sources relative to the inclusion of small coastal islands and the extent to which the coastline was defined by the (upstream) shorelines of small double line streams that flow into coastal waters. Some states included all islands along the coast or incorporated a hydrography-based shoreline that continued further upstream than in other states. These unique characteristics were preserved in each state data source with the exception of portions of the New York and Rhode Island shoreline data adjacent to Connecticut that were replaced with more accurate and complete line feature geometry from Connecticut. Otherwise, the compiler did not re-digitize or redefine coastline or island shoreline features in order to add all missing island features or apply a consistent shoreline definition across all states, for example. Each line feature data source was further visually inspected and, where necessary, feature overshoots, undershoots, and duplicates were corrected in order to ensure that all line features would properly connect to form town polygon feature boundaries in a step 8.  These polygons would form land-based town areas and islands along the coast that are parts to these towns.

3. Edit Attributes of State Data Source Line Features - An attribute named  DATA_SRC was added (and populated with values of  "CT", "ME", "MA", "NJ", "NY", "RI", and "VT") to all features in each line feature state data source in order to retain the source of the geometry of each line feature once all state data sources combined in step 8. All other line feature attributes were deleted in each state data source. Once all state data sources are combined in step 8, a consistent attribution of state, county and town boundaries is later established in step 9.

4. Edit Geometry of State Data Source Label Points - Polygon label point features from each state data source were copied to a separate ArcInfo Coverage for each state. In each label point state data source, the location of label points was visually compared to the line features in the corresponding line feature state data source produced in step 2. Any label point that was not located inside a set of enclosing line features (to be used to form town polygon features) was deleted. These label points will be used to attribute the polygon features in step 8. In general, label points were deleted from the Connecticut and Maine data sources where political boundary line features extending into coastal waters were deleted in step 2. These label points were removed because they described areas of water associated with individual towns along the coast. Label points inside the shorelines of coastal islands were retained. Other visual checks were performed to ensure that only one label point was located within each set of enclosing line features, including islands along the coast. Each label point included town and county information as attributed by the individual state.

5. Edit Attributes of State Data Source Label Points - An attribute named  STATE_COD was added (and populated with values of  "CT", "ME", "MA", "NJ", "NY", "RI", and "VT") to each label point state data source in order to distinguish between States once all state data sources are combined in step 8. All label point state data sources included attributes corresponding to town (or village) numbers and town names. The compiler considered attributing the town polygon features using the FIPS55 codes available at http://geonames.usgs.gov/fips55.html, but FIPS55 code values could not be easily matched to the town numbers and names in all of the state data sources so this idea was dropped. Consequently, the compiler established an alternative approach to encoding town and county designations by mapping (transferring) original attribute values included with individual state data sources to a set common data fields. The compiler added the following common fields to each label point state data source: CNTY_FIELD, CNTY_COD, CNTY_NAME, TOWN_FIELD, TOWN_COD, and TOWN_NAME. These attributes record the field names and values used by the different states for attributing counties and towns. They establish a cross reference back to the attribution in the original data sources. For example, The TOWN_FIELD stores the name of the field used by the state to encode a town, municipality or township number. So for Connecticut, Maine, Massachusetts, New Jersey, New York, New Hampshire, and Vermont, this field is populated with the following strings: "TOWN_NO", "GEOCODENUM", "TOWN-ID", "FIPS", "KEY", "SWIS", "OSP", and "FIPS6". The TOWN_COD field was subsequently populated with the numeric values stored in these fields. And the TOWN_NAME attribute was populated from text values stored in the field used by the state to encode a town, municipality or township name. For example, the attributes for the label point for the town of Andover, Connecticut are STATE_COD="CT", TOWN_FIELD="TOWN_NO", TOWN_COD=1, and TOWN_NAME="Andover"; attributes for the town of Ansonia, Connecticut are STATE_COD="CT", TOWN_FIELD="TOWN_NO", TOWN_COD=2, and TOWN_NAME="Ansonia"; attributes for the town of Abington, Massachusetts are STATE_COD="MA", TOWN_FIELD="TOWN-ID", TOWN_COD=1, and TOWN_NAME="Abington"; attributes for the town of Barrington, Rhode Island are STATE_COD="RI", TOWN_FIELD="OSP", TOWN_COD=1, and TOWN_NAME="Barrington"; and so on. CNTY_FIELD, CNTY_COD, and CNTY_NAME attributes were similarly populated. The VILLAGE attribute was added to preserve the names of villages and borough features included with data from New York. Once these state, county and town attribute values were transferred to the set of common fields, all other attributes in each label point state data source were deleted, resulting in an identical attribute schema for all label point state data sources.

6. Append Line Feature State Data Sources - Depending on the individual state, town boundary feature geometry was either based on 1:24,000-Scale Digital Line Graphs (DLG) and Quadrangle Map files from the USGS or digitized by states from either stable-base Mylar or unstable paper copies of USGS 1:24,000-scale (or 1:25,000-scale) Topographic Quadrangle maps. Consequently, line feature spatial accuracy varies from state to state and does always closely match along state boundaries. In order to append line feature data from seven states together, it was necessary to establish rules for determining which state boundary to use. First, all data would be matched to Connecticut for two reasons - (1) it is based on 1:24,000-scale DLG data from the USGS, the best digital data source for 1:24,000-scale political boundaries, and (2) Connecticut DEP desired a regional data that with boundary information for Connecticut that was consistent with information currently in use. It was also decided that the state boundary line geometry between all other state boundaries was to be based on a complete set of line features from the most accurate state data source. The state boundaries to preserve (i.e. match or snap to) were decided upon after reviewing the data source metadata and visually comparing state data source line feature geometry along state boundaries and choosing the more accurate line work. Beginning with a copy of  the data from Connecticut, individual line feature data state data sources were appended (loaded) one at time and matched to the adjacent state according to the following feature matching rules - Massachusetts was matched to Connecticut, Massachusetts was matched to Rhode Island, Massachusetts was matched to New Hampshire, Massachusetts was matched to New York, New Hampshire was matched to Maine, New York was matched to Connecticut, New York was matched to New Jersey, Rhode Island was matched to Connecticut, Vermont was matched to Massachusetts, Vermont was matched to New York, and Vermont was matched to New Hampshire. For example, when Massachusetts was matched to Connecticut, all line features from the Connecticut data source were preserved, line features from the Massachusetts data source defining the CT-MA state boundary were deleted, and all (dangling and overshooting) municipal boundary line features from the Massachusetts data source extending towards Connecticut were connected to CT-MA state boundary line features from the Connecticut data source. Note, symbolizing line features on the DATA_SRC attribute visually depicts the results of matching the seven state data sources together. Once all line feature state data sources were loaded into a single ArcInfo Coverage, they were ready to form town polygon feature boundaries for the entire region in step 8.

7. Append Label Point Feature State Data Sources - All label point state data sources were appended into a single ArcInfo, ready to be used for attributing town polygon features for the entire region in step 8.

8. Combine Data Source Line and Label Point Features - Line features and label points in the two ArcInfo Coverages created in steps 6 and 7 were combined into a third ArcInfo Coverage. ArcInfo Coverage polygon and line feature topology was established using the ArcInfo CLEAN command with DANGLE and FUZZY tolerances of 10 and 4 feet, respectively. This process generated polygon features from the line features and attributed each polygon with information from the (one) label point feature located inside each polygon. For cartographic purposes, an additional attribute named LAND_CLASS was added to polygon features and populated with values of either "Land" or "Water" to distinguish between areas of land and water both on and offshore. Note, some state data sources included a few miscellaneous polygon features representing lakes, ponds, bays and coves. An additional polygon feature was manually added (digitized) to depict a large area of water off the coast of Connecticut, Maine, Massachusetts, New Jersey, New York, and Rhode Island. For map labeling purposes, an attribute named LABEL_FLAG was added to polygon features to flag town polygon features considered large and significant enough in size to be labeled on a map with town names. Polygons designated for labeling were assigned LABEL_FLAG values equal to "True", whereas small island polygons along coast, not typically labeled with town names, were assigned LABEL_FLAG values equal to "False".

9. Attribute Line Features -  For cartographic purposes, a line feature attribute named BOUNDARY was added and attributed with values of "State", "County", "Town", "Village", "Shoreline" and "Closure Line" using a combination of polygon and line feature topology relationships and manual editing techniques to populate the field. State, and County boundaries were programmatically identified and attributed by comparing the ArcInfo Coverage topological relationships of adjacent polygon attributes. For example, a single line feature between (on the left and right side of the line of) two town poygon features in different states is encoded as a state boundary line feature. A line feature that is not a state boundary line feature between two town polygon features in different counties is encoded as a county boundary feature, and so on.

Create NORTHEASTSTAT (Northeastern United States State Boundary - The automated process for creating (deriving) the Northeastern United States State Boundary layer from the Northeastern United States Political Boundary Master layer is documented in an Arc Macro Language (AML) script named MAKENORTHEASTCOVER.AML for the political and administrative boundary category of data for the State of Connecticut, Department of Environmental Protection. The MAKENORTHEASTCOVER.AML creates the Northeastern United States State Boundary layer by extracting and processing the necessary features from the Northeastern United States Political Boundary Master layer. The following describes the steps undertake by the automated process to create the NORTHEASTSTAT ArcInfo Coverage. First, the following polygon attributes were deleted from a copy of the NORTHEASTM ArcInfo Coverage so that all remaining attributes only described state-level information: CNTY_FIELD, CNTY_COD, CNTY_NAME, TOWN_FIELD, TOWN_COD, TOWN_NAME, VILLAGE, and UNIQUEID. Second, polygon and line features were merged (dissolved and unsplit) based on similar attribute values using the ArcInfo Dissolve command with the NET option (argument). As a result, previously adjacent (town) polygons were combined to form larger state polygon features. Third, the following polygon feature attributes were added and populated with values for classifying, highlighting and differentiating polygon features in one state differently from all other states: CT_LEGEND, MA_LEGEND, ME_LEGEND, NH_LEGEND, NJ_LEGEND NY_LEGEND, RI_LEGEND, and VT_LEGEND. These attributes were added for cartographic purposes. Fourth, the STATE_NAME field, which stores state names, was added and populated to complement the STATE_COD attribute. Fifth, added the CT_LABEL_Y and CT_LABEL_N polygon attributes in order to easily label Connecticut or all states but Connecticut without using the LABEL_FLAG field to query for the appropriate features to label with MAP_LABEL attribute values, which is a slower technique. The name of the resulting ArcInfo Coverage created by this automated process is NORTHEASTAT.

Export to Shapefile format - Converted polygon feature data from an ArcInfo coverage named NORTEASTSTAT to a Shapefile named Northeast_State_Poly.shp. Excluded the AREA, PERIMETER, NORTHEASTSTAT#, NORTHEASTSTAT-ID attributes from the Shapefile because their values are only maintained by ArcInfo software with spatial data that is ArcInfo coverage format. Includes all polygon features from the NORTHEASTSTAT ArcInfo Coverage.

Convert to GeoDatabase Feature Class format - Defined new Feature Class named Northeast_State_Poly; and imported the attribute definitions, loaded features and imported metadata from Northeast_State_Poly.shp shapefile. 

Spatial Reference Properties for Feature Class:

Coordinate System: NAD_1983_StatePlane_Connecticut_FIPS_0600_Feet
XY Domain MinX: -1337538.17925; MaxX: 2957429.11075
XY Domain MinY: -772494.257375; MaxY: 3522473.032625
Precision: 500