Putting an idea on the table, for DPOS

[Nate The Surveyor]

This is only intended to put an idea on the table, for discussion. The idea BEHIND this is the concept, that often the person in the field, is NOT the same person, analyzing the data. AS such, we need to facilitate field-office communication, as much as possible.

Project: Salem ar

I have sent this project to development, so you can look at it, if you like. It's the version sent on Friday evening, May 20th.

The other day, (My nice rain day!) I was on Point Number 280. It was clicking along nicely. Until it came to 200 seconds, (I like 200 seconds), then, it went into verify, and JUMP! it threw it out. Well, DPOS had already run up 300 seconds, and so I just let it cook a bit longer. Finally, WITHOUT verify, I saved the point. I only saved it, to save the DPOS data. Then, went on to 281, and re shot it. This time, it went all the way through, and got it's verify, and I saved that one too. 281 is correct, from a RTK procedure point of view.

When I saved number 280, I only saved it for it's DPOS value. So, I added to the note "dpos". This was to warn me, that it was not a reliable shot, back in the office.

When I got home, and uploaded it all, I found that 280 to 281 was S 76°20'28" E 4.6' feet. I know what happened, and I am keeping track of it. But, as dpos is a bit mucked up right now, and I cannot seem to get dpos out of this, (It seems that there is an attachment problem of sorts) so, I have a warning not to hold to number 280. I NEARLY left after getting a nice long dpos on 280, so glad I did not!
What if there was a quality code, we could insert, that added a symbol, or letter, or the like to the POINT DESCRIPTION, so that we would be warned in the office, that the field person knows RTK is bad?

As I said before, the idea here is to place a convenient, quality control code, somewhere for the office guy. And, this is for discussion. Just to open the discussion. This plat HAS to be out tomorrow. So, I cannot wait for DPOS. Many projects are like this. I was taught when I worked engineering in Chicago, to ALWAYS make notes, that did not require interpretation, for the office guy. That also will be handy in 25 yrs, when I am old, and forgot all the details....

As always, thanks for your hard work, to make the best.

Nate

 

[Adam]

Nate, something along these lines will probably be implemented soon. Possibly a flag on the point screen or an option to save or reject RTK when conditions haven't been met or observation wasn't completed, but static data is collected.

 

[Darren Clemons]

Nate, something along these lines will probably be implemented soon. Possibly a flag on the point screen or an option to save or reject RTK when conditions haven't been met or observation wasn't completed, but static data is collected.

I like the "reject RTK" idea completely on points such as this. No reason at all to store the coordinate if it hasn't finished the three phases. It does, just as Nate describes, cause for confusion if the person who shot it is not analyzing the data. Just allow that point to be processed base/rover and if you stay at least 20 minutes, Cors/rover.
What the team is doing with this post processing at the rover is unmatched by any other brand out there. It will, most likely, become something that sets Javad even farther apart from the competition than it already is! Let's remember this is the absolute infancy of this (and it's working quite smoothly to be honest - just so much data for us to get used to seeing), so tweaks will surely be coming to make it better. That seems to be the Javad way.

 

[Nate The Surveyor]

I'd like it to still store the RTK shot, (if it has one) or, the Code, Float, shot. That shot, even if poor, CAN be useful in the field, so long as it is CLEARLY flagged, in the LS as a poor shot, and CLEARLY flagged in the export file, as a poor shot. ADDING letters to the beginning of the point description seems like one possibility. Sometimes you need that shot, even if poor, to locate another point, such as one that's a certain distance from it. For search purposes.