Changes between Version 51 and Version 52 of Procedures/RCDPhotoProcessing

Timestamp:

Feb 24, 2011, 2:31:07 PM (14 years ago)

Author:

emca

Comment:

--

Procedures/RCDPhotoProcessing

@@ -12 +12 @@
 
 The next stages of the processing incorporate:
- * updating the photograph event file with the post-processed positional data and the exterior camera angles.
+ * creating a kml file, viewing in goggle earth and removing any images that are not relevant to the study area
+ * 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 +22 @@
 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. Check the rcd/logs file for an ***!ImageEvents1.csv and ***!PhotoId1.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.
- 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. 
-  * Load in the *.sol file, the *!ImageEvents1.csv and *!PhotoId1.csv file
-  * Camera Orientation Direction: -90
-  * Event Offset: 0.006 
-  * Lever Arm values: x 0.112 y 0.061 z -0.60
-  * Output file as *!ImageEvents1-processed.csv, file format ASCII Output
- 1. Create a KML file and view it in Google Earth.
+ 
+ 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.
   * 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
   * Open the kml file in google earth
@@ -34 +29 @@
   * Delete these tif files (not the raws) since they are not required.
   * Delete the kml file created above as it is no longer needed. An updated one will be created by the delivery script. 
+ 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. 
+  * Load in the *.sol file and from rcd/logs the *!ImageEvents1.csv and *!PhotoId1.csv file
+  * Camera Orientation Direction: -90
+  * Event Offset: 0.006 
+  * Lever Arm values: x 0.112 y 0.061 z -0.60
+  * Output file as *!ImageEvents1-processed.csv, file format ASCII Output
  1. Check the event log file for erroneous entries
   * If there is no log file then this approach can not be used. See below section on tagging without log files.
@@ -42 +43 @@
 
 {{{
-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
+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 -n "PI Name" | tee camera_delivery.log
 }}}