WhiteboxTools v1.3.0

• Tools will now output DEFLATE compressed GeoTIFFs when the --compress_rasters parameter is used.
• Added support for a newly developed compressed LiDAR data format, the ZLidar file. All tools
  that accepted LAS file inputs and produced LAS outputs can now use '*.zlidar' files as well. I
  have also added the LasToZlidar and ZlidarToLas tools to perform conversions. While the ZLidar
  format does not yield compression rates quite as good as the popular LAZ file format, you can
  expect ZLidar files to be between 20-30% of the size of the equivalent LAS file. A file
  specification will be published in the near future to describe the open ZLidar data format.
• Added the AsciiToLas tool.
• Added the ContoursFromRaster tool for creating a vector contour coverage from a raster surface model (DEM).
• Added the ContoursFromPoints tool for creating a vector contour coverage from vector points.
• Added the UpdateNodataCells tool.
• Modified the Slope tool to optionally output in degrees, radians, or percent gradient.
• Modified the Mosaic tool, which now runs much faster with large numbers of input tiles.
• The vector-to-raster conversion tools now preserve input projections.
• Fixed a bug in the RasterToVectorPolygons tool.
• Fixed several bugs in the MergeTableWithCsv tool.
• Modified the FillMissingData tool to allow for the exclusion of edge-connected NoData cells from the operation.
  This is better for irregular shaped DEMs that have large areas of NoData surrounding the valid data.
• The LidarConstructVectorTin tool has been depreciated. The tool was not creating the proper output.
  Furthermore, since the number of points in the average LiDAR tile is usually many million, this tool
  would usually produce Shapefiles that exceed the maximum allowable number of shape geometries. If
  a vector TIN is required for a LiDAR point set, users should convert the file to a Shapefile and then
  use the ConstructVectorTin tool instead. And of course, if you are interested in a raster TIN from a
  LiDAR file, use the LidarTinGridding tool instead.
• FlattenLakes now handles multipart lake polygons.