AI Assistant
Discrepancy in requ...
 
Notifications
Clear all

Discrepancy in requirements for OPUS shares

4 Posts
2 Users
0 Reactions
853 Views
bill93
(@bill93)
Posts: 9977
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I accidentally left "share" selected on one that I didn't intend to share and had poor quality.?ÿ I got a notice saying the minimum requirements for OPUS-S sharing were:

70% of observations used

70% of ambiguities fixed

0.04 m longitude range

Other parameters were ok so it didn't give me thresholds for them.

But a web page at NGS https://www.ngs.noaa.gov/OPUS/about.jsp?ÿ has some tighter and some looser criteria.?ÿ Not consistent.

While there are no absolute rules, most accurate OPUS solutions contain the following:

  • orbit used = precise or rapid
  • > 90% observations used
  • > 50% ambiguities fixed
  • Static: overall RMS < 3 cm, peak to peak errors < 5 cm.

?ÿ


 
Posted : August 31, 2018 2:29 pm
rankin_file
(@rankin_file)
Posts: 4078
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

from farther down the same page-

?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ


Share Your OPUS Solution

proper field procedure
ƒ??
OPUS side menu logo image

it's simple, upload to OPUS using Yes, Share& the following:

Careful field procedures

A Permanent Mark of Public Interest

A High-Quality OPUS Solution

  • ƒ? 70% observations used & ambiguities fixed
  • ƒ?? 3 cm RMS
  • ƒ?? 4 cm peak-to-peak error ranges, lat. & lon.
  • ƒ?? 8 cm peak-to-peak error range, el. hgt.

 
Posted : August 31, 2018 11:08 pm
bill93
(@bill93)
Posts: 9977
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Ok, I didn't read far enough to see that it does list the same numbers for sharing as my error report.

So if everything is good but 50% ambiguities fixed, it is "most accurate" but can't be shared, and if everything is good but 70% observations use it isn't "most accurate" but can still be shared.?ÿ Also 5 cm pk-pk is "most accurate" but can't be shared.

Inconsistent.


 
Posted : September 1, 2018 8:22 am
rankin_file
(@rankin_file)
Posts: 4078
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I'm not too worried about it. You appear to be interjecting the word "The" in front of the phrase "most accurate"- thus changing the meaning. I feel a correct understanding of the phase "most accurate solutions"?ÿwould be to construe it to be infer that a generally accurate and acceptable solution has the following qualities.... and you can probably use it -?ÿbut you can use your solution anyway you see fit... do whatever your career can stand.

NGS then delineates the criteria for solutions which they will allow to be shared on their website.?ÿ The numbers are different.?ÿ that's ok it's their sandbox.


 
Posted : September 1, 2018 9:32 am