Just to be sure

Nate The Surveyor

Well-Known Member
20211116-18.01.52_00435_DPOS_configuration.png

I have the DPOS config screen as shown.
To be sure I am not out of date, with these settings, it processes ALL the RAW GNSS points, means that if they don't have an rtpk value, then it processes these?
and, below that, I have BASE - ROVER & Base Coors checked as shown.
Tell us all how this works. Because it is important that we KNOW for sure, and that we stay up to date with settings.
Thank you,
Nate
 

Michael Stazhkov

Developer
JAVAD GNSS
To be sure I am not out of date, with these settings, it processes ALL the RAW GNSS points, means that if they don't have an rtpk value, then it processes these?
Actually "ALL raw GNSS points" means all points with attached raw GNSS files (all points which can be processed by DPOS). Without this setting to DPOS will be sent only points that were marked for post-processing (points without fixed RTK coordinate).
I think if you have RTPK you don't need this to be checked as the RTPK coordinate will be replaced by DPOS PPK coordinate. So don't use this setting if you want to keep RTPK coordinates.

and, below that, I have BASE - ROVER & Base Coors checked as shown.
1) DPOS can solve vectors from Base to Rover (Base-Rover processing).
J-Field records PPK coordinates into points using this information and can auto-select the PPK coordinate in some cases (for example when there is no fixed RTK solution).

2) Additionally, DPOS can also process Base data relative to CORS stations, adjust and find the accurate Base position (Base CORS Processing).
J-Field can shift Base and all related rover points using this information.

3) Also DPOS can process Rover points relative to CORS stations (Rover CORS Processing).
J-Field records CORS coordinates into points. Usually, this information can be used as an additional check. But for a short file solution relative to CORS has low accuracy.
 

Nate The Surveyor

Well-Known Member
Thank you @Michael Stazhkov.

This is for the 5 PLS team, @Shawn Billings @Phillip Lancaster @John Evers @Matt Johnson @Matthew D. Sibole @Adam Plumley etc.

In thinking about it, and the recent promotion advertising, and the increase of users, (Which I am in favor of), may I suggest the following:

Either place some FINE print into the above screen, that says "This overwrites RTPK coords, with DPOS values"

AND/OR

Put a BUTTON into the software, that is labeled "INFORMATION". IF the user clicks the "INFORMATION" button, it takes you to a further DETAILED DESCRIPTION. This could serve in the big picture, and long term, as the development team can place pertinent information, for individual parts of the software. The INFORMATION BUTTONS could be placed in IMPORTANT places FIRST, and then added to various places in the whole program. This would allow development to continue, and users to be informed. At the same time.

Inside the DETAILED DESCRIPTION, it could include a LINK to USERS COMMENTS, where the USERS COMMENTS can be included. The USERS COMMENTS can be edited, and monitored by the 5-PLS team, for brevity, and conciseness. Or to remove extraneous material, or rabbit trails.

The USERS COMMENTS are only available when the LS is ONLINE or connected to the internet.

I believe this would Further the whole Javad Program, in a gradual, and functional way, that would continue to serve for many years to come.

Sometimes the Javad system of information makes me feel stupid. Not intentionally, but because of a basic lack of detailed information. Sometimes we don't even have a clue what to ask. Sometimes we don't understand straightforward answers, because we are new to the whole procedure, and are not engineers, or steeped in academia.

This would provide a graduated information system, with USER feedback included, that could help bridge the gap, between software development, and user experience.

I think this basic idea, (In the mechanism I mention above) or similar, is a needed component for the overall program.

Kind Regards
Nate
 

Nate The Surveyor

Well-Known Member
Matt, I am suggesting a basic framework, where each part of the file has it's own list of directions. ONCE the framework is in place. That is, the buttons in parts of the program, then it can be infinitely modified, and built as needed.
Just thinking. Kinda like shoptalk.
Nate
 

Nate The Surveyor

Well-Known Member
Why not start installing active links, that are just an "I", with colored circle around it. That link to the e-manual. ("I" stands for information). Start now installing them. We just make it a bare-bones manual for now, but start it now.
I'm referring to "make the structure". And, make the manual so that the 5-pls team can write modify, and edit the manual. This puts just the addition of the structure onto the programers, NOT the writing of the manual. And, the writing of the manual onto those with more familiar with English, on the actual manual.
What could go wrong?
Maybe Adam plumleys southern drawl. But, nobody would know, unless sound bytes are included!
N
 
Top