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