Is it reasonable to use a single baseline solution in areas where the RTK rover keeps switching base stations? In certain parts of the county we start out with a multiple reference station solution and the RTK rover keeps switching base stations. We use L-Net (Lengemann Corporation, FL).
According to a guide to using the Florida Permanent Reference Network, the following rules should be observed:
- As a General guideline when using a Real-Time Reference Network when within 12
kilometers or 7 miles of a reference station you should use the single baseline correction - If outside the 12km range you should use one of the Network solutions
- Finally, when using Real-Time corrections, whether single baseline or network solution, you
should ??localize? to known control
I assume this could be used as a general guideline when using any reference network. I'm confused about rule 3. If you're fixed (vs. autonomous), aren't you using real-time corrections? We work only using a fixed solution. What if there isn't any known control available to "localize" to?
I have seen RTN's NOT pick the closest CORS, if working a small area, and close to a particular CORS, you might just use the one you want, BUT be careful, the software is supposed to pick the appropriate one, as long as it does, all OK, BUT you picking a single baseline that is way away will introduce some scaling errors.
Usually I am pretty on top of what the system is doing, definitely need to pay attention. Sometimes you are right on edge and it flip between CORS and is probably what you are seeing.
SHG