This is a good summary of where Jesse got with dual plus confidence (dpc) in potree: link
The biggest thing that has not been done yet is filtering the points based on confidence and other parameters (like recommended drop)
The helper/unpack functions that he created in the DataSchemas repo, the file that we upload to the Schemas folder in S3. I currently don't use it from S3. I have saved a copy of this file to the source (schemas) folder. These are functions that we have to use for all the points. They are not like the other _generated.js files in the Schemas folder that only gets used for truth. I didn't look in great detail if potree can use it from S3.
This was tested on a variety of datasets:
test020 and test022 - those have dual plus confidence in their point clouds
test020 is actually a dataset from the HDL 64E
A sled testing dataset (VLS 128 before shipping to Aptiv)
No dpc information here - there was just defaulting to no variation in those attributes (they weren't processed with dpc information)
SH3 aptiv dataset
I don't think Jesse's changes broke anything
There weren't any rebase/merge conflicts either
ATTENTION: these changes would need to be deployed if Veritas DPC also gets deployed. As the new processing then will include DPC and the older version of potree in the servers do not support Veritas DPC processing
_generated.jsfiles in the Schemas folder that only gets used for truth. I didn't look in great detail if potree can use it from S3.ATTENTION: these changes would need to be deployed if Veritas DPC also gets deployed. As the new processing then will include DPC and the older version of potree in the servers do not support Veritas DPC processing