Missing Points Problem

[Nate The Surveyor]

Performed this job about 2 wks ago. I have been wrestling with some missing point numbers.
It is quite strange. It seems it DPOSed fine. And, the coords seem to be related to the rest of them just fine.
Here is a screen shot showing the gap in point numbers:

If you will notice, the point sequence goes 28 then skips 29,30,31,32 and 33. Then it shows number 34
So, 5 points are missing.
Now, notice in this next screen shot I can SEE numbers 31,32, and 33 in the Map Screen:

Through this means I have salvaged numbers 31, 32 and 33.

Then, in the inverse screen, I can inverse to points selected via screen shots.

Now, Here is my dilemma, Where are points number 29 and 30?
Are they lost in the box?
I have tried all kinds of resets. I have updated the software this morning.
So, it seems 29 and 30 are gone.
and it cannot export 31,32,and 33.
I think I was in STAKE TO LINE mode when these were collected. But, they were in a kind of open place, so they only have about 20 seconds or so of time.
Anyway, I have tried all I know.
Here is the file name:
mtnharbor
I have already sent it in to support.
It seems like some sort of bug.
Thank you,
Nate

 

[Adam]

Nate, long hold on the red funnel.

 

[Shawn Billings]

I wonder if Hide Staked is checked. Recall I asked on the phone if you cleared filters. The red funnel says one or more filters are on. Although I'm not sure why filtered points would be visible on the map. Puzzling.

 

[Nate The Surveyor]

OK, I tried the LONG HOLD ON RED FUNNEL. Then, the magnifying glass turned red. So, I long held it. BOOM, the coords showed up as calculated points.
What up with that??
I mean, 30, 31, 32, 33 all showed up.
And, it shows that they were shifted.
Kinda weird.
Now, I'm going to compare them with what I had done manually.
Thanks,
Nate

 

[Nate The Surveyor]

Then, to export them, they don't show up. So, I clicked SURVEYED DESIGN POINTS, and ALL PROJECT POINTS, and it looks like they show up.
Now, they show up as STK_30, STK_31, STK_32, STK_33,
It's odd.
Nate

 

[Shawn Billings]

Sounds like Accept vs Accept As. Check the Action profile you were using to stake those points.

 

[Nate The Surveyor]

This is what I get. It shows them shifted.

Accept As was on.

I think I'll chalk it up as an anomaly. I had field deleted number 29, as it was a STAKE TO LINE point that was only used for flagging line.
Then these anomaly s occurred.
Thanks everybody. I also did a RESET FACTORY IMAGE, so maybe it was the fact that I interrupted it at points that threw the sequence.

I'll pay close attention in the field, next time, on stake.
Nate

 

[Shawn Billings]

When I refer to Accept As being turned on I mean in the How to Stop screen. Note that the option for Accept As New Point is only available on the How to Stop screen when the Action is set to Stake instead of Collect. The white box accomplishes the same thing, but you have two buttons and if you're in the habit of clicking Accept instead of Accept As, then you might accidentally click the wrong one. With this option, Accept becomes Accept As and you don't have to sacrifice a white box to use it.

My guess is that you used Accept on accident and that Hide Stake Points was turned on in the filters. It's an easy mistake to make, I know I have. Since points 30, 31, 32 and 33 were design points (which is what happens when Stake to a Line is used with the Accept button - it creates design points at the perfect coordinates on line and then stores the surveyed point in the design point). When Accept As is used, then the surveyed coordinates are stored as a survey point with the description showing the names of the endpoints of the line.

Using the Accept As New Point setting under How To Stop instead of the Accept As white box removes the chance for accidentally hitting Accept instead of the Accept As white box and creating a problem.

Ultimately, I think the software should be defaulting to Accept As and the current behavior of Accept should be an option. The Accept behavior has a place, but it is much less common in my opinion than Accept As behavior for most survey tasks.

 

[Nate The Surveyor]

Shawn, your ACCEPT AS being un-checked theory does not seem to be true, as shown in the above screen shot, associated with point 33.
Points 30,31,32, and 33 all show ACCEPT AS, as above screen shot indicates, and the active profile was boundary.
Thank you,
Nate

 

[Shawn Billings]

I don't think we're talking about the same thing. When Accept As New Point is checked, it changes how the Accept button works. It has nothing to do with the white box button in your screen capture. In other words, your screen capture doesn't really address what I'm describing, one way or the other.

 

[Nate The Surveyor]

Edit:
OOPS here is the screen shot of it.
Shawn, I think you are on the right track.
Nate

 

[Shawn Billings]

Was Accept As New Point already checked or did you check it on just now? If it was checked on when you collected the stake points, my theory is wrong and there may be a bug. If it was unchecked and you may have accidentally hit Accept instead of Accept As white box button, then I think everything makes sense. It points to a problem with our user interface, but not a bug.

 

[Nate The Surveyor]

ACCEPT AS NEW POINT was already checked. It was checked when those were collected. If you notice number 29 is missing. I stored it, then DELETED it. (because it was in the same area as 30) and was for flagging line. I have not used the ls since this job, other than to UPDATE all things. I have touched the "Accept as new point" since this survey. I am think it is a bug, RELATED to the delete of point 29. (Nates convoluted guesswork)
SO, either way, I go bug theory.

Nate

 

[Shawn Billings]

SO, either way, I go bug theory.

Nate

Could be!

 

[Adam]

Ultimately, I think the software should be defaulting to Accept As and the current behavior of Accept should be an option. The Accept behavior has a place, but it is much less common in my opinion than Accept As behavior for most survey tasks.

ACCEPT AS NEW POINT was already checked. It was checked when those were collected. If you notice number 29 is missing. I stored it, then DELETED it. (because it was in the same area as 30) and was for flagging line. I have not used the ls since this job, other than to UPDATE all things. I have touched the "Accept as new point" since this survey. I am think it is a bug, RELATED to the delete of point 29. (Nates convoluted guesswork)
SO, either way, I go bug theory.

Nate

Can you send this project to support? If it was checked on, this shouldn't be happening. If it's a bug they may not be able to reproduce the exact steps. Your project may help the engineers find out what happened.

 

[Nate The Surveyor]

I've already sent it to support. File Name is MtnHarbor

 

[Nate The Surveyor]

Funnel was red. Magnifying Glass was red.
What did that mean, and why was it hiding stuff? I don't recall every reading about LONG PRESS doing this action. Maybe I missed it.
I think it might be handy there was a button that RESETS ALL FILTERS, not just "resets filters". Maybe add another button, that does this, so that we don't get wadded up, finding stuff. I am thinking of things that REDUCE tech support assist. I can see this as productive.
Especially, I have developed the HABIT of DELETING all the DESIGN points, and re-installing them, as a mechanism to allow the cleaning up of temporary points, and refining files. IF I deleted all design points, in this file, I'd be loosing some important points on this job. These points may (In this case) wind up in court. (It's a concrete driveway encroachment).
Thanks all,
Nate

 

[Matt Johnson]

If one of the filter icons is red it means that filter is active and filtering points. Long pressing the icon resets the filter.

 

[Nate The Surveyor]

Thanks matt