Multi-band receivers, such as Reach RS2, can work up to a 100 km baseline in PPK. But it’s always worth using the shortest possible baseline for the best accuracy. The 20 km, in your case, should work fine. You’re good to go.
The main thing about accuracy is that it depends on several factors besides the baseline, such as the environmental conditions or the satellite visibility. So, it can happen that the accuracy will be different in two different surveys, both with a baseline of 60 km.
Talking about particular values in case of such a baseline, we can get an estimation based on the specifications of Reach RS2.
Horizontally: 5 mm + 0.5 mm/km x 60 km = 35 mm = 3.5 cm
Vertically: 10 mm + 1 mm/km x 60 km = 70 mm = 7 cm
Myself believes in short baselines in all GNSS use. You’ll have a greater guarantee of “fixed” baselines. It so easy to setup a base onsite. I’ve never tried to post process any drone baselines to a CORS and I don’t want to. For me baseline distances are to far (>20km) and they don’t record any faster than a 1 second rate.
Same. Being in Texas CORS is rarely an option, and I would never run a drone on the network here. Texas is just too big, and networks are sketchy unless you are in the more populated areas and that’s not where infrastructure construction and Surveying are happening. More importantly for my use case you can’t put a CORS on localized coordinates. I’ll stick with network derived local base using a localized network and LoRa corrections to the rover with local NTRIP for the drone.