Auckland Lidar 1m DEM (2013)
LINZ - Land Information New Zealand
This layer contains the DEM for LiDAR data from the Auckland region captured in 2013.
The DSM is available as layer [Auckland Lidar 1m DSM (2013)](http://data.linz.govt.nz/layer/3406).
The index tiles are available as layer [Auckland Lidar Index Tiles (2013)](http://data.linz.govt.nz/layer/3407).
The LAS point cloud and vendor project reports are available from [OpenTopography](https://portal.opentopography.org/datasets?loc=New%20Zealand).
Lidar was captured for Auckland Council by NZ Aerial Mapping & Aerial Surveying Limited. The capture of the data commenced on 17th July and was completed by the 23 November 2013. The datasets were generated by both ASL and NZAM. All raw point cloud data was produced by NZAM & ASL prior to data being sent to Genesys International for the data classification and product generation. The survey area includes the Auckland city urban area and adjacent rural land covering approximately 2250 square kilometers. Data management and distribution external to Auckland Council is managed by Land Information New Zealand.
•DEM: 6423 asc files in NZTM projection, tiled into a 1:1,000 tile layout
•DSM: 6423 asc files in NZTM projection, tiled into a 1:1,000 tile layout
•Pont cloud: 8224 las files in NZTM projection, tiled into a 1:1,000 tile layout
Data was collected at > 1.5 point/square metre point density. Attributes include:
-Adjusted GPS time
Vertical accuracy specification is +/-0.2m (@ 95% confidence)
Horizontal accuracy specification is +/-0.6m (@ 95% confidence)
Verical Datum is NZVD2009
Aerial Photography was captured using Vexcel's digital UCLp and UCE cameras:
5-6 January 2015, 11 January 2015, 18-19 February 2015, 28 February 2015, 1-2 March 2015, 21
The equipment used in this project included:
Cessna 206 single engine aircraft equipped with airborne GPS and flight management systems
Optech ALTM3100 LiDAR sensor
Rockwell Aerocommander 680 aircraft equipped with airborne GPS and flight management systems
Cessna 402B twin engine aircraft equipped with airborne GPS and flight management systems
Optech ALTM3100 LiDAR sensor
Optech Orion M200 LiDAR sensor
Optech Orion H300 LiDAR sensor
NZAM replaced the Orion M200 LiDAR system with the Orion H300 system on 21 October 2013.
The subcontractor resources used on this project were:
Ground Control Surveys – Opus International and C&R Surveyors (Auckland)
LiDAR Classification and product generation – Genesys International Corporation (India)
ASL’s acquisition commenced on 17th July 2013 and ended on 21st October 2013
NZAM’s acquisition commenced on the 29th July 2013 and ended on 23rd November 2013
No imagery was captured with this project
The key outputs from each and every sortie included:
Raw LiDAR data
Raw POS data
Flight Log report including any notable conditions encountered during capture
Flight coverage KML file for each sortie
Point cloud generation:
NZAM/ASL used Optech’s LMS (LiDAR Mapping Suite) Professional software for the creation of the laser point cloud data and for the examination, comparison and refinement of the fit of laser points between flightlines.
The point cloud data is output from LMS in LAS v1.2 file format and each flightline of data stored in an individual file. The file names incorporate the unique sortie identifier in them so as the origin of the data is traceable. The las files were then examined in LiDAR production software - TerraSolid as well as LASTools and Global Mapper to complete the various checks on the data against project requirements including point density, point distribution and average point spacing. All point cloud data conformed to project requirements. The data in the LAS files output from LMS are in terms of NZTM map projection and NZGD2000 ellipsoidal heights. This data was then loaded into a TerraScan software project – NZAM and LAStools-ASL , tiled into NZTopo50 1:1,000 tiles and converted into Auckland 1964 vertical datum. (Auckland Council converted the heights to NZVD2009 before providing the data to LINZ.) An initial comparison of the unclassified point data and the Ground Check Surveying data was made to check that there are no gross positional and height errors in the dataset.
All point cloud deliverables were delivered in the following 2 formats:
Both LAS and SHP files include all standard attributes, including:
GPS times recorded as adjusted GPS time, at a precision sufficient to allow unique timestamps for each pulse
Point cloud classification:
Point cloud classification for this project was undertaken by Genesys as the selected mapping subcontractor. Genesys used TerraScan by TerraSolid for point cloud classification.
TerraScan interfaces to Bentley Microstation, enabling both batch and manual visual editing of data to take place. The DTM Point Cloud Classification process for this project involved, not only the identification of laser returns from the ground, but also the separation of the above ground points in to various classes. Classification of the point cloud followed the modified ASPRS classification scheme below:
0 - Created, never classified
1 - Unassigned classification
2 - Ground
3 - Low vegetation
4 - Medium vegetation
5 - High vegetation
6 - Building structures
7 - Low/high noise
9 - Water
Classification of point clouds was done to Level 3 as set out in the ICSM LiDAR specifications for NZ
Classification of ground points was to an accuracy of 99%
All water points are included in the Raw point cloud but removed from the DTM products
All the points in the LAS files output from LMS have their class set to 0
The software algorithms that attempt to classify points into classes such as Ground, Medium vegetation and Buildings do so by examining and testing the relationships between points and their neighbours. A discrete LIDAR return from water has no unique features that allow it to be separated from a return from the ground, and so the classification of points into the Water class is a manual process achieved by visualising the data on a workstation monitor and ‘paint brushing’ the points from their current class into the Water class.
The key processing steps undertaken were:
Prepare and run automated overlap point and ground point classification routines customized for the unique combination of terrain cover and land-use within the project area
Manually edit the auto-classified data to remove artefacts, re-classify incorrectly coded points into and out of the Ground class and re-classify incorrectly coded points into the Water class.
Prepare and run automated point classification routines to populate the Vegetation classes and Building, Structures class.
Supplementary points (LAS Standard Synthetic points) were added to the dataset to facilitate the production of contours and DEM/DSM products. Supplementary points are densely spaced points along breakline features that are manually mapped into the dataset, typically spaced by 0.3m. Such points were added around ponds, lakes and the coastline needed to ensure that contours don’t run into these areas, as well as the points added along the edge of significant streams and rivers to help ensure that contours created through these areas have a natural hydrological flow appearance to them. These points were integrated into the point cloud data but identifiable by their separate class code.
Manual point classification work requires constant attention to detail and interpretation of complex geographies. The work was undertaken in a 2D workstation environment. The point data is viewed in plan and cross-section perspectives and tools are used to move points into and out of classes. The manual classification work for this project was undertaken by Genesys Incorporated in India. The classified data was subject to a two stage quality check. First examined by a dedicated team of QA/QC staff at Genesys and then by staff in NZAM and Aerial Surveys. The last, and very important, task performed during DTM Point Cloud Classification is to compare the ground check survey data with the DTM (ground) points. The computed height difference statistics were recorded and reported within the metadata. Positional checks were also be made, recorded and reported.
All point classifications identified during processing were included in the raw point clouds (e.g. where points are identified to be 'noise', this was attributed as such in the raw point cloud data).
Note that the raw point clouds were post-processed to meet the accuracy specifications of the project. No uncorrected / uncalibrated raw data was supplied.
Sample point cloud filename: RPC_AZ31_1026_2013.las
Bare earth DEM production:
A raster Digital Elevation Model (DEM) was interpolated from the DTM points with the following specifications:
1m cell size.
Format is ESRI ASCII
The DEM was generated from the LiDAR DTM (ground) points and define the bare earth surface.
DEM heights reference the NZVD2009 vertical datum. (Auckland Council adjusted this from the Auckland 1946 datum to NZVD2009 before providing the data to LINZ.)
Void areas (i.e. areas outside the project boundary but within any tiling scheme) are coded using a unique "NODATA" value.
Hydro-flattening undertaken for natural and man-made water bodies and water courses as defined below:
o Non-tidal water bodies with a surface area greater (>) than 625m2
o Non-tidal water courses greater than 30m nominal width. This should not unnecessarily break a stream or river into multiple segments.
o Flat and level bank-to-bank with a gradient following the immediate terrain
o Water courses should break at road crossings and bridges
o Sinks must not be filled
o The entire water surface edge must be at or immediately below the surrounding terrain
o Tidal variations over the course of the collection or between different collections may result in discontinuities along shorelines.
Sample DEM filename: DEM_AZ31_1026_2013.asc
A raster Digital Surface Model (DSM) interpolated from 1st returns with the following specifications:
1m cell size.
Format is ESRI ASCII
The DSM to be created from 1st return LiDAR points and to include ground and non-ground points such as vegetation and buildings.
DSM heights reference the NZVD2009 vertical datum. (Auckland Council adjusted this from the Auckland 1946 datum to NZVD2009 before providing the data to LINZ.)
Void areas (i.e. areas outside the project boundary but within any tiling scheme) coded using a unique "NODATA" value.
Sample DSM filename: DSM_AZ31_1026_2013.asc
-37.320988 174.391862 -36.337212 175.135059