Data format: ArcInfo Coverage
File or table name: e714_1
Coordinate system: Universal Transverse Mercator
Theme keywords: elevation, environment, geoscientific information
| Assiniboine River LiDAR Contours 1 Foot Interval | |
|
|
Data format: ArcInfo Coverage File or table name: e714_1 Coordinate system: Universal Transverse Mercator Theme keywords: elevation, environment, geoscientific information |
|
Abstract:
Contours were generated from a Digital Elevation Model (DEM) was produced for an area of approximately 750 square-kilometers along the Assiniboine River between Brandon and Shellmouth Dam. The LiDAR system combines laser, GPS and Inertial technology to measure the earth's surface. Three-dimensional points are collected, from which a bald earth ground model can be derived. For deliverables, the ground thin points (in XYZ Ascii files) formed the Digital Terrain Model (DTM). From the DTM, an evenly spaced 1-metre horizontal grid was produced to form the Digital Elevation Model (DEM).
LiDAR data was collected using LSI's proprietary Helix LiDAR system - Novatel GPS and SPANS inertial unit, coupled to a Riegl Q560 digital waveform ranging laser and mounted in a Cessna 185 aircraft. LiDAR was collected at 500m AGL, and a ground speed of 170km/h. Data is in an ASCII XYZ coordinate format. |
|
Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.
Contours were generated from a Digital Elevation Model (DEM) was produced for an area of approximately 750 square-kilometers along the Assiniboine River between Brandon and Shellmouth Dam. The LiDAR system combines laser, GPS and Inertial technology to measure the earth's surface. Three-dimensional points are collected, from which a bald earth ground model can be derived. For deliverables, the ground thin points (in XYZ Ascii files) formed the Digital Terrain Model (DTM). From the DTM, an evenly spaced 1-metre horizontal grid was produced to form the Digital Elevation Model (DEM). LiDAR data was collected using LSI's proprietary Helix LiDAR system - Novatel GPS and SPANS inertial unit, coupled to a Riegl Q560 digital waveform ranging laser and mounted in a Cessna 185 aircraft. LiDAR was collected at 500m AGL, and a ground speed of 170km/h. Data is in an ASCII XYZ coordinate format.
DEM's can be used as source elevation data for digital orthophotos, and, as layers in geographic information systems, for earth science analysis. DEM's can also serve as tools for volumetric analysis, for site location of towers, or for drainage basin delineation. The ESRI GRID format allows for analysis involving elevational data and also provides for the possibility of contour generation.
ground condition
Unknown
250, 3115 12th Street NE
This data set was developed for Province of Manitoba by LiDAR Services International Inc.
Ground points were initially classified using an automatic classification routine. The ground surface model was edited and verified by creating a shaded relief model and identifying erroneous points and voids in the ground surface.
Data was verified by viewing shaded relief models. Points were checked against those from adjacent flightlines to ensure positional accuracy. The intensity of the LiDAR returns was viewed and compared against adjacent data to verify horizontal positional accuracy.
Horizontal accuracy is verified by comparison of horizontally identifiable features in the LiDAR data against similar features in another flightline of LiDAR data over the same geographic area. Horizontal accuracy is also verified against known coordinates of building roof edges at the calibration site used for that flight.
Vertical accuracy is verified by comparison of points from the calibration flights to conventionally surveyed ground points at the calibration site.
Control point used to observe during kinematic collection from which positions of kinematic GPS solution were derived. NAD83 published coordinates are Lat: 50 26 09.93862, Long: -101 28 37.19950, Ellipsoid Height: 457.668m. NAD 83 adjusted coordinates are Lat: 50 26 09.90287, Long: -101 28 37.19811, Ellipsoid Height: 457.635m. This point was occupied during kinematic GPS collection.
Control point used to build GPS network from which positions of kinematic GPS solution and calibration points were derived. NAD83 published coordinates are Lat: 49 43 27.4243, Long: -100 27 47.4164, Ellipsoid Height: 407.45m. NAD 83 adjusted coordinates are Lat: 49 43 27.42433, Long: -100 27 47.41521, Ellipsoid Height: 407.407m. This point was occupied during kinematic GPS collection.
Control point used to build GPS network from which positions of kinematic GPS solution and calibration points were derived. NAD83 published coordinates are Lat: 50 46 05.1435, Long: -101 16 32.5157, Ellipsoid Height: 540.929m. NAD 83 adjusted coordinates are Lat: 50 46 05.14440, Long: -101 16 32.51762, Ellipsoid Height: 540.873m. This point was not occupied during kinematic GPS collection.
Control point used to build GPS network from which positions of kinematic GPS solution and calibration points were derived. NAD83 published coordinates are Lat: 50 04 10.63200, Long: -100 53 49.25591, Ellipsoid Height: 438.777m. NAD 83 adjusted coordinates are Lat: 50 04 10.63183, Long: -100 53 49.25556, Ellipsoid Height: 438.786m. This point was occupied during kinematic GPS collection.
Control point used to build GPS network from which positions of kinematic GPS solution and calibration points were derived. NAD83 published coordinates are Lat: 49 53 09.2927, Long: -99 54 41.0582 , Ellipsoid Height: 373.82m. NAD 83 adjusted coordinates are Lat: 49 53 09.29240, Long: -99 54 41.05783, Ellipsoid Height: 373.848m. This point was occupied during kinematic GPS collection.
Control point used to build GPS network from which positions of kinematic GPS solution and calibration points were derived. NAD83 published coordinates are Lat: 50 02 57.33090, Long: -100 21 08.44150, Ellipsoid Height: 462.303m. NAD 83 adjusted coordinates are Lat: 50 02 57.33065, Long: -100 21 08.44169, Ellipsoid Height: 462.327m. This point was not occupied during kinematic GPS collection.
Control point used to build GPS network from which positions of kinematic GPS solution and calibration points were derived. NAD83 published coordinates are Lat: 50 46 16.38510, Long: -101 29 08.48560, Ellipsoid Height: 469.216m. NAD 83 adjusted coordinates are Lat: 50 46 16.38542, Long: -101 29 08.48906, Ellipsoid Height: 469.230m. This point was not occupied during kinematic GPS collection.
Control point used to observe during kinematic collection from which positions of kinematic GPS solution were derived. NAD 83 adjusted coordinates are Lat: 49 53 09.27598, Long: -99 54 42.72408, Ellipsoid Height: 372.005m. This point was occupied during kinematic GPS collection.
Control point used to observe during kinematic collection from which positions of kinematic GPS solution were derived. NAD 83 adjusted coordinates are Lat: 50 46 11.65631, Long: -101 17 43.14824, Ellipsoid Height: 532.528m. This point was occupied during kinematic GPS collection.
GPS static network was processed and adjusted, and kinematic GPS data was processed using coordinates obtained from the static network adjustment. Kinematic GPS and inertial information were combined to create the final position and attitude trajectory. The position and attitude trajectory was combined with data from the scanning laser to produce a raw XYZ point cloud.
250, 3115 12th Street NE
Overlapping flight lines were compared at the calibration site and within the project area to determine the boresight corrections required to remove systematic errors. Raw point clouds were generated using the attitude information and scanning laser ranges.
250, 3115 12th Street NE
Raw XYZ point clouds were combined and divided into 1km x 1km tiles. Redundant data between overlapping flightlines was removed.
#250, 3115 12th Street NE
An automatic ground classification routine was run on the LiDAR data using TerraScan, and the results were verified by viewing a shaded relief model. Points that existed above ground were classified to vegetation and then buildings were classified manually from the vegetation points using the shaded relief model to identify them. Points that could not be identified as vegetation or ground were classified as non-ground; bridges , trains, and transmission structures were classified to non-ground.
250, 3115 12th Street NE
LiDAR data was adjusted from ellipsoid to orthometric elevation using the CGVD28 height model.
#250, 3115 12th Street NE
A gridded ASCII XYZ file with a horizontal spacing of 1m was created. Elevations were derived from triangle facets in the TIN model (built using ground points only) at the centre of the grid cell.
#250, 3115 12th Street NE
A surface was created from the ground, vegetation, building, and non-ground points in TerraScan, and a gridded ASCII XYZ file with a horizontal spacing of 1m was created. Elevations were derived from the highest point elevation within the grid cell.
#250, 3115 12th Street NE
Copied compressed .gz files to local disk and unzipped using GZIP. Used the CREATETIN command with GENERATE to convert ASCII tables to tins. Converted the tins to point coverages with TINARC. Converted point coverages to 1-meter grids using POINTGRID. Used the MERGE command to mosaic the grids. To reclassify major rivers within the LiDAR extent to Nodata, extracted major water body polygons from Manitoba Conservation's 1:20 000 base data. Converted polygons to 1-meter grids using the POLYGRID command and assigned all water cells a value of 9999. Merged the resulting water grid with the LiDAR DEMs. Reclassified the 9999 cells to Nodata.
200 Saulteaux Crescent
Multiplied the DEM grid by 3.28084 to convert elevation values from meters to feet. Used the CONTOUR command in ArcInfo GRID to generate contour lines at 1-foot intervals. Ran the RENODE command on the resulting coverage to renumber arc nodes and update FNODE# and TNODE# values in the arc attribute table (AAT). In ArcEdit, deleted arcs where FNODE# = TNODE# and the length was less than or equal to 110-meters. Edgematched adjacent coverages.
200 Saulteaux Crescent
Internal feature number.
ESRI
Feature geometry.
ESRI
Internal node number for the beginning of an arc (from-node).
ESRI
Internal node number for the end of an arc (to-node).
ESRI
Internal node number for the left polygon.
ESRI
Internal node number for the right polygon.
ESRI
Length of feature in internal units.
ESRI
Internal feature number.
ESRI
User-defined feature number.
ESRI
The only attributes assigned were point classification during the processing phase using TerraScan. See process steps for details.
None
250, 3115 12th Street NE