DPOS > OPUS-RS

[Wes Cole]

I wasn't sure exactly where to post this, so I just stuck it under Triumph-LS/Victor-LS

Been testing short observations and processing them through DPOS lately. I've tested 5 minutes, 15 minutes, and 30 minute observations and haven't observed a significant difference between them, particularly in the horizontal. DPOS is far superior to OPUS in my opinion for several reasons:

1. it incorporates Glonass in it's solution
2. you can get very good horizontal data in less than the 15 minute minimum OPUS-RS requires
3. it will process data nearly immediately. i've noticed it's is almost negligible when waiting 1 or 24 hours to process. See comparison below of observations at 5/15/30 minute intervals, processed within 2 hours of the observation and processed +24 hours of the observation.
4. OPUS doesn't have a sweet forum like this to brag about the results

I've also tested DPOS vs RTN values taken yesterday with the LS, with astounding results. Keep in mind these are in ideal GPS locations, open with little to no multipath. These are 200 second observations!! I processed the static file that was stored while taking the RTN shot.

Pretty incredible.

 

[Adam]

Very nice Wes. Thanks for sharing that.

 

[Nate The Surveyor]

REALLY Wes, thanks!!!

One factor, that I did not find in your solution, was how far from the cors stations you are. I find that things are not that good here. I think I am 60 mi to the closest cors sta.


As I get it, there are several ways to dpos.
Would those of you who know, mind sharing all of them?

1.) LAN wire when you get home.
2.) MIFI device, through your cell phone.
3.) IF your LS came with it's own mechanism, to process cell corrections, then it can process that way? (not sure about that one, but it is logical).
Any other ways?

 

[Wes Cole]

REALLY Wes, thanks!!!

One factor, that I did not find in your solution, was how far from the cors stations you are. I find that things are not that good here. I think I am 60 mi to the closest cors sta.


As I get it, there are several ways to dpos.
Would those of you who know, mind sharing all of them?

1.) LAN wire when you get home.
2.) MIFI device, through your cell phone.
3.) IF your LS came with it's own mechanism, to process cell corrections, then it can process that way? (not sure about that one, but it is logical).
Any other ways?

Nate--you're welcome! I find this sort of thing fascinating. That you can get extremely accurate results, in very short observations, and multiple methods and checks for processing these results, is leaps and bounds above the other GNSS manufacturers. I like that with DPOS I can get another solution to my 3 minute RTN observation. I'm probably not going to rely heavily on the 3 minute DPOS results but it's a great independent check.

We are very fortunate in North Carolina to have a whole bunch of CORS stations around us. It's not that there's one in every county but it's pretty dang close. Add to that, in Western North Carolina I'm very near East Tennessee and Upstate South Carolina I often get TN and SC CORS in my solution too.

Here's a screen grab of my DPOS report showing distance to CORS stations for TP#4 (a/k/a L1-DPOS).

I DPOS from the LS over wifi (mobile or in the office) if I'm using base rover and through the DPOS website if it's an RTN observation. I just archive the project and grab the .jps file and upload to DPOS...about 1 minute later I have a solution. Wham! Bam! Thank you ma'am!

 

[Adam]

Lets see, Marion - Brevard - Hendersonville - Swannanoa? - Madison?

 

[Wes Cole]

Got them all right but one...NCBR is Burnsville. Brevard doesn't have a CORS, looks like they're installing one in Rosman though.

 

[Wes Cole]

REALLY Wes, thanks!!!

One factor, that I did not find in your solution, was how far from the cors stations you are. I find that things are not that good here. I think I am 60 mi to the closest cors sta.


As I get it, there are several ways to dpos.
Would those of you who know, mind sharing all of them?

1.) LAN wire when you get home.
2.) MIFI device, through your cell phone.
3.) IF your LS came with it's own mechanism, to process cell corrections, then it can process that way? (not sure about that one, but it is logical).
Any other ways?

Nate you bring up a great point. We're lucky to have all these CORS around us here, but in areas where the CORS are more sparse you'd probably not get these solutions with short observations due to the vector lengths. 60 miles is a long vector! It'd be interesting to see how those process and other's thoughts on it.

 

[Wes Cole]

Back on another point yesterday where cell services was spotty. The crew on this project tried doing a couple of static sessions with an Epoch 50 and the 2 hour position processed but with terrible peak to peak results. The OPUS-RS session wouldn't even process. The site wasn't exactly ideal, I'll admit that. I went back yesterday with the LS and while the cell data struggled to keep me on the RTN I was able to collect 2 obs on 2 different points in about 12 minutes on each point. One of my observations "L3" had about 6 minutes 45 seconds of static data to get to 200 seconds. I processed that 6:45 file through DPOS and all I can say is WOW! The LS and DPOS is such an awesome tool. I'll add that the NC RTN is top notch too.

See below...

The OPUS position on that same point was N: 585086.359, E: 902368.763, O: 2363.22