Nate The Surveyor
Well-Known Member
This is in DPOS
Our base coordinate origin, can be:
Autonomous
CORS fixed
M-Local (or 1-Local)
Then, FROM this BASE coordinate, we do all out surveying.
And, those side shots, can be RTK, or PPK.
-------------------------------------------------------------------
OPTION A
Here is what is happening:
When we set the base origin to be CORS, and then look at the sideshot coordinates,
we can select RTK, OR PPK, as we wish.
We get a popup, that has 3 options.
1.) Select the PPK coordinate for this point only
2.) Select the PPK Coordinate for ALL points
3.) Auto Select the best RTK/PPK for all points.
This is GOOD, and how it should be.
-------------------------------------------------------------------
OPTION B
When we set the base origin to be 1 LOCAL, and then look at the sideshot coordinates,
we now have ONE LOCAL as an option.... (Which should not be an option, as that should only be an option for the base point).
So, we now have these 3 options, but, should only have 2 options here, and we select RTK, and we get a popup, with 2 options.
1.) Select the RPK Coordinate for ALL points
2.) Auto Select the best RTK/PPK for all points.
But, we should have a popup identical to the one for OPTION A.
---------------------------------------------------------------------------------
I feel that NO MATTER what the base origin is, we should be allowed to select RTK, or PPK, as we wish.
Auto select is ok, but when there is a difference, between these, we should have an option, to "LOOK AT ALL POINTS, with a difference of greater than _________ (User select-able value) , and here, we look at ONLY the points with a significant difference. It would even be better, if we had an option, for
Difference <greater than> 0.30 ft_____ shows up RED. (Worst offenders show up first, and then progressively, by order of magnitude)
Difference <greater than> 0.15' _____ shows up GREY (Worst offenders show up first, and then progressively, by order of magnitude)
Difference <greater than> 0.08'_____ shows up BLUE (Worst offenders show up first, and then progressively, by order of magnitude)
DIfference <greater than> 0.05'_____ shows up green (Worst offenders show up first, and then progressively, by order of magnitude)
RED is the worst difference.
GREY is POOR.
BLUE is tolerable, but not too good.
and, GREEN below all this. (These are
Now, these values should be user select able, but perhaps these can be default values.
By doing this, we can set up a project, to look at what is critical first.
What I'm afraid of, is accidentally overlooking a point, that had an RTK/PPK difference, that was critical, and missing it. This organization of looking at the way coords are created, will help prevent it.
This RED-GREY-BLUE-GREEN filter, should be under DPOS, and should simply be an option, so that we improve our efficiency when viewing results of our work.
I'm sure that this list of ideas could be improved upon, but I'm just throwing this on the site, for discussion, and as raw material, for the production of a better program.
Thank you,
Nate
Our base coordinate origin, can be:
Autonomous
CORS fixed
M-Local (or 1-Local)
Then, FROM this BASE coordinate, we do all out surveying.
And, those side shots, can be RTK, or PPK.
-------------------------------------------------------------------
OPTION A
Here is what is happening:
When we set the base origin to be CORS, and then look at the sideshot coordinates,
we can select RTK, OR PPK, as we wish.
We get a popup, that has 3 options.
1.) Select the PPK coordinate for this point only
2.) Select the PPK Coordinate for ALL points
3.) Auto Select the best RTK/PPK for all points.
This is GOOD, and how it should be.
-------------------------------------------------------------------
OPTION B
When we set the base origin to be 1 LOCAL, and then look at the sideshot coordinates,
we now have ONE LOCAL as an option.... (Which should not be an option, as that should only be an option for the base point).
So, we now have these 3 options, but, should only have 2 options here, and we select RTK, and we get a popup, with 2 options.
1.) Select the RPK Coordinate for ALL points
2.) Auto Select the best RTK/PPK for all points.
But, we should have a popup identical to the one for OPTION A.
---------------------------------------------------------------------------------
I feel that NO MATTER what the base origin is, we should be allowed to select RTK, or PPK, as we wish.
Auto select is ok, but when there is a difference, between these, we should have an option, to "LOOK AT ALL POINTS, with a difference of greater than _________ (User select-able value) , and here, we look at ONLY the points with a significant difference. It would even be better, if we had an option, for
Difference <greater than> 0.30 ft_____ shows up RED. (Worst offenders show up first, and then progressively, by order of magnitude)
Difference <greater than> 0.15' _____ shows up GREY (Worst offenders show up first, and then progressively, by order of magnitude)
Difference <greater than> 0.08'_____ shows up BLUE (Worst offenders show up first, and then progressively, by order of magnitude)
DIfference <greater than> 0.05'_____ shows up green (Worst offenders show up first, and then progressively, by order of magnitude)
RED is the worst difference.
GREY is POOR.
BLUE is tolerable, but not too good.
and, GREEN below all this. (These are
Now, these values should be user select able, but perhaps these can be default values.
By doing this, we can set up a project, to look at what is critical first.
What I'm afraid of, is accidentally overlooking a point, that had an RTK/PPK difference, that was critical, and missing it. This organization of looking at the way coords are created, will help prevent it.
This RED-GREY-BLUE-GREEN filter, should be under DPOS, and should simply be an option, so that we improve our efficiency when viewing results of our work.
I'm sure that this list of ideas could be improved upon, but I'm just throwing this on the site, for discussion, and as raw material, for the production of a better program.
Thank you,
Nate
