Changes between Version 1 and Version 2 of Procedures/PhotoScan


Ignore:
Timestamp:
Oct 17, 2018 4:10:19 PM (13 months ago)
Author:
wja
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/PhotoScan

    v1 v2  
    11'''PhotoScan Processing'''[[BR]]
    22This page will guide a user through conducting photogrammetry processes using Agisoft PhotoScan.[[BR]]
    3 Until the arf_photoscan library is ready to automate a large amount of the processing chain, please refer to ~arsf/doc/photoscan_processing/ for a step by step guide using a PhotoScan GUI.
     3Until the arf_photoscan library is ready to automate a large amount of the processing chain, please refer to ~arsf/doc/photoscan_processing/ for a step by step guide using a PhotoScan GUI.[[BR]]
     4[[BR]]
     5'''Overview:'''
     6The following files comprise the arf_photoscan library:[[BR]]
     7├── arf_photoscan[[BR]]
     8│   ├── __init__.py[[BR]]
     9│   ├── ps_export.py[[BR]]
     10│   ├── ps_processing.py[[BR]]
     11│   ├── ps_tools.py[[BR]]
     12│   ├── ps_tools.pyc[[BR]]
     13├── ps_ortho_processing_after_input_gcp.py[[BR]]
     14├── ps_ortho_processing_before_input_gcp.py[[BR]]
     15├── README.md[[BR]]
     16└── templates[[BR]]
     17    └── ps_workflow.cfg
     18
     19The arf_photoscan library currently contains two scripts for automating PhotoScan processing of NERC-ARF data:
     20'''ps_ortho_processing_before_input_gcp.py''' will set up a PhotoScan project and align photographs. If Ground Control Points (GCPs) are available, then the script will stop and prompt you to manually locate them in the PhotoScan project. If no GCPs are available, the script will complete the whole PhotoScan processing workflow without (obviously accuracy of data is significantly reduced).[[BR]]
     21[[BR]]
     22The second script This step unfortunate is not automated. '''ps_ortho_processing_after_input_gcp.py''' is run after the and placement of Ground Control Points. Coordinates in CSV format can be added to PhotoScan (or input manually). The user will then need to 'drag and drop' the marker locations to their locations visible in the photographs input. This needs to be done for '''all''' photographs each GCP is visible in.[[BR]]
     23Note: once a couple of GCPs have been located in multiple respective photographs; the 'reproject' button (looks like a recycling symbol) will automatically place the remaining photo. These will still need to be accurately places, but will save a lot of time nevertheless.[[BR]]
     24'''Running a script:'''
     25* Update config file (template is located in /templates/ps_workflow.cfg).
     26* As airborne, in the rsg-photoscan virtual machine, run:
     27
     28{{{
     29/opt/photoscan/photoscan.sh -r ps_ortho_processing_before_input_gcp.py -c [CONFIG]
     30}}}
     31
     32* If no GCPs have been input in config file,  (gcp_csv_path = None) '''or if gcp_csv_path does not exist''', then ps_ortho_processing_before_input_gcp.py will run through the whole PhotoScan workflow without GCPs.
     33* If a path to GCP CSV has been input into the config file, these GCP coordinates will need to be manually positioned to their correct locations on the aligned photographs. Once this has been achieved, the second script can be run:
     34
     35{{{
     36/opt/photoscan/photoscan.sh -r ps_ortho_processing_before_after_gcp.py -c [CONFIG]
     37}}}
     38The same config template is used.[[BR]]
     39The project directory (defined in config file) is the location of the PhotoScan project file (*.psx) and other data produced whilst processing.[[BR]]
     40The output directory (also defined in config) is where the Point Cloud, DEM and/or Orthomosaic is exported, if the associated parameters are True in config file.