Great Video. Quick question, it is not giving me the option to merge or not to merge after I send it to process with RTx, I click import it processes it and I'm left with on point. Do you know why this is happening? Great video!
Thank you Robert for the video. What about if we have 2 known control (which we processed with CORS stations) points and we want to process the coordinates of the new static measured point as per the coordinates of those 2 points instead of downloading the CORS coordinates?
When I do the meter conversion by hand it comes out 4'+/- off on easting and 14'.5'+/- on the northing. I have to use the NGS unit conversion to get the proper ussft. My friend learned this the hard way. Have you found that to be the case? I am in California Zone 5.
Great Video. Quick question. We typically use VRS a lot. But we recently done a job in a state where we do not access to the VRS network. So we ran a Static session. I know how to do the OPUS solution on the control point as you showed in this video. My question is, How do I apply this OPUS correction to the rest of the GPS points collected in my Job file?
Do a merge point in TBC. Hold down ctl on keyboard select both points. Follow commands and be sure to select recompute or the red ball when you complete the merge.
Hey Robert, great video. Do you know why I'm getting different values when I upload my data to RTX-PP as apposed to OPUS? The points are feet off, elevation included. However, I get similar values to OPUS in elevation when I post process in TBC using CORS stations manually, but the horizontal is off. I'm using an old version of TBC. Do you think this has any effect? I noticed that CORS stations in California are on a different EPOCH as apposed to OPUS. I'm guessing the Epochs are the reason for the differences? Thanks.
@@aidensanchez6207 RTX-PP data sheet has NAD83 and ITRF listed on your PDF they send you. Also if you are in the US be sure to use NAD83 not NAD83-2011.
Like the entrance. What's in the cup Robert? 🤣🤣
I’m not telling 😎
@Surveying With Robert HHAHAHA I love it. Appreciate what you do man. My only issue is that I work with the metric system here in Canada!!
Thanks Robert, great video.
Well done
Great Video. Quick question, it is not giving me the option to merge or not to merge after I send it to process with RTx, I click import it processes it and I'm left with on point. Do you know why this is happening? Great video!
Always great content Robert, thank you. Any plans to update the process now they have a whole NEW process? ;)
Thanks so much for your video.
Could you please make a video explain about different ITRF coordinate systems and how to use them in real life?
Great video. Thanks!
Hey Robert, where is the video that goes over processing job files to the new adjusted control point?
@@keegs87 there somewhere, I will look. Leaving Dimension at airport.
Keep learning from Robert online school and we appreciate that’s thanks 😊 INDOT
Thank you Robert for the video.
What about if we have 2 known control (which we processed with CORS stations) points and we want to process the coordinates of the new static measured point as per the coordinates of those 2 points instead of downloading the CORS coordinates?
When I do the meter conversion by hand it comes out 4'+/- off on easting and 14'.5'+/- on the northing. I have to use the NGS unit conversion to get the proper ussft.
My friend learned this the hard way. Have you found that to be the case?
I am in California Zone 5.
Great Video. Quick question. We typically use VRS a lot. But we recently done a job in a state where we do not access to the VRS network. So we ran a Static session. I know how to do the OPUS solution on the control point as you showed in this video. My question is, How do I apply this OPUS correction to the rest of the GPS points collected in my Job file?
Do a merge point in TBC. Hold down ctl on keyboard select both points. Follow commands and be sure to select recompute or the red ball when you complete the merge.
Hi Robert
Can I get details about sps 986
Hi Dear How to use files cors station (opus)for adjustment points static
We talked on Facebook but I am thinking about putting something together for you.
@@SurveyingWithRobert THANK YOU SO MUCH
@@SurveyingWithRobert My friend, I am waiting for your help on how to upload the rhinx file to Opus, I am having a problem with that
@@Chief.Surveyor.AliQassim ان كنت لازلت تعاني من هذه المشكلة اتصل على مكتب الازل
@@rehabhatem2169
شكرآ لكم لقد تم تجاوز هذه المشكله
Can you make a video 36 hours single point observation data processing by using IGS
So, single point 36 hours? IGS08? What logging rate? 15 seconds?
Hey Robert, great video. Do you know why I'm getting different values when I upload my data to RTX-PP as apposed to OPUS? The points are feet off, elevation included. However, I get similar values to OPUS in elevation when I post process in TBC using CORS stations manually, but the horizontal is off. I'm using an old version of TBC. Do you think this has any effect? I noticed that CORS stations in California are on a different EPOCH as apposed to OPUS. I'm guessing the Epochs are the reason for the differences? Thanks.
Make sure in RTX your not using the ITRF.
@@SurveyingWithRobert thanks Robert I will try that. How do I switch it off? Thanks!
@@aidensanchez6207 RTX-PP data sheet has NAD83 and ITRF listed on your PDF they send you. Also if you are in the US be sure to use NAD83 not NAD83-2011.
Is there a way to process the static point and view the data in the field with trimble tsc7, or does it have to be uploaded to tbc to process?
Cortlain Waugh you need to wait long enough for the NGS to catch up and download files. You could send from the TSC7.