Add option to ignore global_encoding or apply same calculation to values in LAS and trajectory.Also option to convert between SOW and GPS time.
Indeed it was delivered in iTwin Capture Modeler 2023.0.1, I mark this idea as shipped, thank you again for your suggestion!
Seems to be delivered.
Point clouds:
Offset between timestamps from trajectories and point clouds are automatically compensated whenever possible
sounds great
This idea is being investigated for a future release. Our goal would be to not expose settings, but automatch timetamps by detecting global_encoding diffs or SOW time vs GPS time.
Indeed it was delivered in iTwin Capture Modeler 2023.0.1, I mark this idea as shipped, thank you again for your suggestion!
Seems to be delivered.
Point clouds:
Offset between timestamps from trajectories and point clouds are automatically compensated whenever possible
sounds great
This idea is being investigated for a future release. Our goal would be to not expose settings, but automatch timetamps by detecting global_encoding diffs or SOW time vs GPS time.