I really like this option and cant wait to try it out as for my work it will be the case that i will need to use Base shift to survey sites oth on the ground and from above that are often away from the roads and known points, great video thank you..
Be careful if using a RTK drone and emlid caster. The base shift only affects the rover data, the base is not shifted and therefore your rtk corrections to the drone are not shifted. This will cause inaccuracies when you process the data
Fantastic video, one question, how do you read the new position of the base station so you can record the new TBM that you put in so tomorrow when you set up you can put correct details in and not need to base shift? Ofcourse you still confirm with the known points for good practise but shouldn’t need to base shift again?
Hi Jack, the easiest option would be to use your tilt compensated rover (e.g. Reach RS3) to pickup the point under the base to use the next day as you won't be directly over the mark. A slower but potentially more accurate solution would be to have the base logging RINEX while surveying day 1, then process the RINEX file with AUSPOS on the next UTM day to get your point (rapid static). There may be another (easier) option - but we'll need to double check this before publishing it as a solution.
@@MangoesmappingAUI think going forward I’ll put a new Benchmark inside job whilst base shift is active and re set back up on it the next day with those coordinates and heights. I’ll go back and stake stake out existing control to hopefully confirm its spot on
Localisation is useful when we don’t have the precise parameters of the local coordinate system. In this instance we have the coordinates from the local survey marks (PSM's) so localisation is not required in this instance. Olga from Emlid explains this really well in this link: community.emlid.com/t/localization-in-emlid-flow/35351
I really like this option and cant wait to try it out as for my work it will be the case that i will need to use Base shift to survey sites oth on the ground and from above that are often away from the roads and known points, great video thank you..
Great tutorial! Thanks to sharing knowledge! Success!
Be careful if using a RTK drone and emlid caster. The base shift only affects the rover data, the base is not shifted and therefore your rtk corrections to the drone are not shifted. This will cause inaccuracies when you process the data
Thanks for that tip. I'm not sure our team have come across this as they usually use a PPK workflow.
Could you do a PPK workflow tutorial for collecting GCPs and flying an RTK enabled drone (DJI Prefered?) @@MangoesmappingAU
Fantastic video, one question, how do you read the new position of the base station so you can record the new TBM that you put in so tomorrow when you set up you can put correct details in and not need to base shift? Ofcourse you still confirm with the known points for good practise but shouldn’t need to base shift again?
Hi Jack, the easiest option would be to use your tilt compensated rover (e.g. Reach RS3) to pickup the point under the base to use the next day as you won't be directly over the mark.
A slower but potentially more accurate solution would be to have the base logging RINEX while surveying day 1, then process the RINEX file with AUSPOS on the next UTM day to get your point (rapid static). There may be another (easier) option - but we'll need to double check this before publishing it as a solution.
@@MangoesmappingAU thank you
@@MangoesmappingAUI think going forward I’ll put a new Benchmark inside job whilst base shift is active and re set back up on it the next day with those coordinates and heights. I’ll go back and stake stake out existing control to hopefully confirm its spot on
Question - with the known points that you pick up would you do a project localisation on them within the app?
Localisation is useful when we don’t have the precise parameters of the local coordinate system. In this instance we have the coordinates from the local survey marks (PSM's) so localisation is not required in this instance.
Olga from Emlid explains this really well in this link: community.emlid.com/t/localization-in-emlid-flow/35351
I reckon that hold and copy feature that you have with Benchmrk must be an Apple feature as I can't do it with my Android
Good to know, will pass it on to the Geolocarta team.