can you explain more the "huge need" of structured pointcloud from VLX? Is it just for meshing purpose? <br>
A lot of customers love the small size of our data and the corresponding coverage. Modelling with our pointclouds works perfectly fine.<br>
Also thank you for your business proposal, i will forward to our management ;-)<br>
what issue in particular you see in the export? I just see for line item 16 and 18 strange coordinates which might be caused by incorrect located or POSTed POI. Whatever you find strange, is this when using the POI export in IVION directly or via API based app?<br>
when i understand you correct, you process on a local machine and has access to datasets_proc with pano folder. As soon you have modified the images and considering the hints from Laurin do keep the format and pixels, you can simply go next step for web-processing. The resulting NVD files you can upload to Ivion. In case it is the same file name, it will be directly replaced. Otherwise do the dataset alignment etc.... Thats it.
in case a user need pointclouds of whole floors or the complete site to e.g. create a BIM model out of it i rather suggest to download the pointcloud file generaly from the cloud processing add-on and store it on a defined project folder to grant access to the files for involved team and importing to 3rd party CAD tools. That way you also ensure to not forget any part of the scanned area and have everything in the downloaded files.
one more remark on that question. In case you need to hand-over the device to another colleague to continue mapping by any reason, i suggest to first finish the actual dataset. When the colleague start new dataset and might capture CP he get anyway asked for the size. This should be the easiest way to handle a situation as described by you above.