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] 5
46
General / Re: Optimizing Image Alignment with different flight heihgts
« on: September 04, 2016, 04:36:09 PM »
Hi GrinGEO,

One word of caution. My experience is that changing scales or flying heights by more than 2x can be problematic. Automatic image matching at 3x - in your proposed case more than 3x - may not work. Try flying at 60, maybe 70 meters instead of 100.

Tom

47
General / Re: "Camera Stations"
« on: June 23, 2016, 02:13:20 AM »
In the scenario you describe, the cameras should NOT be grouped. Every camera location is in fact unique, in relation to the subject, as if you moved around the doll.

If you moved the doll independent of the circular scale sheet, that will also be an issue. It would be best to have the circular scale sheet and the doll on a turntable and move both together so that the scale and the doll will be modeled together in the same relative 3D space. Any background that does not move with the doll should be masked out as well.

Hope that is clear.

Tom

48
Bug Reports / Capture View save issues
« on: June 17, 2016, 09:01:35 PM »
With version 1.2.5 when trying to Capture View there are issues with both .jpg and .tif

The behavior is a bit different on a Mac and on Windows. On a Mac a ; is appended to the .jpg and .tif and the system complains about not being able to save or an invalid extension. Entering jpeg and tiff works. On Windows, it does not seem possible to save a jpg or tif even as jpeg or tiff

Tom

49
Bug Reports / Re: 1.2.4 Duplicate Chunks
« on: April 02, 2016, 05:50:12 PM »
Some of the chunks have less than 15 cameras and nothing other than tie points - nothing other than aligned photos and it can still take 3 minutes to duplicate.

Tom

50
Bug Reports / 1.2.4 Duplicate Chunks
« on: March 31, 2016, 09:31:23 PM »
The latest version 1.2.4 can take several minutes to duplicate a chunk. Not always, but by far most of the time. That was an issue in some previous version that went away and seems to be back.

Also, maybe related, saving - even in .psx - can take several minutes as well. Not always, just sometimes.

51
Bug Reports / Re: PLY export coordinates no decimal places
« on: March 12, 2016, 05:43:24 PM »
Hello Alexey,

Yes. Any points export - sparse points or dense points - via file export points or right click on dense point cloud.

Tom

52
Bug Reports / PLY export coordinates no decimal places
« on: March 12, 2016, 01:41:15 AM »
It seems that all versions after 1.2.0 build 2198 do not export any decimal places for the X and Y coordinates when exporting a text PLY file - that is uncheck binary coding.

Actually it looks like 6 digits are exported no matter what - if local coordinates are exported you might get 123.456 but if say UTMs are exported you get 123456 or 1234560

Tried it in 1.2.1 1.2.2 and 1.2.3

Tom

53
General / Re: Automatic sub-chunks?
« on: August 05, 2015, 06:50:06 PM »
The easiest way that I have found is to align all photos together then duplicate that chunk. In the copy of the chunk, select all photos that DID align and right click -> remove cameras. Then select all the remaining cameras and right click -> align selected cameras. The largest number of photos that align together will align pretty quickly - no need to find new match points. Duplicate the chunk and repeat.

Tom

54
General / Re: Agisoft PhotoScan 1.1.0 pre-release
« on: October 03, 2014, 01:09:32 AM »
Using the new multiple photo tab functionality on a Mac is limited. I don't see any way of moving a tab to another tab group like I can on windows.

Am I missing something?

Tom

55
General / Re: Exporting Agisoft aligned photos to Inpho
« on: May 06, 2014, 12:07:34 AM »
Alexey,

Has the export to Inpho been revisited lately?

I exported an Inpho project and noticed that the camera information seemed incorrect. Both for each image and also for the camera definition at the end.

The focal length is exported as the original EXIF value not the calibrated focal length. So, I entered the calibrated focal length into the camera calibration dialog box and reexported. The new value was indeed exported but things are still not correct.

