Statewide Impervious 2012

+ Resource Description

Citation

Information used to reference the data.

Title: Statewide Impervious 2012

Originators: Quantum Spatial Inc., St. Petersburg, FL, Nathaniel Morton, GISP, Geospatial Analytics Team Lead

Publication date: 20170901

Data type: raster and vector digital data

Description

A characterization of the data, including its intended use and limitations.

Abstract:

This is an impervious classification of Connecticut. The thematic information includes three classes in a single feature class: 1-Building, 2-Road and 3-Other. It was based on color infrared aerial imagery with a 1' spatial resolution that was collected between March 18th and 30th, 2012. Impervious features from existing planimetric data sets were updated based on the 2012 imagery through photo interpretation and heads up digitizing through ArcScan. All features greater than 800 square feet in size were included in the data set. The use of ArcScan and the use of the existing planimetric data sets are discussed in the "Lineage/Process Step" section of this metadata report. Upon completion of the entire State of Connecticut the raster images were then vectorized and are supplied at the town level for distribution. The state of Connecticut was collected with the US Census Bureau state boundary, and the town's were clipped using the DEEP TOWN_CLIP.shp. Each town is represented as 1) an .img file and 2) a vectorized feature class within a geodatabase, both consisting of an extent of all of the imagery tiles that contained the town within a 300' buffer, and 3) a vectorized feature class within a geodatabase consisting of the town clipped to the DEEP TOWN_CLIP.shp.

Purpose:

This data set was developed to be used by the Connecticut Department of Energy and Environmental Protection (DEEP) and the UConn Center for Land Use Education and Research (CLEAR) to support planning and decision making for MS4 regulated communities and in other applications where impervious features are concerned.

Dataset credit:

Quantum Spatial Inc.

Point Of Contact

Contact information for the individual or organization that is knowledgeable about the data.

Organization: UConn Center for Land Use Education and Research (CLEAR)

Person: David Dickson

Position: Extension Educator

Phone: (860)345-4511

Email: clear@uconn.edu

Address type: mailing

Address:

PO Box 70 1066 Saybrook Road

City: Haddam

State or Province: CT

Postal code: 06438

Data Type

How the data are represented, formatted and maintained by the data producing organization.

Data type: vector digital data

Native dataset environment: Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.4.0.5524

Time Period of Data

Time period(s) for which the data corresponds to the currentness reference.

Date: 20170901

Currentness reference:

Connecticut

Status

The state of and maintenance information for the data.

Data status: Complete

Update frequency: Unknown

Key Words

Words or phrases that summarize certain aspects of the data.

Theme:

Keywords: Impervious Classification

Keyword thesaurus: Impervious

Place:

Keywords: Connecticut

Keyword thesaurus: None

Data Access Constraints

Restrictions and legal prerequisites for accessing or using the data after access is granted.

Access constraints:

None

Use constraints:

Use with caution at end user's discretion.

Cross Reference

Information about other, related data sets that are likely to be of interest.

Title: Impervious Classification

Originators: unknown

Publication date: 20170901

+ Spatial Reference Information

Horizontal Coordinate System

Reference system from which linear or angular quantities are measured and assigned to the position that a point occupies.

Coordinate System Details

Map projection

Map projection name: NAD 1983 StatePlane Connecticut FIPS 0600 Feet

Standard parallel: 41.2

Standard parallel: 41.86666666666667

Longitude of central meridian: -72.75

Latitude of projection origin: 40.83333333333334

False easting: 999999.999996

False northing: 499999.999998

Planar Coordinate Information

Planar coordinate encoding method: coordinate pair

Coordinate representation:

Abscissa resolution: 0.000000026813284925708565

Ordinate resolution: 0.000000026813284925708565

Planar distance units: foot_us

Geodetic model

Horizontal datum name: D North American 1983

Ellipsoid name: GRS 1980

Semi-major axis: 6378137.0

Denominator of flattening ratio: 298.257222101

Spatial Domain

The geographic areal domain of the data that describes the western, eastern, northern, and southern geographic limits of data coverage.

Bounding Coordinates

In Unprojected coordinates (geographic)

Boundary	Coordinate
West	-72.841484 (longitude)
East	-72.695106 (longitude)
North	41.656680 (latitude)
South	41.546866 (latitude)

