• whitebox version: 1.5.0
• Python version: 3.6.10
• Operating System: Ubuntu 20.04

Description

I would like to use WhiteboxTools v1.5.0 in order to use

https://github.com/NCAR/wrf_hydro_gis_preprocessor

but unforuntately, I can't pin WhiteboxTools to v1.5.0, despite being aware of issues like this:

https://stackoverflow.com/questions/67495221/conda-environment-has-access-to-system-modules-how-to-prevent

What I Did

My steps to reproduce on Ubuntu 20.04 are:

rm -rf ~/miniconda3 ~/.condarc ~/.conda ~/.continuum bash Miniconda3-py38_4.12.0-Linux-x86_64.sh conda init conda config --add channels conda-forge conda create -n wrfh_gis_env -c conda-forge python=3.6 gdal netCDF4 numpy pyproj whitebox=1.5.0 conda activate wrfh_gis_env (wrfh_gis_env) > python

from whitebox.whitebox_tools import WhiteboxTools print(' Using {0}'.format(WhiteboxTools().version().split('\n')[0])) Using WhiteboxTools v2.1.0 by Dr. John B. Lindsay (c) 2017-2021

Please note that outside of wrfh_gis_env, I do not have access to WhiteboxTools v2.1.0:

python3.8

from whitebox.whitebox_tools import WhiteboxTools Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'whitebox'

Does anyone know how I might pin WhiteboxTools to v1.5.0?

PS - Even from inside wrfh_gis_env, it's still not clear where v2.1.0 comes from:

conda activate wrfh_gis_env (wrfh_gis_env) > python

import whitebox as ; print(.path) ['/home/soft/miniconda3/envs/wrfh_gis_env/lib/python3.6/site-packages/whitebox']

conda deactivate cd /home/soft/miniconda3/envs/wrfh_gis_env/lib/python3.6/site-packages/whitebox ls -al

drwxrwxr-x 4 4096 Jun 28 15:54 WBT -rw-rw-r-- 1 25866248 Jun 28 15:54 WhiteboxTools_linux_amd64.zip -rw-rw-r-- 2 221 Jun 6 2021 init.py drwxrwxr-x 2 4096 Jun 28 15:58 pycache -rw-rw-r-- 2 3904 Jun 6 2021 automation.py -rw-rw-r-- 2 416 Jun 6 2021 cli.py -rw-rw-r-- 2 3831 Jun 6 2021 download_wbt.py -rw-rw-r-- 2 2469 Jun 6 2021 example.py drwxrwxr-x 2 4096 Jun 28 15:54 img drwxrwxr-x 2 4096 Jun 28 15:54 plugins drwxrwxr-x 2 4096 Jun 28 15:54 testdata -rw-rw-r-- 2 58608 Jun 6 2021 wb_runner.py -rw-rw-r-- 2 44 Jun 6 2021 whitebox.py -rw-rw-r-- 2 6146 Jun 6 2021 whitebox_example.py -rwxr-xr-x 1 29133144 Jun 28 15:54 whitebox_tools -rw-rw-r-- 2 401432 Jun 6 2021 whitebox_tools.py

grep 2.1.0 * Binary file WhiteboxTools_linux_amd64.zip matches Binary file whitebox_tools matches

cat init.py

-- coding: utf-8 --

"""Top-level package for whitebox."""

author = """Qiusheng Wu""" email = '[email protected]' version = '1.5.0'

from .whitebox_tools import WhiteboxTools from .wb_runner import Runner

• whitebox version:2.0.0
• Python version:3.8
• Operating System: Scientific Linux 7.9, 'Nitrogen'

Description

I have developed a program that uses the python whitebox module on my own computer that uses Centos 8, but when I try to install on our scientific linux machines I get the following error: ./whitebox_tools: /lib64/libm.so.6: version GLIBC_2.27' not found (required by ./whitebox_tools) ./whitebox_tools: /lib64/libc.so.6: versionGLIBC_2.18' not found (required by ./whitebox_tools)

What I Did

I've seen this thread, which seems to address the same issue: (https://github.com/jblindsay/whitebox-tools/issues/112) but the solution is for the whitebox tool and not the python module and I haven't been able to adapt it to my own situation. Is it possible, or am I barking up the wrong tree?

Thanks in advance

• whitebox version: newest
• Python version: python 3.8
• Operating System: Mac

Description

Describe what you were trying to get done. replace the rasterline values with DEM values

What I Did

