FGDC Classic | FGDC FAQ | FGDC Plus | XML

Statewide Impervious 2012

Frequently-asked questions:


What does this data set describe?

Title:
Statewide Impervious 2012

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.

  1. How should this data set be cited?

    Quantum Spatial Inc., St. Petersburg, FL, Nathaniel Morton, GISP, Geospatial Analytics Team Lead, 20170901, Statewide Impervious 2012.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -72.841484
    East: -72.695106
    North: 41.656680
    South: 41.546866

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar date: 20170901
    Currentness reference:
    Connecticut

  5. What is the general form of this data set?

    Geospatial data presentation form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • GT-polygon composed of chains (13489)
      It contains the following raster data types:
      • Dimensions 40001 x 40001, type Pixel

    2. What coordinate system is used to represent geographic features?

      The map projection used is NAD 1983 StatePlane Connecticut FIPS 0600 Feet.

      Projection parameters:
      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 coordinates are encoded using coordinate pair.
      Abscissae (x-coordinates) are specified to the nearest 0.000000026813284925708565.
      Ordinates (y-coordinates) are specified to the nearest 0.000000026813284925708565.
      Planar coordinates are specified in foot_us.

      The horizontal datum used is D North American 1983.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

Back to Top

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)


  2. Who also contributed to the data set?

    Quantum Spatial Inc.

  3. To whom should users address questions about the data?

    David Dickson
    UConn Center for Land Use Education and Research (CLEAR)
    Extension Educator
    PO Box 70 1066 Saybrook Road
    Haddam, CT 06438

    (860)345-4511 (voice)
    clear@uconn.edu
Back to Top

Why was the data set created?

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.

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: 20170901 (change 1 of 2)
    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.

    Date: 20170901 (change 2 of 2)
    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.

Back to Top

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

  5. How consistent are the relationships among the observations, including topology?

Back to Top

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access constraints: None
Use constraints:
Use with caution at end user's discretion.

Distributor 0 of 0

  1. Who distributes the data set?

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

Back to Top

Who wrote the metadata?

Dates:
Last modified: 20171024

Metadata author:
David Dickson
UConn Center for Land Use Education and Research (CLEAR)
Extension Educator
PO Box 70 1066 Saybrook Road
Haddam, CT 06438

(860)345-4511 (voice)
clear@uconn.edu

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata(FGDC-STD-001-1998)

Back to Top