+ Data Structure and Attribute Information

Overview

Summary of the information content of the data, including other references to complete descriptions of entity types, attributes, and attribute values for the data.

Direct spatial reference method:

Detailed descriptions of entity type, attributes, and attribute values for the data.

Description:

Impervious for features greater than 800 sq feet in size.

Source:

Hartford

Attributes

OID

Definition:

Internal feature number.

Attribute values: Sequential unique whole numbers that are automatically generated.

Attribute definition source:

Esri

Value

Count

SDTS Feature Description

Description of point and vector spatial objects in the data using the Spatial Data Transfer Standards (SDTS) terminology.

Spatial data transfer standard (SDTS) terms

Feature class

Type: GT-polygon composed of chains

Count: 13489

Raster Information

Type and number of raster spatial objects in the data.

Raster object type: Pixel

Cell information

Number of cells on x-axis: 40001

Number of cells on y-axis: 40001

+ Data Source and Process Information

Process Steps

Information about events, parameters, tolerances and techniques applied to construct or derive the data.

Process step information

Process Step 1

Process description:

Impervious features were extracted through photo interpretation and heads up ArcScan digitizing of 2012 aerial imagery. The entire image was panned at a scale of about 1:1,000 and the impervious was heads up digitized. After impervious features were digitized the classification went through a quality control (QC) process. During this process the entire project extent was reviewed and all misclassified features were identified. These areas were addressed later by photo interpreters. The process steps for editing the imagery tiles within Esri ArcScan are as follows: 
        1. Convert the image back to three separate images (building, road, other).
        2. Convert three images to binary images. 
        3. Load binary images in ArcMap, set Symbology to "Unique Values". 
        4. Start Editing
        5. In ArcScan toolbar, click [Raster Cleanup]-[Start Cleanup] 
        6. In ArcScan toolbar, select raster name which is to be edited. Switch the raster name if needed during editing. 
        7. Use "Raster Painting" toolbar to do editing. 
        8. When finished, save edits. 
        9. Merge three binary images to deliverable.

Process date: 20170901

Process Step 2

Process description:

