Check Shots

John Thompson

Well-Known Member
I have a habit of establishing a check point for my RTK rover, usually somewhere near my base. I check in to it first thing after starting my base and last thing before shutting down. I also sometimes turn 180° to make sure the pole and bubble are in adjustment. I like to save these shots so I can trace what went wrong and when.

In a recent project (See the Sequence Number thread.) the check point was number 1017. The check shots were automatically named CHK_1017, CHK_1017[1], and CHK_1017[2], and automatically given description "Check Point for 1017". I like that. I didn't have to type a name or description, I just pressed accept. I don't bring the check shots into my drawing, and with the CHK_ prefix, they are easy to sort out.

Questions:
1. I've never seen CHK_ points before. Is that because I used a survey point as the check point, and I usually use a design point? When I stake and accept a design point, it saves the first one as surveyed coordinates and for subsequent checks it prompts me for a point name.

2. Where can I see the deltas? My primary purpose of saving the check shot is so I have a record of how far off I was. I don't see deltas in the points list anywhere. It would be nice if dN, dE, and dU were included in the pdf file for the CHK_ point. If I export as txt/csv, Offset Direction, Offset Distance, and Cut/Fill are blank since there are only surveyed coordinates and no design coordinates. J-Field makes the association with the point name and description. Seems like associating design coordinates shouldn't be difficult, but I'm not the one writing the code. :)

3. When I DPOSed the project, the CHK_ shots didn't get shifted, so now if I use inverse to calc the deltas, they are 5 feet off, instead of a hundredth or two. I exported a pre-DPOS txt file and I calculated the deltas from that, but is this a bug or am I doing something wrong?

00229_Objects_20160810-15.16.47.png
 

John Thompson

Well-Known Member
I found one place where the deltas are shown. Page 21 of the attached pdf shows the A1 screenshots for the check shots. The white boxes have deltas, but they are not the final numbers. I'm not sure why it didn't save the A2 screenshots for those points. It saved A2 screenshots for all the other RTK points. The screen shots ought to be with the check shots, not all on point 1017.
 

Attachments

  • Thompson-160803.pdf
    2.8 MB · Views: 252

Mikhail Drakin

Developer
1. Yes, CHK_ is used because you are staking the surveyed point. The naming can be configured by clicking a small gear button in the top right of the Stake Points Mode screen (called from Stake Prepare screen):
__Stake_Points_Mode_20160811-08.40.14.png

__Surveyed_Check_Points_Names_20160811-08.41.01.png
 

Mikhail Drakin

Developer
2. Points saved separately (i.e. not surveyed coordinates added to a design point) lose connection to the source point, and no deltas are stored. Though, whiteboxes will contain final deltas in the next release (in current release, the whitebox source is not current average but the latest single epoch), so it will be possible to use screenshots for this purpose. Also as a workaround, you can use clustering tools for this purpose (select a point in points list screen, click the right blue panel to go to Base Rover statistics screen, then press the Up arrow (hardware button on the device). You will see spread statistics for the nearby checkpoints. I've added the wish to save deltas to attributes to the todo list, but I cannot predict the implementation time frame.
 
Top