I missed posting about the single GLONASS M launch two days ago.
Currently my planning software shows 23 healthy GLONASS satellites and very good PDOP around the clock. I expect that the most recent launch would fill in the lone empty slot making the GLONASS constellation full.
Paul in PA
Dumb here - Will lightsquared mess with their signals too?
Don't have any idea if they are even close to the same band.
Might have to rely on them for good positioning;)
Yep, almost full, apparently with a few more coming in the next couple of years if I remember correctly. Now I am having a new problem. I use 5 sec record rate for static, and all my receivers have 4 meg of memory. The units that can get GLONASS are now filling up 1/3+ quicker then the GPS units. I am able to get about an 8 hr day out of GPS units, but only 5-6 with the GLNOASS. I need more memory now, just don't want to spend that on units of this age. They work great for what they are now, but I am not sure adding more memory is wise money spent right now.
All in all, I guess it is a good problem to have.
Switch To 10 Seconds
I have used 10 seconds for years, only switching to 5 when I want to match up with another surveyor who uses 5. If I find I need 1 or 5 seconds later I interpolate my 10 second data. The only real time I needed to interpolate to 5 seconds was when the only nearby CORS were COOPS that collected at 15 seconds and I downloaded directly from the COOP. Now all are avaialble through NGS and there are so many new CORS it is no longer a problem. Since NGS stores the data at 30 secon epochs I can easily request 10 second data from a a 15 second CORS and let "ufcors" do the interpolating for me.
Paul in PA
Are you required to log 5 sec data?
Overhere, when we did static, we logged at a 10 sec interval.
Chr.
It depends on which type of static you are using. For classical static, 60 sec is good enough. For fast/rapid static, then you're stuck with 5 sec (or 10 sec as the other guys noted).
http://facility.unavco.org/kb/questions/70/GPS+Data+Collection+Methods
> Yep, almost full, apparently with a few more coming in the next couple of years if I remember correctly. Now I am having a new problem. I use 5 sec record rate for static, and all my receivers have 4 meg of memory. The units that can get GLONASS are now filling up 1/3+ quicker then the GPS units. I am able to get about an 8 hr day out of GPS units, but only 5-6 with the GLNOASS. I need more memory now, just don't want to spend that on units of this age. They work great for what they are now, but I am not sure adding more memory is wise money spent right now.
>
> All in all, I guess it is a good problem to have.
Not really 'required' to use 5 sec, but I have been using it for years, and have better results then longer durations. Talking classic static here. Yes, 30, or 60 seconds would work fine, but when I am pushing the limits with trees, the more 'shots' you can get between the trees the better chance you are going to get a good solution. CORS download at any rate I want, so that is not an issue. 5 sec is just what I have been using for a very long time. Maybe it is time to drop to 10 seconds, anything longer, I would be worried that I would be getting less (good) data, or more noisy data.