Version 7 (modified by knpa, 8 years ago) (diff)

--

Individual RCD image processing stages

Tagging images which have camera log files

Tag_tiffs.py is a python script that uses the exiftool command line tool too add tags to a tiff. It draws this data from an image event file (this should be the processed event file from IPAS CO). In addition to the data in the image event file the user can use several arguments to supplement the information. For information on the script use the -h option

tag_tiffs.py -V -d dd/mm/yyyy -p <projcode> -l <sitename> ( -s sortie ) <eventfile> <photographs_directory>

where:

dd/mm/yyyy is the date the image data was collected

sortie is the flight letter (e.g a, b, etc)

to check the changes use exiftool.

exiftool /users/rsg/arsf/arsf_data/2010/flight_data/iceland/IPY09_11-2009_219_Helheim/leica/rcd/proc_images/07120958100001G4.tif 

A second script is used to then rename the files with useful names containing the project code, year and day. this script also takes the processed image events file and the folder containing the images as arguments, renames the files and creates a new image events file with the file names updated.

for more information on the script use -h option

rename_photos_update_events_file.py -v -d dd/mm/yyyy -c <projcode> ( -s sortie ) <eventfile> <photographs_directory>

Tagging images which do not have camera log files

Only minimal tagging can be performed: original filename, project code, flight day and site name. This is because without the timestamp of the image event we cannot match up any navigation information. Ask mark1 for a clunky script to do this (will get updated to a better script soon).

Renaming the files can take place once they have been tagged with the original filename information. Ask mark1 for a clunky script to do this (will get updated to a better script soon).

Creating an Event File

Create a KML file for the delivery, using the eventfile created using rename_photos_update_events_file.py above

generateKMLforPI.py -d <main_project_dir> -e <eventfile> -o <kml_output_filename>

Creating Thumbnails

We need to create thumbnail images for the delivery and for getting an overview of the images for the checking procedure. To do this use the photo2thumb.sh script.

Example:

photo2thumb.sh -d proc_images -o proc_thumbnails

Will create JPG thumbnails of all the TIF images in the proc_images directory and save them into a directory called thumbnails. For further usage run photo2thumb.sh -h

Photographic data delivery ¶

Once the data has been processed, it needs to be put into a delivery directory. This is the final file structure in which it will be sent to the customer. Delivery directory structure ¶

COPYRIGHT.txt

Read_Me-DATE.txt

doc/ - contains data quality report and calibration certificate

eventfile/ - contains Image events file created from photo_renamer script

PROJCODE-YEARJDAY-SITENAME.kml - Google Earth file that shows photograph locations

photographs/ - contains processed and tagged tifs (named from 00001 onwards)

thumbnails/ - contains thumbnails of the tifs from photographs Creating a delivery directory ¶

The quick way If you are lucky then you should just be able to run a script to do the stages of processing and it will auto create a delivery directory. The stages of the script involve creating the delivery structure, populating it with files, tagging and renaming the tif images, creating thumbnail images, creating a KML file and generating the Read_Me file.

The slow way Once the instructions on photo processing have been followed you should have a directory of processed, tagged tiffs which have been renamed as per the convention. Also, there should be a directory of thumbnail images of the processed tiffs. These should be moved over into the photographs and thumbnails directories respectively. The event file created from the renaming script should be copied into the eventfile directory. Use this event file to create a kml file in the delivery directory using kmlise_project.py -d <main_project_directory> -e <eventfile> > PROJ_CODE-YEARJDAY-SITENAME.kml

Run sorte_fixer.sh in the photograph directory to correct the misspelt 'sorte' tag. To create a readme for the delivery: ¶ Latex PDF readme ¶

This is still largely untested and probably buggy

To create a PDF read me file for the delivery takes 3 stages.

  • Generate a config file containing the project information that will be used in the next stage. To do this, use the script generate_readme_config.py with the -d option (giving the delivery directory) and "-r camera". See generate_readme_config.py -h.
  • Check and edit the config file:

o Any remarks about the photograph quality / missing items etc should be entered in the "data_quality_remarks" section as a sentence. To add new line characters enter '
' o tagtype should be "full" if photos have been tagged with pos/att information or "min" if only tagged with project details. If both types are present in the delivery then use full and in the "data_quality_remarks" section add a sentence explaining which photos have been unable to be tagged with pos/att and why. o line_numbering should contain a space separated list of names/numbers identifying flight lines.

  • Create the LaTeX TeX file. This is editable in any text editor and can be manually edited to correct mistakes or insert new text. To create the TeX file use the script create_latex_camera_readme.py with the -f option, giving the location of the config file generated above.
  • Convert the TeX file into a PDF file. This is done using the command latex <TeXFile> and should create a file named Read_me-TODAYSDATE.pdf.

It is advisable to keep the TeX file somewhere safe until after the delivery has been checked in case some changes to the Read_me need to be made (the TeX file should not be part of the delivery).