<metadata><idinfo><citation><citeinfo><origin>
          AeroMetric, Inc.
        </origin><pubdate>
          20110201
        </pubdate><title>Minnesota River Basin LiDAR Acquisition, Geodatabases</title><geoform>
          remote-sensing image
          </geoform></citeinfo></citation><descript><abstract>An ESRI geodatabase was created on a tile basis for all 25 counties. Each geodatabase has a feature dataset named Terrain Data which contains bare earth points, bridge breaklines, and hydro breaklines (if present). Each geodatabase also has a raster DEM that was generated from the LAS points and the breaklines. The raster DEM tiling shceme was an orthogonal setup based on the original tile sheme. Each geodatabase contains georeference information. The geodatabases use the same coordinate reference system as the LAS point cloud. The tiling scheme was provided by the Minnesota Department of Natural Resources and is from the USGS 16th 1:24,000 quadrangle tiles.Project Data was delivered according to project requirements in NAD83 UTM15N NAVD88 GEOID 03 Meters</abstract><purpose>AEROMETRIC, INC. acquired highly accurate Light Detection and Ranging (LiDAR) data for the Minnesota Department of Natural Resources, The Minnesota River Basin LiDAR Acquisition project included 25 Minnesota Counties with a total area of approximately 17,260 square miles.  Using multiple Optech Gemini LiDAR systems, data was collected at 1700 meters to support the project area requirements.  Survey checkpoints were collected by AeroMetric to assist with the validation of the LiDAR point cloud. The data was to meet a 15cm Vertical RMSE which was exceeded with a Verticle RMSE values better than 10cm throughout the project. 

Accuracy statement is based on the area of moderate to flat terrain. Diminished accuracies are to be expected in areas in dense vegetation. The accuracy of the LiDAR data as tested met the vertical accuracy or better, however, derived products may be less accurate in areas of dense vegetation due to a lesser number of points defining the bare-earth in these areas.</purpose></descript><timeperd><timeinfo><sngdate><caldate>
            20110201
          </caldate></sngdate></timeinfo><current>
        ground condition
        </current></timeperd><status><progress>
        Complete
      </progress><update>
        unknown
      </update></status><spdom><bounding><westbc>
          -96.628762
        </westbc><eastbc>
          -93.401415
        </eastbc><northbc>
          46.158043
        </northbc><southbc>
          43.417905
        </southbc></bounding></spdom><keywords><theme><themekt>
          None
          </themekt><themekey>
          Light Detection and Ranging
        </themekey><themekey>
          LIDAR
        </themekey><themekey>
          Bare Earth
        </themekey><themekey>
          Point Cloud
        </themekey><themekey>
          DEM
        </themekey><themekey>
          breaklines
        </themekey><themekey>
          Intensity
        </themekey></theme><place><placekt>
          None
        </placekt><placekey>
          US
          </placekey><placekey>
          State
        </placekey><placekey>
          Minnesota
        </placekey></place></keywords><accconst>
      None.
    </accconst><useconst>
      None.
    </useconst><datacred>AeroMetric, Inc.</datacred></idinfo><dataqual><attracc><attraccr>
        The Fundamental Vertical Accuracy (FVA) of the Classified Bare Earth files for the project area achieved an RMSE of 0.07 meters.  
      </attraccr></attracc><logic>None</logic><complete>
      Complete
    </complete><posacc><horizpa><horizpar>
          All Area data products were acquired at or below 1700 meters above mean terrain (AMT) and have a horizontal accuracy of 0.30 meters, with a nominal point spacing of 1.3 meters.  
          </horizpar></horizpa><vertacc><vertaccr>The Fundamental Vertical Accuracy (FVA) of the Classified Bare Earth for all Areas achieved is 0.07 meters at a 95% confidence level in the "Open Terrain" land cover category.  502 control points were used in this evaluation.
        </vertaccr></vertacc></posacc><lineage><procstep><procdesc>
          The LiDAR data was captured using multiple fixed wing aircraft equipped with a LiDAR systems.  Each LiDAR system includes a differential GPS unit and inertial measurement system to provide superior accuracy.

