Changes between Version 33 and Version 34 of Procedures/EagleHawkProcessing


Ignore:
Timestamp:
Jul 4, 2011 11:14:25 AM (8 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EagleHawkProcessing

    v33 v34  
    5252=== Problems ===
    5353
    54 Sync
     54'''Sync'''
    5555
    5656If you get something in the log file like:
     
    7575A less likely reason for the above output is that the raw header file in question contains invalid GPS times (either start time or end time) and therefore also results in not lying within the times of the .nav file. If both GPS Starting Position and GPS Start Time are missing (accordingly for End Position/End Time) then the best guess is to replace the invalid time/position with the raw header file from the other sensor (eagle/hawk), making sure that it is the correct corresponding flightline. If only one of the two are missing, time or position, then the navigation files should be used to find the missing data, this is easier done when the position is missing (open .gpb file from applanix/extract) but still possible when the time is missing (.gpb again, but will have to track position).
    7676
    77 Turns
     77'''Turns'''
    7878
    7979If you get something in the log file like: