2 base points and Dpos

Darren Clemons

Well-Known Member
I started a job on a 325 acre site Friday and ended up setting two bases on my first day in the field. I took 26 design points with me to the field so my original base point was 27. I collected a few corners and then shot a second base point (33). This site has lots of width and over 200' elevation change and unfortunately the center was in heavy coverage so 2 bases, even with the 35w radio were going to be needed. I shot one more corner after shooting the second base and then broke down and moved to the second base and re started (session point 35). I then collected approximately 12 more shots.
The following morning I dpos ed the original base (27) and it shifted everything shot from that point 2.7'. Now, of course, the shot point on base 2 and the session point were 2.7' apart, which I expected. I then dpos ed the 2nd base (35). It went through everything fine and I though it would've shifted that point as well as all the shots collected from it automatically but when I went back to the points screen the were not shifted. Still had 2.7' from 33-35. I then looked at the solutions for point 35 and it had not changed it to the cors solution it acquired from the 2nd dpos. I clicked on that and it asked "are you sure you want to move this coordinate and ALL points associated with it" (or something close...I'm paraphrasing a bit). I hit yes and then when I escaped to points all had the "shift" icon next to them. Points 33 & 35 were now 0.02'.

Is this the way this should've worked,NOT shifting the second base and points associated with it automatically?
I've had multiple bases on several sites but I think this is the first time I've done it on day one. Usually the 1st base is processed and the 2nd is shot after everything has already been adjusted.

Also, in this scenario I noticed this morning it created every "survey" point in that job as a duplicate "design" point with a [2] beside it. They are identical to the final complete shifted coordinates of those points. What was the purpose of these duplicates?
image.jpeg

Just wondering if I did something wrong or out of order to cause this to happen.
 

Nate The Surveyor

Well-Known Member
Well, I was reviewing a job recently. Points screen. About half of the points shifted, (autonomous to dpos based coord values) and the SECOND half of the coords did not shift.
What had happened, it had crashed, at a stage, in dpos.
Now, if it had crashed, right at the end of your first dpos, or at some stage of dpos, or, if the internet connection was interrupted, such behaviour could result.
So, it might simply take a re-dpos to fix it.
Now, delete those duplicate points, and you might be ok.
Before you do anything though, back up that job. And then reboot it.
This way you can go back, if need be. No data loss is good.
The above may, or may not help.
N
 

Nate The Surveyor

Well-Known Member
One more significant item. Every data collection session, base, and all its points, are treated as a single entity, or unity. This is evidenced by the fact that it requires you to make a new base point, for every session. Keep this concept in mind, as you tackle improper behaviour.
This concept is not used, with other popular data collectors. It's an important difference.
Trying to be helpful.
Nate
 

Matt Johnson

Well-Known Member
5PLS
Hi Darren,

DPOS not does shift rover points automatically if they have "Known" base coordinates. Currently, when a base position is chosen from the list, it is always flagging the new base point as a known base station. Idealy it should inherit the autonomous flag if the chosen point currently has an autonomous base. I will see if Michael will fix this.
 

Darren Clemons

Well-Known Member
Hi Darren,

DPOS not does shift rover points automatically if they have "Known" base coordinates. Currently, when a base position is chosen from the list, it is always flagging the new base point as a known base station. Idealy it should inherit the autonomous flag if the chosen point currently has an autonomous base. I will see if Michael will fix this.
So was I correct in clicking the CORS coordinate on the second base and then okaying the option to move all points associated with that base? I think that was the only way to get all the points translated correctly.
Everything seems to check out okay now....
 

Darren Clemons

Well-Known Member
So was I correct in clicking the CORS coordinate on the second base and then okaying the option to move all points associated with that base? I think that was the only way to get all the points translated correctly.
Everything seems to check out okay now....
Also, any idea why it made duplicate points of all survey points and threw them in design?
 

Matt Johnson

Well-Known Member
5PLS
So was I correct in clicking the CORS coordinate on the second base and then okaying the option to move all points associated with that base? I think that was the only way to get all the points translated correctly.
Everything seems to check out okay now....

Yes

Also, any idea why it made duplicate points of all survey points and threw them in design?

Are you sure that you didn't use one of the CoGo Shift functions and choose "Create New Points" with these points?
 

Darren Clemons

Well-Known Member
Yes



Are you sure that you didn't use one of the CoGo Shift functions and choose "Create New Points" with these points?
No Matt, I didn't do any move or shift at all on this job (after Dpos). I did my usual out in the field but didn't use the Dpos option to move any design points.
Again, this was all after my "lockdown" period Friday night when the LS would not come on. I've got to think maybe it had something to do with that.
 

Michael Stazhkov

Developer
JAVAD GNSS
No Matt, I didn't do any move or shift at all on this job (after Dpos). I did my usual out in the field but didn't use the Dpos option to move any design points.
Again, this was all after my "lockdown" period Friday night when the LS would not come on. I've got to think maybe it had something to do with that.
I just can say that DPOS algorithms can't create points. DPOS creates/changes coordinates attached to a Point.
 

Darren Clemons

Well-Known Member
Darren do you have an archive of the project in that state?
Matt I just emailed you the file I sent you Saturday. I think it was in the state where both bases had been dpos ed but I hadn't yet selected the CORS point on base 2 to shift those coordinate to match the rest of the job. If those duplicate points are not there then it must've created them when I "switched" point 35 from RTK to CORS.
 

Matt Johnson

Well-Known Member
5PLS
Matt I just emailed you the file I sent you Saturday. I think it was in the state where both bases had been dpos ed but I hadn't yet selected the CORS point on base 2 to shift those coordinate to match the rest of the job. If those duplicate points are not there then it must've created them when I "switched" point 35 from RTK to CORS.

It is not in this state. As Michael said DPOS does not create points. In the database it only attaches coordinates to existing points. The only process that I can find that creates design points with this naming convention is Import. It appears you (or maybe one of your employees) exported a text file of the survey points and then later imported that same file. Doing this would display a prompt with an option to Rename the imported points since there is a naming conflict because these points already exist:

IMPORT-CSV-PARAMS_20160615-21.07.20.png


Doing this with the default import settings would import the surveyed points' codes into the description field like is shown in the photo you posted. Here are screenshots I captured when I duplicate this:

EXPLORER-OBJECTS_20160615-21.10.54.png


EXPLORER-OBJECTS_20160615-21.10.46.png
 

Darren Clemons

Well-Known Member
Interesting. At least that shows a process of how to duplicate the screen I showed, but honestly I don't recall importing a txt file (I was the only one messing with this file as well). Also, I've overwritten design points many times and always have the "overwrite existing" button checked. However, that being said, with the frantic state I was in Saturday & Sunday trying to get the LS back on and not lose an entire days work on an absolutely horrendous farm, it appears I had to do something like this to create the duplicates.
Thanks for looking at the file.
 
Top