This layer is a component of Fairfield Parcel Geometry Service.

© Town of Fairfield

This layer is a component of Fairfield Inland Wetlands Layers.

© Town of Fairfield

Download .zipThis theme shows detailed watersheds for Fairfield County, as digitized in vector mode from mylar copies of maps maintained by the U.S. Geological Survey, Water Resources Division.

Original coverage data was converted from the .e00 file to a more standard ESRI shapefile(s) in November 2014.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Download .zipThese data were derived from multiple sources, one of which was the USGS DLG data which was captured at 1:24,000-scale. The accuracy for DLG data is ± 40 feet. Although the USGS does not claim legal responsibility for the accuracy of these data.These files were obtained from the GIS Support Center, Ohio Department of Administrative Services and were originally prepared by the Ohio State University Center for Mapping in cooperation with the United States Geological Survey with additional funding from several state agencies and other groups. These files were augmented in a few instances with hand digitizing where small missing line segments were found. Originally the Lake Erie shoreline and islands in Lake Erie were added from the Hydrography layer (hy). At the time, the quadrangles used varied over a wide rangle of years this line does not represent a particular water level and is for illustrative purposes only. For example there is a wide offset between the shoreline on the Metzger Marsh Quadrangle and that of the Oak Harbor Quadrangle. This distance is so large that no attempt was made to edgematch the two quadrangles. The line connecting the two shorelines represents the quadrangle boundary. For the purposes of this map Sandusky Bay and Muddy Creek Bay were included as a part of Lake Erie. The Lake Erie shoreline is not meant to represent any Lake Erie shoreline which may be used for regulatory puposes. This has since been modified to be more accurate and inline with the NOAA project that mapped the bathymetry of the Great Lakes. The boundaries were modified to better match these data. An updated boundary for Fairfield-Licking-Perry Counties within Buckeye Lake was included by digitizing the boundary from a more recently updated quadrangle map.

Conversion from the dlg format to ArcInfo was accomplished using ArcInfo software in conjuction with an AML program to adjust the quadrangles so that their corners fall on the exact coordinates of the quadrangle corners. Due to the way in wihich coordinates are stored in the dlg's there is some variation in the quadrangle corner coordinates.

Since 200; additional edits to these data were made in 2002 by ODNR staff through the creation of the Public Lands Survey digitization project.

Further edits were made in 2012 in conjunction with a BLM project to establish cadastral standards.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesOffice of Information TechnologyGIS Records2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

This feature service is available through CT ECO, a partnership between UConn CLEAR and CT DEEP. It is also available as a map service and a tiled map service. This dataset is a statewide service of municipal parcels (properties) including their geometry (polygon shape) and attributes (tabular information about each parcel). In order to preserve the attributes, each municipality is added individually to the service.

This feature service is available through CT ECO, a partnership between UConn CLEAR and CT DEEP. It is also available as a map service and a tiled map service. This dataset is a statewide service of municipal parcels (properties) including their geometry (polygon shape) and attributes (tabular information about each parcel). In order to preserve the attributes, each municipality is added individually to the service.

Polygon feature of Significant Flood Hazard Area (SFHA) within Fairfield County. All fields were kept from the original National Flood Hazard Layer which this layer was derived from. Descriptions of the flood risk zones that fall within the SFHA can be found here.

This layer is a component of Fairfield Easements.

Fairfield Easements

See full Data Guide here. 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.

The Connecticut Department of Environmental Protection's (CTDEP) Permanently Protected Open Space Phase Mapping Project Phase 1 (Protected Open Space Phase1) layer includes permanently protected open space parcels in towns in Phase 1 that meet the CTDEP's definition for this project, the Permanently Protected Open Space Mapping (CT POSM) Project. The CTDEP defines permanently protected open space 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 recreations, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities.

Towns in Phase 1 of the CT POSM project are situated along the CT coast and portions of the Thames River and are the following: Branford, Bridgeport, Chester, Clinton, Darien, Deep River, East Haven, East Lyme, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Lyme, Madison, Milford, Montville, New Haven, New London, North Branford, North Haven, Norwalk, Norwich, Old Lyme, Old Saybrook, Orange, Preston, Shelton, Stamford, Stonington, Stratford, Waterford, West Haven, Westbrook, Westport.

