The LAS To Raster function is used to render lidar data stored using the LAS file format. The function will be used when you add lidar data to a mosaic dataset using the LAS raster type. With this function, you need to specify both input and output properties. Also, due to the resolution of the data and the time it can take to convert the point data to raster data, this function can write preprocessed raster data files to an output location (cache).
LAS is an industry format created and maintained by the American Society for Photogrammetry and Remote Sensing (ASPRS). This function supports version 1.0, 1.1, 1.2, and 1.3.
The LAS To Raster function allows you to add the LAS data by selecting individual LAS files or selecting one or more folders containing LAS files. When adding a folder, all LAS files in the folder will be added to the mosaic dataset as individual items. Therefore, you will see each LAS file's extent and properties (such as average point distance) in the mosaic dataset. However, for folders with hundreds or thousands of LAS files, you may want to add the LAS folder as one dataset, thereby creating only one item in the mosaic dataset. To do this, check Treat each folder as a dataset. When using this option, the LAS files must all use the same spatial reference system; otherwise, they will not be added correctly.
The output location for the preprocessed raster data files defaults to the location next to the geodatabase where the mosaic dataset is stored, for file or personal geodatabases. When using a geodatabase stored in ArcSDE, they are stored within the geodatabase, by default. This location can be changed on the General tab of the LAS To Raster function dialog box.
Input properties
Input—The path and name of the LAS files or folder containing the LAS files. You can modify this value if the input is moved. Using a folder is recommended when using many LAS files as multiple partial signals.
Return types—A single pulse from a laser can be returned as multiple signals as it reflects off objects at different heights on or above the ground, resulting in pulses returning to the sensor at different times. Therefore, the return type can be used to differentiate ground returns from other returns, such as tree canopy. You can select one or more return values.
Class types—Classifications are defined for the points by the provider of the LAS files. You can select Any to add all the points regardless of their classification; you can also select more than one. The classification types from the LAS specification 1.3 .pdf
are Any, (0) Never Classified, (1) Unclassified, (2) Ground, (3) Low Vegetation, (4) Medium Vegetation, (5) High Vegetation, (6) Building, (7) Noisy Low Point, (8) Model Key Point, and (9) Water.
Data types—Defines the value to represent when generating the surface.
- Las Data Z—Uses a height (elevation) value.
- Las Data Intensity—Intensity is a measure, collected for every point, of the return strength of the laser pulse that generated the point. It is part of the light cone that is reflected back to the plane. Its value depends on the portion of the cone that was reflected back (for example, roof—100%, leaf—much less) and the reflectivity of the surface hit. If the cone hits a mirror at an angle, nothing comes back. Intensity is used as an aid in feature detection and extraction, in lidar point classification, and as a substitute for aerial imagery when none is available. If your lidar data includes intensity values, you can make images from them that look something like black-and-white aerial photos.
Output properties
Output properties affect how the LAS data is converted from points to raster and is displayed.
Pixel size—The minimum pixel size that will be generated to create the raster. Generally, if the pixel size is three times greater than the point spacing, the voids in the data should be filled (unless, for example, the voids are due to water).
The pixel size must be specified when adding the LAS data to the mosaic dataset.
It's important to understand that the point spacing estimates are for either all points or only the points per return type or class type. For example, with first or last return types, the point density is high, whereas, if you select fifth return types only, the point density will be much less and the average point spacing will be much higher. Typically, the Ground class type has many points, but there will be many voids due to buildings or trees that are removed. If you select buildings only or large trees only, there are even more voids and, therefore, a smaller point density and larger average point spacing.
It is better to go with a pixel size that is several times larger than the average point spacing but small enough to identify gaps or voids. A reasonable size is four times the point spacing. For example, if your data is sampled at 1 meter and your pixel size is 4, you can expect, on average, to get 16 points in a pixel.
In most cases, the point spacing is supplied by the vendor along with the point data files and can be found in a metadata file. If the point spacing is unknown and you have the ArcGIS 3D Analyst extension, you can use the Point File Information tool to obtain a point spacing for the supplied data files; otherwise, enter 1, add the LAS files, and check the mosaic dataset's attribute table for the correct value. If necessary, you can edit the value you entered in the LAS To Raster function.
Binning—This is the process of determining the value of a pixel by examining the points that fall within the pixel to determine the final value. It uses the following inputs:
Cell aggregation type—Determines which z-value to use when generating the raster surface when there is more than one point to consider.
- Maximum—Uses the largest z-value
- Minimum—Uses the smallest z-value
- Mean—Uses a mean (average) of all the z-values
- Sum—Uses the sum of all the z-values
- Mean Distance Weighted—Uses the z-value resulting from a weighted mean distance
Void filling—Voids occur when there are no points collected within the area represented by a pixel in the resultant raster. Voids are often caused by water bodies or by class type selection or exclusion. Void filling is most commonly used when generating a ground surface.
- None—No voids will be filled.
- Simple—Computes the average using up to eight neighboring cells (with values). Only small voids will be filled.
- Plane Fitting/IDW—A Simple method is applied first and a plane fitting method is used; however, if the fitting error is too large, an inverse distance weighted algorithm is applied. If the width or height of the bounding box around the void is larger than the Maximum width value, the void is not filled.
- Maximum width—The width value used for void filling when using the Plane Fitting/IDW void filling method. This is defined in the units of the LAS file's spatial reference system. No maximum width will be used if this is blank or a value of 0 is entered.
To learn about the limitations of using Plane Fitting/IDW, see Adding lidar data to a mosaic dataset.
Triangulation—Uses Delaunay triangulation to create a surface from a network of triangular facets defined by nodes and edges that cover the surface, which is then rasterized. This is recommended for low density lidar data, when binning can't be used to create an appealing surface, or when zooming in to an area that will cause a low density lidar surface to be displayed.
Z factor—The scaling factor used to convert the z-values. The scaling factor is used for two purposes: (1) to convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees, and (2) to add vertical exaggeration for visual effect.
To convert from feet to meters or vice versa, see the table below. For example, if your z-units are feet and your mosaic dataset's units are meters, you would use a value of 0.3048 to convert your z-units from feet to meters (1 foot = 0.3048 meters).
This is also useful when you have geographic data (such as GCS_WGS84 using latitude and longitude coordinates) where the z-units are in meters. In this case, you need to convert from meters to degrees (0.00001; see below). The values for degree conversions are approximations.
Conversion factor between feet and meters
| From | To | ||
|---|---|---|---|
Feet | Meters | ||
Feet | 1 | 0.3048 | |
Meters | 3.28084 | 1 | |
To apply vertical exaggeration, you must multiply the conversion factor by the exaggeration factor. For example, if both z-values and dataset coordinates are meters and you want to exaggerate by a multiple of 10, the scaling factor would be unit conversion factor (1 from the table) multiplied by the vertical exaggeration factor (10), or 10. As another example, if the z-values are meters and the dataset is geographic (degrees), you would multiply the units conversion factor (0.00001) by 10 to get 0.0001.
Cache folder—The location where the cached LAS surfaces will be stored. By default, the cache is generated and stored in a folder next to where the mosaic dataset resides. This folder has the same name as the geodatabase, with a .cache extension. However, if the mosaic dataset is created in an ArcSDE geodatabase, the cache will be created within that geodatabase.
Number of cached surfaces—The maximum number of caches that can be created using different properties (in this dialog box) for this surface. For example, you might add the LAS data to create a surface displaying all the points, but you also want to visualize only the points that are classified as ground from the same dataset; therefore, you can create two caches to visualize this data in two ways. Entering a value of 0 will disable caching or clear an existing cache.
Disconnect from LAS files—Check this box if you do not want your mosaic dataset to communicate with the source LAS files. If you use this option, the cache will be used to render the mosaic dataset. Cached files are faster than accessing the source LAS files; this is especially true when serving a mosaic dataset that has the source LAS files experiencing low performance due to a poor network connection or due to slowdown with the data server. If the service becomes too slow, it may become unusable.
Rendering the LAS data can be computationally intensive. Without the cache, you may have to wait several minutes for some surfaces to display. The cache is generated when the following occur:
- You view the mosaic dataset where the LAS files are used to generate the mosaicked image.
- The overviews are built.
- The Synchronize Mosaic Dataset tool is run with Build Item Cache checked.
The cache will be updated in the following scenarios:
- The input has been updated.
- The cache has been deleted or is missing.
- The function parameters are set to define a different surface than the one that matches the cache (for example, use a different Return type).