han16nah

You can differentiate the individual **sceneparts** as stored in the .XML-file by the hitObjectId. If you are looking for a way to distinguish different **materials**, you can add the helios...

fixed with #142

The trajectory output has been fixed with 13c55a1fe7f13ca4e9173289185aa98f4297259e The survey still produces no output. But there is a very simple explanation for this. **Explanation** In the waypoint-mode, we use the...

This has been solved and a `basePlatform` parameter was added. Remaining TO DOs: - [x] update documentation in Wiki - [x] Add/update demo survey (and reference in Wiki)

Dear @xjy11 Our new "interpolated trajectory" feature should allow exactly this: reproducing a survey based on a real trajectory file, no matter if it's a more or less straight path...

Dear @xjy11 please see my update posted on #227 As @lwiniwar stated, the trajectory output and behaviour is perfectly fine. The issue is that you are probably doing and airborne...

Currently, the trajectory file is expected as a comma separated file. We should have an option `separator` which allows specifying different separators, like for the `xyzloader` of the scene XML.

There is a `scanner.fwfSettings.beamSampleQuality` property. https://github.com/3dgeo-heidelberg/helios/blob/f1835c00c76cd1b81351c5347052812ede776bde/src/pybinds/PyHelios.cpp#L688-L692 Not sure, if this will also report the correct value if the `beamSampleQuality` is set in the `FWFSettings` of the survey XML or if...

@albertoesmp I tested the implementation and while the pattern looks realistic now, the simulated swath width is too small. (Altitude a.g.l: 1000 m, scan angle: 20°, expected swath width: ~728...

Hi @thomasTUK can you try navigating to the HELIOS++ root directory (in your case one directory up to "D:\Users\user\Downloads\helios-plusplus-win"; just type `cd ..` and then run the tests from there...