Poplar Point 1-metre LiDAR Contours

File Geodatabase Feature Class


Full-color, fli-map, LiDAR, FLI-MAP, intensity image, Upper Elm Creek, FLIMAP, Light Detection and Ranging, flimap, Intensity, intensity, Linescan, topography, Manitoba, high-resolution, Poplar Point, contour


Dataset created under request from Manitoba Infrastructure and Transportation


Contours generated from a 1 m resolution bare-earth DEM obtained from ground filtering of FLI-MAP LiDAR survey data in area A of the Upper Elm Creek project region.


Use limitations

Data not to be used beyond the limits of the source scale


West -98.161427   East -97.711475
North 50.151122   South 49.962146

Scale Range
Maximum (zoomed in) 1:5,000
Minimum (zoomed out) 1:150,000,000

ArcGIS Metadata 

Topics and Keywords 

Themes or categories of the resource  elevation

*Content type  Downloadable Data

Place keywords  Upper Elm Creek, Manitoba

Theme keywords  Full-color, fli-map, LiDAR, FLI-MAP, intensity image, FLIMAP, Light Detection and Ranging, flimap, Intensity, intensity, Linescan, topography, high-resolution


Title Poplar Point 1-metre LiDAR Contours
Publication date 2013-01-15

Presentation formats* digital map

Citation Contacts 

Responsible party
Organization's name Fugro SESL Geomatics Ltd.; Fugro FLI-MAP 400
Contact's role  originator

Resource Details 

Dataset languages  English (CANADA)
Dataset character set  utf8 - 8 bit UCS Transfer Format

Status  completed
Spatial representation type* vector

Supplemental information
LiDAR Acquisition

LiDAR acquisition for this project was performed by Fugro Horizons  in a Twin Cessna 310 equipped with a Flimap Fx LiDAR system including an inertial measuring unit (IMU) and a dual frequency GPS receiver.  Acquisition was accomplished between October 2nd 2012 and October 11th 2012. The LiDAR flight specifications follow:
Field of View: 60 Degrees
Altitude:2100 feet AMT
Scan Rate:50 rps 
Pulse Rate:200 kHz
Airspeed:130 knots
Average Post Spacing: 4pts/m^2 
Average Swath Width: 650 Meters
Total Flight Lines: 47
Number of Lifts: 4

GPS Data Collection

A GPS receiver was in constant operation over a control point during flight acquisition.  The base station identification and location are listed in the following table. 
Base S1:49 48 46.10892, 97 58 57.04743, 220.363
Base S1a: 49 48 46.15541, 97 58 53.93487, 220.260
Base S2: 49 42 52.08990, 98 11 14.27833 , 265.333
Base S2a: 49 42 55.97045, 98 11 14.13693, 265.965

GPS Data Processing

All GPS phase data was post processed with continuous kinematic survey techniques using “On the Fly” (OTF) integer ambiguity resolution.  The GPS data was processed with forward and reverse processing algorithms.  The results from each process, using the data collected at the airport, were combined to yield a single fixed integer phase differential solution of the aircraft trajectory.   The differences between the forward to reverse solution within the project area were within project specifications (<10cm) in both the horizontal and vertical components, indicating a valid and accurate solution.

IMU Data Processing

An IMU (inertial measurement unit) was used to record precise changes in position and orientation of the LIDAR scanner at a rate of 200 Hz.  All IMU data was processed post flight with a filter to integrate inertial measurements and precise phase differential GPS positions.  The resulting solution contains geodetic position, omega, phi, kappa, and time for subsequent merging with the laser ranging information.
*Processing environment Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS

ArcGIS item properties
*Name e174_pp1m
*Location file://\\Wpgcvn1212ap10\mb_lib\elv\e17\4_\pp\e174_pp.gdb
*Access protocol Local Area Network


Geographic extent
Bounding rectangle
West longitude -98.162125
East longitude -97.71247673
South latitude 49.96352794
North latitude 50.15082579

Geographic extent
Bounding rectangle
Extent type  Extent used for searching
*West longitude -98.161427
*East longitude -97.711475
*North latitude 50.151122
*South latitude 49.962146
*Extent contains the resource Yes

