Long ago I was told that baseline length limit for rapid static vectors is 20km. This because the atmospheric conditions are assumed to be the same at both the base and the rover, which is also true for an RTK vector.?ÿ I believe that limit is arbitrary, but it is certainly true that getting a good resolution becomes more difficult to achieve as you approach that limit.?ÿ There will be errors to the extent that the assumption about the atmosphere is untrue. A 24km long vector is apt to be sketchy.
I wouldn't go 24km, 10km has always been the recommendation. Much of what has been rule of thumbs about GPS comes from older units.
Some of the ideas about GPS procedures are way outdated, but pushing RTK out to 24km isn't one of them.?ÿ
I would say (as usual), it depends. CORS stations in my area are few and far between, and not always functioning, so there are occasions that we have little choice. We try to keep below 10-12 km for most purposes. On one occasion a crew checked one that was over 80 miles away and had a horizontal check within 0.10 feet and vertical less than that. We know this was a fluke, but thought it was quite interesting...
Single-base solution? No more than 20km or so before the solution really starts to degrade. Same as base-rover configuration with corrections over UHF or cellular.
Network solution? As long as you are within the service envelope, you'll be fine.
Now, the latter assumes the RTN operators have spaced their stations appropriately. Generally 30-70km is the recommended spacing for networks. You'll see precisions float around depending on distance from surrounding stations.
Latency, whether over cell or UHF, does affect things.
Thank you for the info
It depends on your accuracy requirements. Trimble R10/12 for RTN/VRS use is plus/minus 0.5 PPM which creeps into larger values when you get far from your CORS base
