FGDC Classic | FGDC FAQ | FGDC Plus | XML

Connecticut Statewide LiDAR 2016

Frequently-asked questions:


What does this data set describe?

Title:
Connecticut Statewide LiDAR 2016

Abstract:
This metadata record describes the hydro-flattened bare earth digital elevation model (DEM) derived from the classified LiDAR data for the 2016 Connecticut LiDAR project covering approximately 5,240 square miles.

Supplemental information:
Project Projection, Datums and Units.  Projection - State Plane Connecticut.  Horizontal datum - North American Datum of 1983 (NAD83 (2011)).  Vertical datum - North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12b) for converting ellipsoidal heights to orthometric heights.  Units - US feet

  1. How should this data set be cited?

    State of Connecticut, 2016, Connecticut Statewide LiDAR 2016: Capitol Region Council of Governments, Connecticut.

    Online links:
  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -73.745809
    East: -71.782632
    North: 42.063615
    South: 40.971166

  3. What does it look like?

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

    Beginning date: 20160311
    Ending date: 20160416
    Currentness reference:
    ground condition

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

    Geospatial data presentation form: raster digital data

  6. How does the data set represent geographic features?

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

      This is a Raster data set.

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

      The map projection used is Lambert Conformal Conic.

      Projection parameters:
      Lambert Conformal Conic
      Standard parallel: 41.2
      Standard parallel: 41.8666666666667
      Longitude of central meridian: -72.75
      Latitude of projection origin: 40.8333333333333
      False easting: 999999.999996
      False northing: 499999.999998

      Planar coordinates are encoded using coordinate pair.
      Abscissae (x-coordinates) are specified to the nearest 2.
      Ordinates (y-coordinates) are specified to the nearest 2.
      Planar coordinates are specified in survey feet.

      The horizontal datum used is North American Datum of 1983 (2011).
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222101004.

      Vertical coordinate system definition:
      Altitude system definition:
      Altitude datum name: North American Vertical Datum of 1988(GEOID12b)
      Altitude resolution: 0.1
      Altitude distance units: feet
      Altitude encoding method: Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    Entity and attribute overview:
    Bare Earth only
    
    Classes:
    2 - Bare-Earth Ground

    Entity and attribute detail citation:
    USGS Base Specification 1.2, QL2 meeting 19.6 cm NVA
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?

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

    Erik D. Snowden
    Capitol Region Council of Governments
    IT/GIS Coordinator
    241 Main Street
    Hartford, CT 06106
    U.S.A.

    860.522.2217 x217 (voice)
    860.724.1274 (FAX)
    esnowden@crcog.org
    Hours of Service: 8:00 AM - 5:00 PM
Back to Top

Why was the data set created?

To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. LAS and bare earth DEM data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL2. 19.6 cm VVA.

Back to Top

How was the data set created?

  1. Where did the data come from?

    LIDAR and GPS_RAW (source 1 of 6)

    Sanborn Map Company Inc., Unpublished Material, LiDAR Data: None, None.

    Type of source media: disc
    Source contribution:
    Aerial LiDAR and GPS/IMU data are recorded for the defined project area at an altitude, flight speed, scanner swath width and scanner pulse frequency to achieve the design goals of the project.

    CONT (source 2 of 6)

    Sanborn Map Company Inc., 2010, Ground control: None, None.

    Type of source media: disc
    Source contribution:
    Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy.  Predefined points (NGS when available) within the project area are targeted.

    GPS (source 3 of 6)

    Sanborn Map Company Inc., Unpublished material, Post processed GPS/INS.

    Type of source media: disk
    Source scale denominator: 1200
    Source contribution:
    Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system

    LAS (source 4 of 6)

    Sanborn Map Company Inc., Unpublished material, Post processed lidar.

    Type of source media: Disk
    Source scale denominator: 1200
    Source contribution:
    The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud.

    LAS (source 5 of 6)

    Sanborn Map Company Inc., Unpublished material, Classified lidar.

    Type of source media: disk
    Source scale denominator: 1200
    Source contribution:
    The classified lidar point cloud is used to derive various data products such as, but not limited to, bare earth gridded DEM, triangulated irregular networks (TIN), contours, digital surface models (DSM).  The output format is fully compliant LAS v1.4, Point Record Format 6

    TLDEF (source 6 of 6)

    Capitol Region Council of Governments, Unpublished Material, Tile Definition.

    Type of source media: disk
    Source scale denominator: 1200
    Source contribution:
    The tile definition defines discreet non-overlapping rectangular areas used as cut lines to break up the large classified lidar dataset into smaller, more manageable data tiles.  Each tile is 2500ft by 2500ft in dimension.

  2. What changes have been made?

    Date: 2016 (change 1 of 6)
    At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.

    Data sources used in this process:
    • None

    Data sources produced in this process:
    • CONT

    Date: 2016 (change 2 of 6)
    New LiDAR data is captured for the project area using a Leica ALS70 w/MPiA LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane.

    Data sources used in this process:
    • None

    Data sources produced in this process:
    • LIDAR, GPS_RAW

    Date: 2016 (change 3 of 6)
    The airborne GPS data is post-processed in Intertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey.

    Data sources used in this process:
    • GPS_RAW

    Data sources produced in this process:
    • GPS_SOL

    Date: 2016 (change 4 of 6)
    The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud.

    Data sources used in this process:
    • LIDAR, GPS_SOL

    Data sources produced in this process:
    • LAS

    Date: 2016 (change 5 of 6)
    The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software.  Data is classified to produce:  Class 1:  unclassified,  Class 2:  ground,  Class 7:  low point,  Class 9: water,  Class 10: ignored ground, Class 17: bridge deck,  Class 18: high noise. 

    Data sources used in this process:
    • CONT, GPS_SOL, LIDAR

    Data sources produced in this process:
    • LAS

    Date: 2016 (change 6 of 6)
    The bare earth points of the processed lidar data are then output to a DEM tile format. The DEM is compared to the ground control and elevation differences between the surface and surveyed elevation are recorded in tabular form.  Vertical accuracy statistics are then developed to produce vertical RMSE and overall accuracy estimates and reports.

    Data sources used in this process:
    • CONT, LIDAR

    Data sources produced in this process:
    • None

