LiDAR Elevation, Chisago County, Minnesota, 2007

This page last updated: 04/28/2014
Metadata created using Minnesota Geographic Metadata Guidelines


Go to Section:
1. Overview
2. Data Quality
3. Data Organization
4. Coordinate System
5. Attributes
6. Distribution - Get Data
7. Metadata Reference

Section 1 Overview
Originator Chisago County Surveyor's Office
Title LiDAR Elevation, Chisago County, Minnesota, 2007
Abstract The LiDAR data for Chisago County was collected under contract by Chisago County. Thus, the data format is not entirely consistent with some of the other LiDAR data collected by the State of Minnesota. Specifically, the Chisago County collect did not require classification of anything other than Bare Earth in the LiDAR LAS files, so there is not information on buildings, vegetation, or model key points.

Breaklines captured as part of this effort are also a bit different. In Chisago County the breaklines are 3D Polyline features vs 3D Polygon features. They also include road centerlines, stream courses and other features that are not part of the Statewide collect specifications.

LiDAR was classified and stereo-pairs were generated from LiDAR intensity data which were used to collect breaklines. A surface was generated from the bare earth LiDAR DTM (digital terrain model) and the collected breakline data to produce the contours and the DEMs.

Tiling: Bare-earth and first-return LiDAR data in LAS format are divided into 5000' X 5000' sheet tiles named according to the Lower Left XY coordinate value. Five-foot posted raster bare-earth DEMs in ArcGrid format are divided into 5000' X 5000' sheet tiles. The contours are divided into township areas.

Optimal Geomatics, Inc. collected and processed the LiDAR data, and authored the procedures quality control reports.
Purpose The bare-earth data and breakline data was utilized to produce terrain surface models for the generation of the one-foot contours and the raster DEM.
Time Period of Content Date 04/2007
Currentness Reference Ground condition. Data was collected between April 18 - 28, 2007.
Progress Complete
Maintenance and Update Frequency Unknown
Spatial Extent of Data Chisago County
Bounding Coordinates -93.144138
-92.641809
45.732329
45.294135
Place Keywords Chisago County, Minnesota
Theme Keywords elevation, LiDAR, DEM, digital elevation model, contour, topographic, topo, DTM, LAS
Theme Keyword Thesaurus ISO 19115 Topic Category
Access Constraints None
Use Constraints The topographic data represents the results of data collection/processing for Chisago County and indicates the existing general conditions. As such, they are only valid for their intended use, content, time and accuracy specifications. The user is responsible for the results of any application of data other than its intended purposes.
Contact Person Information , County Administrator
Chisago County
313 North Main Street
Center City, MN  55012
Phone: 651-257-1300
Email: administration@co.chisago.mn.us
Browse Graphic None available
Associated Data Sets For more information about elevation data for Minnesota, see: www.mngeo.state.mn.us/chouse/elevation/index.html

Section 2 Data Quality
Attribute Accuracy 0.3 foot (9.25cm) RMSE. The accuracy of the LiDAR DEM is intended to meet or exceed NSSDA Accuracy Standards for 1-foot contours.

RMSE can also be expressed in NSSDA 95% accuracy terms. This is accomplished by multiplying the root mean square error (RMSE) by 1.96. Therefore accuracy of this product is intended to meet or exceed 0.6 foot (18cm) at 95% confidence.

See the Vertical Positional Accuracy field for more information on the accuracy of the elevation values.
Logical Consistency
Completeness The project area covered all of Chisago County.
Horizontal Positional Accuracy 1 foot RMSE in X or Y. Horizontal accuracy meets or exceeds ASPRS Class 1 Accuracy Standards for 1-inch=100 foot mapping.

Horizontal datum: NAD83
Vertical Positional Accuracy Vertical datum: NAVD88 (Geoid03)

0.3 foot (9.25cm) RMSE. Compiled to meet or exceed NSSDA Accuracy Standards for 1-foot contours.

The DEMs for these survey areas are believed to be accurate. The inclusion of breaklines collected from the LiDAR data provides for a more accurate DEM around hydro edges than could be achieved with the LiDAR points alone.

Tested 0.37 US Survey Feet fundamental vertical accuracy at 95% confidence level in open terrain using RMSE(z) x 1.96.

Tested 0.55 US Survey Feet consolidated vertical accuracy at 95% confidence level in open terrain and low grass using RMSE(z) x 1.96.

