Hello Steve,
first - just for anyone on the list who may not know - let me explain the '-reversible' option again and when it needs to be used. Most people will probably not need to ever use it: When you have one long flightline with 253 million points (or so) that you want to, for example, ground-classify ***while*** preserving their current order in the file then (and only then)
the '-reversible' option of lastile is useful. Because lasground / lasground_new cannot be used directly on
253 million points
we need to tile the flightline (with buffers) to get to around 10 - 15 million points per file. In order to reassemble the ground classified tiles into the original flightline (and only for that) the '-reversible' option of lastile is used.
What does this option do? It stores with every point its original position in the
flightline file (e.g. its index in the array of all points) using an unsigned 4 byte integer that is stored as extra bytes. For all points that are buffers points it stores a special number. This information allows to read the points (after classifying them) from the set of tiles and store them
back into their original order into a single flightline.
This does not currently work with the '-cores n' option because when doing spatially accelerated seeks in the file (note: *only* use use lastile to tile flightlines on multiple cores after spatially indexing the LiDAR with lasindex - aka creating a LAX file for every flightline) the original point index (the one you get when doing a sequential read) is currently not exposed in the LASlib API and that is needed to store the point position.
Regards,
Martin @rapidlasso