Changes between Version 60 and Version 61 of Procedures/EagleHawkProcessing
- Timestamp:
- Jul 3, 2012, 12:18:54 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/EagleHawkProcessing
v60 v61 3 3 This guide describes how to process hyperspectral data using the apl suite. This should be used for 2011 data onwards. If you are processing earlier data, see [wiki:Procedures/AZEagleHawkProcessing here] for instructions for processing with the az suite. 4 4 5 The apl suite consists of the following programs: '''aplcal''', '''aplnav''', '''aplcorr''', '''apltran''', '''aplmap''' , '''aplsite'''.5 The apl suite consists of the following programs: '''aplcal''', '''aplnav''', '''aplcorr''', '''apltran''', '''aplmap'''. 6 6 7 7 Before starting, make sure the [wiki:Procedures/ProcessingChainInstructions/NavigationProcessing navigation is processed] and all raw data is present and correct. … … 11 11 === DEM === 12 12 13 To 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 make_lidardem_or_intensity.sh.13 To return sensible results for all but very flat areas, you will need a dem. You can create a DEM by running asterdem.sh or nextmapdem.sh and output this in the hyperspectral DEM directory; otherwise use the liDAR aster DEM from the liDAR processing. 14 14 15 15 Note: If you create a nextmap DEM then this can not be included with the delivery as there are restrictions on it's distribution. Generate a separate ASTER DEM to be included with the delivery.