Magnet Tools GPS+ Static Processing
I am trying to study Magnet Tools GPS+ module.
Whenever you load a rinex file the software creates a GPS observation vector (from point ---> to point). Magnet sometimes reverses the "from pt" with the "to pt". I first load the base gps rinex file and load the rover files after. But still Magnet reverses the order of a vector and because of this, one of the rover becomes a base and vice-versa.
I have been trying to find how you can reverse the "to point" and "from point".
Can you point me how to do this?
Not a Magnet user, but in other software the from->to vector direction is dependent on which point is set to "Control" or "Reference."
Hmm. In Leica world you could also right click the vector and reverse the direction... Hopefully a Magnet user will chime in soon.
When importing RINEX data you are processing STATIC data, not RTK. Therefore there is no base/rover relationship. The software is processing vectors between each observation. Why are you concerned with direction of the vector? I think the direction of the vector may be relative to the time the receiver was started.
Static baselines are just delta 3D vectors - there is no "from" or "to", only a difference in XYZ between two points. The assumption is that an adjustment will be performed using one or more constraints that are input by the user, hence the term "relative positioning". Direction is irrelevant, at least it should be, in most software packages.
Static files store an autonomous location that is used by the post-processing software to build the a priori - that is, approximate - coordinates of the network. Import order usually doesn't matter, as long as the user eventually inputs control coordinates for one of the positions and constrains to them during adjustment. Some software builds off the first point imported for the a priori coordinates, others have a heirarchy, and some require user input. It all depends on your software suite.
There *might* be a problem if a static file happens to have an autonomous coordinate in the header that is drastically off, as in thousands of feet or more. This is rare, but it can happen. Sometimes it will take a few more iterations to solve for the network positions - other times a solution is not possible. The closer those a priori coordinates are to the true values, the easier it is to find a solution.
Some users speak in terms of "bases" (receivers logging data throughout the entire campaign) and "rovers" (receivers that are being moved around and logging at shorter intervals while the bases continue to log), and insist that the base files must be imported first. This is not necessarily the case.