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

Pages: [1]
General / Export Region (specify four dimensions)
« on: September 01, 2016, 09:11:50 PM »
I'm looking to specific regions of products from PhotoScan. I'm building models of forested areas and am only interested in a subset of the model. Rather than build my products and edit extents in GIS software, I was wondering whether it is currently possible to functionally export an extent of the model as specified by four coordinate pairs rather than two?

Feature Requests / Console Reflect GUI actions
« on: March 24, 2016, 07:35:07 AM »
Sorry if too general.

I find the API difficult to navigate. There's been several occasions where I've tried to replicate a step from the GUI in a Python script, and have had a lot of difficulty finding the correction code snippet to use.

It would be awesome, if the console updated with Python commands as tools are executed. This would help users looking to make the transition from manual, to scripted processing.


Hi Folks,

Working on some scripting and have run into a road-block. I've got a script set-up to re-cursively test accuracy settings for the initial alignment.

I've got a list containing the Accuracy Settings (PhotoScan.HighAccuracy, PhotoScan.MediumAccuracy)

When I try to pass one of these values to the matchPhotos parameter I get the error

2016-02-24 14:30:08 TypeError: argument 1 must be PhotoScan.Accuracy, not str

I understand the error, the program doesn't want a string (which is what I'm serving it from the list) via my iterator. Is there a way to get around this, by somehow converting my string into something PhotoScan will accept?

I've made a separate version of the script where the accuracy settings are hard coded that works fine as a back-up. I just want to clean this up, so I can make quicker changes as required.

Thank you,

General / Different Results
« on: February 17, 2016, 03:13:57 PM »
Hi All,

I've noticed that when aligning photos, with the same Alignment settings, I am getting different numbers of cameras to align.

In my latest process, I aligned the same chunk of 135 photos five times. Each step was processed with:

Lowest Accuracy
Reference Pair Preselection
Keypoint Limit (0)
Tiepoint Limit (0)

However when I look at my results (keeping in mind these are the same 130 photos) the results are very different. (Photo attached)

In the best case, 105/130 cameras were aligned. In the worst, 95/130. What's the explanation? Is there a random element to the matching process or feature extraction? I'd like to be able to explain where these differences are coming from.

Thank you,

Python and Java API / Running Scripts in PhotoScan Pro [RESOLVED]
« on: October 22, 2015, 06:15:58 PM »
I had a hyphen in the script name rather than an underscore. Once script name was corrected, the custom menu item appeared to the left of the Help button in the PhotoScan bar as described by SC. Thanks for your help

Hi everyone, Ian here. I'm trying to run a script from the PhotoScan wiki to automate the process of chunking a project.

The script in question is here:

I copied and pasted the script from the wiki page, on to my local drive (as per instructions I searched out on this forum). Specifically C:/User:/Me/AppData/Local/Agisoft/PhotoScan Pro/scripts

From reading the scripts comments and posts on this forum, I'm led to believe that this script creates a custom menu item. I'm sure this is probably a super obvious question, but what exactly is a custom menu item and where can I find/access it?

I've scoured the forum and PhotoScan documentation, but can't seem to find a solution. If it's posted somewhere, could someone please link to the topic? If not, could someone with experience running the wiki scripts with AgiSoft Pro could outline a general workflow for running scripts.

Thanks a million,

General / Working with Chunks
« on: October 14, 2015, 03:41:50 PM »
Hi there folks,

A quick question regarding working with Chunks in PhotoScan. I've got a large set of photos ~550. The photos are taken with a UAV, and the total scene include 8 control points with average GPS locations.

My end goal is to produce both an Orthophoto mosaic and Digital Terrain model of the study area. I can run all the required processing with a Medium setting, however my computer runs out of memory when using high quality photos.  Small details are really important for the final product, so I'd really like to create a product at the highest settings.

After doing some reading on this forum, and other online PhotoScan resources, it looks like the best way to circumvent this memory issue is by processing my project into separate chunks. I've given it a shot, but unfortunately the final product was poor.

My questions are:

1. Is using chunks the best/only way to work-around the memory shortage warning?
2. If so, is there an optimal time to split the dataset into chunks? E.x before photo alignment, after dense cloud.

3. When is the best point in the workflow to merge chunks?

Thank you in advance,

Pages: [1]