the problem was not collecting if not reviewing points already measured
Have you encountered this issue since the last test?
If yes, can I ask you to describe your steps starting from placing the base on?
hello Andrew, the configuration of the base is not a problem, visit already measured points and there was very little difference I measured them again and in the same points there is a difference of 26 cm. After a few minutes the stakeout did not have the difference of 26 cm. It’s very weird
RS+ right? Same here all the time. My localizations with FieldGenius aren’t even consistent because I can’t get every point to tie correctly. I end up cutting my network down to 4-5 points just to get a consistent 3-4cm which is pushing our contracted tolerances. Unfortunately I think it is just the conditions I am in so I will have to bear with it until I can get the RS2’s…
it is only in some conditions, I did not obtain more than 2 cm of difference between points already measured as I did a resection with total station and the differences were of mm. I also wait for the RS2 !!!
Only in some conditions? Curious, are you using FIX AND HOLD or CONTINUOUS?
Do you think you’re getting a FALSE FIX using FIX AND HOLD?
Normally you must also make a transformation of the WGS-84 system towards the terrestrial system (utm ground coordinates), so that the measurements made with the GNSS receiver are in conformity with the measurements made by the conventional instruments.
Did you record the BASES Average Single coordinates of the first visit, then plug them back in on the next visit to remeasure at the same exact BASE mark?
I don’t think that is the issue in this case with the way he shot them in. If they were originally located with the Reach RS+ and then resected by the instrument the relativity should be the same. He should be able to consistently stakeout with expected tolerances with the Reach RS+. This is most likely a matter of GNSS precision and the quality of the RTK.
@chascoadmin I agree with you…
Now I think your scenario comes in if he was using local grid, collected those points with the instrument off the ground coordinates and then tried to match them up… That’s what happens to me all the time when I try to localize to the network our surveyors already had setup. It would be nice if I could just import there localization file… Ok, back on topic.
Yes Fix and Hold
the same base
Wonder if you need to measure a THIRD time all the good, the bad (and the ugly) points? First FIX AND HOLD, then CONTINUOUS to see if something weird is still happening. (Third time’s a charm… or it’s all just effed up).
I don’t think your holding your mouth the right way, or the planets haven’t lined up just right. ; )
They were not just simple checks to see the quality of the measurements. It is very rare what happened I always have a difference between 1 and 2 cm with the total station by the cartographic projection. I noticed it for the first time when I wanted to check a stake I had put weeks ago! It’s like you say a fixed false. And I clarify that it is when I make a stakeout of a point already measured, only twice I pass. once with Lora and once with Ntrip
I would temporarily leave the total station out of the equation for now. Re-check using ONLY your RS+ BASE & RS+ ROVER via LoRa. See if you get very close results with either FIX AND HOLD, then try with CONTINUOUS. Once you dwindle that down, then you can use the total station or even your CORS station to compare again. It may just be a FALSE FIX, so CONTINUOUS should solve that, but you won’t know until you try.
Thank you ! I will try it and I will comment.
unfortunately I do not have CORS available to a radius of 15 km, I can not do that test. I’ll do it when the RS2 arrives
No worries, just use your (2) RS+ BASE & ROVER via LoRa so you can rule out if there is a problem with the receiver(s) or the RTK settings etc. Then go from there.
These are the data of the second day of survey, always use the same work with which I could review points of the previous day with the same base in NTRIP.