Changes between Version 3 and Version 4 of Procedures/DeliveryCreation/DigitalPhotography


Ignore:
Timestamp:
Oct 12, 2017 9:28:02 AM (20 months ago)
Author:
dac
Comment:

Made readme config command more 'copy and pastable'

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/DigitalPhotography

    v3 v4  
    1717== Creating the Read me ==
    1818
    19  * Run `generate_readme_config.py` with the -d option (giving the delivery directory) and "-r camera" as airborne.
     19 * Generate the readme config file using: `generate_readme_config.py -r camera -d delivery/*camera*` as airborne.
    2020 * 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.
    2121 * 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