Changes between Version 16 and Version 17 of Procedures/RCDPhotoProcessing

Timestamp:

Feb 8, 2010, 10:57:44 AM (14 years ago)

Author:

mark1

Comment:

--

Procedures/RCDPhotoProcessing

@@ -36 +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.
   * 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).
+ 1. Try running the script. Pipe the output to a text file in case you wish to review it afterwards.
 
+Example command:
+
+{{{
+make_delivery_folder.sh -c -d ~airborne/workspace/project_dir -y 2010 -j 297 -p EX01_01 -a "Example Site" -e ~airborne/workspace/project_dir/leica/rcd/logs/ImageEvent1.csv -s ~airborne/workspace/project_dir/leica/ipas/proc/sbet_from_sol.sbet -n "PI Name" | tee camera_delivery.log
+}}}
+
+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: 
+ * SBET file GPS times do not overlap with photograph log file times. Either fix the SBET (if possible) else use the logfile to tag the images (and mention in the Read_Me)
+ 
 
 = Individual processing stages =