Tested 0.51 US Survey Feet fundamental vertical accuracy at 95% confidence level for the Chisago County 2007 adjusted HARN stations (Geoid03) using RMSE(z) x 1.96.

Expected horizontal accuracy of elevation products as determined from system studies and other methods is 1/2000th of the flight height, which, in this particular project, was 850m (2788.7 US survey feet) AGL, giving a horizontal tolerance of less than 0.43m (1.39 US survey feet).

Details of the comparison of validation points vs. the LiDAR DEM are provided in the LiDAR DEM Quality Control Report: ftp.lmic.state.mn.us/pub/data/elevation/lidar/county/chisago/Chisago_LiDAR_QC_Report.pdf
Lineage Optimal Geomatics, Inc. collected and processed the LiDAR data, and authored the Data Processing Procedures Report and the LiDAR DEM Quality Control Report.

Data collection of the survey area resulted in a total of 110 flightlines including four control lines covering the project area. The range files, flight logs, raw air and ground GPS files were then processed using REALM, a LIDAR processing software package from Optech. Processing began by downloading these files into a REALM database. For redundancy and accuracy purposes, the airborne GPS data were processed from two base stations using POSGPS from Applanix, Inc. The agreement between a minimum of two solutions checked or combined between a minimum of two stations was better than 10 cm in each of X, Y, and Z. These trajectories were used in the processing of the inertial data. The inertial data were processed using POSProc from Applanix, Inc. This software produces an SBET (smooth best estimate of trajectory) using the GPS trajectory from POSGPS and the roll, pitch and heading information recorded by the POS (Position Orientation System). REALM uses the SBET to generate a set of data points for each laser return in the LAS file format. Each data point is assigned an echo value so it can be segregated based on the first and last pulse information. This project's data were processed in strip form, meaning each flight line was processed independently. Processing the lines individually provides the data analyst with the ability to QC the overlap between lines.

Strips were imported into a project using TerraScan (Terrasolid, Ltd.) and the project management tool GeoCue (GeoCue Corp.). By creating a project, the various flightlines are combined while breaking the dataset as a whole into manageable pieces. This process also converts the dataset from geographic coordinates to the Minnesota County Coordinate System (NAD83), Chisago Co utilizing NADCON. The ellipsoid height values were converted to NAVD88 orthometric values using Geoid03, provided by NGS.

Individual lines were then checked against adjacent lines to ensure a cohesive dataset. The data from each line were then combined and a classification routine was then run to determine the initial surface model. This initial surface model was then reduced using Optimal Geomatics' proprietary methods to create the final bare-earth dataset. A Triangular Irregular Network (TIN) was generated using the final surface data. Contours were then created from the TIN. The bare-earth data were then checked against the validation points across the project area. The results of these checks showed the DEM fitting the validation points well (see LIDAR DEM Quality Control Report for results, as well as camera calibration parameters).

Stereo pairs were generated from the LIDAR intensity data using Geocue and LIDAR1CuePac (Geocue Corp.). LIDARgrammetry was then utilized to collect breaklines where necessary along hydro features to support the contour generation. These breaklines were collected as a 3D element in the MicroStation (Bentley Systems, Inc.) environment utilizing ISSD (Z/I Imaging).

The deliverables constituted: LIDAR bare-earth in .LAS format, LIDAR first-return in .LAS format, raster bare-earth DEM in ESRI ArcGRID format at 5-foot resolution, and an ArcGIS File Geodatabase containing one-foot topographic contour data, breaklines, and control points as 3D feature classes. Deliverables were in County Coordinates (County Coordinate Zone ID 41) with elevation value units in feet.


DNR Processing Steps

The Chisago county data was processed in the following way:

