Robert P Stenerson
Active Member
I went to COGO, then DPOS, then I see the base file already highlighted, but no DPOS button?
Javad DPOS and Triumph 1/LS
- Thread starter Jason Scott
- Start date
You need to press Undo first.
Robert P Stenerson
Active Member
Ahhh...the glasshoppah is learning, thanks Matt 
That result is looking much better. you'll need to hit adjust once you're comfortable with the results.
RMS looks good, plus you've got a lot more CORS now being used. Notice that the actual coordinates didn't change much between the DPOS solution with one CORS and the DPOS solution with multiple CORS. The statistics were overly pessimistic from your first run. Previously the N was .8892 now .8852 the East was .9053 now .8139 and the Up was .2116 now .2402 (this is comparing your first DPOS result with the new DPOS result). Less than 0.10 foot difference! But I wouldn't have trusted the earlier one, even though it proved out ok. The statistics may have false flagged the result, but how do you know? This result I'd take to the bank.
How long should you wait to submit to dpos for the best solution?
Robert P Stenerson
Active Member
I didn't realize it would come back so fast, I'd already left office, it indicated it was waiting for the new solution (how cool is that!) So now if I want to readjust my points that came off that base, what's the steps for that?
Since I 've got you on a hot stove here, the next day I set up a stand alone session, a mag I set in the State Game Lands, SGL etc. etc. I set it to record every 30 seconds (my old OPUS habits) for about 2-1/2 hours. Since there was no Base/Rover setup, is there a similarly easy routine to submit that to DPOS as well in the LS. Or will I have download the .Jps file and submit through the web site?
You guys have been great
Since I 've got you on a hot stove here, the next day I set up a stand alone session, a mag I set in the State Game Lands, SGL etc. etc. I set it to record every 30 seconds (my old OPUS habits) for about 2-1/2 hours. Since there was no Base/Rover setup, is there a similarly easy routine to submit that to DPOS as well in the LS. Or will I have download the .Jps file and submit through the web site?
You guys have been great
If you didn't use base rover setup, you won't be able to use DPOS in J-Field. You can use DPOS from the web or of course OPUS from the web. Once you get results back, you will go to points, highlight any point that used that base position, press the blue field next on the right side of the point list screen, and you'll be taken to a base/rover statistics screen. In the upper left, you'll see a blue button marked "BASE". When you press it, you'll be warned about modifying the base position. Select OK and you'll be shown the base position in the currently active coordinate system. Manually enter the coordinates from the OPUS or DPOS websites. Then when you apply ALL points that were collected with the same autonomous coordinates for the base will be translated to your shiny new base coordinates. You'll also see SHIFT values in the base rover statistics screen just like you would from DPOS through J-Field. It's not nearly as slick and elegant as DPOS through J-Field, but it works just the same.
Adam, you asked about how long to wait for best results. I'm not sure just how fast you can get results. I've made it part of my workflow to collect data today with my autonomous base, and process the DPOS file first thing in the morning before I draw up my work in CAD. So far it's been very successful. I don't know if I could pull that off earlier if my field day was short, for example. Maybe Alexey can offer some insight, but it just hasn't been much of a problem to wait until first thing in the morning. Having said that, you mentioned "best solution". For that, in theory, you'd want to wait until the precise orbits have been published. That takes two weeks. I believe DPOS uses the precise orbit once available, but I'm not certain. As a practical matter, I've not seen enough difference between the rapid orbit and the precise orbit to worry about it.
While we're talking DPOS, they're working on something as we speak that is going to blow the doors wide open on DPOS. I'm really stoked about what's just around the bend.
Adam, you asked about how long to wait for best results. I'm not sure just how fast you can get results. I've made it part of my workflow to collect data today with my autonomous base, and process the DPOS file first thing in the morning before I draw up my work in CAD. So far it's been very successful. I don't know if I could pull that off earlier if my field day was short, for example. Maybe Alexey can offer some insight, but it just hasn't been much of a problem to wait until first thing in the morning. Having said that, you mentioned "best solution". For that, in theory, you'd want to wait until the precise orbits have been published. That takes two weeks. I believe DPOS uses the precise orbit once available, but I'm not certain. As a practical matter, I've not seen enough difference between the rapid orbit and the precise orbit to worry about it.
While we're talking DPOS, they're working on something as we speak that is going to blow the doors wide open on DPOS. I'm really stoked about what's just around the bend.
Yes.....he said it and meant it....Stoked!!!
Robert P Stenerson
Active Member
Okay, I've submitted my Base and Stand alone points to DPOS and OPUS, they agree pretty good with each other, except in height, delta 0.027m. I noticed OPUS is now using GEOID12B, and DPOS is using GEOOID12A. I then moved my stand alone manually, kind of faked me out a little there, but once I deleted the actual coordinates, then it was moved to the target coordinates. Also my stand alone solution/new position checks in pretty well with a shot I'd taken using my VRS setup.
I liked the DPOS for two reasons, it's using GEOD12A which matches my Carlson SurvCE work and two I don't have to do any extra calculation to generate a NGS ARP height to input, (i.e. with the proper Antenna selection DPOS takes my slant height at face value, one less thing to screw up.) Again, guys thanks for the help.
I liked the DPOS for two reasons, it's using GEOD12A which matches my Carlson SurvCE work and two I don't have to do any extra calculation to generate a NGS ARP height to input, (i.e. with the proper Antenna selection DPOS takes my slant height at face value, one less thing to screw up.) Again, guys thanks for the help.
As I understand it, 12B is mostly (if not entirely) a revision for Alaska.
I'm not always sure what to make of OPUS with heights from Triumph-2 data. I never expected to say this, but I have more confidence in DPOS for Javad receivers than I do for OPUS.
I'm not always sure what to make of OPUS with heights from Triumph-2 data. I never expected to say this, but I have more confidence in DPOS for Javad receivers than I do for OPUS.
We had a big headache with Triumph-2 NGS calibration because of we have to calibtated it twice. First, as Triumph-2 (ARP at the bottom adapter). Second, as Triumph-2A/JAVTRIUMPH_2A/ (ARP at the bottom of receiver). Actualy Triumph-2 was removed from NGS list. I want to notice two pitfalls whith Triumph-2A. 1. Surveyor can mesure antenna height to adapter instead of receiver. 2. OPUS uses old calibration (Triumph-2) for Triumph-2A data. Take in account that adapter height equals 0.025 m (you got 0.027 m OPUS vs DPOS difference).
As a rule CORS station complete upload data every day till 3 AM UTC. In the meantime some stations are doing this faster than others. Check submitting to DPOS every hour after field job and mark the time when a list of stations (DPOS report) will be completed. It depends on your location.
Robert P Stenerson
Active Member
Thanks Alexey, but I don't have a Triumph-2 (yet), I was using a Triumph-1 and Triumph-LS, and I saw the height differences between OPUS and DPOS on both units. No worries though, I'm such a newbie I'm still just pouring over Shawn's localizing video to get a grip on the basics. It's scary what I don't know, and that I've been doing it for years
Nate The Surveyor
Well-Known Member
Does the test group have it yet?
Any idea how soon?
And, will it be supporting local coord systems?
It's not currently implemented in the test version. There are some aesthetics (filters and screens) that exist, but they are not quite functional yet.
It's a top priority right now, so I'm sure it will be very soon.
As I understand it, the vector will be processed by DPOS between the base and rover, then the vector will be returned to the LS (just like a position is returned now). Of course it will work with a local coordinate system, so long as the local system is tied to planet Earth, either by localization or if you're using a custom projection. Remember, every survey point is already stored internally as a WGS84 coordinate, so when the vector comes back related in WGS84, the resulting coordinates are WGS84 which are then related to your local system by the geodetically pure coordinate systems of J-Field.
This is one of many examples that show that geodesy being at the core of the LS has benefits to the user, even if he doesn't necessarily care about the intricacies of geodesy himself.
It's a top priority right now, so I'm sure it will be very soon.
As I understand it, the vector will be processed by DPOS between the base and rover, then the vector will be returned to the LS (just like a position is returned now). Of course it will work with a local coordinate system, so long as the local system is tied to planet Earth, either by localization or if you're using a custom projection. Remember, every survey point is already stored internally as a WGS84 coordinate, so when the vector comes back related in WGS84, the resulting coordinates are WGS84 which are then related to your local system by the geodetically pure coordinate systems of J-Field.
This is one of many examples that show that geodesy being at the core of the LS has benefits to the user, even if he doesn't necessarily care about the intricacies of geodesy himself.
Nate The Surveyor
Well-Known Member
We need a double like button!
Nate The Surveyor
Well-Known Member
Somebody is giving the Javad team some GOOD advice.
Whoever you are, wherever you are, thanks!
Whoever you are, wherever you are, thanks!
Jim Frame
Well-Known Member
Are you saying that OPUS currently uses the Triumph-2 offsets for data submitted as using a Triumph-2A antenna?
No, I supposed. I am trying to find a reason of 0.027 m difference. I hope somebody will check T-2 data OPUS post-processing on known point.