QCoherent Software, LLC

Exporting LIDAR Data to Raster Files

LIDAR data may be converted into rasters or gridded data representing elevations, or even derived values such as slope, hillshade (brightness), aspect, or intensity. This may be useful for better viewing of the LIDAR data or modeling that requires raster inputs rather than vector-oriented inputs such as points or TIN surfaces. LIDAR data is exported in one of two raster formats: ASCII and Binary. These two formats are industry standards and can be used by ArcGIS™ or ArcView™ 3.x to import to an ESRI™ Grid format.

Note

It is highly recommended to use binary rasters over ASCII rasters, as the file sizes will be smaller, and the export of the raster will always be faster using the binary raster format.

Learn more about ASCII Raster Files

Learn more about Binary Raster Files

Grid cell values can also be stored in an ASCII XYZ file. The text file contains the easting (x coordinate) and northing (y coordinate) coordinates of the center of the grid cell, as well as each exported surface attribute> (i.e., elevation, slope, aspect, hillshade, intensity) as columns in the file separated by the specified delimiter.

Slope, Aspect, and Hillshade Rasters

Typically, elevation data is the value that is exported to raster files. However, other derived values from interpolated elevations such as slope, aspect, and hillshade can be exported as well. These derived values can be used in visualization applications or for modeling applications.

Examples of Derived Rasters

Shaded Relief Map using Hillshade or Brightness Values

 
 

Map of Slope - High Slopes (Red) to Low Slopes (Green) blended with hillshade

 
 
Map of Aspect  

Learn more about hillshades or brightness

Learn more about slope

Learn more about aspect

Using Breakline Enforcements

As a part of generating an elevation surface, breaklines may be used to enforce significant topographic breaks in the surface, such as stream centerlines or ridge lines. Breakline enforcement can significantly influence the aesthetics or functionality of a surface model. When exporting contours, the use of breaklines can provide a much more cartographic display of contour lines. Breakline sources can be any layer within the map that is suitable to be used as breaklines.

Example of the effect of using breaklines

Not using breaklines
Using breaklines

Learn more about breakline enforcement

How to Export LIDAR Data to Raster Files

  1. Open the LP360 Export Wizard by clicking the Export LIDAR Data command on the LP360 toolbar. The Export Wizard dialog will open with the Step 1 of 3 page displayed.

  2. Click the arrow in the Export Type list, and select Surface.

  3. Click the arrow in the Surface Method list and select either Triangulation (TIN) or Inverse Distance Weighted (IDW) as the surface method to export.

    Learn more about surface methods

  4. Enter a No-Data value for the raster files.

  5. Enter a Cell Edge Length greater than zero Map Units or click the 'Auto Compute Cell Size' checkbox.

  6. If you selected Triangulation (TIN) as the export surface method, click Breakline Enforcements to define the breaklines to export. The Breakline Enforcement Property Page will open.

    1. On the Breakline Enforcement dialog, define which layers/sources to use as breaklines.

    2. Click OK to close the Breakline Enforcement dialog.

  7. If you selected the Distance Weighted (IDW) export surface method, do the following:

    1. Enter a Power greater than zero.

    2. Select Fixed Radius and enter a radius value greater than zero Map Units.

      OR

      Select Minimum Number of Neighbors and enter the minimum number of points to use to interpolate elevations.

      Also, if you are using the Minimum Number of Neighbors option, click the Maximum Search Window check box if you want to specify a maximum search window size, and then enter the value in Map Units. If you leave this check box unselected, the system will determine a maximum search window size using average point densities of the LIDAR data.

  8. In the Surface Attribute to Export list, select the surface attribute(s) to export.

    Notes 
    • For exporting the slope, clicking Slope in the list displays a tab next to the Surface tab. Click the Slope tab and click Calculate in Percent if you want the slope calculation to be in percents. If not selected, the slope is calculated in degrees.

    • For exporting the hillshade attribute, clicking Hillshade in the list displays a tab next to the Surface tab. Click the Hillshade tab and enter the azimuth and altitude of the sun/light source. The default values are set up to produce a standard shaded relief map.

    • For exporting contours, click Contours in the list and follow the instructions for exporting contours.

  9. Click the arrow on the Export Format list, and select ASCII Raster, Binary Raster, ASCII XYZ, ESRI Binary Grid, GeoTIFF, IMG, or Cloud Optimized GeoTIFF. (The "ESRI ArcGrid" option is only available in the LP360 ArcGIS extension.)

  10. If exporting to ASCII XYZ text files, click the Include Headers in File(s) checkbox if you want to include the column names for each exported attribute on the first line of the text file. Then select the Delimiter (i.e., comma, space, or tab) to use for separating the columns in the text file.

Tips

  • When using the IDW surface method, use caution when deciding the radius or the minimum number of points to use. Take into account the density of LIDAR data and the point filter used in the export. Large radii and minimum neighbors may result in slow exports.

  • Exporting areas with large voids, such as lakes or other large water bodies, may require adjustments to default export settings. Please read Surface Exports with Large Void Areas for more information.

  • When exporting to the ESRI ArcGrid format, the file naming scheme using X and Y values when cookie cutting by tiles may not be practical due to the length of the resulting filename. For all other naming options, if the resulting filename begins with a numeric value (i.e., 0-9), a "g" will be inserted at the beginning of the filename to conform to the ESRI ArcGrid naming limitations.