Changes between Version 21 and Version 22 of Procedures/RCDPhotoProcessing


Ignore:
Timestamp:
May 24, 2010, 10:55:04 AM (15 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Procedures/RCDPhotoProcessing

    v21 v22  
    3434 1. Check the event log file for erroneous entries
    3535  * If there is no log file then this approach can not be used. See below section on tagging without log files.
    36   * Anything with a -1 in GPS time will cause an error in the tagging script. 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.
    37   * If the !SensorStat log cannot be used to estimate the time then there is nothing that can be done for this image - can only be tagged with minimal information via a separate script (see below section on tagging without log files).
     36  * 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'''
    3837 1. Try running the script. Pipe the output to a text file in case you wish to review it afterwards.
    3938