Javad DPOS and Triumph 1/LS

Adam

Adam

Well-Known Member
5PLS
Alexey, I am curiuos what is the advantage to using OPUS instead of DPOS for our receivers. DPOS is so much easier to use. I only use OPUS for these other recievers usually. How did you convert the data from the Epoch's for use with DPOS? I can set the Triumph LS up and get some static data too, if you like.
 
Alexey Razumovsky

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
Adam said:
Alexey, I am curiuos what is the advantage to using OPUS instead of DPOS for our receivers. DPOS is so much easier to use. I only use OPUS for these other recievers usually. How did you convert the data from the Epoch's for use with DPOS? I can set the Triumph LS up and get some static data too, if you like.
Click to expand...
1. I guess some surveyors trust OPUS more than DPOS because of they used OPUS for years. 2. Justin software converts RINEX to jps. 3. Triumph-LS is OK for testing. Your last scheme is excellent.
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
If someone is planning on discussing this with NGS again I think it would be best if we had data from some of their control points. See http://www.ngs.noaa.gov/NGSDataExplorer/ to find control points:

upload_2016-2-3_10-2-23.png


"GPS and Vertical Control" points would be best.
 
J

John Evers

Well-Known Member
5PLS
I agree Matt. We can plan a campaign on that.

Alexey, I ran into a problem borrowing my neighbors receivers. Our ground thawed out, and they are all being used to run various machines right now. Using my T2 the past several days I recorded and submitted three files. OPUS has not yet accepted Day 3.
Day 1 @ 6 HOURS : ORTHO HGT: 289.922(m) 0.031(m) OPUS = 951.186' -- DPOS = 951.083'
Day 2 @ 7 HOURS: ORTHO HGT: 289.911(m) 0.025(m) OPUS = 951.149' -- DPOS = 951.025'
Day 3 @ 8 hours: OPUS = not yet -- DPOS = 951.091'
 
Shawn Billings

Shawn Billings

Shawn Billings
5PLS
John Evers said:
I agree Matt. We can plan a campaign on that.

Alexey, I ran into a problem borrowing my neighbors receivers. Our ground thawed out, and they are all being used to run various machines right now. Using my T2 the past several days I recorded and submitted three files. OPUS has not yet accepted Day 3.
Day 1 @ 6 HOURS : ORTHO HGT: 289.922(m) 0.031(m) OPUS = 951.186' -- DPOS = 951.083'
Day 2 @ 7 HOURS: ORTHO HGT: 289.911(m) 0.025(m) OPUS = 951.149' -- DPOS = 951.025'
Day 3 @ 8 hours: OPUS = not yet -- DPOS = 951.091'
Click to expand...


Those height error estimates look pretty rough. I would recommend posting the ellipsoid heights, John. You'll notice that the height errors are less and it removes one extra source of interpretation (geoid model).
 
J

John Evers

Well-Known Member
5PLS
Re-post with ellipsoid elevations.

Day 1 @ 6 HOURS : OPUS = EL HGT: 257.207(m) 0.013(m) DPOS = EL HGT: 257.166(m) 0.005(m) .041 below OPUS
Day 2 @ 7 HOURS : OPUS = EL HGT: 257.196(m) 0.007(m) DPOS = EL HGT: 257.172(m) 0.005(m) .024 below OPUS
Day 3 @ 8 HOURS : OPUS refuses to accept this file DPOS = EL HGT: 257.195(m) 0.008(m)
OPUS AVG = 257.201 DPOS AVG = 257.177

That difference sure matches the length of the adapter. For now, it looks like the answer is to subtract 0.083' from the OPUS elevation. It appears to me that OPUS is actually subtracting the adapter offset from the measured antenna height?
 
Alexey Razumovsky

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
John Evers said:
I agree Matt. We can plan a campaign on that.

Alexey, I ran into a problem borrowing my neighbors receivers. Our ground thawed out, and they are all being used to run various machines right now. Using my T2 the past several days I recorded and submitted three files. OPUS has not yet accepted Day 3.
Day 1 @ 6 HOURS : ORTHO HGT: 289.922(m) 0.031(m) OPUS = 951.186' -- DPOS = 951.083'
Day 2 @ 7 HOURS: ORTHO HGT: 289.911(m) 0.025(m) OPUS = 951.149' -- DPOS = 951.025'
Day 3 @ 8 hours: OPUS = not yet -- DPOS = 951.091'
Click to expand...
Please, files.
 
Shawn Billings

Shawn Billings

Shawn Billings
5PLS
Alexey Razumovsky said:
What is a height in reality?
Click to expand...

From many observations on this mark using many different receivers over many years, the NAD83(2011) Ellipsoid Height is 96.450m.

It is a 5/8"x11 threaded mount. So the measured height is always 0.00m except in the case of the Triumph-2 which uses the 25mm adapter.
 
J

John Evers

Well-Known Member
5PLS
Alexey,

I have combined three files into the attached zip file.
 

Attachments

  • john jps files.zip
    11.7 MB · Views: 379
Alexey Razumovsky

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
John Evers said:
Re-post with ellipsoid elevations.

Day 1 @ 6 HOURS : OPUS = EL HGT: 257.207(m) 0.013(m) DPOS = EL HGT: 257.166(m) 0.005(m) .041 below OPUS
Day 2 @ 7 HOURS : OPUS = EL HGT: 257.196(m) 0.007(m) DPOS = EL HGT: 257.172(m) 0.005(m) .024 below OPUS
Day 3 @ 8 HOURS : OPUS refuses to accept this file DPOS = EL HGT: 257.195(m) 0.008(m)
OPUS AVG = 257.201 DPOS AVG = 257.177

That difference sure matches the length of the adapter. For now, it looks like the answer is to subtract 0.083' from the OPUS elevation. It appears to me that OPUS is actually subtracting the adapter offset from the measured antenna height?
Click to expand...
Shawn Billings said:
From many observations on this mark using many different receivers over many years, the NAD83(2011) Ellipsoid Height is 96.450m.

It is a 5/8"x11 threaded mount. So the measured height is always 0.00m except in the case of the Triumph-2 which uses the 25mm adapter.
Click to expand...
Got it.
 
You must log in or register to reply here.
Top