Anyone familiar with Survey Pro and VRS?

I have one comment, but not answers. If you want data from an actual GPS base point, its not really VRS is it?

If I want to adjust various occupations of the same point, then the vectors need to be from a common point (i.e. physical CORS). Otherwise, they will be from different virtual base locations (for occupations done at different times). The adjusted (fixed) coordinates of the physical CORS are used to compute the virtual base locations, so they are connected mathematically. The reason for using a virtual nearby base is to reduce the baseline length (and also to account for varying ionospheric conditions around the point).

I could adjust the positions rather than the vectors, but that is not how my workflow is setup.

I would think to check the network mount points when you go to start survey uncheck the connect to box and it will give you all available mount points. many networks have the option to use single baseline vs the network solution.

mvanhank222, post: 421883, member: 8673 wrote: I would think to check the network mount points when you go to start survey uncheck the connect to box and it will give you all available mount points. many networks have the option to use single baseline vs the network solution.

Not Trimble VRSnow in the UK.

The VRS - virtual reference station - is just that. The base is "imagined" for you and will be different from day to day. So although Access will store vectors they are fairly meaningless I think. (although you will get error estimates if you import them to star*net).

Leica's RTN uses a different system - the master auxiliary concept - that they (leica and it's dealers) believe is vastly superior. The base is the same from day to day and is a CORS. Corrections from other CORS are blended into the correction from the single base. (That's how I understand it anyway).

The results will be the same as if you had a base station on the CORS.

Single base mountpoints are also offered from Leica Smartnet here in NZ. (and in the UK I believe).

I wouldn't get hung up on the correction broadcast format (eg CMR+), it's only a different format for the same message.

mvanhank222, post: 421883, member: 8673 wrote: I would think to check the network mount points when you go to start survey uncheck the connect to box and it will give you all available mount points. many networks have the option to use single baseline vs the network solution.

What I am describing is NOT single base. It is VRS but the vector is stored as if it came from the nearest physical CORS.

Can you use the RCTM 3.net correction? I believe this might do what you are looking for at least the times I have tried it in the mount point list it says it's VRS but uses the same base point day to day.

I will have them try that, but I am skeptical. I just spoke to my dealer, they also sell Spectra products. He says this issue has come up before, and he believes the Survey Pro software will only do it with a virtual base position.

John Hamilton, post: 421988, member: 640 wrote: I will have them try that, but I am skeptical. I just spoke to my dealer, they also sell Spectra products. He says this issue has come up before, and he believes the Survey Pro software will only do it with a virtual base position.

Here is a screen plot of the Sensor Map (individual stations) for our local system and screen plot of a recent job, as you can see the vectors are to an actual station not a virtual one. I was told that the DC uses a virtual station but saves vectors to an actual station, so "you don't have to explain to a judge what a "virtual reference station is""

This is a pretty common question. When you are using a Trimble Network with a Trimble Receiver the software recognizes what they call a "seed station". This "seed station" is what the baseline vectors are are pulled from. When you use another brand Receiver with that network it doesn't work no matter what mountpoint you are using.

I have my own opinion about this, I'll keep it to myself 🙂

Here is what I get if I import the .job file into TBC (it also imported the .raw file).

David: are you using Trimble (see post in between this one and yours about only working with Trimble) or Spectra receivers? If Spectra, would you mind sharing your configuration.

Here is what I get when I import the .job file (which brings in the .raw file as well) to TBC:

David C. Newell RPLS LS CFM, post: 421992, member: 6347 wrote: Here is a screen plot of the Sensor Map (individual stations) for our local system and screen plot of a recent job, as you can see the vectors are to an actual station not a virtual one. I was told that the DC uses a virtual station but saves vectors to an actual station, so "you don't have to explain to a judge what a "virtual reference station is""

David: are you using a Trimble receiver (see post right after yours)? If you are using a Spectra, would you mind sharing the configuration?

We have one S.P. epoch 50 (trimble) we use on the NC RTN and use CMR+ for our mount point in Survey Pro (Version 6.0.something). When using CMR+ it will bring in the nearest CORS base and when i import the .survey file into TBC I can get the CORS-to-rover vectors. When using this same setup on RTCM3 survey pro stores a "VRS" point and does not get the CORS, I believe...it's been a while since I've used that mount point. I'd see what happens on their end if they mount to CMR+, that is if it's available and they're using a trimble/spectra rover as Bucky suggested.

JWCole: Great info, they are using a VRS_RTCM3 mountpoint. I will see if they can change it to CMR+

I believe that is the opposite of the way it works in access. I think if I specify CMR+ I get a local base, if I specify VRS(CMS), then I get the nearest CORS. I can't check it right now because our login is being used this afternoon out near Philly.

JWCole, post: 422027, member: 10389 wrote: We have one S.P. epoch 50 (trimble) we use on the NC RTN and use CMR+ for our mount point in Survey Pro (Version 6.0.something). When using CMR+ it will bring in the nearest CORS base and when i import the .survey file into TBC I can get the CORS-to-rover vectors. When using this same setup on RTCM3 survey pro stores a "VRS" point and does not get the CORS, I believe...it's been a while since I've used that mount point. I'd see what happens on their end if they mount to CMR+, that is if it's available and they're using a trimble/spectra rover as Bucky suggested.

Wes is correct here. The Spectra Epoch 50 works because it is a Trimble Receiver (R8), if you were to use any other receiver made by Spectra it wouldn't. I don't believe it would use GLONASS either on the CMR mountpoint (may be wrong about that though).

John Hamilton, post: 422023, member: 640 wrote: David: are you using a Trimble receiver (see post right after yours)? If you are using a Spectra, would you mind sharing the configuration?

John,
We're using Spectra Survey Pro (6.0.0.40) on a Ranger, and processing using Spectra Precision Survey Office (64-bit) 3.70, we transfer the *.survey file from ranger to desktop and process.
We're using Promark 700 set up as Network rover, sever type NTRIP, let me know what other info you'd like.
Attached is a different project.

JWCole, post: 422027, member: 10389 wrote: We have one S.P. epoch 50 (trimble) we use on the NC RTN and use CMR+ for our mount point in Survey Pro (Version 6.0.something). When using CMR+ it will bring in the nearest CORS base and when i import the .survey file into TBC I can get the CORS-to-rover vectors. When using this same setup on RTCM3 survey pro stores a "VRS" point and does not get the CORS, I believe...it's been a while since I've used that mount point. I'd see what happens on their end if they mount to CMR+, that is if it's available and they're using a trimble/spectra rover as Bucky suggested.

I stand corrected. Every day's a school day...