MightyMoe, post: 428697, member: 700 wrote: not every point gets 4 plus hours of set on time
Exactly. With the density of CORS in southeast Louisiana, I can get very good results with occupation times as short as ten minutes (not that I make a habit of that). Even in places like West Texas where the CORS are less dense, I can get extremely tight results with 2 - 3 hour sessions - exactly the occupation times that OPUS often struggles with.
Lee D, post: 428700, member: 7971 wrote: Exactly. With the density of CORS in southeast Louisiana, I can get very good results with occupation times as short as ten minutes (not that I make a habit of that). Even in places like West Texas where the CORS are less dense, I can get extremely tight results with 2 - 3 hour sessions - exactly the occupation times that OPUS often struggles with.
I've been processing 3 minute PPK sessions against CORS 30 miles distance and getting good results. The idea of setting on every point for 4-8hrs is a no go of course. No problem collecting that type of data for a base/rover on the base since it's sitting there anyway, but taking OPUS data on each point is just a time waster.
Often times the PPK session won't process to a far away base, but it doesn't hurt to give it a go when the CORS point is sitting there in the file anyway.
I recently had a 70 minute setup, I processed it to three CORS points (20mi, 95mi, 140mi), no problem, RTX wouldn't look at it, you couldn't even check the box.
I've been using OPUS more and more lately. It's a great free lunch.
mattharnett, post: 428732, member: 6458 wrote: I've been using OPUS more and more lately. It's a great free lunch.
And if you only one, older receiver you're not even in deep.