Hello again.
here the work-flow for the whole data set in one piece (at the example
of 12 tiles):
(1) run lasinfo on the merged set of 12 tiles and print the
point_source_ID histogram (aka flight line info)
lasinfo -i tiles\*.las -merged -no_header -no_minmax -histo
point_source 1
point source id histogram with bin size 1
bin 23022 has 1703567
bin 23023 has 3487026
bin 23024 has 3305249
bin 23025 has 3298939
bin 23026 has 3967651
bin 23027 has 4118496
bin 23028 has 3994599
bin 23029 has 4119683
bin 23030 has 1065201
so we have 9 flight lines numbered 23022 to 23030
(2) run the newest tool "lassplit.exe" on the folder of tiles to
extract the individual flight lines
lassplit -v -i tiles\*.las -merged -v -o tiles\flightlines.las
reading 29060411 points of type 1 from 'tiles\61946-64_1.las'.
creating output file 'tiles\flightlines.23024.las'
creating output file 'tiles\flightlines.23022.las'
creating output file 'tiles\flightlines.23023.las'
creating output file 'tiles\flightlines.23025.las'
creating output file 'tiles\flightlines.23026.las'
creating output file 'tiles\flightlines.23027.las'
creating output file 'tiles\flightlines.23028.las'
creating output file 'tiles\flightlines.23029.las'
creating output file 'tiles\flightlines.23030.las'
split 'tiles\61946-64_1.las' into 9 files. took 114.61 sec.
(3) create a boundary polygon for each of the nine flight lines
lasboundary -i tiles\flightlines*.las -oshp
(4) look at the resulting flight lines with the GUI and notice that
only consecutively numbered flight lines overlap
lasview -i tiles\flightlines*.las -gui
(5) hence, instead of clipping every flight line boundary polygon
against every flight line, clip only those adjacent flight lines where
we know that there is overlap:
first on one side
lasclip -i tiles\flightlines.23022.las -poly
tiles\flightlines.23023.shp -o tiles\flightlines.23022_23023.las
lasclip -i tiles\flightlines.23023.las -poly
tiles\flightlines.23024.shp -o tiles\flightlines.23023_23024.las
lasclip -i tiles\flightlines.23024.las -poly
tiles\flightlines.23025.shp -o tiles\flightlines.23024_23025.las
...
then on the other side
lasclip -i tiles\flightlines.23023.las -poly
tiles\flightlines.23022.shp -o tiles\flightlines.23023_23022.las
lasclip -i tiles\flightlines.23024.las -poly
tiles\flightlines.23023.shp -o tiles\flightlines.23024_23023.las
lasclip -i tiles\flightlines.23025.las -poly
tiles\flightlines.23024.shp -o tiles\flightlines.23025_23024.las
...
for every flight line we now have two files that contain the points of
overlap with the neighboring flight lines on both sides, except for
23022 and 23030 which are the end flight lines and have only overlap
on one side.
regards,
martin @lastools