https://geodesy.noaa.gov/web/science_edu/webinar_series/Webinars.shtml
Above is the page to register for an upcoming NGS Webinar. The title is ??Using RTN Data in OPUS Projects 5 for GPSonBM.?
It will deal with the collection of short GNSS observations using RTN for submission as .GVX files to the NGS Beta OPUS Projects 5 page in support of the GPSonBM effort.
Webinar is scheduled for 12 January 2023. It will run from 1400 to 1530 Eastern Time.
?ÿ
This webinar is tomorrow! Thursday 12 January 2023 at 1400 Eastern Time or 0900 in Hawaii. That??s 2000 in Paris.?ÿ
@geeoddmike do they provide us Professional Development Hours documentation for attendance?
If you attend the whole thing they send a pdf of an attendance certificate. They don't check whether it is acceptable in any particular jurisdiction-that's your problem.
Attended the webinar. I was a little surprised to learn of 5 cm positional vertical tolerance on repeated observations. That's certainly a new twist on the part of NGS for acceptable precision requirements. I suppose that's because the CORS policy as I understand it is that the published height of the CORS station has to be out 5 cm before it's corrected.?ÿ?ÿ
@norm yes but they need the vectors to go along with them to analyze
I was unable to attend today. The wife said it was good. Whats the good bad and ugly. She said they will allow submittal of rtk possibly for gps on benchmarks. Something about 3 hour gaps etc.?ÿ
5cm. Is that vertical or just xyz etc. ?ÿwe use to get fussed at if one of our stations moved beyond 2cm that we had in the cors ?ÿ I use to check weekly all our stations and we monitored daily ?ÿ Let me say this buildings move during the day ?ÿwe had some stations that moved more than 2cm per day during certain times of the year. We didn??t send those to cors ?ÿwe moved them as quickly as we could . ?ÿ
?ÿ
yes, I was a little surprised at the precision tolerances as well. But I found the different methods intriguing. I??m kinda curious how much difference in precision between the 2hr and 4hr static observations.?ÿ
As Bill93 notes the NGS sends a certificate of attendance to attendees. Attendees will also receive an email announcing the posting of the presentation. Only attendees will receive an email with the Q&As not addressed during the webinar as an attachment.
I did NOT attend today's event as I do not use RTN, nor am I convinced that heights derived short occupation times provide good heights. ?ÿ
As a non-attendee I will not receive the Q&A document. I will appreciate someone posting it to this site.
?ÿ
?ÿ
Also, am I to assume that by setting the RTN receiver to vector than this allows the post processing of RTN observations to be more precise??ÿ
Also, am I to assume that by setting the RTN receiver to vector than this allows the post processing of RTN observations to be more precise?
?ÿ
RTN (and RTK) vectors can't be post-processed, or improved upon. But they can be used in an adjustment.
If vectors are not stored, only a point (with some sort of metadata depending on field software) is stored. No observations to adjust.
?ÿ
I missed the tail end of the presentation, so this might have been addressed....but I would think that vectors would also need to be tied to a physical reference station (PRS) rather than a VRS.
the webinar was 'thought provoking'.?ÿ The end result was to tie RTN data to benchmarks.?ÿ Some discussion about RTN (including VRS) 3 ea 5 minute sessions (spaced > 3 hrs apart) collecting vectors and writing a?ÿ GVX file.?ÿ Only problem is most of us do not have capability of providing GVX data.?ÿ I can collect all 4 (GPS, Glonass, Galileo, and Beidou) but appears only two proprietary software programs can output GVX at this time - others are working on it.?ÿ
Does not look like many of us will be able to help NGS (and our fellow surveyors) at this time.
What is needed is for NGS (or a contractor) to write a public domain program that compiles the vector data we collect together with the metadata for deliverables to NGS.
?ÿ
What is needed is for NGS (or a contractor) to write a public domain program that compiles the vector data we collect together with the metadata for deliverables to NGS.
I'm not sure how anyone other than the equipment manufacturers would be able to parse their proprietary files to spit out GVX format.
But as long as users can push out the actual vector deltas and statistics, I could see working up a fillable form through something like MS Access where those values and the rest of the relevant info could be input by the user.
Then an XSL transform could be applied on the XML Export command to get all the data into the GVX schema.
I'm not sure how anyone other than the equipment manufacturers would be able to parse their proprietary files to spit out GVX format.
Either way NGS said they were not going to create a program to spit out GVX. That's on the equipment manufacturers.
The xml file is not that complicated to a good programmer.?ÿ See the following GVX sample format from the Opus 5.1 Beta site:?ÿ
https://geodesy.noaa.gov/data/formats/GVX/sample_gvx.xml
?ÿ
Webinar has been posted, Q&A document is attached.
?ÿ
Regarding the GVX format as discussed above:
?ÿ
Q: As a follow-up to the "are there 3rd-party" GVX convertors for my receiver &
software that doesn't export GVX: What would it take, if someone is a good
programmer, to create such a converter?
A: We are unaware of any 3rd party converters. You would need to be able to
read/decipher the proprietary vector file from your GNSS receivers and convert that
output to the GVX format. With that said, it may be that not all the required elements of
the GVX format exist in the proprietary vector file, which would then require that the
manufacturer of the receiver be involved in developing the converter. We recommend
you talk to your equipment suppliers about your desire for GVX exports from the
software you purchase from them. Another venue may be the customer support team
for the software you use. If those contacts you make have questions about GVX,
please connect them to us via your Regional Geodetic Advisor or other NGS contacts.