Comments (6)
jblindsay
commented on June 1, 2024
1
This is very odd. Are you able to get me the source LAS files on which you are applying LidarJoin? I'll need to take a closer look at what is happening. As for the difference in file size between lasmerge and LidarJoin, I believe that LASTools outputs LAS v 1.4 while WhiteboxTools outputs LAS 1.3. That may account for the difference there.
from whitebox-tools.
jblindsay
commented on June 1, 2024
Which version of WhiteboxTools are you using? I made some modifications to the LidarJoin tool in the latest version (v.0.9) that may impact this. May I see what the 'correct image' also looks like, i.e. the LASTools image?
from whitebox-tools.
Hutch07
commented on June 1, 2024
Thank you very much for the tools!
This is what I have, Windows 10 and Python version 3.7. I have attached 2 views of the same file. This is lasview but it looks the same on other viewers.
whitebox_tools.exe --version
whitebox-tools v0.9.0 by Dr. John B. Lindsay (c) 2017-2018
from whitebox-tools.
Hutch07
commented on June 1, 2024
I am going to test just 2 files and I will send you the results.
from whitebox-tools.
jblindsay
commented on June 1, 2024
Good news, I just encountered this very same issue when I was trying to process LAS files that had been created by using LASTools' LAS2LAS software. As it turns out LASTools can sometimes create LAS files where the point records have more bytes than the specification mandates. I'm not sure what LASTools is storing in these extra bytes, but either way, WhiteboxTools was previously expecting strict adherence to the LAS specifications. I've now re-written the LAS reader to handle extra bytes (ignoring them but not offsetting the other point data) and this seems to have resolved this issue. I've committed the updated code. As such, I am closing this issue. I will be releasing the next version of WhiteboxTools sometime this week, which will have this bug fix. If you happen to test it and encounter any further problems, please feel free to re-open the issue.
from whitebox-tools.
Hutch07
commented on June 1, 2024
Thank you very much for the reply. If you ever get over to Standish,
Michigan, stop on in. I will reload WBT and open some other files. We
have several systems creating las/laz files - mostly Riegl systems.
I haven't used WhiteBox tools much but will try out the new code.
Thanks again,
Cary Hutchinson
Surveying Solutions Inc
…On Tue, May 21, 2019 at 1:44 PM John Lindsay ***@***.***> wrote:
Good news, I just encountered this very same issue when I was trying to
process LAS files that had been created by using LASTools' LAS2LAS
software. As it turns out LASTools can sometimes create LAS files where the
point records have more bytes than the specification mandates. I'm not sure
what LASTools is storing in these extra bytes, but either way,
WhiteboxTools was previously expecting strict adherence to the LAS
specifications. I've now re-written the LAS reader to handle extra bytes
(ignoring them but not offsetting the other point data) and this seems to
have resolved this issue. I've committed the updated code. As such, I am
closing this issue. I will be releasing the next version of WhiteboxTools
sometime this week, which will have this bug fix. If you happen to test it
and encounter any further problems, please feel free to re-open the issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#17?email_source=notifications&email_token=ACYI2WJTJBKWVKXV7J2OPDDPWQYF7A5CNFSM4FTEV7H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4VAVY#issuecomment-494489687>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACYI2WILNVYDJMSAKNWPIY3PWQYF7ANCNFSM4FTEV7HQ>
.
from whitebox-tools.
Related Issues (20)
- Geomorphons - edge effects and difficulties in geographic coordinates
- WhiteboxWorkflows: kernel dies if file not found
- whitebox.Runner() urllib.error.URLError: <urlopen error unknown url type: https> HOT 1
- whitebox_tools 'Unrecognized tool name NormalizeLidar' HOT 16
- Whitebox-Worflows: Erroneous results when using raster files in NAD83 projection HOT 1
- DTM outputs have a shift between tiles HOT 3
- lidar_digital_surface_model extent changed HOT 1
- Feature Requests: lidar_digital_surface_model HOT 2
- FlowAccumulationFullWorkflow gracefully exits without writing all 3 results
- documentation of PercentElevRange
- [feature request] add option to use D-infinity pointer grid in ElevationAboveStream
- "extract_by_attribute" tool missing from "whitebox_tools.py" (?) HOT 3
- TimeInDayLight - error when calculating local almanac
- WhiteboxWorkflows: Filters based on DEM reading not working
- Arc::try_unwrap fails intermittently during breach_depressions_least_cost
- LidarThinHighDensity throw "panicked at 'index out of bounds:'" depending on the resolution
- Unable to instance WhiteBoxTools in 2.3.1 HOT 7
- Vector Stream Network Analysis argument mismatch in documentation
- Whitebox 2.3.3 (Python): Unrecognized tool name ConditionalEvaluation HOT 18
- The Linux binaries does not contain whitebox_runner HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from whitebox-tools.