Acquisition parameters:  
1. Scanner - Optech Gemini  
2. Flight Height - 1700m above mean terrain
3. Scan Angle - 40 degrees
4. Sidelap - 50%
5. Nominal Post Spacing - 1.3m
6. Scan Frequency - 34 Hz

GPS and IMU processing parameters:  
1. Processing Programs and version - Applanix - POSGPS and POSProc, versions 4.4, MMS version 5.2  
2. Maximum baseline length - Not greater than 60km.
3. Number of base stations during LiDAR collection - A minimum of 1.  
4. Max separation between base stations during LiDAR collection - 0.05m  
5. IMU processing monitored for consistency and smoothness - Yes.

Point Cloud Processing:  
1. Program and version - Optech ASDA, Dashmap  
2. Horizontal Datum - NAD83(NSRS2007)  
3. Horizontal Coordinates - Universal Transverse Mercator, Zone 15, in Meters.
4. Vertical Datum - NAVD88  
5. Geoid Model used to reduce satellite derived elevations to orthometric heights - NGS Geoid03.

LIDAR Processing:  
1. Processing Programs and versions - TerraSolid TerraScan (version 010.021), TerraModeler (version 010.005 and TerraMatch (version 010.012) and Intergraph MicroStation (version.08.05.02.55).
2. Point Cloud data is imported to TerraScan in a Microstation V8 (V) CAD environment on a specified tiling scheme.
3. Analyze the data for overall completeness and consistency.  This is to ensure that there are no voids in the data collection.  
4. Inspect for calibration errors in the dataset using the TerraMatch software.  This is accomplished by sampling the data collected across all flight lines and classify the individual lines to ground.  The software will use the ground-classified lines to compute corrections (Heading, Pitch, Roll, and Scale).  
5. Orientation corrections (i.e. Calibration corrections) are then applied (if needed) to the entire dataset.  
6. Automatic ground classification is performed using algorithms with customized parameters to best fit the project area. Several areas of varying relief and planimetric features were inspected to verify the final ground surface.  
7. AEROMETRIC, INC. provided Quality Assurance and Quality Control (QAQC) data for this project.  AEROMETRIC captured QA/QC points in 'open terrain' land cover category that were used to test the accuracy of the LiDAR ground surface.  TerraScan's Output Control Report (OCR) was used to compare the QAQC data to the LIDAR data. This routine searches the LIDAR dataset by X and Y coordinate, finds the closest LIDAR point and compares the vertical (Z) values to the known data collected in the field.  Based on the QAQC data, a bias adjustment was determined, and the results were applied (if necessary) to the LIDAR data.  A final OCR was performed with a resulting RMSE of 0.088m for the project.  
8. Once the automatic processing and the testing of LiDAR is complete, AEROMETRIC meticulously reviews the generated bare-earth surface data to ensure that proper classification was achieved as part of a Quality Control process. 
9. Breaklines were collected for all 25 counties. The criteria for breaklines was 100 ft or larger rivers with double lines and 2 acre ponds or larger. Breaklines were delivered as an ESRI feature class (PolygonZ format). Each shapefile contains georeference information. Breakline elevations use the same coordinate reference system as the LAS point cloud. Breaklines were delivered in tile format and edge match seemlessly both verically and horizontally. The tiling scheme was provided by the Minnesota Department of Natural Resources and is from the USGS 16th 1:24,000 quadrangle tiles
10.Final deliverables are generated and output to a client specified tiling scheme.
        </procdesc><procdate>
          20110606
        </procdate></procstep></lineage><cloud>Unknown</cloud></dataqual><spdoinfo><direct>Point</direct></spdoinfo><spref><horizsys><planar><gridsys><gridsysn>
            Universal Transverse Mercator
          </gridsysn><utm><utmzone>
              15
            </utmzone><transmer><sfctrmer>
                0.9996
              </sfctrmer><longcm>
                -90
              </longcm><latprjo>
                0
              </latprjo><feast>
                500000
              </feast><fnorth>
                0
              </fnorth></transmer></utm></gridsys><planci><plance>
            coordinate pair
          </plance><coordrep><absres>
              0.01
            </absres><ordres>
              0.01
            </ordres></coordrep><plandu>
            meters
          </plandu></planci></planar><geodetic><horizdn>
          North American Datum of 1983 (NSRS 2007)
        </horizdn><ellips>
          Geodetic Reference System 80
          </ellips><semiaxis>
          6378137.000000
        </semiaxis><denflat>
          298.25722210088
        </denflat></geodetic></horizsys><vertdef><altsys><altdatum>North American Vertical Datum of 1988</altdatum><altres>0.01</altres><altunits>meters</altunits><altenc>Explicit elevation coordinate included with horizontal coordinates</altenc></altsys></vertdef></spref><metainfo><metd>
      20110603
    </metd><metc><cntinfo><cntorgp><cntorg>
            AeroMetric, Inc.
          </cntorg></cntorgp><cntaddr><addrtype>
            Mailing and physical address
          </addrtype><address>
            4020 Technology Parkway
          </address><city>
            Sheboygan
          </city><state>
            WI
          </state><postal>
            53083
          </postal><country>US</country></cntaddr><cntvoice>
          1-920-457-3631
        </cntvoice><cntfax>1-920-457-0410</cntfax><cntemail>
          rmerry@aerometric.com
        </cntemail><hours>Monday through Friday 8:00 AM to 5:00 PM (Central Time)</hours></cntinfo></metc><metstdn>
      FGDC Content Standard for Digital Geospatial Metadata
      </metstdn><metstdv>
      FGDC-STD-001-1998
      </metstdv></metainfo><dataIdInfo><idPurp>AEROMETRIC, INC. acquired highly accurate Light Detection and Ranging (LiDAR) data for the Minnesota Department of Natural Resources, The Minnesota River Basin LiDAR Acquisition project included 25 Minnesota Counties with a total area of approximately 17,260 square miles.  Using multiple Optech Gemini LiDAR systems, data was collected at 1700 meters to support the project area requirements.  Survey checkpoints were collected by AeroMetric to assist with the validation of the LiDAR point cloud. The data was to meet a 15cm Vertical RMSE which was exceeded with a Verticle RMSE values better than 10cm throughout the project. 

Accuracy statement is based on the area of moderate to flat terrain. Diminished accuracies are to be expected in areas in dense vegetation. The accuracy of the LiDAR data as tested met the vertical accuracy or better, however, derived products may be less accurate in areas of dense vegetation due to a lesser number of points defining the bare-earth in these areas.</idPurp><idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;An ESRI geodatabase was created on a tile basis for all 25 counties. Each geodatabase has a feature dataset named Terrain Data which contains bare earth points, bridge breaklines, and hydro breaklines (if present). Each geodatabase also has a raster DEM that was generated from the LAS points and the breaklines. The raster DEM tiling shceme was an orthogonal setup based on the original tile sheme. Each geodatabase contains georeference information. The geodatabases use the same coordinate reference system as the LAS point cloud. The tiling scheme was provided by the Minnesota Department of Natural Resources and is from the USGS 16th 1:24,000 quadrangle tiles.Project Data was delivered according to project requirements in NAD83 UTM15N NAVD88 GEOID 03 Meters&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs><idCredit>AeroMetric, Inc.</idCredit><idCitation><resTitle>Minnesota River Basin LiDAR Acquisition, Geodatabases</resTitle></idCitation><searchKeys><keyword>Light Detection and Ranging</keyword><keyword>LIDAR</keyword><keyword>Bare Earth</keyword><keyword>Point Cloud</keyword><keyword>DEM</keyword><keyword>breaklines</keyword><keyword>Intensity</keyword></searchKeys><resConst><Consts><useLimit>None.</useLimit></Consts></resConst></dataIdInfo><Esri><ArcGISProfile>FGDC</ArcGISProfile><ArcGISFormat>1.0</ArcGISFormat></Esri></metadata>
