I am trying to stake out elevations on the fly by simply using the elevation value that is shown when in point staking mode however the value in on average 5-7 cm higher than the final point value that gets recorded. See pictures below. When creating the point the elvation showing was 463.834m but when I go look at the point data is was recorded as 463.768cm, a difference of 6.6cm. See pictures below.
Why the difference?
I see that total observed time was 42 seconds. Maybe the final value is the average of all recorded Fix values? Not sure, maybe better to wait for someone from Emlid to chime in.
I performed some testing to and took points at the same location over longer periods of time and the elevation when taking a point is exactly 6.5 cm higher than actual recorded point elevation. Not sure if this is related but 6.5cm the the height from the base of the unit to the centreline if the gps antenna.
Do you have the raw-files, so you can check by post-processing ?
May I ask you to share the CSV files? I believe they can help to detect the possible cause of the issue.
Attached is the CSV. What I’ve been doing to get real time elevations in the field is lowering my pole height by 6.5cm, rather annoying by it works.
Test3-CSV.zip (557 Bytes)
Thanks for the data. I’ll check it and answer you as soon as possible.
As you’ve noticed, a 6.5 cm offset is the antenna height. Our Survey tool includes the automatic antenna adjustment feature. So, the antenna height was automatically added to the result.
During the survey, the height is displayed with only the pole height applied. The antenna height offset is applied after the point is collected.
Thank you Kseniia. Will this issue be resolved in future updates? This is misleading to the user if he is not aware.
You can try our beta ReachView 3 app. In ReachView 3, the antenna height is added during the point collection.
Thank you for this information. I noticed this exact same problem yesterday and it was a real head scratcher for me. The forum is great, here i found the answer. I will download reachview 3 and try it out! In my case it was the RS2 antenna offset that wasnt inclided during the survey.
Glad to hear that! It’d be great if you could share your experience with the ReachView 3 app.
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.