For the purposes of the project a number of categories or classifications of open space have also been created. These include: Land Trust, Land Trust with buidlings, Private, Private with buildings, Utility Company, Utility Company with buildings, Federal, State, Municipal, Municipal with buildings, Conservation easement, and non-DEP State land. The layer is based on information from various sources collected and compiled during the period from August 2002 trhough October 2003. These sources include municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions on the date of research at each city or town hall.

The Protected Open Space Phase1 layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town's Assessor lot numbering system, and system-defined (automatically generated) fields. In addition, the Protected_Open_Space_Phase1 layer has an accompanying table containing more detailed information about each parcel's collection, standardization and storage. This table is called Protected Open Space Phase1 Data and can be joined to Protected Open Space Phase1 in ArcMap using the parcel ID (PAR_ID) field. Detailed information 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 project-specific parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, acreage collected during site reconaissance and the data source. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygon feature type that represent the best available locational information, i.e. "best fit" to the land base available for each.

Phase 1 of the Protected Open Space Mapping (POSM) Project was accomplished by a contractor using only a querying process to identify open space. The contractor obtained assessor's data from the various towns and created programs to cull open space parcels strictly by query processes. We have found many errors and omissions in the data, but at this point in the project we cannot revisit all the coastal towns. Therefore, this data is being sent with a disclaimer for accuracy. You are welcome to use it but not to publish it. Please note that we do not include any water company parcels despite them being listed as part of our criteria because we must first obtain written clarification and clearance from the U.S. Department of Homeland Security.

We have since changed our data collection method for Phase 2 of this project. DEP staff now visit each town hall and thoroughly research the land records. The project is expected to be complete by 2010.

Download .zipGround Water Resources for Fairfield County. This coverage was digitized in a vector mode from a county map at a scale of 1:63360, utilizing ARC/INFO software. It gives an estimate of sustainable yield available from the aquifers in the area.

Original coverage data was converted from the .e00 file to a more standard ESRI shapefile(s) in November 2014.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Download .zipA potentiometric surface map is a contour map that represents the top of the ground water surface in an aquifer. The contour lines illustrate the potentiometric surface much as the contour lines of a topographic map represent a visual model of the ground surface. A potentiometric surface map is very similar to a water table map in that both show the horizontal direction and gradient of ground water flow.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Geological Survey2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6693Email: gis.support@dnr.ohio.gov

This data was created through the modification of an existing sewer service dataset from the CT Office of Policy and Management (OPM), in addition to sewer data from the Southeastern Connecticut Council Of Government (SCCOG) and the Town of Stonington. It also includes data from the Sewer Service Area 2018 file in areas where the OPM dataset was not as current. The OPM data was modified by reducing the extensive categories which represent all areas containing sewers to a "Connected" classification.SCCOG Data: Data was clipped to individual municipal boundaries for all 21 municipalities with sewer information within the SCCOG. The "Existing" category from attribute table was extracted via selection to create the "Connected" areas for 19/21 municipalities. The Town of Stonington data was merged with the SCCOG data as both had areas which were not included in the other. The North Stonington data was combined with SSA 2018 data to get the most accurate representation for that town. OPM Data: Data was modified to isolate the undefined and fragmented categories, (QA- using municipal websites, PDF maps and local contacts for verification where available) then Clipped to municipal boundaries. All the areas that are connected to sewers were Dissolved, only maintaining the key fields listed and described below. The datasets were combined using the Merge tool to get all the connected sewer service areas in the state.Description of Fields:TOWN- Represents all the municipalities with the state of CTs boundaries. CNTY_NAME- Represents the eight (8) county names to which each municipality belongs to.

SEWERS- This field has two classes "Existing" and "No Sewer" and this identifies if a municipality has sewers existing within its boundary or not. SEWER-STATUS- The Sewer Status field represents the areas within in each municipality that are "Connected" to sewers.TREATMENTFACILITY- This field represents the sewer service treatment facility (endpoint) that processes the waste for each municipality. For municipalities without sewers, “Not Applicable” is the designated value. PASSTHROUGH- This field identifies if the wastewater passes through other municipalities on the way to the treatment facility (endpoint) as denoted by a "Yes" or "No" value. Feature class is symbolized on the Sewer Status field to show the “Connected” (green). DEEP welcomes the opportunity to receive any feedback that can help improve the quality of the information presented in this map by contacting Carlos Esguerra (carlos.esguerra@ct.gov).

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

