Messages

1

General / Re: Aligning single flight line, i.e. Pipe or road

« on: January 02, 2016, 08:30:43 PM »

Hi ,  I have done 50km single line images with 80% forward overlap, no problems just to produce a stitched mosaic.
I little more difficult when you want to do a accurate DTM & ortho.
What I have noticed is that if the width ratio to the length get lower than 20% then the processing struggles
What helps to improve the geometry is to fly the same area at two different heights
With the the single lines the original alignment sometimes gets twisted, before you do the the rest of the processing rotate the bounding box that the red bottom section is parallel to the surface if it is rotated
Regards
Herman

2

Bug Reports / Re: Agisoft projects not opening

« on: December 03, 2015, 12:48:52 PM »

Hello Alexey,

Thank you very much for the quick response, I switched of the model view by default and that did just the trick!!

Once again I must just say, Brilliant product, Brilliant Service!! 10 out of 10

Thank you

3

Bug Reports / Agisoft projects not opening

« on: December 03, 2015, 08:26:20 AM »

Good Day,

I am experiencing a problem that it is a bit strange, two of my pojects, (.psz files) do not not open correctly. I can open the files, and photoscan starts to open it, but then the program stops responding. I have tried leaving the projects on for quite a few hours, but still no luck. the two file sizes are 7.3gb and 3.6gb respectively, and we have done much bigger projects, so I am unsure what caused this.

Anyone have any ideas as to what I can do? I would like to recover the two files, since my backups are saved at a point before I built my mesh and classified  ground points, so it will take a while to rerun those processes.

Other than this little problem, the software is great! thanks guys

4

General / Re: low accuracy align produces better results than high accuracy

« on: September 15, 2015, 09:44:50 PM »

Hi

I have a similar problem on a rather large photo set 11500 images , a big portion is desert landscape with few features ,
but we still have a very high success rate with only 30 images not aligning - see attached image.

Any suggestion to include these images with re-aligning all 11500 images?

Regards
Herman

5

General / Re: Classification of Ground points

« on: July 12, 2015, 07:38:45 PM »

Hello Diego

Thank you for the reply , maybe I did not explain too well.

 I appreciated that one cannot expect a 100% clean result, but what we find is that it seems that the classification  seems to be 100% ignored when the DEM is created form a surface where only the ground classification is selected.

The level too which Agisoft manages to classify is amazing but you will allays need some human intervention , the only problem is that its seems that Agisoft was completely ignoring the classification.

However the problem was found , with some good advice from Dmitry , the classification parameters was just increased.
The initial problem was that the classification seems to work perfectly when visibly observed , once the DEM is tested their is still 2m height differences  present  which  seems to be removed when the visible classification is inspected.

The increased parameter settings removes some other detail , this will be manually re-classified - basically just underwriting the comments form Diego.

Diego thanks for your comments and once again thanks a lot to the Agisoft team for a great product and amazing support

Regards
Herman

6

General / Re: Hasselblad?

« on: July 11, 2015, 05:25:09 PM »

Hi

Another possible advantage would be that one would be able to fly higher and get greater footprint  coverage and still the same resolution. This would probably save on the amount and distance between ground control points.

Regards

7

General / Classification of Ground points

« on: July 11, 2015, 04:47:34 PM »

Hi

Have experienced problems with the classification in the sense that when building the mesh and selecting only the ground points to be used , the resulting DEM would still include buildings & trees.

The automatic  classification generates "Unclassified"  , "Ground" & "Low Point (noise)" with the ground showing brown and all other (buildings and trees)  showing in white. Using this classification and building the mesh it seems the buildings and trees are not removed and still included in the final DEM
When manual classification is done and building & trees are defined as such they will change from being shown in white to the resulting Red & green and the resulting DEM from the mesh would would have these building and trees excluded.

Also when writing a LAS file and selecting only the ground points to be exported the resulting DEM generated from the LAS still include buildings & trees

Regards
Herman

We are using ver 1.1.6 64 bit , previously the automatic classification successfully managed to remove all buildings & trees.

8

