I took this course this morning to evaluate it for use within the agency I work for. I found it to be a solid primer to understanding the factors to consider when planning and preparing for a field GNSS control campaign. I tend to go a little deeper in to the use of NGS Data Explorer to perform what I call "Desktop Recon" by using the street view feature to evaluate the conditions around the marks being considered. Often, some or many can be eliminated from the field recon list based on what is seen in street view, such as obvious sky obstructions, safety concerns, or signs of new construction that likely destroyed or disturbed the mark.?ÿ
Still, this short course gets my "thumbs up" for use in educating any surveyors who are planning such a campaign. How many of you look at time series plots for CORS? I do, and I teach it in the classes I present.?ÿ
You will need to set up an account to access it here:
"How many of you look at time series plots for CORS?"
ALWAYS! Evaluating BOTH the "short term" and "long term" behavior of ANY CORS that you plan on using to determine your "remote" [new] station position(s), should be the FIRST thing on your "to do list." I NEVER EVER let OPUS chose CORS Stations (although it does a much better job than it used to), and tend to be very picky about the CORS that I use whether it's for an OPUS_S, OPUS_Projects, or a Roll-Yer-Own solution & adjustment.
Loyal
A strategy when working in a new area could be to let OPUS pick three CORS, then run the same file again with the option to EXCLUDE those three. That will give you the six that OPUS likes best so should be somewhat reasonable choices.?ÿ Then look at the six to pick the three you like and run specifying USE those.