wbt.conditional_evaluation( i='/home/jovyan/data/mynotebook/data/rasterline.tif', output='/home/jovyan/data/mynotebook/data/boundry.tif', statement='value >= 0.0', true='/home/jovyan/data/mynotebook/data/Elevation1.tif', false='#')

Paste the command(s) you ran and the output.
return 0

• whitebox version: 2.1.4
• Python version: 3.8
• Operating System: Scientific Linux (Rocky 8)

Description

This is probably not an issue with the tools, but am struggling to extract a continuous stream network from a DEM. I've been experimenting with it for some time but have been unable to improve on what I have now, which is 95% of a drainage network, but with intermittent gaps. The gaps occur where the downhill slope flattens off, even though there is still an obvious channel. I'm guessing that issue originates at the breach_depressions_least_cost stage, but I've experimented with the parameters and can't improve on what I have now, which is no good.

What I Did

dem.zip

My method is:

breach_depressions_least_cost: dist=10, max_cost=100, min_dist=True, fill=True, d8_flow_accumulation: out_type="catchment area" extract_streams: threshold=3000

Regarding the parameters. I've experimented with a wide range of values for breach depressions dist and max_cost. The values I've shown here work for most of the DEM, but still leave gaps in the stream network.

Any help would be appreciated.

Thanks, Rick

