I am trying to enter what I believe to be the trajectory files to accompany the LAS files. CC will only accept txt or csv files. However the list of files I was provided by a surveyor has the fomat "log" at the end of it so it is not being recognized as a text file (I think). Any way around this so CC will import it into as trajectorry file? see attached screenshot:
Contextcapture SDK doesn't allow custom trajectory to be imported only txt.
class Trajectories Trajectories handler suited for importing point clouds from mobile scans. readFromFiles((list)file_path_array, (FileFormat)trajectory_file_format) → MasterKernelError Return MasterKernelError. Read trajectories from formatted text files. File format must be defined for the input files with fields ‘x’, ‘y’, ‘z’, and ‘time’
Yes take a SBET and convert it using utility I attached in other post. Do a search of sbet in communities. Also I have registered feature request to add sbet format to CC so please register also so Bentley consider to add it as only one user who request it may not be enough.
In latest CC U15 at last it is now possible to use Python API so will later take a look if it is possible to add trajectory from SBET using API but not sure if API has such possibilty. But overall adding API also to desktop edition of CC is right move as it makes it more popular and also can be used in such cases of missing format support.
The report tells me the trajectory files are indeed SBET
however, the SBET file I found appears to be in a "OUT" format??
Does not seem to be trajectory files but log files after processing lidar point clouds with trajectory in RiWorld software. Not sure what it is but it seems the lidar data should be already in WGS84 after processing.
yes i believe it is sbet