Extent in the item's coordinate system
*West longitude 560139.793590
*East longitude 592061.500000
*South latitude 5535211.500000
*North latitude 5555772.500000
*Extent contains the resource Yes

Resource Points of Contact 

Point of contact
Individual's name Roberto Infante
Organization's name Fugro GeoServices Ltd..
Contact's role  point of contact

Resource Maintenance 

Resource maintenance
Update frequency  not planned

Resource Constraints 

Limitations of use
Data not to be used beyond the limits of the source scale

Spatial Reference 

ArcGIS coordinate system
*Type Projected
*Geographic coordinate reference GCS_North_American_1983
*Projection NAD_1983_UTM_Zone_14N
*Coordinate reference details
Projected coordinate system
Well-known identifier 26914
X origin -5120900
Y origin -9998100
XY scale 99999.999999999985
Z origin -100000
Z scale 99999.999999999985
M origin -100000
M scale 10000
XY tolerance 2.0000000000000002e-005
Z tolerance 0.0001
M tolerance 0.001
High precision true
Latest well-known identifier 26914
Well-known text PROJCS["NAD_1983_UTM_Zone_14N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-99.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",26914]]

Reference system identifier
Dimension horizontal
*Value 26914
*Codespace EPSG
*Version 7.11.2

Spatial Data Properties 

*Level of topology for this dataset  geometry only

Geometric objects
Feature class name e174_pp1m
*Object type  composite
*Object count 272503

ArcGIS Feature Class Properties
Feature class name e174_pp1m
*Feature type Simple
*Geometry type Polyline
*Has topology FALSE
*Feature count 272503
*Spatial index TRUE
*Linear referencing FALSE

Spatial Data Content 

Image Description
Attribute described by cell values LiDAR

Band information
Symbol m

Triangulation has been performed No
Radiometric calibration is available No
Camera calibration is available No
Film distortion information is available No
Lens distortion information is available No

Data Quality 


Process step
Description LIDAR Data Preprocess: (1) Flight Line Data Acquisition/Quality Control Check: LiDAR data and the IMU files were processed together using LIDAR processing software. The data set for each flight line was checked for project area coverage, data gaps between overlapping flight lines, and tension/compression areas (areas where data points are more or less dense than the average project specified post spacing). Based on this check it appears the entire project area is covered without gaps. (2) Boresighting Process: Pre-processing of LiDAR corrects for rotational, atmospheric, and elevation differences that are inherent to LiDAR data sets. This process is called boresighting. LiDAR data was collected for bi- and cross-directional flight lines over the project area. Using an iterative process that involves analyzing raster difference calculations the Omega, Phi, Kappa angle corrections of the LiDAR instrument were determined. The corrections were applied to the LiDAR data set for the project area. (3) Vertical Accuracy Check: Extensive comparisons were made of vertical and horizontal positional differences between points common to two or more LiDAR flight lines. This was done for the project area. All flight lines were within project specifications for vertical accuracy. (4) LiDAR Intensity Check: An intensity raster for each flight line was generated. The raster was checked and verified that intensity was recorded for each LiDAR point. (5) Project Coordinate System: LiDAR preprocessing software outputs data to its corresponding UTM zone in meters and a GRS80 ellipsoidal height. LiDAR data was transformed to a project coordinate system of NAD83 UTM zone 14 N CGVD 28 Geoid HT 2.0 Meters. (6) Vertical Bias Correction: LiDAR has a consistent vertical offset. LiDAR ground points were compared to independently surveyed and positioned ground control points at both the airport bore-sight area and the project area. Based on the results of these comparisons, the LiDAR data was vertically biased down to the ground. (7) Project Ground Control Check: Comparisons between on-site ground survey control points and LiDAR data yielded the following results: Vertical Accuracy (RMSE): 0.039, Standard Deviation: 0.039, Mean Difference: -0.010, Number of Points: 14

Process contact
Individual's name Roberto Infante
Organization's name Fugro GeoServices Ltd.
Contact's role  point of contact

