Protected Open Space was compiled as a result of the Protected Open Space Mapping (POSM) Project. This project was a joint venture between the Connecticut Department of Environmental Protection and Applied Geographics, Inc. The intent of this data is to collect protected open space parcels throughout Connecticut. This dataset is not updated. For the most current open space parcel data, contact the appropriate town.
This layer includes polygon features that depict protected open space for towns of the Protected Open Space Mapping (POSM) project, which is administered by the Connecticut Department of Energy and Environmental Protection, Land Acquisition and Management. Only parcels that meet the criteria of protected open space as defined in the POSM project are in this layer. Protected open space is defined as: (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non-facility-based outdoor recreation, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities. Includes protected open space data for the towns of Andover, Ansonia, Ashford, Avon, Beacon Falls, Canaan, Clinton, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bridgewater, Bolton, Brookfield, Brooklyn, Canterbury, Canton, Chaplin, Cheshire, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Goshen, Granby, Griswold, Groton, Guilford, Haddam, Hampton, Hartford, Hebron, Kent, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Monroe, Montville, Morris, New Britain, New Canaan, New Fairfield, New Milford, New Hartford, Newington, Newtown, Norfolk, North, Norwich, Preston, Ridgefield, Shelton, Stonington, Oxford, Plainfield, Plainville, Pomfret, Portland, Prospect, Putnam, Redding, Rocky Hill, Roxbury, Salem, Salisbury, Scotland, Seymour, Sharon, Sherman, Simsbury, Somers, South Windsor, Southbury, Southington, Sprague, Sterling, Suffield, Thomaston, Thompson, Tolland, Torrington, Union, Vernon, Wallingford, Windham, Warren, Washington, Waterbury, Watertown, West Hartford, Westbrook, Weston, Wethersfield, Willington, Wilton, Windsor, Windsor Locks, Wolcott, Woodbridge, Woodbury, and Woodstock. Additional towns are added to this list as they are completed. The layer is based on information from various sources collected and compiled during the period from March 2005 through the present. These sources include but are not limited to municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions as of the date of research at each city or town hall. The Protected Open Space layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town Assessor's lot numbering system, and system-defined (automatically generated) fields. The Protected Open Space layer has an accompanying table containing more detailed information about each feature (parcel). This table is called Protected Open Space Dat, and can be joined to Protected Open Space in ArcMap using the parcel ID (PAR_ID) field. Detailed information in the Protected Open Space Data attribute table includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the unique parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, and acreage. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygons that represent the best available locational information, and are "best fit" to the land base available for each.
Use this layer to show protected open space as defined in the Protected Open Space Mapping project. Join this layer to the Protected Open Space Data table using the PAR_ID attribute. Then use the attribute data to, for example, display open space parcels by open space type or official name, compare current open space (as of the date of town hall data collection) to older open space data sources, or analyze the ratio of open space to developed or developable land in a particular Phase 2 town or region. Use this layer with base map data such as hydrography, orthophotography, streets, and topographic quadrangles. It can also be used with other related layers such as land use, DEP property, geologic features, soils, etc.
A related attribute data table known as Protected_Open_Space_Dat should be used in conjunction with this data layer.
79 Elm Street
publication date
None. The data is in the public domain and may be redistributed.
No restrictions or legal prerequisites for using the data. The data is suitable for use at appropriate scale, and is not intended for maps printed at scales greater or more detailed than 1:12,000 scale (1 inch = 1,000 feet). Although this data set has been created by the State of Connecticut, Department of Energy and Environmental Protection, no warranty, expressed or implied, is made by the State of Connecticut, Department of Energy and Environmental Protection as to the accuracy of the data and or related materials. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the State of Connecticut, Department of Energy and Environmental Protection in the use of these data or related materials. The user assumes the entire risk related to the use of these data. Once the data is distributed to the user, modifications made to the data by the user should be noted in the metadata. When printing this data on a map or using it in a software application, analysis, or report, please acknowledge the State of Connecticut, Department of Energy and Environmental Protection as the source for this information.
| Boundary | Coordinate |
|---|---|
| Left | 730512.187000 (survey feet) |
| Right | 1263058.250000 (survey feet) |
| Top | 944279.125000 (survey feet) |
| Bottom | 556642.875000 (survey feet) |
| Boundary | Coordinate |
|---|---|
| West | -73.742172 (longitude) |
| East | -71.781498 (longitude) |
| North | 42.052612 (latitude) |
| South | 40.984615 (latitude) |
Protected Open Space includes the geometry of the parcels defined as open space in Phase 2 of the CT DEEP Protected Open Space Mapping Project. This layer provides minimal attribute information; however, it has an accompanying table containing more detailed information about each parcel's collection, standardization and storage. This table is called Protected Open Space Data, and can be joined to this layer using the Par_ID field.
Protected open space represented as polygon features.
State of Connecticut, Department of Environmental Protection
Internal feature number
ESRI
Feature geometry
ESRI
Parcel identification number comprised of a three-digit state assigned town ID number and the respective parcel's 1-5 digit Object ID number. This parcel ID field is used to link Protected Open Space with Protected Open Space Data, the attribute table containing detailed feature information.
State of Connecticut, Department of Environmental Protection
The completeness of the data reflects the feature content of the data sources, which include recorded surveys, deeds, and electronic parcel data. The Protected Open Space layer is complete in the sense that it accurately reflects the contents of the source information available at the time the CT DEEP created the layer. However, compared to current conditions, the layer may not be complete. This data is not updated.
Protected Open Space retains only a basic few attributes necessary to define each feature. The primary attribute is the parcel identification number (PAR_ID) that can be used to join this layer to the Protected Open Space Data table. That table contains detailed information about each parcel. Other attributes include: ARCS_ADD, which is not applicable to Phase 2 (this phase) of the POSM project, but was saved from Phase 1 to perpetuate consistency; and NOTES, which contains any comments regarding automation of the parcel data; OBJECTID, SHAPE, SHAPE_Length and SHAPE_Area, all four of which are automatically generated by ArcGIS. Accuracy of the attributes is determined by the quality of the data received from each town and by the processes used to assign a PAR_ID to each feature. All attributes have valid values.
The horizontal positional accuracy of this data varies town by town, based on the source of the data, the method used and the accuracy of the original source. The majority of the parcels in this layer were acquired from each town and the accuracy of the geometry and attribute data is unknown. Some features are accurately positioned because they were automated using coordinate geometry and coordinate information was available on the source surveys. Other features may be inaccurately positioned because a "best fit" methodology or georeferencing were used.
There is no vertical component to this data layer.
Digital parcel data was obtained from municipalities that had pre-existing electronic GIS parcel data at the time of data collection. Parcel data format varies by municipality, but was provided in either shapefile, geodatabase, coverage or CAD format and converted into the standard project geodatabase.
publication date
This source include CAMA (Compter Aided Mass Appraisal) data, or other assessment data created by the town. It is used to provide attribute data for each parcel in Source 1, Digital Parcel Data. It can be joined to the digital data via the unique PAR_ID attribute.
publication date
Municipal maps from the assessor, town clerk, or other municipal offices were used to verify digital data already collected or to digitize those towns where digital data was not provided.
publication date
Assessor data in paper format when electronic CAMA data was not available.
publication date
Preliminary geodatabase prior to qa/qc procedures being performed.
publication date
Final product.
Digital data was acquired from each municipality, a geodatabase was created, and a parcel id assigned to each polygon. The accompanying attribute data, either CAMA (Computer Aided Mass Appraisal) data or other town assessment data, was incorporated into the geodatabase model by populating the data model fields with relevant data from the municipality. This step was performed by Applied Geographics, Inc., the consultan chosen for this project. The digital data acquired by Applied Geographics, Inc. includes the following 60 towns: Andover, Ansonia, Avon, Bethel, Bloomfield, Bolton, Canton, Colchester, Coventry, Cromwell, Derby, East Grancy, East Hartford, East Haddam, East Windsor, Ellington, Enfield, Farmington, Glastonbury, Granby, Hartford, Hebron, Kent, Killingworth, Kent, Lisbon, Litchfield, Manchester, Mansfield, Marlborough, Meriden, Middletown, Morris, New Canaan, New Hartford, Newington, Newtown, North Stonington, Oxford, Pomfret, Prospect, Rocky Hill, Salem, Seymour, Simsbury, Somers, South Windsor, Southbury, Southington, Suffield, Tolland, Vernon, Watertown, West Hartford, Wethersfield, Wilton, Windsor, Windsor Locks, Woodbridge, and Woodbury.
48 Purnell Place
Digital parcel data was obtained from municipalities that had pre-existing electronic GIS parcel data at the time of data collection. Parcel data format varies by municipality, but was provided in either shapefile, geodatabase, coverage or CAD format and converted into the standard project geodatabase.
publication date
This source include CAMA (Compter Aided Mass Appraisal) data, or other assessment data created by the town. It is used to provide attribute data for each parcel in Source 1, Digital Parcel Data. It can be joined to the digital data via the unique PAR_ID attribute.
publication date
Municipal maps from the assessor, town clerk, or other municipal offices were used to verify digital data already collected or to digitize those towns where digital data was not provided.
publication date
Preliminary geodatabase prior to qa/qc procedures being performed.
publication date
This step is similar to Process Step 1, with the exception that DEP GIS staff collected the digital data, assigned a parcel id and populated relevant attributes into the geodatabase. The towns with digital data acquired by DEP are: Bethany, Bloomfield, Brookfield, Chaplin, Goshen, Griswold, Haddam, Killingly, Lebanon, Monroe, New Milford, Norfolk, Portland, Redding, Scotland, Sharon, Sprague, Sterling, Wallingford, Warren, Willington, and Winchester. This process is currently ongoing.
79 Elm Street
Digital parcel data was obtained from municipalities that had pre-existing electronic GIS parcel data at the time of data collection. Parcel data format varies by municipality, but was provided in either shapefile, geodatabase, coverage or CAD format and converted into the standard project geodatabase.
publication date
This source include CAMA (Compter Aided Mass Appraisal) data, or other assessment data created by the town. It is used to provide attribute data for each parcel in Source 1, Digital Parcel Data. It can be joined to the digital data via the unique PAR_ID attribute.
publication date
Municipal maps from the assessor, town clerk, or other municipal offices were used to verify digital data already collected or to digitize those towns where digital data was not provided.
publication date
Preliminary geodatabase prior to qa/qc procedures being performed.
publication date
In the towns where digital spatial data was not available, paper records and maps were used to enter both attribute data and parcel data into the final geodatabase. Attribute data entry was manually entered. For parcel data entry, the digitizing methods used were COGO (coordinate geometry), scanning and georeferencing, CAD conversion, or screen digitizing, depending on the type of map received. Towns where this process step was applied are Beacon Falls, Bethlehem, and Weston. Additional towns to be added as they are completed.
79 Elm Street
Municipal maps from the assessor, town clerk, or other municipal offices were used to verify digital data already collected or to digitize those towns where digital data was not provided.
publication date
Assessor data in paper format when electronic CAMA data was not available.
publication date
Preliminary geodatabase prior to qa/qc procedures being performed.
publication date
Quality Assurance/Quality Control procedures were performed to verify that the parcel data collected was accurate and valid. A DEP GIS specialist used the following procedures, when applicable: 1. Newly subdivided parcels were checked and verified for future parcel digitizing. 2. Orthophotos were studied to reveal any structures or buildings on each parcel. 3. Parcels collected were compared with DEP owned properties, previous Municipal Open Space data, and known Land Trust holdings. 4. Map/Block/Lot in geodatabase was verified against town records.
79 Elm Street
Preliminary geodatabase prior to qa/qc procedures being performed.
publication date
Final product.
Protected Open Space
Geographic information system (GIS), computer-aided drawing or other mapping software is necessary to display, view and access the information.
79 Elm Street
The data distributor does not provide custom GIS analysis or mapping services. Data is available in a standard format and may be converted to other formats, projections, coordinate systems, or selected for specific geographic regions by the party receiving the data.
79 Elm Street