Messages

1

Bug Reports / Re: chunk.importShapes results in crash

« on: October 12, 2016, 10:07:30 AM »

Hi Alexey,

yes I have submitted some crash reports. The issue does not occur when loading a shapefile via a GUI. We found the workaround in the end which was already having a chunk with a manually loaded shapefile and then we can overwrite the shapefile through python API without crashing.

2

Bug Reports / chunk.importShapes results in crash

« on: October 11, 2016, 04:42:16 PM »

When i try to load a shapefile or KML through the following code:

app = PhotoScan.Application()
doc = PhotoScan.app.document
chunk=doc.chunks[0]  #this is a chunk with an orthomosaic, sparse point cloud, mesh and cameras
chunk.importShapes(path="pathtoshapefile.shp",replace=False,boundary=PhotoScan.Shape.OuterBoundary)

then the system crashes. Since I saw nothing like this issue on the forum i would like to know if anyone succesfully loaded a shapefile through python. Loading the shapefile works when i do it manually.

3

General / Re: Using Global (ASTERDEM) as ground control points?

« on: August 22, 2016, 04:11:10 PM »

well I did the 10 minutes of googling plus an extra long post here on this forum, so if you have any tips here Arie, that would be great 

4

General / Using Global (ASTERDEM) as ground control points?

« on: August 10, 2016, 11:22:33 AM »

I am having problems with my DEM. The details are mostly correct but i get convex/concave dems and large rifts when using photoscan for dem generation from aerial imagery. Would it be valid to use the global dem (Aster DEM or worldDEM V3) as ground control points without manual correction? If so what would be the correct processing method?

What i have done before is extract a ground control point for every 30 meters and loaded these values as ground control points. However, when i optimized camera's based on the ground control points my whole sparse point cloud would tilt way too much and neither the camera's nor the ground control points would still be in the bounding box.

5

General / Re: convex DEM and rifts in DEM

« on: August 03, 2016, 05:24:37 PM »

Hi Alexey,

I did all these things and the project is loading. This does still not solve any issues regarding rifts and convex dems so any help is still very much wanted.

6

General / Re: convex DEM and rifts in DEM

« on: August 03, 2016, 04:07:42 PM »

Hi Stihl and Alexey,

unfortunately i just broke the project (don't know how, photoscan keeps crashing), so i cannot share any more screenshots (running the project takes 2 days). no orientation data was loaded but nothing strange was to be seen on the sparse point cloud. i have attached overlaid the location of the cameras in altitude. though you can see that the pilot went down one way and up the other way (flightline) i do not know why this would create such big gaps.

7

General / Re: convex DEM and rifts in DEM

« on: August 03, 2016, 12:56:04 PM »

Dear Stihl,

thank you for your reply. The images are good in that they have no blur, no oversaturation or strong noise, no rolling shutter (D810 DSLR camera), fixed aperture and no autofocus or autostabilisation. The coordinate system and the photo positions are also correct (EPSG:4326 format). The overlap in the area with the rift is 7-9. We have not calibrated the camera's and the GPS shows strong inaccuracy in the photoscan report in the southwest area but this is also where the rift is occurring. Therefore i am wondering why photoscan pulls the images in the west down (accuracy of -47 meters) and up in the east part of the southwest area the gps position is pulled up and i can imagine that this causes this rift (see attachment).

Is there any way that i can prevent photoscan from doing this and if so should I?

8

General / convex DEM and rifts in DEM

« on: August 03, 2016, 10:47:21 AM »

I am using Photoscan to build DEM's from aerial imagery and at moments i get the following problems:

The DEM that photoscan produces is convex (see attachment) or tilted.

The DEM shows rifts (height can drop over 60 meters within one meter.

Did anyone else experience these issues and what is your solution? Note: ground control points are not possible for me.

9

Python and Java API / autoIt python script start

« on: June 09, 2016, 11:18:21 AM »

Dear All,

In this forum I found that some people have a workaround solution to automate running a script for photoscan. I would like to implement this but cannot seem to get it to work (Especially the run python script window is not very controllable). Does any one of you have a script for this? What I need is:

-Click the run python script icon in the console tab.
-select the Arguments line
- Type in customized text
- Press ok (or enter)

10

General / Re: How to restrict camera location adjustment to be less than accuracy spec?

« on: May 31, 2016, 12:25:49 PM »

I've encountered the same problem. Anyone found a solution for this?

11

Python and Java API / Re: Zero resolution after region resize in python

« on: April 04, 2016, 12:57:53 PM »

Hi Alexey,

there are more than enough matching points and as I stated, if i change the size manually in the GUI the dense cloud generation will work, even if I make the area smaller (which would lead to less matching points). So it has to do something with the project.

12

Python and Java API / Zero resolution after region resize in python

« on: April 01, 2016, 09:45:46 AM »

I've written a script that sets the rotation, size and center of the region of a chunk. I run this script on an aligned chunk and if i then want to create a dense point cloud i can see that 0 cameras have been selected which leads to an error of Zero Resolution. If i then manually change the chunk boundaries only even a tiny bit then the dense point cloud creation will work. With a tiny bit I mean that the boundaries do not change in any significant way. This leads me to think that when you manually resize the region photoscan updates in some way but I have already tried the following things and nothing seems to work except for manually resizing:

- update the project
- copied the chunk and made the new one active
- saved the project
- saved, closed and opened the project
-optimize cameras after resizing of the region

Does anyone have any ideas about this?

13

Python and Java API / rotate from true north and resize

« on: March 24, 2016, 07:26:00 PM »

I'm trying to resize my region with a new center, size and rotation. I read all topics that are on this forum but could not get a conclusive answer on this. Setting the center is going okay, but changing the size or doing the rotation proves a problem.

about the size: my images are referenced in epsg:4326 so in LatLon. my chunk also has this reference system. i set the size to half the bounding box width and half the bounding box height, which are:

         x                     y
0.001210391   0.00532877

These do not correspond at all with the x and y sizes of the chunk region, which are about 20 and 35. Which function do I need to apply to get to the correct values? I calculated s with the script as given in http://wiki.agisoft.com/wiki/Bounding_Box_to_Coordinate_System.py

but in this s is 44 so still no way to get to the right value.

about the rotation matrix:
I want to rotate my bounding box with +4 degrees from true north but i have no idea how to first set the bounding box to true north and second how to rotate it 4 degrees.

14

General / Error: can't read image

« on: January 27, 2016, 10:46:30 AM »

I'm currently trying to process a large orthomosaic. the whole thing was processed (the second to last processing step stated 'Finished Processing' and right after that I got the error 'Error: can't read image: 2688'. How can this error come about and how can i prevent it from happening again. This were the two final lines of build orthomosaic. The chunk in which i build this orthomosaic contains a suitable DEM on which the orthomosaic is based. The error occurred both with and without color correction. The disk space did increase during the building of the orthomosaic so something was made in the meantime.

Edit: the result was that the entire orthomosaic was not showing up in my chunk and seeing from the save-file size it was entirely removed.

15

General / depth filtering processing time

« on: January 19, 2016, 02:08:10 PM »

Hi All,

I am currently running quite big datasets on my computer and noticed that quite often there is a big time lag in processing time during the depth filtering step. In the attachment you can see a plot of time related to camera count and I would like to know three things:

1: can I expect that with, say,  600 camera's my system will never finish?
2: what parameters can I set to control the number of camera's used in a substep in the depth filtering step?
3: how can i further decrease this processing time?

I'd like to note that my system is not swapping and the RAM is only 30% used. the 32 CPU cores are running full-time (XEON E-5 Dual @ 3.5GHz)