• whitebox version: v0.13.0
• Python version:
  • Python 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 03:02:14)
  • [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
• Operating System: MacOS Mojave 10.14.2

Description

Describe what you were trying to get done.

I have a small, 200 MB, colorized, indoor lidar point cloud of a conference room. I'm trying to extract a slice of it.

The lidar_info output is the following:

File Signature: LASF
File Source ID: 0
Global Encoding:
GPS time=GpsWeekTime,
Waveform data internal=false,
Waveform data external=false,
Return data synthetic=false,
CRS method=WellKnownText
Project ID (GUID): {0-0-0-00-000000}
System ID: EXTRACTION
Generating Software: WhiteboxTools 
Las Version: 1.3
File Creation Day/Year: 18/2019
Header Size: 235
Offset to Points: 440
Number of VLRs: 2
Point Format: 3
Point Record Length: 34
Num. of Points (32-bit): 5869712
Number of Points by Return: [11739424, 0, 0, 0, 0]
X Scale Factor: 0.0001
Y Scale Factor: 0.0001
Z Scale Factor: 0.0001
X Offset: -19.8205
Y Offset: -44.6813
Z Offset: 0.15910000000000002
Max X: 21.220100000000002
Min X: -19.8205
Max Y: 82.7065
Min Y: -44.6813
Max Z: 7.1942
Min Z: 0.15910000000000002
Waveform Data Start: 0
Min Intensity: 514
Max Intensity: 63737

Tell us what happened, what went wrong, and what you expected to happen.

When I try to use the lidar_elevation_slice command, it outputs a file the exact same size and no points have been removed as far as I can tell.

What I Did

Here is the command I'm running:

import whitebox
wbt = whitebox.WhiteboxTools()
wbt.set_working_dir(os.getcwd())
wbt.lidar_elevation_slice("test1.las", "test2.las", minz=3.0, maxz=5.0, cls=False)

The command-line output looks ok:

./whitebox_tools --run="LidarElevationSlice" --wd="<full path removed>/Data" --input='test1.las' --output='test2.las' --minz='3.0' --maxz='5.0' --inclassval=2 --outclassval=1 -v

***********************************
* Welcome to lidar_elevation_slice *
************************************
Reading input LAS file...
Performing analysis...
Saving data: 0%
Saving data: 1%
Saving data: 2%
Saving data: 3%
Saving data: 4%
Saving data: 5%
Saving data: 6%
Saving data: 7%
Saving data: 8%
Saving data: 9%
Saving data: 10%
Saving data: 11%
Saving data: 12%
Saving data: 13%
Saving data: 14%
Saving data: 15%
Saving data: 16%
Saving data: 17%
Saving data: 18%
Saving data: 19%
Saving data: 20%
Saving data: 21%
Saving data: 22%
Saving data: 23%
Saving data: 24%
Saving data: 25%
Saving data: 26%
Saving data: 27%
Saving data: 28%
Saving data: 29%
Saving data: 30%
Saving data: 31%
Saving data: 32%
Saving data: 33%
Saving data: 34%
Saving data: 35%
Saving data: 36%
Saving data: 37%
Saving data: 38%
Saving data: 39%
Saving data: 40%
Saving data: 41%
Saving data: 42%
Saving data: 43%
Saving data: 44%
Saving data: 45%
Saving data: 46%
Saving data: 47%
Saving data: 48%
Saving data: 49%
Saving data: 50%
Saving data: 51%
Saving data: 52%
Saving data: 53%
Saving data: 54%
Saving data: 55%
Saving data: 56%
Saving data: 57%
Saving data: 58%
Saving data: 59%
Saving data: 60%
Saving data: 61%
Saving data: 62%
Saving data: 63%
Saving data: 64%
Saving data: 65%
Saving data: 66%
Saving data: 67%
Saving data: 68%
Saving data: 69%
Saving data: 70%
Saving data: 71%
Saving data: 72%
Saving data: 73%
Saving data: 74%
Saving data: 75%
Saving data: 76%
Saving data: 77%
Saving data: 78%
Saving data: 79%
Saving data: 80%
Saving data: 81%
Saving data: 82%
Saving data: 83%
Saving data: 84%
Saving data: 85%
Saving data: 86%
Saving data: 87%
Saving data: 88%
Saving data: 89%
Saving data: 90%
Saving data: 91%
Saving data: 92%
Saving data: 93%
Saving data: 94%
Saving data: 95%
Saving data: 96%
Saving data: 97%
Saving data: 98%
Saving data: 99%
Saving data: 100%
Writing output LAS file...
Complete!
0

But I get the entire file and not a slice.

What am I doing wrong?

Thanks in advance!

I was able to install whiteboxtools in AWS Sagemaker notebook instance. When I tried to execute commands:

import whitebox wbt = whitebox.WhiteboxTools() print(wbt.tool_help("ElevPercentile")) and print(wbt.help())

There is no output printed. Can anyone help me with how to use whiteboxtools and get results in AWS cloud. Thank you in advance.

• whitebox version: 2.0.3
• Python version: 3.9
• Operating System: RedHat Enterprise

Description

When using any whitebox functions for python, the current working directory is reset to the whitebox directory in my anaconda environment (e.g. /home/user_name/minconda3/envs/osgeo-env-v1/lib/python3.8/site-packages/whitebox). This causes many problems, since I am using whitebox functions across multiple scripts for my automated workflow.

To clarify, after importing whitebox, the current working directory is set to my project directory where my python file is calling whitebox, which is what I want. But after using a function it is reset to the whitebox directory, so the functions do not end up running.

I am attempting this in jupyter notebook.

What I Did

from whitebox import whitebox_tools
wbt = whitebox_tools.WhiteboxTools()
CWD = "/home/user_name/project/data"
wbt.set_working_dir(CWD)
wbt.clip_lidar_to_polygon("./filename.las", polygons="./poly_shapefile.shp", output="./lidarClip.las")

Below is the error messages I receive.

Thank you for your time in reading this.

• whitebox version: 1.4.0
• Python version: 3.6
• Operating System: Linux 18.04 LTS

Description

Hey, I'm getting error in the Docker geemap container when import whitebox for the first time.

It is not a problem if I type again an import. I couldn't understand why this throws an error. Here is a related issue: https://stackoverflow.com/questions/42441211/python-urllib-error-httperror-http-error-404-not-found

I guess this is not an important error and related to network issues. I wanted to add in case someone sees the error message.

What I Did

docker run -it --name geemap_latest -p 8888:8888 -p 6006:6006 -v C:/Users/batuh/Desktop:/geemap/data bkavlak/geemap:latest bash
import whitebox

• whitebox version: (latest, as of sept 2020)
• Python version: 3.7
• Operating System: Ubuntu 18.04

Description

I tried installing the latest version of Whitebox using: pip install whitebox

It seems to install, but it won't run because I don't have glibc 2.29 ... (I can't even check the version) error: ./whitebox_tools: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./whitebox_tools)

I'm running GLIBC 2.27... is upgrading to 2.29 really the only way to get whitebox working?

Description

Hello! Mr.WU. When I turn a single pixel wide raster into a line vector, the previously continuous closed shape becomes a broken line segment. How to avoid this problem?

code

from WBT.whitebox_tools import WhiteboxTools

if __name__ == "__main__":
    rasterPath = "/home/BE/results/cq_test_edge.tif"
    outputPath = "/home/BE/results/cq_test_edge4.shp"
    wbt = WhiteboxTools()

    wbt.raster_to_vector_lines(rasterPath, outputPath)

A bit of CI maintenance:

• Adds Python 3.10 and 3.11 jobs to the GitHub Action CI build matrix
• It also adds a weekly run each Monday at 06:00 UTC and the ability to manually trigger the CI
• Finally, it updates the checkout and setup-python actions to their latest versions.