Changes between Version 62 and Version 63 of Procedures/RCDPhotoProcessing


Ignore:
Timestamp:
Jul 1, 2011 11:56:20 AM (8 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/RCDPhotoProcessing

    v62 v63  
    99=== Post-processing ===
    1010
    11  1. Create temporary thumbnail images of the processed tiff files using photo2thumb.py. Open the first image with eog and use either spacebar to scroll though the images or view/slideshow. Remove any images that that are over/under exposed.
    12  1. Check there is a *_camera.sol file in the IPAS/proc directory. If there is not, then you will need to create one. See details here: http://arsf-dan.nerc.ac.uk/trac/wiki/Procedures/ProcessingChainInstructions/NavigationProcessing
    13  1. Create a KML file and view it in Google Earth. Check the rcd/logs file for an ***!ImageEvents1.csv. There may be some empty files with this name so be sure to choose the correct one. If there are more then one then you need to specify which one to use.
    14   * Run `kmlise_project.py -d <main_project_dir> -e ***ImageEvents1.csv > kml_file.kml` - this creates a kml file using the !ImageEvents1-processed.csv file **NOTE- this program currently falls over unless the eagle directory is clear of unrecognised files**
     11 1. Get a camera .sol file
     12  * Check there is a *_camera.sol file in the IPAS/proc directory. If there is not, then you will need to create one. See details here: http://arsf-dan.nerc.ac.uk/trac/wiki/Procedures/ProcessingChainInstructions/NavigationProcessing
     13 1. Remove "bad" images
     14  * Create temporary thumbnail images of the processed tiff files using photo2thumb.py.
     15  * Open the first image with eog and use either spacebar to scroll though the images or view/slideshow. Remove the corresponding tiff images for any that are over/under exposed.
     16 1. Remove images that don't correspond to flightlines
     17  * Create a temporary kml file:  `kmlise_project.py -d <main_project_dir> -e ***ImageEvents1.csv > kml_file.kml` Make sure the correct eventfile is being pointed to **NOTE- this program currently falls over unless the eagle directory is clear of unrecognised files**
    1518  * Open the kml file in google earth
    16   * Note which blocks of photographs do not overlap with any Eagle/Hawk data. Usually consists of a group of photographs at the start of the survey where they set up the exposure rates etc for the camera. Often the log sheet notes which images too.
    17   * Delete these tif files (not the raws) since they are not required.
    18   * Delete the kml file created above as it is no longer needed. An updated one will be created by the delivery script.
    19  1. Open IPAS CO (on the windows machine). This is used to create a new image event file with post-processed positional data and omega,phi,kappa values.
     19  * Note which blocks of photographs do not overlap with any Eagle/Hawk data. Usually consists of a group of photographs at the start of the survey where they set up the exposure rates etc for the camera. Often the log sheet notes which images too. Delete these tif files (not the raws) since they are not required.
     20  * Delete the kml file created above as it is no longer needed (an updated one will be created by the delivery script)
     21 1. create a new image event file with post-processed positional data and omega,phi,kappa values
     22  * Open IPAS CO (on the windows machine)
    2023  * Load in the *_camera.sol file and from rcd/logs the *!ImageEvents1.csv and *!PhotoId1.csv file
    2124  * Camera Orientation Direction: -90
     
    2326  * Output file as *!ImageEvents1-processed.csv, file format ASCII Output
    2427 1. Check the event log file for erroneous entries
    25   * If there is no log file then this approach can not be used. See below section on tagging without log files.
     28  * If there is no log file then you will need to look See [wiki:RCDPhotoProcessing/RCDPostProcessing here] for information on tagging without log files.
    2629  * Anything with a -1 in GPS time will not be able to be tagged fully, but only with project information data. If possible, you might be able to use the !SensorStats log file to estimate the GPS time of the erroneous events. Use the time differences in the log file to estimate the GPS time. Note down any image names you do this to so that it can be put in the Read Me. '''This is probably no longer worth doing - seems to be too imprecise'''
    2730
     
    3437 * Creating the final kml
    3538 * Making final version of the eventfile, including removing any lines referring to photos you have removed
     39 * Creating and populating delivery directory
    3640
    37 Run it as follows:
     41Run as follows:
    3842
    3943{{{