Changes between Version 48 and Version 49 of Procedures/RCDPhotoProcessing

Timestamp:

Feb 23, 2011, 4:11:43 PM (14 years ago)

Author:

emca

Comment:

--

Procedures/RCDPhotoProcessing

@@ -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. 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.
-  * 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
+  * Run `generateKMLforPI.py -d <main_project_dir> -e ***!ImageEvents1-processed.csv -o kml_file.kml` - this creates a kml file using the !ImageEvents1.csv file
   * Open the kml file in google earth
   * Note which blocks of photographs do not overlap with any Eagle/Hawk data. Usually consists of a group of photographs at the start of the survey where they set up the exposure rates etc for the camera. Often the log sheet notes which images too.
@@ -30 +37 @@
   * 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.