= LiDAR Data Delivery Contents = This page describes the file formats and delivery structure used in the LiDAR data deliveries. == Delivery Structure == A standard delivery directory contains the following sub directories: * '''bin''' - Contains useful post-processing applications * [wiki:Processing/LidarNoisyPoints pt_cloud_filter] - Windows and Linux versions of software to remove classified points from ASCII files. * [#DEM dem] - Contains a Digital Elevation Model suitable for use with APL hyperspectral processing software. * [#PDFFILES doc] - Contains a copy of the most recent data quality report. * '''flightlines''' - Contains the processed LiDAR point cloud data. * [#LAS1.0FILES las1.0] - Contains LAS version 1.0 point data files. * [#LAS1.3FILES las1.3] - Contains LAS version 1.3 point data and waveform data files. * [#ASCIILIDARFILES ascii] - Contains ASCII point data files. * [#PDFFILES logsheet] - Contains a logsheet that gives a brief overview of the flown project * [#JPGFILES screenshots] - Contains JPEG files of level-3 processed data including mosaics. === Digital Elevation Model === #DEM The format of the delivered Digital Elevation Model (DEM) is band Sequential (BSQ) ENVI format binary data. The projection is in WGS-84 latitude and longitude, with heights relative to the WGS-84 spheroid. There is an accompanying ASCII text header file containing the required information to read the binary data. In most cases, the LiDAR data will have been 'patched' with ASTER data. This will extend the coverage of the DEM which is often required for processing the hyperspectral data. === ASCII LiDAR Point Clouds === #ASCIILIDARFILES The processed LiDAR data are delivered in multiple formats. One such format is as an ASCII list. These point cloud files contain a space separated summary of the data for each point, with each point being described on a separate line of the file. The ordering of the point data is described [wiki:FAQ/lidarasciiformat here]. The files can be opened and viewed in any simple text reader but because of their large size this may not be appropriate. It is possible to import these data in to GIS systems such as GRASS or ENVI. === LAS LiDAR Point Clouds === The processed LiDAR data are delivered in multiple formats. One such format is as LAS files. These are currently delivered by ARSF-DAN in two possible formats depending on whether full waveform data has been collected or not. The LAS files are binary data files that have a series of headers and then a collection of data points. They are the standard data type for storing LiDAR data. They can be read by most GIS systems that process LiDAR data, or using the various free software libraries such as [http://www.cs.unc.edu/~isenburg/lastools/ LASTools] and [http://liblas.org/ libLAS]. ==== LAS v1.0 ====#LAS1.0FILES These LAS files are delivered by standard and do not have the capacity for storing waveform data. Detailed information about LAS 1.0 can be found in this document: [http://www.asprs.org/a/society/committees/standards/asprs_las_format_v10.pdf] ==== LAS v1.3 ====#LAS1.3FILES These LAS files are delivered only if full waveform data has been collected. Detailed information about LAS 1.3 can be found in this document: [http://www.asprs.org/a/society/committees/standards/LAS_1_3_r11.pdf] === Screenshot images === #JPGFILES The screenshots are supplied as JPEG images. This is a type of compressed image format that can be opened by most image viewers. The supplied screenshots include one of the DEM and one of the LiDAR intensity values. If the flight is in the UK and one where Ordnance Survey licensing allows, the intensity images will contain vector overlays to show the expected accuracy of the geocorrection. === Read-Me, Logsheet and Data quality report === #PDFFILES The documents included with the delivery are in PDF. This is an open, platform independent standard for distribution of documentation, which allows graphical, text and tabular data to be included in the same file. Free viewers are available for displaying these documents.