Changes between Version 56 and Version 57 of Procedures/EagleHawkProcessing


Ignore:
Timestamp:
Oct 11, 2011 11:43:52 AM (8 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EagleHawkProcessing

    v56 v57  
    1313To 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.
    1414
    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.
     15Note: 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.
    1616
    1717=== Creating config file ===
     
    8080If the project is in the UK, you will need to check the positional accuracy of the images against the OS line overlay. These should have been ordered before hand and are located in ~arsf/vectors.
    8181
    82 
    8382=== Making a delivery ===
    8483
     
    8786Use --final if happy with what it says it will do. Use -m <config> to generate screenshots and mosaics
    8887
    89 Note: this script automatically moves over the contents of the DEM directory. You will need to revert this if this is a nextmap DEM as these shouldn't be delivered.
     88Note: this script automatically moves over the contents of the DEM directory. You will need to revert this if this is a nextmap DEM as these shouldn't be delivered, and include an ASTER DEM instead.
    9089
    9190==== Making the Readme ====