-ignore_edge_of_flightline

[Malcolm Elliott]

Hello, 

I am developing some macros for processing LAS 1.4 data and realized that in lasheight, lasnoise, lasground, etc, there is no way to ignore points flagged as EOF.

Similarly extended classifications seem to not be respected in the -ignore_extended_classification.    

Currently the workaround I am using is to assign the points a withheld bit flag and use -ignore_ withheld.

Thanks,

Malcolm

[LAStools - efficient tools for LiDAR processing]

Hi Malcolm,
most likely uses want to drop those points during processing.
It is possible to use
    lasheight64 -i foo.laz -o bar.laz -drop_edge_of_flight_line

Does this helps or do you really want to ignore them and write them with their e.g. original height to the result file?

About the extended classification: Extended classes should be supported if you are in LAS 1.4 and point format >=6.
You can use:
    lasheight64 -i in.laz -o out.laz -drop_edge_of_flight_line -ignore_class 45

If this does not work with your data please provide an example and a small set of data.

Cheers,

Jochen @rapidlasso

[Elliott, Malcolm]

Hi Jochen, 

I would like these to be written to the resulting file.  Just simply ignored during processing. 

I'll check on the extended classification. 

Thanks!

Malcolm Elliott

Project Manager – Hydrography

Marine Site Characterization

Fugro

T +1 902 332 8340 | +1 713 396 5600 ext. 997034 | Book a Meeting

---

From: LAStools - efficient tools for LiDAR processing <last...@googlegroups.com>
Sent: Friday, June 20, 2025 13:30
To: LAStools - efficient tools for LiDAR processing <last...@googlegroups.com>
Subject: [LAStools] Re: -ignore_edge_of_flightline

 

--
Download LAStools at
https://rapidlasso.de
Manage your settings at
https://groups.google.com/g/lastools/membership
---
You received this message because you are subscribed to a topic in the Google Groups "LAStools - efficient tools for LiDAR processing" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/lastools/_gFA8opePic/unsubscribe.
To unsubscribe from this group and all its topics, send an email to lastools+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lastools/f404df4a-bf45-416c-ba59-2397e85ab69bn%40googlegroups.com.

[Terje Mathisen]

I have created a local copy (fork?) of the laszip github project and
tried very carefully to follow the instructions:

(I have Visual Studio Community Edition 2022 installed, with both the
Microsoft and clang compilers, I have previously used this to compile
and debug my own C(++) programs.)

According to README.md I just need to run
  cmake -DCMAKE_BUILD_TYPE=Release CMakeLists.txt
  cmake --build .

and this seems to work nicely, I get two sets of DLL & PDB files
generated: laszip_api3.dll/pdb and laszip3.dll/pdb, but nothing happens
in the example directory.

It is when I try to compile laszipdllexample.cpp that things break down.
SInce there is a CMakeLists.txt file there I tried to run the same pair
of cmake commands from the example directory but this does not work, I
suspect the idea is that the top level build should handle everything?

Have anyone any tips for me?

I am pretty sure this is a user error on my side, I just have not been
able to figure it out!

Terje

--
- <Terje.M...@tmsw.no>
"almost all programming can be viewed as an exercise in caching"

[LAStools - efficient tools for LiDAR processing]

Hi Terje,

thanks for this hint. We don't think you do something wrong. It is just like this: We, at rapidlasso, do not use the examples. The core code of the examples is about 9 years old and was never changed or maintained. laszip is complete open source: If some one needs or want to use those examples we are happy if this person will update and enhance this. We then will integrate those pull requests into this official repository.

Cheers,

Jochen @rapidlasso