Process step
Description LiDAR Data Surfacing Process: (1) Raw LiDAR Data Set: LiDAR data in overlap areas of project flight lines was removed and data from all swaths was merged into a single data set. The data set was trimmed to the digital project boundary including an additional buffer zone (buffer zone assures adequate contour generation from the DEM). Resulting data set is the Raw LiDAR data. The Raw LiDAR data set was processed through a minimum block mean algorithm and points were classified as either bare earth or non-bare earth. User developed “macros” that factor mean terrain angle and height from the ground, were used to determine bare earth point classification. (2) LiDAR Surfacing Process: The surfacing process is a 2D-edit procedure that ensures the accuracy of the automated feature classification. Editors used a combination of imagery, intensity of the LiDAR reflection and tin-editing software to assess points. The resulting data set is 2D Surfaced Bare Earth. The LiDAR data is filtered using a quadric error metric to remove redundant points. This method leaves points where there is a change in the slope of surfaces (road ditches) and eliminates points from evenly sloped terrain (flat field) where the points do not affect the TIN LiDAR data. The resulting data set is 2D Surfaced/Filtered Bare Earth

Process contact
Individual's name Roberto Infante
Organization's name Fugro GeoServices Ltd.
Contact's role  point of contact

Process step
When the process occurred 2013-10-21 00:00:00
Description The 1-metre bare earth DEMs provided by Fugro were mosaiced. The raster mosaic was smoothed using Focal Statistics with MEAN and a 3x3 cell neighbourhood. The Spatial Analyst tool, Contour, was used to generate 1-metre contours from the smoothed DEM.

Process contact
Individual's name Tanya Dixon
Organization's name GeoManitoba
Contact's position GIS Specialist
Contact's role  distributor

Contact information
Type both
Delivery point 1007 Century Street
City Winnipeg
Administrative area Manitoba
Postal code R3H 0W4
Country CA
e-mail addressTanya.Dixon@gov.mb.ca

Geoprocessing history 

Process name
Date 2013-09-13 10:23:33
Tool location c:\program files\arcgis\desktop10.0\ArcToolbox\Toolboxes\Spatial Analyst Tools.tbx\Contour
Command issued
Contour "G:\LiDAR DATA\Poplar Point 2012 LiDAR\DEM\poplar_point.gdb\poplar_pt_smooth" "G:\LiDAR DATA\Poplar Point 2012 LiDAR\DEM\poplar_point.gdb\contours" 1 0 1
Include in lineage when exporting metadata No


Distribution format
Version GRID
*Name File Geodatabase Feature Class


Details for object e174_pp1m 
*Type Feature Class
*Row count 272503
Contour Lines
Definition source

*Data type OID
*Width 4
*Precision 0
*Scale 0
*Field description
Internal feature number.
*Description source
*Description of values Sequential unique whole numbers that are automatically generated.

Field Shape
*Alias Shape
*Data type Geometry
*Width 0
*Precision 0
*Scale 0
*Field description
Feature geometry.
*Description source
*Description of values Coordinates defining the features.

Field Id
*Alias Id
*Data type Integer
*Width 4
*Precision 0
*Scale 0
Field description
Description source

Field Contour
*Alias Contour
*Data type Double
*Width 8
*Precision 0
*Scale 0
Field description
Elevation in metres
Description source

Field Shape_Length
*Alias Shape_Length
*Data type Double
*Width 8
*Precision 0
*Scale 0
*Field description
Length of feature in internal units.
*Description source
*Description of values Positive real numbers that are automatically generated.

Metadata Details 

Metadata language English (CANADA)
Metadata character set  utf8 - 8 bit UCS Transfer Format

Metadata identifier 82B6E5B9-FEC7-4A2A-B237-22F3789CE31E

Scope of the data described by the metadata  dataset
Scope name* dataset

*Last update 2014-11-19

ArcGIS metadata properties
Metadata format ArcGIS 1.0
Metadata style North American Profile of ISO19115 2003
Standard or profile used to edit metadata NAP

Created in ArcGIS for the item 2013-09-13 10:23:33
Last modified in ArcGIS for the item 2014-11-19 13:55:22

Automatic updates
Have been performed Yes
Last update 2014-11-19 13:39:11

Metadata Contacts 

Metadata contact
Individual's name Roberto Infante
Organization's name Fugro GeoServices Ltd.
Contact's role  point of contact

Thumbnail and Enclosures 

Thumbnail type  JPG

FGDC Metadata (read-only) 

Entities and Attributes