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.


Messages - macsurveyr

Pages: [1] 2 3 4
1
Bug Reports / Selected cameras incorrect in camera calibration dialog
« on: February 09, 2019, 12:24:01 AM »
If cameras are selected in the model, workspace pane or photo pane and then open the camera calibration dialog box, the wrong cameras are identified as being selected.

Bug showed up in 1.5 and remains in 1.5.1

Tom

2
General / Re: Best way to deliver 3D model locally
« on: November 04, 2018, 01:24:07 AM »
Have you looked at the Viewer app included with PhotoScan and now, Metashape? You can export .tls or .oc3 files and then view them in Viewer.

Or you could just use Metashape to view. You can open projects in an unlicensed version of Metashape and view without restriction.

Just some thoughts.

Tom

3
General / Re: Auto rotate images in portrait orientation?
« on: November 03, 2018, 09:08:57 PM »
Hello

This is an important issue. If at all possible, turn off autorotation on the camera. Since that is not always possible, or is sometimes overlooked, there can be issues such as several of you have noted.

First scenario. Autorotation is on and the images from the camera have the orientation flag set. Importing those images directly into Metashape will be just fine. There will be only one camera created since Metashape understands and honors the orientation flag as it should.

Second scenario. Autorotation is on and the RAW images from the camera are processed using Bridge, Lightroom, DxO or any other RAW processing software. If the images appear rotated in the RAW processing software, then there will be issues. The images will be exported in the orientation that they appear at, but will have a new orientation flag set to 1, meaning zero rotation, no matter what the original orientation flag was. When imported into Metashape, rotated images will have the image width and height swapped and will be imported as a different camera than the landscape images.

The easiest, most efficient way to deal with the issue is to in fact destroy the orientation flag in the RAW file BEFORE you import into the RAW processing software. When I say destroy, I mean set the orientation flag to no value.

The exiftool to command to change a DNG orientation flag to nothing is

exiftool -Orientation= SOMEFILE.DNG

As Dave said, it is actually beneficial to have images rotated relative to each other as long as all images are properly grouped together as a single camera.

The orientation flag is evil. Destroy it before processing RAW files.

Tom

4
General / Re: Agisoft Metashape 1.5.0 pre-release
« on: October 23, 2018, 07:31:12 PM »
I submitted a crash report but wanted to provide additional information.

After optimizing and checking Estimate tie point covariance then switching to view Point cloud variance in the Model view - then selecting a camera in the Photos pane and Choosing Look Through will crash Metashape every time

Tom

5
General / macOS Mojave
« on: September 26, 2018, 07:33:36 PM »
Is there any word on compatibility with the just released macOS Mojave?

I have to upgrade for several reasons but can put it off for a bit if PhotoScan has issues.

Tom

6
General / Re: GCP's and bundle adjustment
« on: September 13, 2018, 05:01:15 AM »
I think you should change your marker accuracy estimate to a more realistic value than 0.005 before making a determination about GCP accuracy.

Tom

7
General / Re: Your opinion on USGS Agisoft Processing Workflow
« on: August 24, 2018, 11:44:03 PM »
Hello All,

Learning and executing photogrammetry properly is so much more than following a workflow, a recipe or a checklist. Understanding the physics of light and the workings of a camera/lens system and the identification of sources of error in order to either eliminate or effectively model those errors is more challenging than checking all the boxes of a checklist or following all the steps of a workflow.

It is very difficult to teach and learn in a software forum - there are just too many variables - so many variables.

I will tell you that the reason to do any optimization is to improve the camera calibration. However, if the camera is not stable, with no consistent focus, has rolling shutter effect, has a small sensor, if the focal length is to long, the images are compressed, etc., then improving the calibration - no matter what parameters are checked - might be a futile effort. If the camera calibration can be improved, how far things can or should be optimized are also not always the same - many variables. The workflow cited in this forum topic - that has its origins from me - is for high quality cameras with a relatively large sensor, relatively wide angle lens, high quality photos, and is modeled after being able to achieve high quality results comparable to several other tried and true, more traditional, photogrammetry software suites from days gone by, but are still the gold standard as far as quantifiable results. Much more effort was necessary and no, it wasn’t at all obvious or straightforward as to how to achieve those results. It took a lot of experience. PhotoScan is very good and capable of achieving excellent results and while I sometimes wish good results were possible with no background knowledge and/or no experience, that just is not the case. PhotoScan has made incredible strides to that end. Maybe someday it will be the case.

Tom

8
General / Re: Rolling Shutter
« on: August 14, 2018, 05:07:54 PM »
The rolling shutter is a property of the camera, not the project. As such enabling it has been moved to the camera calibration dialog box.

Tom

9
General / Re: measuring two cameras distance
« on: May 17, 2018, 12:54:59 AM »
You can select two cameras in the Reference pane and create a scale bar. View estimated to see the distance.

Tom

10
I am also interested if this value can be accessed through python

Tom

11
General / Re: weird tall pixel artifacts in Z-axis
« on: February 27, 2018, 07:48:58 PM »
You must chosen Height field for the surface type.

Choosing Arbitrary (3D) will model everything but will definitely take more time and resources.

Tom

12
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: December 21, 2017, 08:43:27 PM »
When exporting a sparse point cloud as ply, with Point colors selected, the RGB values are all 0

1.4.0 build 5532 macOS

Tom

13
General / Re: Dealing with incorrect marker placement
« on: November 22, 2017, 12:09:30 AM »
Hi David,

You are in fact doing the right thing in BOTH cases.

A marked marker is only correct if it is in fact marked only on the visible, unambiguous target. It is incorrect to leave a marker just because it is more or less in the right image location. The actual target must be visible.

Tom

14
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: October 19, 2017, 06:29:59 PM »
I have been playing with the new Model View <Camera><Show Images> feature.  Objects I work with tend to be symmetric.  The new feature shows the image on both side of the camera; when looking through the camera as well as when you are looking into the camera.  It should only display the image when looking through the camera at the object, otherwise you can't tell which side of a symmetric object you took the picture from!

I would also like to seem indication of which side of the thumbnail is towards the object.

In addition, it would also be helpful to have an indication of camera groups. Perhaps a different border color for each workspace camera group?

Tom

15
General / Re: Set camera distance for dual camera rig
« on: October 09, 2017, 10:56:24 PM »
It is possible to select two cameras, right-click and create a scale bar.

Tom

Pages: [1] 2 3 4