Python and Java API / Re: Auto exporting of multiple single photos to ortho - phyton 1.1.0

« on: February 06, 2015, 09:06:44 AM »

Hi Alexey,

I have uploaded a sample project via a file sharing service.

Thank you.

9

Python and Java API / Re: Auto exporting of multiple single photos to ortho - phyton 1.1.0

« on: February 03, 2015, 12:05:31 PM »

Hi Alexey,

The project is saved but once the script start, all cameras are deactivated and the 1st camera is activated which cause changes to the project.  Do I have to save the project at line 184?  I have hard coded path = "c:\\Users\\project" at line 184 but still get the same error.

Thank you.

10

Python and Java API / Re: Auto exporting of multiple single photos to ortho - phyton 1.1.0

« on: February 02, 2015, 08:05:20 PM »

Hi Alexey,

I have excluded the projection definitions and the script proses up to line 186 with an error that the 'path' attribute is not defined.  However, it is defined and when I print 'path', I get a valid path.

Thank you in advance.

11

Python and Java API / Re: Auto exporting of multiple single photos to ortho - phyton 1.1.0

« on: February 02, 2015, 07:21:51 PM »

Hi Alexey,

Thank you.  I am making progress but it is slow.  Attach is the script I have changed so far.  My current error is 'PhotoScan.PointCloudProject' object does not support indexing.  My assumption is that I am using a local coordinate system (no projection defined) which is causing the problem. The error is at line 44.

Regards.

12

Python and Java API / Re: Auto exporting of multiple single photos to ortho - phyton 1.1.0

« on: February 02, 2015, 01:20:57 PM »

Hi Alexey,

I appreciate your quick response. 

If I use v0_gc = chunk.transform * photo.transform *v0, I get an error of unsupported types.  Pardon my ignorance, but what have changed?

Thank you.

13

Python and Java API / Auto exporting of multiple single photos to ortho - phyton 1.1.0

« on: February 02, 2015, 10:54:56 AM »

Hi.

I am modifying a sample script from Alexey from a previous version (1.0.0) to try and make it compatable with v1.1.0.  My knowledge of Python is limited and have a hard time finding samples of changes implemented in v1.1.0.  Please help.

I have defined my projection in a local coordinate system and would like to export single cameras as single ortho photos, type Planar, projection plane Top XY.  Attached is the modified script.  I get stuck at line 106,  PhotoScan.Matrix object has no attribute 'matrix'.

Thank you.

14

General / Re: Wavy trees and errors ob building edges

« on: June 14, 2013, 09:27:12 AM »

Hi Santiago

The buildings I am sure is caused by relief distortion and the tress by a mixture of movement between successive pictures and relief distortion.  This together with the poor blending between tiles (the 2GB limit of  the ortho photo tiles) unfortunately make a good product look very poor sometimes.
I have noticed that some more GCP around such features helps a litlle bit.
Regards
Herman

15

General / Re: Trees!

« on: March 05, 2013, 05:06:51 AM »

Hello Santiago

I used the las data exported from Agisoft and used the "lasground" function. Data was then used in GlobalMapper. Ver14 of GM has the possibility to only select the "ground" points (2) classified as such by the lasground function. The "shift" I have experienced before  was not caused by Agisoft (appologies), but by GM. It however seems that ver14 has solved this - just don't use the "South Orientated" option in TM projection. I have now done some projects in more densely forested area's now and here lasground was not that successful. Terrain was mostly covered in 1m high grass and otherwise with very dense trees 2-3m high. No clean area clear of vegetation to start off with. I am sure with a better understanding of the lastools I would be able to do better.   In the end a day of visual editing (300ha) with GM was sufficient to remove the "tree points" and leave sufficient ground points . This was verified with some spot shots taken and tested by comparing with the interpolated ground surface. I barely know the lastools and hope that with more understanding to be more efficient. As mentioned by George Lidar is the answer , also with the more "intelligent" classified data (first, last, soft , hard return data) of Lidar lastools would work much better.
As long as you can see the ground and have the ability to mass edit your point cloud with the image as a backdrop you can still achieve results.
Regards
Herman