Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - ps10

Pages: [1]
1
Hi,
I would like to use the same 3D model as the orthorectification surface for images from different sensors (processed in different chunks). Is there a way to point 'surface_data' for buildOrthomosaic() to a model in a different chunk? importModel requires a path to the model file as well, so my workaround is to export and then import the model. Is there an efficient way to do this?
Appreciate any suggestions.

Thanks :)

2
Hi,

I am trying to install numpy and a few other external packages with Metashape Pro 1.8.3. This is a script we have been using for a while and the installation step for Windows worked until now (previous version tested was likely Metashape 1.7.5)

"C:\Program Files\Agisoft\Metashape Pro\python\python.exe" -m pip install numpy

Error:
IimportError: cannot import name 'InvalidSchemeCombination' from 'pip._internal.exceptions' (C:\Program Files\Agisoft\Metashape Pro\python\lib\site-packages\pip\_internal\exceptions.py)

Please see attachment for Traceback.

Appreciate any help with resolving this.

Thanks


3
Hi,

I am trying to convert my Metashape script workflow to use Tasks (and eventually enable network processing). I am seeing errors in the dense cloud generation step. The following code works fine (as does 'Build dense cloud' on GUI):

Code: [Select]
chunk.buildDepthMaps(downscale = 4) # medium quality. and default: mild filtering.
chunk.buildDenseCloud()

In a new project, I ran the same workflow using the equivalent functions in Metashape.Tasks and got this error: "Exception: null photo". I found that aligning and optimising cameras ran fine, depth maps are created, but BuildDenseCloud failed (same error with subdivide_task enabled). I have checked that the chunk was created fine, images were aligned,  etc. I have tested this in a new console, on a new project file, etc. Any pointers on what I could check would be much appreciated.

Code: [Select]
task = Metashape.Tasks.BuildDepthMaps()
task.downscale = 4
#task.subdivide_task = True
tasks.append(task)

task = Metashape.Tasks.BuildDenseCloud()
#task.subdivide_task = True
tasks.append(task)
:
:
for task in tasks:
    if task.target == Metashape.Tasks.DocumentTarget:
        task.apply(doc)
    else:
        task.apply(chunk)


4
General / RedEdge-M: changing the master band for camera alignment
« on: August 26, 2021, 05:31:31 AM »
Hi all,

My question is about changing the master band for calibration and alignment of multispectral imagery. I have seen other Forum posts on this topic but this issue has not been covered.

I am working with Micasense RedEdge-M data, and selected multi-camera system to add photos. I want to use the NIR band as the master band (and primary channel) and update the positions for these cameras based on post-processing. I have set NIR as master under Camera Calibration. I imported updated positions (Import Reference) for the NIR cameras (IMG*_4). But only the lowest wavelength (IMG*_1 corresponding to Blue band) cameras are displayed under Workspace and Reference.  To confirm that the NIR positions were updated and that the NIR sensor is being used as the master, I ‘Exported Cameras’. In the xml in the <sensors> section, the master_id points to NIR sensor. However, under the <cameras>, master_id is the id of the IMG*_1 cameras (default Blue band). 

I tried updating layer indices (under Camera Calibration – Bands) so NIR is 0 but that does not seem to influence this. Appreciate any suggestions on updating the master band used for calibration and camera alignment.
Also, is there any documentation on interpreting the tags in the xml generated on Export Cameras? Please let me know if additional information will help.

Thanks.

Pages: [1]