Changes between Version 61 and Version 62 of Procedures/RCDPhotoProcessing
- Timestamp:
- Jul 1, 2011, 11:14:13 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/RCDPhotoProcessing
v61 v62 26 26 * 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''' 27 27 28 == Script==28 === Script === 29 29 30 30 The script incorporates: 31 * tagging the images with positional and navigational data as well as project information 32 * renaming the images to conform to ARSF standards 33 * generating thumbnail images of the tiffs 31 * Tagging the images with positional and navigational data as well as project information 32 * Renaming the images to conform to ARSF standards 33 * Generating thumbnail images of the tiffs 34 * Creating the final kml 35 * Making final version of the eventfile, including removing any lines referring to photos you have removed 34 36 35 37 Run it as follows: … … 42 44 * SOL file GPS times do not overlap with photograph log file times. Either fix the SOL (if possible) else use the logfile to tag the images (and mention in the Read_Me) 43 45 44 == Creating the Read me file==46 === Creating the Read me file === 45 47 46 48 An ascii Read me file is no longer automatically generated from the above script. Instead, a config file for the latex PDF script is created. This will need some editing. Also remember to add information on any photos which could not be tagged fully, or any images which look like they have anomalies or over/under exposure. For more information on how to generate the PDF file see [wiki:Procedures/DeliveryCreation/photos here] 47 49 48 == Subsequent processing ideas==50 === Subsequent processing ideas === 49 51 50 52 There are several other steps that could be undertaken in the future: