Skip to content

WhiteboxTools v0.15.0
Compare
Choose a tag to compare
@jblindsay jblindsay released this 10 Mar 19:13
· 369 commits to master since this release
v0.15
8839309
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Version 0.15.0 (03-03-2019)

  • The following tools were added to the project:
    BoundaryShapeComplexity
    NarrownessIndex
    ShapeComplexityIndexRaster

  • Fixed a bug with the PanchromaticSharpening tool.

  • Previously, if a LAS v1.4 file were input to a tool, the output LAS file, which is currently
    always in LAS v1.3 format, would not correctly translate the 64-bit information (point
    return, number of returns, classification) into 32-bit format. I have added the
    get_32bit_from_64bit function to handle this translation more gracefully; albeit it is
    still a lossy translation where returns greater than 5 are ignored and classification
    values greater than 31 are lost.

  • Added a maximum triangle edge length parameter to the LidarTinGridding tool to allow
    for the exclusion of large-area triangles (i.e. low point density) from the gridding.

  • The NormalizedDifferenceVegetationIndex tool has been renamed to NormalizedDifferenceIndex
    to indicate the more general nature of this tool (i.e. NDVI, NDWI, OSAVI, etc.).

  • Significant changes have been made to the BreachDepressions tool to make it more in-line
    with the behaviour of the GoSpatial algorithm described in the original Lindsay (2016)
    paper. These changes include: 1) the inclusion of an optional parameter to fill single-cell
    pits prior to breaching, 2) the addition of a --flat_increment parameter, which overrides
    the automatically derived value assigned to flat areas along breach channels (or filled
    depressions), and 3) the tool now performs a fast post-breach filling operation, when
    run in constrained-breaching mode (i.e. when the user specifies values for either
    --max_depth or --max_length, placing constraints on the allowable breach channel size).

Assets 5
Loading