Here is one photo and the camera definition from the original export

$PHOTO
  $PHOTO_NUM : pr0909_50mm_0778.TIF
  $PHOTO_FILE : G:/PowderRiver2009/APC/pr0909_50mm_0778.TIF
  $CAMERA_ID : Canon_EOS-1Ds_Mark_II_(50_mm)
  $TERRAIN_HEIGHT : 1282.3846198138667000
  $PIXEL_SIZE : 0.0069918047717751
  $SCAN_POS : 0
  $IO_PARS : 2 2
  $IO_STAT : manual
  $EXT_ORI : 08:20:46 05/05/2014
        50.0000000000000000    405615.6194925598100000   4863478.9887055010000000       1514.3143030865913000
      0.8310341536382675      -0.5444507272856713      0.1138228493969121
      0.5558503132780518      0.8054316153965812      -0.2056947790984157
      0.0203141506202012      0.2342078531513363      0.9719742881408036
$END
$CAMERA
  $TYPE : Canon_EOS-1Ds_Mark_II_(50_mm)
  $DATE : 08:20:46 05/05/2014
  $BRAND : Custom
  $KIND : CCDFrame
  $CCD_INTERIOR_ORIENTATION :
     143.0297329511802800       -0.0000000000000000    2509.2457364247275000
       0.0000000000    -143.0194439471396200    1700.4109677756908000
  $CCD_COLUMNS : 4992
  $CCD_ROWS : 3328
  $PIXEL_REFERENCE : TopLeftTopLeft
  $FOCAL_LENGTH :    50.0000000000000000
  $PRINCIPAL_POINT_PPA :     0.000000     0.000000
  $DISTORTION_TYPE :  Polynomial
  $RADIAL_COEFFS :
                      0.0000000000000000             0.0000304526480109                  0.0000000361957312                  -0.0000000000592217
                      0.0000000000000709             0.0000000000000000                  0.0000000000000000                  0.0000000000000000
  $DECENTRE_COEFFS :
                      0.0000099585304794             0.0000153221698427                  0.0000000000000000                  0.0000000000000000
  $GPS_ANTENNA_OFFSET :     0.000000     0.000000     0.000000
  $CAMERA_MOUNT_ROTATION :     0.000000
$END


Here is the second export - after only entering the calibrated focal length.


$PHOTO
  $PHOTO_NUM : pr0909_50mm_0778.TIF
  $PHOTO_FILE : G:/PowderRiver2009/APC/pr0909_50mm_0778.TIF
  $CAMERA_ID : Canon_EOS-1Ds_Mark_II_(50_mm)
  $TERRAIN_HEIGHT : 1282.3846198138667000
  $PIXEL_SIZE : 0.0072005638580535
  $SCAN_POS : 0
  $IO_PARS : 2 2
  $IO_STAT : manual
  $EXT_ORI : 11:46:32 05/05/2014
        51.4928841199999990    405615.6194925598100000   4863478.9887055010000000       1514.3143030865913000
      0.8310341536382678      -0.5444507272856710      0.1138228493969121
      0.5558503132780515      0.8054316153965814      -0.2056947790984157
      0.0203141506202011      0.2342078531513363      0.9719742881408036
$END
$CAMERA
  $TYPE : Canon_EOS-1Ds_Mark_II_(50_mm)
  $DATE : 11:46:32 05/05/2014
  $BRAND : Custom
  $KIND : CCDFrame
  $CCD_INTERIOR_ORIENTATION :
     138.8830082015420300       -0.0000000000000000    2509.2457364247275000
       0.0000000000    -138.8730174967908200    1700.4109677756908000
  $CCD_COLUMNS : 4992
  $CCD_ROWS : 3328
  $PIXEL_REFERENCE : TopLeftTopLeft
  $FOCAL_LENGTH :    51.4928841199999990
  $PRINCIPAL_POINT_PPA :     0.000000     0.000000
  $DISTORTION_TYPE :  Polynomial
  $RADIAL_COEFFS :
                      0.0000000000000000             0.0000287124754340                  0.0000000321772187                  -0.0000000000496384
                      0.0000000000000561             0.0000000000000000                  0.0000000000000000                  0.0000000000000000
  $DECENTRE_COEFFS :
                      0.0000096698122950             0.0000148779487735                  0.0000000000000000                  0.0000000000000000
  $GPS_ANTENNA_OFFSET :     0.000000     0.000000     0.000000
  $CAMERA_MOUNT_ROTATION :     0.000000
