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

Pages: [1]
The createDifferenceMask tool has been very helpful for masking background in typical three-band images.  However, it would be nice if the tuple used for the background parameter could be different lengths other than three to support one- or four-band images.  Thank you. 

Feature Requests / Have "Convert" button ignore fiducial markers
« on: May 15, 2020, 12:11:38 AM »
If I am working with a project with scanned film and I wish to convert to a different coordinate system using the convert button on the reference pane, it always messes up my project because it appears that this forces a conversion of the fiducial coordinates as well. 

Thank you

I have many thousands of images that I wanted to organize into different calibration groups based on the date they were collected, which is reflected in the label.  I wrote the script below to accomplish this.  While the script works for this purpose, it also forces the resolution of all images to 0x0 (screenshot attached).  If I try to align the images, it goes through one batch where 0 points are detected for each image, and I get the error "Error: Can't select tile size."  If I click on the image in the workspace, it still shows the appropriate dimensions,17588 x 16039. 

Is this a bug, or am I doing something wrong in the script? 
Thank you

Code: [Select]

chunk =

# Make list of dates to create calibration groups
calGroups = []
for camera in chunk.cameras:
    yr = camera.label[:2]
    if yr not in calGroups:

#Create the calibration groups
for i in calGroups:
    sensor = chunk.addSensor()
    sensor.label = i
    sensor.type = Metashape.Sensor.Type.Frame
    sensor.focal_length = 208.047
    sensor.pixel_height = 0.0125
    sensor.pixel_width = 0.0125

#Assign cameras to calibration groups. 
for camera in chunk.cameras:
    for s in chunk.sensors:
        if s.label == camera.label[:2]:
            camera.sensor = s

Feature Requests / Support for NITF imagery
« on: March 05, 2020, 12:18:23 AM »
Now that the RPC sensor model has been added, it would be nice if there were support for NITF (.NTF) images.  Thanks! 

General / All tie points are invalid for WorldView Scenes
« on: February 10, 2020, 10:39:38 PM »

I am attempting to process WorldView 2 and 3 scense in version 1.6.1.  After alignment, all my images say that they are aligned, but there are zero points in my point cloud.  When I look at view matches, I see several thousand matches between the pairs of images, but all of them are invalid.  I'm having this same issue across a number of tests, from 2-4 scenes, both multispectral and panchromatic, with and without guided matching, as well as both WV2 and WV3.  Any thoughts on what might be going wrong here?  I followed the steps in the tutorial section, but did not always build optimized TIFFs. 

As an aside, every time I use the "Viiew Matches" pane Metashape crashes after about 30 seconds. 

Thank you for your help. 

General / Capture distance in reference settings.
« on: January 15, 2020, 06:16:23 PM »
I recently noticed that "Ground altitude (m)" has disappeared from the reference settings and appears to be replaced by "Capture distance (m)."  Does this serve the same purpose as ground altitude did, i.e. to allow proper preselection with oblique imagery? 

Thank hyou

Bug Reports / Issue viewing Photos, Orthos, and DEMs
« on: October 04, 2019, 05:38:43 PM »
I'm having an issue within Metashape, the cause of which may actually be outside the software.  Whenever I try to view any images, either the input photos or orthos/DEMs,  the row of icons disappears and the loading image does not move from 0%.  Interestingly, the icons still respond even though they disappear.  Also, if the aspect ratio of the Metashape window is changed, the window will appear squished or stretched.  Screenshots attached.  When the model pane is active, the program works fine.

I don't think the problem is with the software, because I uninstalled version 1.5.3 and replaced it with 1.5.5 and the problem persists.  Any thoughts on other system settings or drivers that may be causing this? 


We have a number of users distributed across offices with often poor internet connection, and these users are using Photoscan/Metashape by accessing a floating license server.  One user messaged me today saying that their connection must have cut out momentarily during processing, and it required the user to click OK on a prompt to resume.  This is problematic because the job was run on the weekend specifically because it would take a long time. 

So would it be possible to have Metashape automatically search for a license over the server a few times so that if the connection is restored it would resume processing?  I've seen this behavoir with the ArcMap license server where it'll look five times or so over the series of several minutes.  Anyway, I think this would be helpful instead of having users check in/check out licenses. 

Thank you

I've used on a number of scripts in order to provide some user feedback, but about half the time the message boxes that appear are small and cutoff some of the text (example image attached).  Even within a single script, some message boxes are fine while others are small and cutoff, and there is no clear pattern to me.  Has anyone else experience this? 

Thank you

Hi all,

Has anyone had Photoscan freeze up while performing gradual selection in a python script run within Photoscan? I work with an organization that uses an error reduction workflow where, among other things, they use gradual selection to select up to 10% of the sparse point cloud based on reprojection error, remove those points, optimize cameras, then repeat until a target value is reached. 

I was trying to implement this process as a python script run within Photoscan, and it usually works well.  With certain values, however, Photoscan passes through the iterative loop a few times then freezes.  This usually occurs when the value used for gradual selection is small.  The process freezes at a weird spot as well.  I set up the filter with the code below.

f = PhotoScan.PointCloud.Filter()
f.init(chunk, criterion = PhotoScan.PointCloud.Filter.ReprojectionError)

In most cases, this prints to the console the following message
Analyzing point cloud...
Finished processing in 0.141 sec (exit code 1)

However, in some cases it prints "Analyzing point cloud..." and then freezes so that I have to exit Photoscan using the task manager.  I've used nearly this exact same loop with reconstruction uncertainty with no issue, and when most values for reprojection error are chosen.

If anyone can help me identify why this is getting hung up on analyzing the sparse point cloud for gradual selection, that would be greatly appreciated.


Pages: [1]