Job File Corrupted due to bad base point

View Only

Job File Corrupted due to bad base point

Ellen Cox posted 12-13-2024 13:46

Hi all,

I conducted an RTK survey using the CRTN network, but when I connected to the network the base I chose was down. Because of this, I switched to using my own R8 base to complete the survey. I received an error when importing this job file into Trimble Business Center because the bad base location came in as a point with coordinates ?,?. This made it such that I was unable to upload the .job file to TBC.

Workaround attempt #1: I deleted the points from my project, then re-exported the job file. The job file remained unchanged and would not upload to TBC.

Workaround attempt #2: I created a new job and transferred the old job file to the new job. I also imported the points as a CSV (without the bad base point) into the new job. I then exported this job file and successfully brought it into TBC.

Problem: The new job has all the points, but does not have observations. Because of this, when I try to Merge Points to my OPUS solution base point, only my one base point moves. The rest of the observations should all move with it (yes, I pushed the red circle). It seems as if the link to the base is lost.

Question: Is there any way to get this link back? Is there a workaround I should have done instead?

Thanks!

ian bissonnette posted 12-14-2024 10:08

a couple ideas.

when/what does the error look like? it is not as simple as unchecking the bad base on the import and only keeping the good one? i suggest this because somewhere you are seeing the ? ? coordinate.

another workaround might be to try exporting a jxl from the initial survey. jxl will have all the observation data and there is a small chance it would load. i actually do not know the difference between jxl and job but we have had instances where this has helped. like if you have a newer version of access and do not have the tbc device manager updated. seems like the jxl is easier to ‘read’.

csv are just coordinates with no observation data. but if the project is real basic with just rtk ties then you could always cheat and just manually shift these rtk ties to the updated opus coordinate. might depend on how much processing you need to do. and if you have other total station info as well??

Ellen Cox posted 12-16-2024 10:00

Relying to Ian and reporting solution:
The error says that it's a WGS 1984 error, which tells me the observations do not coincide with any points within the coordinate system because they are at coordinates ? ,?. We tried unchecking them but it didn't work. We also tried the .jxl and it didn't work.
My coworker fixed it by applying coordinates to the ?? points, then he was getting an error for the input string for the measured height. He went into Review Job and the antenna height for the bad base points was a very large number, so he changed it to 10 and it solved the problem.