Changes between Version 37 and Version 38 of Procedures/RCDPhotoProcessing


Ignore:
Timestamp:
Jul 7, 2010 5:29:53 PM (9 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/RCDPhotoProcessing

    v37 v38  
    33The RCD produces raw files that need to be processed in order to create TIFF files.  The processing basically uses a gain and offset scaling and (probably) corrects for lens distortion.  See the [wiki:Sensors/RCD_CH39 RCD page] for more details, including filename convention.
    44
    5 The procedure for processing raw images to tif images can be found [wiki:Procedures/RCDPhotoProcessing/RawtoTif here].
     5=== Raw to Tiff ===
    66
     7The first stage in processing the photographic data is to convert the raw file format into a 16-bit tiff format. The procedure for processing raw images to tif images can be found [wiki:Procedures/RCDPhotoProcessing/RawtoTif here].
    78
    8 = Tagging the Images, creating thumbnails and delivery folder =
     9=== Post-processing ===
    910
    10 == Fully scripted processing approach ==
     11When the tiffs have been created the next stages of the processing can be started. This incorporates:
     12 * updating the photograph event file to subtract the frame grabbing time delay (0.006s) and update the real-time positional/navigation data to post-processed values from the IPAS SOL file.
     13 * tagging the images with positional and navigational data as well as project information
     14 * renaming the images to conform to ARSF standards
     15 * generating thumbnail images of the tiffs.
    1116
    12 If you are lucky you should be able to do the whole processing chain through running one script. To improve the chances of this working follow the stages below to set up the data and remove as many anomalies as possible.
     17For "perfect" projects this can all be done using one script which will generate a delivery directory and populate it with correctly processed data. Unfortunately a lot of projects are not perfect and may require a more hands on approach. A step by step procedure can be found [wiki:RCDPhotoProcessing/RCDPostProcessing here] for post-processing data for problem projects.
    1318
    14  1. Process the IPAS data and create a SOL file
     19To improve the chances of this single script approach working, follow the stages below to set up the data and remove as many anomalies as possible.
     20
     211. Process the IPAS data and create a SOL file
    1522 1. Create a KML file and view it in Google Earth.
    1623  * Run kmlise_project.py <main_project_dir> > kml_file.kml - this create a kml file using the !ImageEvents1.csv file
     
    3037}}}
    3138
    32 If the script fails then you will have to fix the problem and follow the individual stages below. Possible causes of failure, excluding the ones previously mentioned above, could be:
     39If the script fails then you will have to fix the problem and try again, or follow the individual stages listed [wiki:RCDPhotoProcessing/RCDPostProcessing here]. Possible causes of failure, excluding the ones previously mentioned above, could be:
    3340 * SOL file GPS times do not overlap with photograph log file times. Either fix the SOL (if possible) else use the logfile to tag the images (and mention in the Read_Me)
     41
     42
     43= Tagging the Images, creating thumbnails and delivery folder =
    3444 
    3545== Individual processing stages - if above script does not work ==