North Vancouver Area Classified LiDAR 2022
Classified LiDAR LAS files for the area shown in magenta on the thumbnail image. The collection year is 2022. Includes data for: District of North Vancouver, City of North Vancouver. Download size is approximately 30.54GB. The Horizontal Coordinate System has been defined in the header of the accompanying .LAS file by Metro Vancouver GIS staff as:
EPSG:3157
The vertical datum used in the collection of this LiDAR data was CGVD28GVRD2018. This is not available as an option to specify in ArcGIS Pro software. According to MV Surveyors and Aeroquest, EPSG:10588 (Canadian Geodetic Vertical Datum of 1928, height transformation version 2.0) is the closest available vertical coordinate system that is included in the default ArcGIS Pro installation, and in the Lower Mainland the difference between EPSG:10588 and CGVD28GVRD2018 is typically 1 to 2 centimeters.
This LiDAR achieves British Columbia LiDAR standards Quality Level 3.
============================================================================================= The following information was taken from the LiDAR Processing and Accuracy Report that accompanied the LiDAR data provided by Aeroquest Mapcon Inc. Note that the full report is available on the Metro Vancouver open data portal. =============================================================================================
-
Field Operations Nine missions were flown between April 4th and September 27th, 2022, to cover the area successfully. The Early Spring lines were acquired between April 7th and August 6th, the Late Spring lines were acquired on August 24th and 25th, and the final re-flight was on September 27th. Surveying the entirety of Metro Vancouver including the watersheds posed a significant challenge due to the congested airspace that is managed to the minute by YVR Air Traffic Control.
-
Lidar Equipment A Riegl VQ-1560ii lidar sensor (two lasers in one unit) equipped with a GSM4000 gyro-stabilized mount was used for this project. It was installed in a Piper Aztec (registration C-GXNF) which is owned and operated by Kisik Aerial Surveys Inc. Scanner parameters used for acquisition.
-
Positioning Information This project was based on the NAD83 (CSRS) v6 (2002) horizontal datum which is derived from ITRF2008 (International Terrestrial reference Frame. The vertical datum used was, CGVD28GVRD2018 using the Metro Vancouver Geoid, with the data projected to UTM Zone 10. The trajectory was based on the BCLC base station in Langley using differential GPS processing. POSPac software was used for processing the trajectory.
-
Point Cloud Edit Ingest and automated classification. Upon receipt of the raw point cloud data it was subjected to a basic quality control process, primarily checking for consistent calibration (agreement) between flight swathes and acceptable point density and coverage of the client AOI. The software package Terrasolid, was used to create the project file for the calibrated point cloud data ensuring the required projection system, datums and units are included in all aspects of the LiDAR classification.
The data was initially auto- classified within Terrasolid into the following classes: 0 - unclassified never classified 2 - bare earth 7 - noise This autoclassification was inspected to ensure the software settings were giving the classification an appropriate/accurate initial class assignment. -
Manual classification and Quality Control Following successful autoclassification run(s) a series of manual classification edits were accomplished to ensure data fidelity and accuracy. Common examples of these edits include reassigning points initially classified as class 2 (bare earth) to class 1 (unclassified points) and the movement of points, erroneously classified as class 0 (unclassified) to class 2 (bare earth) points. Water points are commonly manually assigned to class 9 (water) as the auto-classification often fails at this task. 100 percent of the LiDAR data is subjected to this quality control process. Quality Assurance Following the manual editing/Quality control process the data is again combed in a quality assurance process. -All water areas are checked to ensure correct classification. -10% of all areas were re-checked for an evaluation of quality and adherence to specifications. If issues are found in this step the data would be returned for further manual edits.
Click here to download the full 2022 LiDAR Processing and Accuracy Report
Datasets available for download
This dataset has no data
Additional Info
| Field | Value |
|---|---|
| Last Updated | June 16, 2026, 20:16 (UTC) |
| Created | June 16, 2026, 20:16 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
North Vancouver Area Classified LiDAR 2022 |
|
Description
A description of the dataset.
|
Classified LiDAR LAS files for the area shown in magenta on the thumbnail image. The collection year is 2022. Includes data for: District of North Vancouver, City of North Vancouver. Download size is approximately 30.54GB. The Horizontal Coordinate System has been defined in the header of the accompanying .LAS file by Metro Vancouver GIS staff as: The vertical datum used in the collection of this LiDAR data was CGVD28GVRD2018. This is not available as an option to specify in ArcGIS Pro software. According to MV Surveyors and Aeroquest, EPSG:10588 (Canadian Geodetic Vertical Datum of 1928, height transformation version 2.0) is the closest available vertical coordinate system that is included in the default ArcGIS Pro installation, and in the Lower Mainland the difference between EPSG:10588 and CGVD28GVRD2018 is typically 1 to 2 centimeters. This LiDAR achieves British Columbia LiDAR standards Quality Level 3. ============================================================================================= The following information was taken from the LiDAR Processing and Accuracy Report that accompanied the LiDAR data provided by Aeroquest Mapcon Inc. Note that the full report is available on the Metro Vancouver open data portal. =============================================================================================
|
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
32026873.46 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2026-04-28 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
public |
|
License
License used to access the dataset.
|
Open Government License |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://open-data-portal-metrovancouver.hub.arcgis.com/datasets/metrovancouver::north-vancouver-area-classified-lidar-2022 |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
agoladmin4_metrovancouver |
|
Contact Point
Who to contact regarding access?
|
Metro Vancouver |
|
Contact Point Email
The email to contact regarding access?
|
[email protected] |
|
Publisher
Publisher of the dataset.
|
Metro Vancouver |
|
Publisher Email
Email of the publisher.
|
|
|
Author
Author of the dataset.
|
agoladmin4_metrovancouver |
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
2026-04-29 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
4210878817624e3dac39026838131e43 |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://open-data-portal-metrovancouver.hub.arcgis.com/datasets/metrovancouver::north-vancouver-area-classified-lidar-2022 |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
Metro Vancouver |
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
|
|
Number of data columns
If tabular dataset, total number of unique columns.
|
|
|
Number of data cells
If tabular dataset, total number of cells with data.
|
|
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments