Apologies if I’m missing something obvious …
So I’ve loaded several point clouds and overlaid them so I have a complete representation of a set. I used point of interest to cull areas not required.
However the combined point count is now WAY more than it needs to be for meshing, and much too much for calculating normals to generate single side meshes.
Is there an operator to reduce the point count of the cloud and then export that result?
No, you are not missing anything. We never expected anyone would want LESS data in Sequoia. So the controls for loading every Nth point from the file were removed very early in the development. We might have to bring them back, probably under the Export options… Or let you export different LOD levels. We will discuss this internally.
As workaround you can save the result to PRT 1.1 file, load in 3ds Max using Krakatoa PRT Loader (Viewport loading disabled), set the Render percentage to whatever number you want, the mode to “Load Every Nth Particle”. Then open Krakatoa GUI, set to “Save Particles To File Sequence”, specify a file name and the channels you want to keep, and resave. Then you can load the resulting file in Sequoia and resave as as SPRT for speed. Of course this would be quite slow, but better than nothing…
Can you give us an idea how big your data is, and how big you want it?
The cloud is a quite excessive 95m points for buildings clustered around a single intersection. The problem arose in that the 4 scans made on the set overlap greatly so the density in some areas is extremely high, whereas in others it’s much more reasonable. I couldn’t find tools in Faro SCENE to reduce that point count to give me a nice overall average balance (nor in Mesh Lab).
In Sequoia, the different levels I can display for areas (point of interest) do give me the type of visual control I’m expecting, e.g. level 2 == 11m points == sweet! So if I could lock a point cloud to reduce to that amount and then generate normals (for creating 1-sided geo) I’d be in great shape.
I’ve spent the last 5 days trying multiple sw packages trying to solve this problem. To be honest, most of them are pretty nasty, so I’m much more interested in using Sequoia to do the job as a one stop shop. I figured the workaround for Krakatoa would be the way to do it, so I will try that. But that adds a pre-process step in I’d prefer to leave out (and would require more software/hardware on set and time to process).
I have logged a User Wish for LOD controls over the Output stream for processing/export in addition to the current LOD controls for display.
We will have an internal discussion and will see what we can do 
That would be extremely useful! Thanks!
A little surprise (even for me) was that KMX 2.4.1 can read SPRT files already (as well as all other LiDAR formats supported by Sequoia).
So you can just set it to All Files and pick an SPRT in a KMX PRT Loader and you can do the reduction.
Then save as PRT (no SPRT saving from KMX), and load in Sequoia.
One step less, as you don’t have to save to PRT from Sequoia first…