I'm trying to break a large point cloud into smaller groups so that multiple people can work on a job simultaneously. However, when I export a portion of my point cloud as las (us survey feet) the resulting file always comes back in to TBC shifted-- I suspect it is shifted to international feet. I get the same results using other formats also. What could I be doing wrong?
I had a similar situation. I had geo referenced the cloud in realworks using points exported from TBC
the TBC project had some scan data from an S7 and was using a local site scaled to 1
I exported a las file from RW, yet upon import into TBC it shifted by about half meter
I found that if you don't setup your project with a project location, and you inadvertently leave the export on ground, or on grid with a scale only project, your project gets scaled from 0,0,0. I don't know if that is a solution, but I am always setting a site location now and it seems to be fixing that issue for me.
I don't see why I can't just import a georeferenced and registered point cloud ( in realworks) into TBC ( scale only job SF1) and have it be located in the correct position in my TBC project that also contains scan from an S7 etc
have an option for " do not scale" perhaps?
I see this post is from February. Did you find an answer? How much is your shift? There's a setting when exporting an LAS to scale it to ground by default. If your control was set using GPS and is georeferenced, chances are you should export using grid.