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 - bwatkins

Pages: [1]
1
General / Import Cameras is no longer an option in Batch Process?
« on: March 29, 2022, 03:26:11 AM »
I recently updated my copies of Metashape Pro after returning to office and I've discovered that Import Cameras is no longer an option when running a Batch Process. Why is this? What can I do to keep a consistent scale and camera position in a large batch of chunks to process?

2
It feels like using a batch process on multiple chunks I should be able to export models with their texture files into unique, individual folders instead of dumping everything into one big folder. I.e., exporting to a path that looks like ".../{chunklabel}/{chunklabel}.obj", where that "/{chunklabel}" folder would contain the .obj, .mtl, and .tiff files, for example.  Trying that only gets me an error that that directory doesn't exist/can't find the path.

This seems like a pretty simple feature add (disclaimer: not a programmer).

Previously posted here without response:
https://www.agisoft.com/forum/index.php?topic=10648.0

3
I've been scanning large batches and batch processing multiple chunks at once for a few years now using just menu commands - I don't have a background in coding, so I've never gotten into the Python end of things.

When exporting, however, it feels like I should be able to export models with their texture files into unique, individual folders instead of dumping everything into one big folder. I.e., exporting to a path that looks like ".../{chunklabel}/{chunklabel}.obj", where that "/{chunklabel}" folder would contain the .obj, .mtl, and .tiff files, for example.  Trying that only gets me an error that that directory doesn't exist/can't find the path.

Is PhotoScan capable of creating new folders using an export command? Or should I post this to feature requests?

Pages: [1]