Changes between Initial Version and Version 1 of Procedures/DeliveryCreation/DigitalPhotography


Ignore:
Timestamp:
Aug 3, 2017, 2:49:50 PM (7 years ago)
Author:
dac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/DigitalPhotography

    v1 v1  
     1= Digital Camera Delivery =
     2
     3Now that the processing has been completed the delivery can be made. This, as with the hyperspectral and lidar, uses the [wiki:Procedures/DeliveryCreation/pythonlibrary arsf_delivery_library] together with the convenience script make_arsf_delivery.py. An example usage:
     4
     5{{{make_arsf_delivery.py --projectlocation /users/rsg/arsf/arsf_data/2013/flight_data/uk/MYPROJECT --deliverytype camera --steps STRUCTURE}}}
     6
     7check that the output looks correct, and if so repeat with {{{--final}}}. This creates an empty structure. Then run:
     8
     9{{{make_arsf_delivery.py --projectlocation /users/rsg/arsf/arsf_data/2013/flight_data/uk/MYPROJECT --deliverytype camera --notsteps STRUCTURE}}}
     10
     11This will do a dry-run on the camera delivery and output information clearly labelled for each step. If this script outputs no error messages, repeat with {{{--final}}}.
     12
     13== Creating the Read me ==
     14
     15 * Run `generate_readme_config.py` with the -d option (giving the delivery directory) and "-r camera" as airborne.
     16 * Edit the config (should be located in processing directory). 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. To add new line characters enter '\\'. 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. Line_numbering should contain a space separated list of names/numbers identifying flight lines.
     17 * Create the LaTeX TeX file. To create the TeX file run the script create_latex_camera_readme.py from the processing directory with the -f option, giving the location and name of the config file generated above. This is editable in any text editor and can be manually edited to correct mistakes or insert new text
     18 * Convert the TeX file into a PDF file. This is done using the command `pdflatex <TeXFile>` and should create a file named Read_me-<TODAYSDATE>.pdf. If you get an error about missing .sty files, then yum install whatever is missing. For example, if you get complaints about supertabular.sty being missing, do yum install texlive-supertabular.
     19 * 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).