Changes between Version 12 and Version 13 of Procedures/PhotoScan


Ignore:
Timestamp:
Jan 28, 2019, 9:25:16 AM (5 years ago)
Author:
wja
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Procedures/PhotoScan

    v12 v13  
    11== Generating Photogrammetry Products ==
    2 This page aims to guide a user through photogrammetry processing using Agisoft PhotoScan.[[BR]]
    3 Refer to ~arsf/doc/photoscan_processing/ for a step by step guide using a PhotoScan GUI.[[BR]]
     2This page aims to guide a user through photogrammetry processing using Agisoft Metashape (formally PhotoScan).[[BR]]
     3Refer to ~arsf/doc/photoscan_processing/ for a step by step guide using a Metashape GUI.[[BR]]
    44[[BR]]
    55
    6 == Processing using PhotoScan ==
     6== Processing using Metashape ==
    77
    88'''Overview:'''
    … …  
    2020|| ||ps_workflow.cfg||
    2121
    22 The arf_photoscan library currently contains two scripts for automating PhotoScan processing of NERC-ARF data:
    23 '''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). This step is not automated. '''ps_ortho_processing_after_input_gcp.py''' is run after the and placement of Ground Control Points.[[BR]]
     22The arf_photoscan library currently contains two scripts for automating Metashape processing of NERC-ARF data:
     23'''ps_ortho_processing_before_input_gcp.py''' will set up a Metashape 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 Metashape project. If no GCPs are available, the script will complete the whole Metashape processing workflow without (obviously accuracy of data is significantly reduced). This step is not automated. '''ps_ortho_processing_after_input_gcp.py''' is run after the and placement of Ground Control Points.[[BR]]
    2424
    2525'''Ground Control Points'''[[BR]]
    26 Coordinates of GCPs in CSV format can be added to PhotoScan. 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]]
     26Coordinates of GCPs in CSV format can be added to Metashape. 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]]
    2727Note: 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]]
    2828
    … …  
    3535}}}
    3636
    37 * 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.
     37* 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 Metashape workflow without GCPs.
    3838* 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:
    3939
    … …  
    4444'''Config Information'''[[BR]]
    4545The same config template is used.[[BR]]
    46 The project directory (defined in config file) is the location of the PhotoScan project file (*.psx) and other data produced whilst processing.[[BR]]
     46The project directory (defined in config file) is the location of the Metashape project file (*.psx) and other data produced whilst processing.[[BR]]
    4747The 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. If the output directory does not exist, then it will be created.[[BR]]
    4848[[BR]]
    … …  
    5656  * Check the values in the eventfile. There may have been a problem when extracted them from the navigation data.
    5757 * Processing
    58   * Check that the GCP placement in PhotoScan has been undertaken in as many photographs that GCPs are present in as possible. Also look at the residual error of the project's spatial fit. Unusually high error values for a particular GCP marker would suggest that it has been placed in the wrong location.
     58  * Check that the GCP placement in Metashape has been undertaken in as many photographs that GCPs are present in as possible. Also look at the residual error of the project's spatial fit. Unusually high error values for a particular GCP marker would suggest that it has been placed in the wrong location.
    5959
    6060== Creating Delivery ==
    … …  
    6565|| || || Read_Me-20171018.pdf ||  Instructions for use and description of dataset, plus any problems encountered ||
    6666|| || || Read_Me-20180222_orthomosaic.pdf || Instructions for use and description of photogrammetry products ||
    67 || dem || || || Digital Surface Model(s) produced from PhotoScan. ||
     67|| dem || || || Digital Surface Model(s) produced from Metashape. ||
    6868|| || || PHASEONE-IXU-ES17_126-2017170_dsm-utm30n.dem || Digital Surface Model in ENVI format ||
    6969|| || || PHASEONE-IXU-ES17_126-2017170_dsm-utm30n.hdr || Header for accompanying Digital Surface Model in ENVI format ||
    7070|| doc || || || Useful documents ||
    7171|| || || camera_data_quality_report2012.pdf || Camera data quality report ||
    72 || || || ES17_126-2017170_ground_gps_points_composite.csv || Ground control point (supplied by PI) used during PhotoScan Processing ||
    73 || || || PHASEONE-IXU-ES17_126-2017170_photoscan_processing_report_20180222.pdf || Agisoft PhotoScan generated processing report. ||
     72|| || || ES17_126-2017170_ground_gps_points_composite.csv || Ground control point (supplied by PI) used during Metashape Processing ||
     73|| || || PHASEONE-IXU-ES17_126-2017170_photoscan_processing_report_20180222.pdf || Agisoft Metashape generated processing report. ||
    7474|| || || RCD105_SN21_Calibration_Certificate.pdf || Camera Calibration Certificate ||
    7575|| eventfile || || PHASEONE-IXU-ES17_126-2017170-ImageEvents.csv || CSV file containing pos/att info per photograph event (may be missing if camera crashed) ||
    7676|| orthomosaic || || PHASEONE-IXU-ES17_126-2017170_mosaic-utm30n.tif || Orthorectified mosaic of photographs in GTiff format ||
    7777|| photographs || || photographs/PHASEONE-IXU-ES17_126-2017170-00001.tif || Tagged tif files of each photograph in area of interest ||
    78 || point_cloud || || || Exports of the 'Dense Cloud' generated in PhotoScan ||
     78|| point_cloud || || || Exports of the 'Dense Cloud' generated in Metashape ||
    7979|| || ascii || PHASEONE-IXU-ES17_126-2017170_point_cloud.txt || Point cloud in ASCII format ||
    8080|| || las1.2 || PHASEONE-IXU-ES17_126-2017170_point_cloud.laz || Point cloud in LAS 1.2 format ||