1) LAS files were projected from county coordinates to UTM Zone 15, NAD83, NAVD88 (Geoid03)
2) LAS point Z values were scaled from feet to meters
3) LAS files were retiled into the state tile scheme (1/16 of a USGS 1:24,000 scale quadrangle)
4) Breakline features were merged together into a single feature class
5) Breakline features were projected from county coordinates to UTM Zone 15, NAD83, NAVD88 (Geoid03)
6) Breakline Z Values were scaled from feet to meters
7) LAS Bare Earth Points and breaklines were used to create a Terrain data type
8) 1-meter DEM was derived from Terrain using nearest neighbor interpolation option (DEM01)
9) Hillshade was derived from 1-meter DEM Altitude 45, Azimuth 215 (DEM01HS)
10) 3-meter DEM was derived from Terrain using nearest neighbor interpolation option (DEM03)
11) Hillshade was derived from 3-meter DEM Altitude 45, Azimuth 215 (DEM03HS)
12) Aspect was derived from 3-meter DEM (DEM03ASPECT)
13) Slope in degrees was derived from 3-meter DEM (DEM03SLOPE_DEGREES)
14) Slope in percent was derived from 3-meter DEM (DEM03SLOPE_PERCENT)
15) DEM03 was smoothed using a 3x3 mean smoothing filter
16) 2-foot contours were created from the smoothed 3-meter DEM

All DEMS are hydro flattened and enforced using the breakline features.

All processing was done using ArcGIS V10 and LP360 Extensions.

Section 3 Spatial Data Organization (not used in this metadata)

Section 4 Coordinate System
Horizontal Coordinate Scheme Universal Transverse Mercator
UTM Zone Number 15
Horizontal Datum NAD83
Horizontal Units meters

Section 5 Attributes
Overview Type: Definition: String, 50
Fcode: Double, Scale 0
Elevation: Double, Scale 3
Detailed Citation Index Contour: Every fifth contour of the one-foot contour dataset
Intermediate Contour: Contours depicted between index contours

Index Depression Contour: Every fifth depression contour of the one-foot contour dataset
Intermediate Depression Contour: Depression contours depicted between index contours.
Table Detail:

Section 6 Distribution
Publisher Minnesota Department of Natural Resources
Publication Date 2008
Contact Person Information Nancy Rader, GIS Data Coordinator
Minnesota Geospatial Information Office (MnGeo)
658 Cedar Street, Room 300
St. Paul, MN  55155
Phone: 651-201-2489
Fax: 651-296-6398
Email: gisinfo.mngeo@state.mn.us
Distributor's Data Set Identifier Chisago LiDAR 2007
Distribution Liability 1. Chisago County: The digital vector data represents the results of data collection/processing for Chisago, MN and indicates the general conditions existing at the time of flight. As such, it is only valid for its intended use, content, time and accuracy specifications. The user is responsible for the results of any application of the data other than for its intended purpose.

2. Minnesota Department of Natural Resources General Geographic Data License Agreement is online: www.dnr.state.mn.us/sitetools/data_software_license.html

3. MnGeo's data disclaimer is online: www.mngeo.state.mn.us/chouse/disclaimer.html
Ordering Instructions The LiDAR data provided by Chisago County and DNR may be viewed online or downloaded in several ways:

1. MnTOPO website: www.dnr.state.mn.us/maps/mntopo/index.html (or click the link below in the Online Linkage field)

- view data online
- download data in Esri and open formats (tiles for most data formats will be mosaicked together during download)
- see the help file for details: files.dnr.state.mn.us/aboutdnr/gis/mntopo/mntopo_help_document.pdf

2. MnGeo's FTP site
Use the tile_index.pdf maps to locate the tiles you need. Except for the county file, tiles will not be mosaicked.

a. From the county folder: ftp.lmic.state.mn.us/pub/data/elevation/lidar/county/chisago/
The county mosaic is named elevation_data.gdb.zip For details of its contents and size, see this table: geoint.lmic.state.mn.us/lidar.php

b. In the 250k tiles folder: ftp.lmic.state.mn.us/pub/data/elevation/lidar/q250k/


For more help with Minnesota's LiDAR data, see www.mngeo.state.mn.us/chouse/elevation/lidar.html
Online Linkage I AGREE to the notice in "Distribution Liability" above. Clicking to agree will either begin the download process or link to download information. See "Ordering Instructions" above for details.

Section 7 Metadata Reference
Metadata Date 04/28/2014
Contact Person Information Nancy Rader, GIS Data Coordinator
Minnesota Geospatial Information Office (MnGeo)
658 Cedar Street, Room 300
St. Paul, MN  55155
Phone: 651-201-2489
Fax: 651-296-6398
Email: gisinfo.mngeo@state.mn.us
Metadata Standard Name Minnesota Geographic Metadata Guidelines
Metadata Standard Version 1.2
Metadata Standard Online Linkage http://www.mngeo.state.mn.us/committee/standards/mgmg/metadata.htm


This page last updated: 04/28/2014
Go back to top