Changes between Version 47 and Version 48 of Procedures/RCDPhotoProcessing

Timestamp:

Feb 18, 2011, 4:47:52 PM (14 years ago)

Author:

emca

Comment:

--

Procedures/RCDPhotoProcessing

@@ -12 +12 @@
 
 The next stages of the processing incorporate:
- * 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.
+ * updating the photograph event file with the post-processed positional data and the exterior camera angles.
  * tagging the images with positional and navigational data as well as project information
  * renaming the images to conform to ARSF standards
@@ -21 +21 @@
 To 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.
 
- 1. Process the IPAS data and create a SOL file - Make sure to use the RCD camera lever arms not the LiDAR lever arms (and name the sol file appropriately so as not to get confused).
  1. Create a KML file and view it in Google Earth.
   * Check the rcd/logs file for an ***!ImageEvents1.csv file. 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. Run `generateKMLforPI.py -d <main_project_dir> -e main_project_dir/rcd/logs/***!ImageEvents1.csv -o kml_file.kml` - this create a kml file using the !ImageEvents1.csv file
@@ -31 +30 @@
   * If there is no log file then this approach can not be used. See below section on tagging without log files.
   * 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'''
+ 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. 
+  1. Load in the *.sol file and from rcd/logs the *!ImageEvents1.csv and *!PhotoId1.csv file
+  1. Camera Orientation Direction: -90
+  1. Event Offset: 0.006 
+  1. Lever Arm values: x 0.112 y 0.061 z -0.60
+  1. Output file as *!ImageEvents1-processed.csv, file format ASCII Output
  1. Try running the script. Pipe the output to a text file in case you wish to review it afterwards.
 
@@ -36 +41 @@
 
 {{{
-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/solfile.sol -n "PI Name" | tee camera_delivery.log
+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-processed.csv -s ~airborne/workspace/project_dir/leica/ipas/proc/solfile.sol -n "PI Name" | tee camera_delivery.log
 }}}