The current coordinate, i.e. the coordinate selected in the Processed Point Info screen will always be displayed and exported throughout J-Field.
Matt - Are you certain? In tests just now creating PDF format reports, the first test which I attached in the top topic starter had only the base GNSS1 shifted and none of the other points were moved. In the second test [1624_Davis-160521B.pdf] all points were shifted and selected in the PROCESSED-POINT-INFO-SCREEN. In the third test [1624_Davis-160521C.pdf] all points were moved back to pre-shift; i.e., autonomous base positions. Which leads me back to the point: how can we tell exactly what we're looking at?
I'm not sure which points you think there is a problem with after looking at the project. All the points I see in the reports are clustered averaged points and only have one possible coordinate which is the same coordinate that is being exported in the reports:
If you wanted to have the averaged points be averaged from other coordinate types you would need to perform the cluster average after you have chosen the desired coordinates for the underlying points.
Kelly, we need to investigate your problems with dropbox/google drive access, as they can also influence DPOS connection.
Is there a file size limitation for cloud drives possibly. When I placed Kellys project archive in my Dropbox, the file was not visible with the files explorer in J-Field.
Hello Matt, thank you for the reply.
I know that they are averaged. That never was the concern; whether they were averaged or not. The concern is that the report fails to clearly identify the bucket.