@lee-d?ÿ
The geophysicists I worked debated this topic a bit.
Tectonic movement obviously can use slower collection times, and if you're not collecting at a local base, the nearest CORS might only be collected at 30sec.
The most important part is that the satellites are getting time to move across the orbital to provide better solutions. Sometimes it's not ideal to collect at 1hz, just depends.?ÿ And the most interesting thing about the collection is that the GPS doesn't need to be collected simultaneously.?ÿ This was the best thing I learned while working for the aero mapping company I worked for.
Fun topic.
@lee-d Trimble RTX post processing processes data at a 10s rate, though if you??re logging data for 2+ hours, 30s is fine. And I only hear of people using OPUS, if they ever observe static anymore.
@lee-d?ÿ
Not to mention storage space isn't a factor for pretty much any receiver manufactured in the last decade...I can't remember the last time I set up a receiver to log at anything other than 1s/1Hz. It gives you the most flexibility for post processing and costs nothing extra to set up or work with it.
The CORS I'm used to using tend to collect data at a 1 second rate. I normally collect my field data at a 5 second rate and try and locate PPK points such as property corners for at least 45 seconds.
Except for the base point, I don't structure anything I do to match up with OPUS. Even running static control I will keep to the 10 plus 1 per mile rule. That is woefully outdated but it is usually accomplished as I work other tasks with static control work.?ÿ
The modern storage capabilities of receivers override many of the old rules along with their accuracy. Nothing is as outdated as a GPS textbook from 20 years ago.?ÿ
@mightymoe just because CORS data you intend to use records at 1s, doesn??t mean that you must too!