This layer is a component of Stratford Parcel Geometry Service.

This feature layer is a general representation of detachments from the City of Columbus. It is not a legal record. This feature layer is updated throughout the annexations and detachment submission and approval process. Annexations and detachments to the City of Columbus are adopted by legislation approved by City Council and take effect upon recording within the appropriate County Recorder’s Office. This feature layer is a digitized representation of the process for annexation and detachment and is mapped based upon underlying parcel geography from the three County Auditor’s (Franklin, Fairfield, and Delaware) GIS parcel feature layers in which the City of Columbus currently resides.The City of Columbus makes no guarantee as to the accuracy of this mapping. It is provided as a general reference tool. User’s are advised to consult legal annexation records available within the various County Recorder’s Offices when attempting to determine the precise boundaries for the City of Columbus. Users are advised not to use this feature layer if they are unwilling to accept the conditions stated herein.Questions regarding this feature layer should be directed to the City of Columbus, Department of Public Service, Division of Infrastructure Management’s Map Room at OneStopPlans@columbus.gov.

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.

Source Darien (2009), Tighe and Bond 2008: Ridgefield (2008), New Fairfield (2009)Sewell Sherman (2009)Parcel Data Suspected is from DEEP Parcel Data (2011): Wilton, Bethel, New Fairfield, Brookfield, Bridgewater. Deep Description Below.Connecticut Parcels includes parcel information for selected towns in Connecticut where parcel data was available in digital format at the time the data was acquired from the town or other state agency data sources. Data is neither comlete nor current. Boundaries are not based on survey information. This parcel layer includes information provided by individual municipalities. These parcel data are incomplete and out of date. The accuracy, currency and completeness of the data reflect the content of the data at the time DEEP acquired the data from the individual municipalities. Attribute information is comprised of values such as town name and map lot block number. These data are not updated by CT DEEP and should only be used as a general reference. Critical decisions involving parcel-level information should be based on more recently acquired information from the respective municipalities. These parcels are not to be considered legal boundaries such as boundaries determined from certain classified survey maps or deed descriptions. Parcel boundaries shown in this layer are based on information from municipalities used for property tax purposes. Largely due to differences in horizontal accuracy among various data layers,these parcel boundaries wll not line up exactly with or be properly postioned relative to features shown on other layers available from CT DEEP such as scanned USGS topography quadrangle maps, roads, hydrography, town boundaries, and even orthophotograpy.A 2017 set of parcel data was collected from TeleAtlas for the following towns: Greenwich, Stamford, Norwalk, Westport, New Canaan, Redding, Danbury, Newtown, New MilfordWeston had its own 2017 update from NEGEOModifications to data: Data was edited to standardize it among multiple sources. Building units, water bodies, slivers, and right of way have been removed. Parcels which had no identifer but looked like parcels were provided a code 'UNK' + ID2Data Limitations: The data is not consistent from original sources, and time acquired. There are different formats in the database from the original sources and geometry is not consistent on the borders.

This feature layer is a general representation of the current corporate boundary for the City of Columbus. It is not a legal record. This feature layer is updated upon the effective date off all new annexations to, and detachments from, the City of Columbus. Annexations and detachments to the City of Columbus are adopted by legislation approved by City Council and take effect upon recording within the appropriate County Recorder’s Office. This feature layer is a digitized representation of the process for annexation and detachment and is mapped based upon underlying parcel geography from the three County Auditor’s (Franklin, Fairfield, and Delaware) GIS parcel feature layers in which the City of Columbus currently resides. The City of Columbus makes no guarantee as to the accuracy of this mapping. It is provided as a general reference tool. User’s are advised to consult legal annexation records available within the various County Recorder’s Offices when attempting to determine the precise boundaries for the City of Columbus. Users are advised not to use this feature layer if they are unwilling to accept the conditions stated herein. Questions regarding this feature layer should be directed to the City of Columbus, Department of Public Service, Division of Infrastructure Management’s Map Room at OneStopPlans@columbus.gov.