Back to Top

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

  1. How well have the observations been checked?

    State of Connecticut:
    
    The LiDAR surface was evaluated using a collection of 181 GPS surveyed checkpoints for the raw NVA report. The DEM was compared to these checkpoints yielding a better result than was required for the project. 
    
    Raw NVA Control Accuracy Report (feet)
    
          --------- Report Disclaimer ---------
    
          This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a thorough quality control process.
    
          --------- Report Summary ---------
    Average dz       	0.004
    Minimum dz       	-0.829
    Maximum dz       	0.622
    Average magnitude	0.170
    Root mean square 	0.227
    Std deviation    	0.228
    
    ----------------------------------------------------------------------------------------
    
    Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The NVA report is generated from the comparison of the DEM and the ground control collected within the project area.
    
    The DEM surface was evaluated using a collection of 181 GPS surveyed checkpoints for the NVA report. The DEM was compared to these checkpoints yielding much better result than was required for the project. 
    
    NVA Control Accuracy Report (feet)
    
          --------- Report Disclaimer ---------
    
          This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a thorough quality control process.
    
          --------- Report Summary ---------
    Average dz       	0.004
    Minimum dz       	-0.778
    Maximum dz       	0.576
    Average magnitude	0.158
    Root mean square 	0.207
    Std deviation    	0.207
    
    ----------------------------------------------------------------------------------------
    
    Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The VVA report is generated from the comparison of the DEM and the ground control collected within the project area.  
    
    The DEM was evaluated using a collection of 95 GPS surveyed checkpoints. The DEM was compared to these checkpoints yielding much better result than was required for the project. 
    
    VVA Control Accuracy Report (feet)
    
          --------- Report Disclaimer ---------
    
          This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a thorough quality control process.
    
          --------- Report Summary ---------
    Average dz       	0.147
    Minimum dz       	-0.771
    Maximum dz       	0.625
    Average magnitude	0.212
    Root mean square 	0.261
    Std deviation    	0.217
    
    ----------------------------------------------------------------------------------------

  2. How accurate are the geographic locations?

    Horizontal positional accuracy for the Connecticut LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture.  The data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 1.0 meter RMSEx/RMSEy.

  3. How accurate are the heights or depths?

    For the DEM data derived from the classified point cloud, the NVA and VVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within Connecticut. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey check points were distributed throughout the state. Specifications for this project require that the NVA be 19.6 cm or better @ 95 percent confidence level.

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

    LiDAR data is collected for the project area.  Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums.  The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes.  Anomalous laser returns that occur infrequently are removed entirely from the data set.  Once clean bare earth points are established, DEMs are created using bare earth points and hydro features. The DEM surface is then compared to the survey checkpoints. These accuracies must pass the NVA and VVA accuracy specifications.

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

    LiDAR data is collected within the project area and processed. After the DEMs were created, the dataset was verified against control.  Well-distributed control was collected for the entire state of Connecticut.  Accuracy is reported for the state as a whole.

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: This data may be used by the requested party for stated purposes and may be re-distributed.
Use constraints:
This data is for planning purposes only and should not be used for legal or cadastral purposes. Any conclusions drawn from analysis of this information are not the responsibility of Sanborn Map Company. Users should be aware that temporal changes may have occurred since this dataset was collected and some parts of this dataset may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations.

Contact:
State of Connecticut

Distributor 1 of 1

  1. Who distributes the data set?

    Erik D. Snowden
    Capitol Region Council of Governments
    IT/GIS Coordinator
    241 Main Street
    Hartford, CT 06106
    U.S.A.

    860.522.2217 x217 (voice)
    860.724.1274 (FAX)
    esnowden@crcog.org
    Hours of Service: 8:00 AM - 5:00 PM

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

    Connecticut 2016 LiDAR project

  3. What legal disclaimers am I supposed to read?

    The Capitol Region Council of Governments digital data have been tested and their documentation carefully reviewed.  However, the Capitol Region Council of Governments and its representatives make no warranty or representation, either expressed or implied, with respect to the digital data and their documentation, their quality, performance, merchantability, or fitness for a particular purpose.  The digital data are distributed on "as is" basis, and the user assumes all risk to their quality, the results obtained from their use, and the performance of the data.  In no event will the Capitol Region Council of Governments or its representatives be liable for any direct, indirect, special, incidental or consequential damages resulting from and defect in the State of Connecticut or in their documentation.  This disclaimer of warranty is exclusive and in lieu of all others, oral or written, express or implied.  No agent or employee is authorized to make any modification, extension, or addition to this warranty.

  4. How can I download or order the data?

    • Availability in digital form:


    • Data format:
      in format DEM (version 1.4) Size: 6.4
      Network links:http://crcog.org
      Media you can order:5 - 1/2 inch hard drive(format LAS)

    • Cost to order the data: unknown


    • Special instructions:

      Capitol Region Council of Governments

    • How long will it take to get the data?

      unknown

  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: 2016

Metadata author:
Shawn Benham
Sanborn Map Co
Project Manager
1935 Jamboree Dr
Colorado Springs, CO 80920
U.S.A.

719.502.1296 (voice)
sbenham@sanborn.com
Hours of Service: 8:00 AM - 5:00 PM

Metadata standard:
FGDC CSDGM(FGDC-STD-001-1998)

Back to Top