Changes between Version 10 and Version 11 of Procedures/EagleHawkProcessing


Ignore:
Timestamp:
Oct 8, 2010 9:57:03 AM (9 years ago)
Author:
iopa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EagleHawkProcessing

    v10 v11  
    9191...
    9292
     93A 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)
     94and 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)
     95then 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
     96is missing (open .gpb file from applanix/extract) but still possible when the time is missing (.gpb again, but will have to track position).
     97
    9398-----------------------------------------------
    9499