Changes between Version 32 and Version 33 of Procedures/EagleHawkProcessing

Jul 4, 2011, 11:14:09 AM (13 years ago)



  • Procedures/EagleHawkProcessing

    v32 v33  
    77Before starting, make sure the [wiki:Procedures/ProcessingChainInstructions/NavigationProcessing navigation is processed] and all raw data is present and correct.
    9 == DEM ==
     9=== DEM ===
    1111To return sensible results for all but very flat areas, you will need a dem. One should have already been completed in the unpacking stage. If not, it will need to be created. For the UK, use [wiki:Processing/NextMapDEMs NextMap]. Otherwise use [wiki:Processing/SRTMDEMs ASTER]. If you can't use ASTER for some reason, then you can also create one from our own LiDAR using
    13 == Creating config file ==
     13=== Creating config file ===
    1515This file will be used to automatically generate the commands necessary to process your hyperspectral lines.
    5050You shouldn't have to worry about this unless something goes wrong. However something often does! Detailed explanation of each step is explained [wiki:Procedures/AplSuiteDetails here]
     52=== Problems ===
     56If you get something in the log file like:
     58** End of POSATT file with NO Specim sync found
     59** no sync within 5.00 secs of raw file header time: 49915.66
     61then there is no sync info in the nav file for that line and and the range of possible sct values will increase (up to a few seconds). You will need to include 'has_sync = false' in the config file line entry and input a wider range of scts, e.g.
     67has_sync = false
     68sctend = -1
     69sctincrement = -0.1
     70sctstart = 1
     75A 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).
     79If you get something in the log file like:
     81** flight line may have a turn in it **
     82** heading spread over approximately: 120 degs **
     84** run terminated due to turn **
     86then there is a bend in the line that is too sharp. You need to add a -bend flag to the azcorr arguments for the line entry in the config file, e.g.
     92azgcorr_args_extra = -bend
     97Once processed, it is best to exclude the lines which are causing the problems by including a -l flag in azspec followed by the line numbers delineating the part of the line you want to keep, then reprocessing. E.g. if the bend is at the start of the line:
     103azgcorr_args_extra = -bend
     104azspec_args_extra = -l 50 2000
     106will exclude the first 50 lines. Make sure the second value takes into account dark frames: the number of lines given in the header file will include dark frames and if you want to process to the end of the line you should therefore specify the line number before the figure given in 'autodarkstartline' (also in the header file).
    52108=== Making a delivery ===