Below is the list of towns displaying the classes that were previously captured in existing planimetric data sets that were provided by the regional COGs. The existing planimetric data sets were then utilized in this update of impervious features for the State of Connecticut. 
        Andover(1): No data set.  
        Ansonia(2): No data set. 
        Ashford(3): No data set. 
        Avon(4): No data set. 
        Barkhamsted(5): No data set. 
        BeaconFalls(6): Partial data set of 2-Road. 
        Berlin(7): No data set. 
        Bethany(8): No data set. 
        Bethel(9): Full data set of 1-Building, 2-Road, and 3-Other. 
        Bethlehem(10): Partial data set of 1-Building and 2-Road. 
        Bloomfield(11): No data set. 
        Bolton(12): No data set. 
       Bozrah(13): No data set. 
       Branford(14): No data set. 
       Bridgeport(15): Full data set of 1-Building, 2-Road, and 3-other. 
       Bridgewater(16): Full data set of 1-Building, 2-Road, and 3-Other. 
       Bristol(17): No data set. 
       Brookfield(18): Full data set of 1-Building, 2-Road, and 3-Other. 
       Brooklyn(19): No data set. 
       Burlington(20): No data set. 
       Canaan(21): No data set. 
       Canterbury(22): No data set. 
       Canton(23): No data set. 
       Chaplin(24): No data set. 
       Cheshire(25): Partial data set of 1-Building, 2-Road, and 3-Other. 
       Chester(26): No data set. 
       Clinton(27): No data set. 
       Colchester(28): No data set. 
       Colebrook(29): No data set. 
       Columbia(30): Partial data set of 1-Building. 
       Cornwall(31): No data set. 
       Coventry(32): Partial data set of 1-Building. 
       Cromwell(33): No data set. 
       Danbury(34): Full data set of 1-Building, 2-Road, and 3-Other. 
       Darien(35): Full data set of 1-Building, 2-Road, and 3-Other. 
       DeepRiver(36): No data set. 
       Derby(37): No data set. 
       Durham(38): No data set. 
       Eastford(39): No data set. 
       EastGranby(40): No data set. 
       EastHaddam(41): No data set. 
       EastHampton(42): No data set. 
       EastHartford(43): No data set. 
       EastHaven(44): No data set. 
       EastLyme(45): No data set. 
       Easton(46): Full data set of 1-Building, 2-Road, and 3-Other. 
       EastWindsor(47): No data set. 
       Ellington(48): No data set. 
       Enfield(49): No data set. 
       Essex(50): No data set. 
       Fairfield(51): Full data set of 1-Building, 2-Road, and 3-Other. 
       Farmington(52): No data set. 
       Franklin(53): No data set. 
       Glastonbury(54): No data set. 
       Goshen(55): No data set. 
       Granby(56): No data set. 
       Greenwich(57): Full data set of 1-Building, 2-Road, and 3-Other. 
       Griswold(58): No data set. 
       Groton(59): No data set. 
       Guilford(60): No data set. 
       Haddam(61): No data set. 
       Hamden(62): No data set. 
       Hampton(63): No data set. 
       Hartford(64): Full data set of 1–Building, 2–Road, and 3–Other. 
       Hartland(65): No data set. 
       Harwinton(66): No data set. 
       Hebron(67): No data set. 
       Kent(68): No data set. 
       Killingly(69): No data set. 
       Killingworth(70): No data set. 
       Lebanon(71): No data set. 
       Ledyard(72): No data set. 
       Lisbon(73): No data set. 
       Litchfield(74): No data set. 
       Lyme(75): No data set. 
       Madison(76): No data set. 
       Manchester(77): No data set. 
       Mansfield(78): Partial data set of 1-Building. 
       Marlborough(79): No data set. 
       Meriden(80): No data set. 
       Middlebury(81): No data set. 
       Middlefield(82): No data set. 
       Middletown(83): No data set. 
       Milford(84): No data set. 
       Monroe(85): Full data set of 1-Building, 2-Road, and 3-Other. 
       Montville(86): No data set. 
       Morris(87): No data set. 
       Naugatuck(88): Partial data set of 2-Road. 
       NewBritain(89): No data set. 
       NewCanaan(90): Full data set of 1-Building, 2-Road, and 3-Other. 
       NewFairfield(91): Full data set of 1-Building, 2-Road, and 3-Other. 
       NewHartford(92): No data set. 
       NewHaven(93): No data set. 
       Newington(94): No data set 
       NewLondon(95): No data set. 
       NewMilford(96): Full data set of 1-Building, 2-Road, and 3-Other. 
       Newtown(97): Full data set of 1-Building, 2-Road, and 3-Other. 
       Norfolk(98): No data set. 
       NorthBranford(99): No data set. 
       NorthCanaan(100): No data set. 
       NorthHaven(101): No data set. 
       NorthStonington(102): No data set. 
       Norwalk(103): Full data set of 1-Building, 2-Road, and 3-Other. 
       Norwich(104): No data set. 
       OldLyme(105): No data set. 
       OldSaybrook(106): No data set. 
       Orange(107): No data set. 
       Oxford(108): Partial data set of 2-Road. 
       Plainfield(109): No data set. 
       Plainville(110): No data set. 
       Plymouth(111): Partial data set of 2-Road. 
       Pomfret(112): No data set. 
       Portland(113): No data set. 
       Preston(114): No data set. 
       Prospect(115): No data set. 
       Putnam(116): No data set. 
       Redding(117): Full data set of 1-Building, 2-Road, and 3-Other. 
       Ridgefield(118): Full data set of 1-Building, 2-Road, and 3-Other. 
       RockyHill(119): No data set. 
       Roxbury(120): No data set. 
       Salem(121): No data set. 
       Salisbury(122): No data set. 
       Scotland(123): No data set. 
       Seymour(124): No data set. 
       Sharon(125): No data set. 
       Shelton(126): No data set. 
       Sherman(127): Full data set of 1-Building, 2-Road, and 3-Other. 
       Simsbury(128): No data set. 
       Somers(129): No data set. 
       Southbury(130): Full data set of 1-Building, 2-Road, and 3-Other. 
       Southington(131): No data set. 
       SouthWindsor(132): No data set. 
       Sprague(133): No data set. 
       Stafford(134): No data set. 
       Stamford(135): Full data set of 1-Building, 2-Road, and 3-Other. 
       Sterling(136): No data set. 
       Stonington(137): No data set.
       Stratford(138): Full data set of 1-Building, 2-Road, and 3-Other. 
       Suffield(139): No data set. 
       Thomaston(140): Partial data set of 2-Road. 
       Thompson(141): No data set. Tolland(142): No data set. 
       Torrington(143): No data set.
       Trumbull(144): Full data set of 1-Building, 2-Road, and 3-Other. 
       Union(145): No data set. 
       Vernon(146): No data set. 
       Voluntown(147): No data set. 
       Wallingford(148): No data set. 
       Warren(149): No data set. 
       Washington(150): No data set. 
       Waterbury(151): Partial data set of 1–Building and 2-Road. 
       Waterford(152): No data set. 
       Watertown(153): Partial data set of 1–Building and 2-Road. 
       Westbrook(154): No data set. 
       WestHartford(155): No data set. 
       WestHaven(156): No data set. 
       Weston(157): Full data set of 1-Building, 2-Road, and 3-Other. 
       Westport(158): Full data set of 1-Building, 2-Road, and 3-Other. 
       Wethersfield(159): No data set. 
       Willington(160): Partial data set of 1 – Building. 
       Wilton(161): Full data set of 1-Building, 2-Road, and 3-Other. 
       Winchester(162): No data set. 
       Windham(163): No data set. 
       Windsor(164): No data set. 
       WindsorLocks(165): No data set. 
       Wolcott(166): No data set. 
       Woodbridge(167): No data set. 
       Woodbury(168): Partial data set of 1–Building, 2–Road, and 3-Other. 
       Woodstock(169): No data set.

