Changes between Version 59 and Version 60 of Procedures/RCDPhotoProcessing

Timestamp:

Jul 1, 2011, 11:05:04 AM (13 years ago)

Author:

knpa

Comment:

--

Procedures/RCDPhotoProcessing

@@ -9 +9 @@
 === Post-processing ===
 
-Create temporary thumbnail images of the processed tiff files using photo2thumb.py. Open the first image with eog and use either spacebar to scroll though the images or view/slideshow. Remove any images that that are over/under exposed. 
-
-Check there is a *_camera.sol file in the IPAS/proc directory. If there is not, then you will need to create one. See details here: http://arsf-dan.nerc.ac.uk/trac/wiki/Procedures/ProcessingChainInstructions/NavigationProcessing
-
-The next stages of the processing incorporate:
- * 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
- * generating thumbnail images of the tiffs.
-
-For "perfect" projects this can all be done using one script which will generate a delivery directory and populate it with correctly processed data. Unfortunately a lot of projects are not perfect and may require a more hands on approach. A step by step procedure can be found [wiki:RCDPhotoProcessing/RCDPostProcessing here] for post-processing data for problem projects.
-
-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. Create temporary thumbnail images of the processed tiff files using photo2thumb.py. Open the first image with eog and use either spacebar to scroll though the images or view/slideshow. Remove any images that that are over/under exposed. 
+ 1. Check there is a *_camera.sol file in the IPAS/proc directory. If there is not, then you will need to create one. See details here: http://arsf-dan.nerc.ac.uk/trac/wiki/Procedures/ProcessingChainInstructions/NavigationProcessing
  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 **NOTE- this program currently falls over unless the eagle directory is clear of unrecognised files**
@@ -39 +25 @@
   * 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. Try running the script. Pipe the output to a text file in case you wish to review it afterwards.
+
+== Script ==
+
+The script incorporates:
+ * tagging the images with positional and navigational data as well as project information
+ * renaming the images to conform to ARSF standards
+ * generating thumbnail images of the tiffs
+
+
+A step by step procedure can be found [wiki:RCDPhotoProcessing/RCDPostProcessing here] for post-processing data for problem projects.
 
 Example command: