Changes between Version 3 and Version 4 of Processing/GrafNavProcessing


Ignore:
Timestamp:
Feb 13, 2009 11:01:32 AM (10 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/GrafNavProcessing

    v3 v4  
    1616 1. Analyse the X, Y and Z accuracy of the exported ASCII file (.lat).  Acceptable SD results are 3.5cm in XY, 5cm in Z.  Excellent SD results are 2cm XY, 3cm Z. These assume basestations within 25km.  These figures are from the user manual.
    1717
     18=== PPP Processing ===
     19
     20If the PPP processing method doesn't work and gives the error "Cannot fin epoch ... blah blah blah", then try this:
     21 1. Go to "Help" and "About GrafNav"
     22 1. Click download manufacturer files
     23 1. Re-try running the PPP
     24
    1825=== Exporting GrafNav Result to POSPAC ===
    1926It is possible to do the GNSS processing in GrafNav and then export the result into POSPAC. This saves doing the GNSS processing two times (one for LiDAR IMU and one for Applanix IMU). The version of GrafNav is newer than the POSGNSS version and should be used instead of POSGNSS.
    2027
    21 When the solution in GrafNav is ready to be exported, save the project and go into POSGNSS. Open the GrafNav project into POSGNSS, ignore warnings about being an older version. Then click the "combine GNSS" or "combine PPP" button. This will load in the previous solution. This can then be exported to POSProc as per usual.
     28When the solution in GrafNav is ready to be exported, save the project and go into POSGNSS. Open the GrafNav project into POSGNSS, ignore warnings about being an older version. Then click the "combine GNSS" or "combine PPP" button. This will load in the previous solution. This can then be exported to POSProc as per usual.  If the "combine" buttons are not highlighted, then you can goto the menu and select combine solutions, select the files and load in the forward and reverse ones.