Process date: 20170901

+ Metadata Reference

Metadata Date

Dates associated with creating, updating and reviewing the metadata.

Last updated: 20171024

Metadata Point of Contact

Contact information for the individual or organization responsible for the metadata information.

Organization: UConn Center for Land Use Education and Research (CLEAR)

Person: David Dickson

Position: Extension Educator

Phone: (860)345-4511

Email: clear@uconn.edu

Address type: mailing

Address:

PO Box 70 1066 Saybrook Road

City: Haddam

State or Province: CT

Postal code: 06438

Metadata Access Constraints

Restrictions and legal prerequisites for accessing or using the data after access is granted.

Use constraints:

Use with caution at end user's discretion.

Metadata Standards

Description of the metadata standard used to document the data and reference to any additional extended profiles to the standard used by the metadata producer.

Standard name: FGDC Content Standard for Digital Geospatial Metadata

Standard version: FGDC-STD-001-1998

Time convention: local time

FGDC Plus Metadata Stylesheet

Stylesheet: FGDC Plus Stylesheet

File name: FGDC Plus.xsl

Version: 2.3

Description: This metadata is displayed using the FGDC Plus Stylesheet, which is an XSL template that can be used with ArcGIS software to display metadata. It displays metadata elements defined in the Content Standard for Digital Geospatial Metadata (CSDGM) - aka FGDC Standard, the ESRI Profile of CSDGM, the Biological Data Profile of CSDGM, and the Shoreline Data Profile of CSDGM. CSDGM is the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies are ordered to use this standard to document geospatial data created as of January, 1995. The standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the federal level with State and local governments adopting the metadata standard as well. The Biological Data Profile broadens the application of the CSDGM so that it is more easily applied to biological data that are not explicitly geographic (laboratory results, field notes, specimen collections, research reports) but can be associated with a geographic location. Includes taxonomical vocabulary. The Shoreline Data Profile addresses variability in the definition and mapping of shorelines by providing a standardized set of terms and data elements required to support metadata for shoreline and coastal data sets. The FGDC Plus Stylesheet includes the Dublin Core Metadata Element Set. It supports W3C DOM compatible browsers such as IE7, IE6, Netscape 7, and Mozilla Firefox. It is in the public domain and may be freely used, modified, and redistributed. It is provided "AS-IS" without warranty or technical support.

Instructions: On the top of the page, click on the title of the dataset to toggle opening and closing of all metadata content sections or click section links listed horizontally below the title to open individual sections. Click on a section name (e.g. Description) to open and close section content. Within a section, click on a item name (Status, Key Words, etc.) to open and close individual content items. By default, the Citation information within the Description section is always open for display.

Download: FGDC Plus Stylesheet is available from the ArcScripts downloads at www.esri.com.