An ArcGIS Web AppBuilder application used to view lead service lines.

A map used in the Lead Service Line Viewer application to view the utility and customer side of lead service lines.

View for hub

2017 .pdf of Sierra Vista Westbrook Neighborhood Association.

A feature layer view with view only capabilities.

Sign Posts Locations For the City of Westbrook. This feature service has full create, delete, query, update, and sync functionality.

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

This is a view

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

Eelgrass Beds 2009 Set:

This data layer was created by the Conservation Management Institute, Virginia Tech University for the USFWS National Wetlands Inventory, Region 5. The project area encompasses the eastern end of Long Island Sound, including Fishers Island and the North Fork of Long Island. It includes all coastal embayments and nearshore waters (i.e., to a depth of -15 feet at mean low water) bordering the Sound from Clinton Harbor in the west to the Rhode Island border in the east and including Fishers Island and the North Shore of Long Island from Southold to Orient Point and Plum Island. The study area includes the tidal zone of 18 sub-basins in Connecticut: Little Narragansett Bay, Stonington Harbor, Quiambog Cove, Mystic Harbor, Palmer-West Cove, Mumford Cove, Paquonock River, New London Harbor, Goshen Cove, Jordan Cove, Niantic Bay, Rocky Neck State Park, Old Lyme Shores, Connecticut River, Willard Bay, Westbrook Harbor, Duck Island Roads, and Clinton Harbor, and two areas in New York: Fishers Island and a portion of the North Shore of Long Island. Delineations of 2009 eelgrass beds were completed using 1:20,000 true color aerial photography flown at low tide on 7/14/2009 and 7/15/2009. Extensive field work was conducted by the USFWS Region 5 Southern New England-New York Bight Coastal Program Office in October, November, and December 2009 with 193 field sites checked. The 2009 photography was scanned and geo-rectified using 2006 NAIP 1 meter true color imagery. Data have been summarized in a technical report: Tiner, R., K. McGuckin, M. Fields, N. Fuhrman, T. Halavik, and A. MacLachlan. 2010. 2009 Eelgrass Survey for Eastern Long Island Sound, Connecticut and New York. U.S. Fish and Wildlife Service, National Wetlands Inventory Program, Northeast Region, Hadley, MA. National Wetlands Inventory report. 16 pp. plus Appendix.

This data layer was created by the Conservation Management Institute, Virginia Tech University for the USFWS National Wetlands Inventory, Region 5. The project area encompasses the eastern end of Long Island Sound, including Fishers Island and the North Fork of Long Island. It includes all coastal embayments and nearshore waters (i.e., to a depth of -15 feet at mean low water) bordering the Sound from Clinton Harbor in the west to the Rhode Island border in the east and including Fishers Island and the North Shore of Long Island from Southold to Orient Point and Plum Island. The study area includes the tidal zone of 18 sub-basins in Connecticut: Little Narragansett Bay, Stonington Harbor, Quiambog Cove, Mystic Harbor, Palmer-West Cove, Mumford Cove, Paquonock River, New London Harbor, Goshen Cove, Jordan Cove, Niantic Bay, Rocky Neck State Park, Old Lyme Shores, Connecticut River, Willard Bay, Westbrook Harbor, Duck Island Roads, and Clinton Harbor, and two areas in New York: Fishers Island and a portion of the North Shore of Long Island. Delineations of 2009 eelgrass beds were completed using 1:20,000 true color aerial photography flown at low tide on 7/14/2009 and 7/15/2009. Extensive field work was conducted by the USFWS Region 5 Southern New England-New York Bight Coastal Program Office in October, November, and December 2009 with 193 field sites checked. The 2009 photography was scanned and geo-rectified using 2006 NAIP 1 meter true color imagery.

A layer showing GPCOG's 26 member communities: Bridgton, Cape Elizabeth, Casco, Chebeague Island, Cumberland, Cumberland County, Durham, Falmouth, Freeport, Frye Island, Gorham, Gray, Harrison, Long Island, Naples, New Gloucester, North Yarmouth, Portland, Pownal, Raymond, Scarborough, Sebago, South Portland, Standish, Westbrook, Windham, Yarmouth.

I am pleased to share the updated context map DRAFT for your review and comments.Of course, review to note any obvious omissions or anomalies in the map. Also, please share your general thoughts on the look and feel of the map. The way we have it right now with the basemap labeled “Light Gray Canvas”, the building footprints show up as you zoom in. I find that very helpful to visually confirm the context.There are actually have many different criteria that can lead to classification. This detail was necessary to refine the map. You can check on and off the different criteria on the left to see how it impacts the map if you would like.There are many different considerations, but mostly context is defined by the development of buildings - how close the buildings are to the road, how densely they have been built together, and how large the building area is. Urban and Rural Village contexts tend to have more buildings close to the road and suburban contexts tend to have buildings further back. Here is the primary data considered: Immediate Building Density Immediate Building Area Density Immediate Building Count Wide Building Density Wide Building Area Density Wide Intersection Density Wide Segment Density Federal and State Urban Compact AreasThe “immediate” building information considers buildings that partially within 60 feet of the road centerline. For a sports analogy, that is about the distance from a baseball pitching rubber to home plate. The “wide” data looks at buildings, segments, and intersections in the general area 1/8 of a mile from centerline in all directions. That is about the distance of two football fields. Both types of data have value, especially when they are strategically used together.The Map is split into 5 contexts categories: Red - Urban Orange - Suburban Dark Green - Rural Village (Heavily Developed) Light Green - Rural Village (Moderately Developed) Blank – RuralThe red urban and the dark green village areas have exactly the same criteria except one is inside federal or state urban compact and one is outside both urban compacts. You will also notice some of the major arterial roads cutting through urban areas have been identified as suburban. Examples of this include William Clark Drive in Westbrook, Center Street and Minot Avenue in Auburn, and Pleasant Street in Brunswick. This typically occurs because the buildings are mostly built back further from the road.Important to note: We will need two “rural village” layers. We realized we need to separate how we treat the very densely developed villages like downtown Camden and the fringe villages like Searsmont and Jefferson.

Thank you for giving this map a look over and providing your feedback.