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 - Erik Holmlund

Pages: 1 2 [3]
31
You can solve it with a list comprehension, like you started on.

Code: [Select]
chunk = doc.chunk
points = chunk.point_cloud.points
nselected = len([p for p in points if p.selected])

or just
Code: [Select]
chunk = doc.chunk
nselected = len([p for p in chunk.point_cloud.points if p.selected])

It calculates it really quickly on my computer.

32
Hi Alexey,
I had completely missed the latest build! Now it works like a charm.

Thanks!

33
Hi,
I'm very interested in the new fiducial support, as it greatly reduces the effort of using analog imagery. I can however not make it work completely, as marker placement seems non-functional.

If I use the images separately as non-analog, the marker placement works (as bad as it does without fiducials). If I specify the fiducials and place a marker, it ends up on the other side of the solar system. Below is an example of an estimated coordinate I get, from a point added through the sparse point cloud:

East 8 144 283.304 m
North: 13 169 867.186 m
Altitude: 7 982 093 517.095 m

The pixel error is also massive, at 2895.922.

My suspicion is that the internal coordinate system produced by fiducial placement is wrong, creating invalid marker projections and therefore the position. The fiducials I have in the same project are:

X,Y in millimeters, with the focal length: 152.83 mm
Upper left: -106.073, 105.904
Upper right: 105.919, 106.098
Lower right: 106.06, -105.902
Lower left: -105.906, -106.099

I've tried it in several projects, and with different X and Y directions (positive X or negative X etc.). I've also tried the calibrate fiducials tool with no change.

Reproducing the problem is as easy as importing the images, placing fiducials, calibrating them, aligning the images and then placing a marker in the point cloud.

I would love to have the tool working, but evidently it's clearly not!

34
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: December 01, 2017, 07:10:24 PM »
I noticed a bug in the new Refine Mesh tool, where some compressions, or amount of bands, return an "Unsupported data type" error.

I used 8 bit B&W images with the color profile "Gray Gamma 2.2", and with what I think was ZIP compression (it doesn't say in the metadata). After converting them all to 8 bit 3 channel "Adobe RGB 1998 (1998)" with no compression, the tool worked fine. My suspicion is the ZIP compression, but I can't reliably say so since I'm not entirely sure what the compression was.

Either way, the tool works with that simple workaround!

35
General / Re: Using a rendered model from drone images in QGIS
« on: December 01, 2017, 05:35:49 PM »
Do you mean when building the orthomosaic? I never specify a custom resolution, but just export it in PhotoScan's calculated one.

36
General / Re: Using a rendered model from drone images in QGIS
« on: November 30, 2017, 01:32:38 PM »
If you're after the texture, isn't it an orthomosaic that you want, instead of a DEM? You create and export it the same way as a DEM

37
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: November 27, 2017, 10:55:57 PM »
Hi,
I have an issue with the fiducial feature in the newest and second newest builds. Everything works correctly except for markers that don't work whatsoever.

If I have a pointcloud and try to create a marker it creates a marker millions of meters away. It doesn't work either to create markers in Photo view (neither Add nor New). With known camera coordinates it works the same. I've tried it on several different projects with different images.

I would love to have this fixed as the feature makes it so much easier to work with old imagery!

Pages: 1 2 [3]