These are the formats of the data that Terrasolid can read and create laser data files and trajectory files of. All they can be *.txt files and theirs internal structure must be in one of formats above.

I was trying to find someone that would tell me exactly what kind of information should be input to Terrasolid and what for; and in fact I didn't succeed. Helen Burman and Dan Klang are on vacation, the guy at Terrasolid, Finland, responsible for software support told me to write him an email with my questions; he offered answering the email in a couple of days as he's on vacations also.

I've read the user guide (more or less, it consists of about 4 hundred of pages) and I can deduce that trajectory file can be built of a data set as followings:

TYXZRPH or TXYZ (look at the table above)

Space is the separator.

I think that you might use GPS coordinates and corresponding R,P,H (TYXZRPH) or just XYZ coordinates after GPS-IMU integration (TXYZ). The choice is yours

The trajectory points should probably (!) be the ones focusing all the laser beams.

What is important: we need all the exported coordinates in the same coordinate system, I think that this should be WGS-84. If it appears that we need coordinates in another coordinate system, we won't need your help with the transformation. Terramatch need coordinates in UTM, but it performs the transformation from WGS-84.

About the timestamp: I didn't find out what should be the time stamp. The only info user guide says is that `laser points have flightline numbers and time stamps matching trajectory information'. So probably there is no special demand for the time stamp format, it just should be the same for both trajectory and laser data files. The position should be every lasershot maybe, I don't know. If you make a position every lasershot, then when it appears that we need every second - we can simply remove unnecessary positions.

---