$END

FYI

Both exports had virtually the same info in the console - here it is

lm optimize: xxxxx-----------x-x----------- 0.077662 -> 0.00225481
Calibration converted, mean error = 0.442852 pix, max error = 0.884545 pix


I do not have Inpho, but can import an Inpho project into Stereo Analyst and with both projects, there is quite a bit of parallax away from the center of the model - actually worse with the calibrated focal length entered.

Tom
 

56
General / Re: Tie Point Accuracy setting in Ground Control Settings
« on: October 31, 2013, 02:07:56 AM »
I really think this needs more discussion.

As with all least squares analysis, the weight - the error estimates - for any and all measurements - the sources of error - need to be correct in order for the results, and just as importantly, the statistics quantifying the results to be correct.

I do not believe that a 4 pixel error is a valid estimate for the tie points image matching accuracy.

We can have a long discussion about what it should, or rather could be, depending on the matching algorithms used, but it is quite common to expect sub-pixel matching - sub-pixel error - even as low as 0.1 to 0.2 of a pixel of error. In PhotoScan Pro with minimal optimization and gradual selection removal of the worst points, a point variance RMSE of less than 0.5 pixel is very easy to obtain. So, a 4 pixel error estimate is very pessimistic. An unreasonably pessimistic error estimate.

It also seems to me that entering a much more realistic estimate - in the sub-pixel range - does not in fact change the statistics as much as it should. It still seems that control, whether it is true ground control or camera position values, are given too much weight not necessarily honoring the entered values.

Tom

57
General / Re: 1.0.0 Scaling with two markers at a known distance
« on: September 05, 2013, 11:47:28 PM »
Select two markers and right click

58
General / Re: Agisoft PhotoScan 0.9.1 pre-release
« on: May 09, 2013, 07:23:48 PM »
Hello Alexey,

I just tried the latest build 1676 with both fixed and not fixed camera calibrations and it is the same as 1667. it does not work properly. I can hold all cameras fixed or all cameras unfixed and have predictable errors. Mixing fixed and unfixed cameras does not work.

Tom

59
General / Re: Agisoft PhotoScan 0.9.1 pre-release
« on: May 01, 2013, 10:00:06 PM »
Alexey,

I just tried build 1667 with a project with fixed cameras and errors jump from ~0.25 pixels per photo to over 100 pixels.

The project actually has four cameras - two have to be held fixed and the other two can, need, to be calibrated. The alignment went great with no real problems. As soon as I optimized, the errors increased to over 100 pixels. I loaded the successfully aligned photos - before any optimization - into build 1647 and everything behaves fine. I can optimize and refine the project and refine the two unfixed cameras.

I saved and opened the project in build 1667 again and the errors once again jumped from ~0.25 to over 100 on both the fixed cameras. The errors remain at ~0.25 pixels for the other two cameras.

If I go to the camera calibration and uncheck fixed for those two cameras, the errors immediately drop to less than 0.25 pixels for all cameras. If I go back in and check fixed again, the errors jump back to over 100

Tom

60
Bug Reports / Re: Large coordinates truncated in PLY
« on: March 18, 2013, 12:24:07 AM »
jedfrechette

I believe you are exactly correct. It is probably an accident that the ascii version works in some viewers. And it comes back to declaring float is the problem, even if the data is stored at double precision.

Tom

Pages: 1 2 3 [4] 5