Aren't these vectors already solved in the RTK process? Don't they form the basis of the gfile export?
Yes, generally.
This will allow users to process vectors if they lose communication between base and rover (range, interference, terrain, etc.) It won't always be the best solution, particularly if you have many points to collect without communication to the base. For those cases, it will likely be more efficient to move the base or set up a repeater. It should be a great utility for getting that one or two shots that are just beyond radio range, without requiring a relocation of the base or repeater.
It may also be useful for improving RTK vectors using a more superior post processing algorithm. But that remains to be seen until it is implemented.
Primarily Hybrid RTK will provide a highly automated approach to what Trimble refers to as "infill". Javad's approach will not require users purchase additional software, nor even downloading to a PC. Like DPOS in J-Field, it will be available entirely within J-Field. Unlike DPOS, Hybrid RTK will process the vector from base to rover even if the CORS data for determining the base position is unavailable, meaning this processing could be accomplished in the field if necessary.
The user would return to the base, stop and download the base raw data file and submit both to DPOS/Hybrid RTK. The returned vector would be applied to the standalone point in the J-Field database.
