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.

Topics - JMR

Pages: 1 [2] 3
Feature Requests / Flatten areas
« on: October 19, 2016, 01:45:54 PM »
I would love to have a flatten area tool that could be applied to a selection on the dense cloud. It would be useful in many situations one would want to get flat surfaces. It could have several options for calculating the plane where the points should be projected. For example:
1. Fit plane a to selection and flatten points. (this may generate sloped planes also)
2. Flatten to a given fixed elevation (bottom of a swimming pool)
3. Flaten to average elevation of selected points (a tennis court)

Best regards

Feature Requests / outer boundary applied to exports
« on: August 26, 2016, 02:52:18 PM »
As far as I know, boundary limits are just applied during ortho and DEM export. I'd like it was possible to apply it also to void mesh and dense cloud outside during export.
This would be very convenient for corridor mapping.
By now my only workaroung consist on creating a low poly mesh, crop out selection made by hand laso (one of my least favourite tools currently), then use mesh for masking prior to run dense cloud cleation. it mostly works, but the boundaries look like an ugly saw.

Feature Requests / Import masks from shape
« on: August 19, 2016, 07:25:41 AM »
I think it would be nice if masks could be importimported from polygons and even better if a buffer in pixels or in meters is allowed.

Bug Reports / colour picker malfunction
« on: August 15, 2016, 05:06:46 PM »
Screen colour picker malfunction: When I try to use colour picker for sampling areas for classifying points, I cannot. It looks like if the picker pointer is picking the pixel colour in wrong place. (build 2735). I cannot say id this worked fine in the past, but now it seems it doesn't
kind regards,

Bug Reports / New in 1.2.5
« on: June 25, 2016, 04:14:41 PM »
1 the new version is not announced by Photoscan and it even says the 1.2.4 is the latest after having installed 1.2.5
2 the colour numbers displayed are weird. the lower limit is expresed as exponential in mm and the upper in meters.
3 the layer property for shapes is too hidden. and all new shapes are assignet to no layer even if one highligts a layer... in my humble opinion the current implementation it is almost useless as is but still I say welcome to steps towards a built in simple CAD
4 the ruler readout resolution seems to be linked to zoom level during its use, but it's behaviour with this regard is not completely consistent. You should aslo make clear if the distance displayed is sloped or horizontal. A more complete measure tool would be highly welcome as well as having cursor coordinates displayed somewhere.
5 I MISS the CAMERA LOCATIONS PAGE in report. It is a very important one.
Thanks for the great additions and carry on improving Photoscan

General / Some tutorials in Spanish
« on: March 01, 2016, 03:48:14 PM »
Hola amigos: Os invito a ver algunos tutoriales en español creados para un curso de virtualización de Patrimonio en el que participamos hace dos años. Están un poco obsoletos y fueron creados para la versión 1, a pesar de ello, espero que sigan teniendo algún valor para ustedes.

Hello friends: I invite you to a set of tutorials in Spanish that were created for a course about Cultural Heritage Virtualization two years ago. As long as they were created for Photoscan 1.0 they are a little outdated,  even though I hope you find them usefull.

Best regards (Agisoft Reseller)

Enjoy our Point cloud publication service at

General / PointBox launch
« on: January 12, 2016, 11:33:23 PM »
Hello friends:
GEOBIT is pleased to announce PointBox, an online pointclouds publishing tool allowing you to interact in very agile and easy way with large point cloud models in the network.

With PointBox you can show your work by means of an attractive and user friendly interface and send your customers and friends, links for them to visualize your point clouds from anywhere through Internet connection.

Please, enter sign up and create your portfolio.

The viewing platform is at an advanced stage of testing and we believe that it already works rather satisfactorily. However you may still have some minor flaws we'll address as soon as we can. Be patient if you suffer from any kind of problem and, please, let us to know about it. We need your feed back

The display engine is based on WebGL technology, an already well-established standard for displaying 3D data on the Internet. Therefore, for your enjoyment it is necessary that both your browser and your graphic's hardware supports this technology. If you receive error messages that refer to the lack of these features, we regret to say that you can not enjoy the cloud display in your computer.

Show us your masterpieces!, enjoy sharing!

Best regards!

Please, let user to set ortho unit/pix also when the model has been scaled by scale bars and not by control points... More than a feature request is a "why on earth I can't ...?"  ;D
Thanks, folks

General / amazing work
« on: September 11, 2015, 06:04:33 PM »
I've seen this movie and suspected our beloved Photoscan was involved...
I was right: look at this "making of..." at 2:27 and later at 3:35
I would have liked they had mentioned
Congrats to authors!

Feature Requests / import camera accuracy
« on: August 10, 2015, 09:23:58 PM »
Hi: I'm working in some hardware hacks that have allowed me to write 2miliseconds accurate timestamp in my drone photos and do precise GPS postprocess calculations. This gives me a good estimation of accuracy of the image coordinates.
As long as this accuracy varies from one photo to another during the flight it could be a good idea to allow us to assign weight to each geo-tag according to its calculated accuracy.
So please enable import of a-priori individual precission for each photo and use them as weights in the adjustment. Thanks

Python and Java API / may not be a bug but simply a change
« on: November 03, 2014, 12:06:28 PM »
well I was happy using a python script Alexey published for leveling the bounding box but now it is not working any more with 1.1
Can you tell me what should I change in order to make it right?

Console: Traceback (most recent call last):
  File "C:/temp/", line 4, in <module>
    chunk = doc.activeChunk
AttributeError: 'PhotoScan.Document' object has no attribute 'activeChunk'

******************************************************Python script********************
import PhotoScan, math

doc =
chunk = doc.activeChunk

if chunk.transform:
       T = chunk.transform
       T = PhotoScan.Matrix().diag([1,1,1,1])

v = PhotoScan.Vector( [0,0,0,1] )
v_t = T * v
v_t.size = 3

   m =
   m = PhotoScan.Matrix().diag([1,1,1,1])
m = m * T

s = math.sqrt(m[0,0]*m[0,0] + m[0,1]*m[0,1] + m[0,2]*m[0,2]) #scale factor
R = PhotoScan.Matrix( [[m[0,0],m[0,1],m[0,2]], [m[1,0],m[1,1],m[1,2]], [m[2,0],m[2,1],m[2,2]]])
R = R * (1. / s)

reg = chunk.region
reg.rot = R.t()
chunk.region = reg

General / Pany GM1 ... banned for aerial! seriously
« on: October 21, 2014, 02:00:14 AM »
Yes, believe me! wonderfull cameras most senses, they're great for terrestrial job. but DON'T EVER put on board of a UAV, just trust me. Don't waste your money. It took me a while to understand why because photos looked beautifully sharp, but even sharpness can hide the worst evil.

Kind regards


General / model lower than ground control
« on: June 24, 2014, 12:48:09 AM »
I've done a project (aerial work) in wich an average deviation of -0.07m in dense cloud with respecto to ground control points (targets) is annoying me.
It seems that Photoscan underestimates elevations of all automatic matchings causing an error lowering results by some amount. Note that none of the ground control points exhibits a deviation with the opposite sign, and that makes it unlikely that the error came from a bad adjustment of the bundle block.
In this project all photos suffer from noticeable defocusing due to a bad focus set but they still  appeared to be useable.
Does someone have experienced something like this?


Bug Reports / chunk normals inverted during merging.
« on: October 21, 2013, 05:57:38 PM »
Hi Alexey: I'm testing the beta 1745
I have a project with three chunks. All have been correctly oriented and all dense clouds and models show the right orientation, but the resulting model of a merging command yields to a dense cloud that shows one model (chunks 3) has been inverted without a good reason.
If I switch multiple chunks visible ON, the three originals are right while the merged is partially inverted.
best regards!

Feature Requests / scale bars
« on: September 17, 2013, 11:25:27 AM »
1. Exportable to text file just like the rest of ground control actors.
2. Default name should be that of the two markers a scale bar links, for instance "point 1-point 2". A comprehensive link between a scale and the markers it has as end points, should survive to any renaming and/or must be explicit as a property of the scale bar
3. I'd rather prefer the old fashioned tool for picking scales on model window better than choosing two GCP and right click for calling contextual menu.
4. Scale bars could be exportable as segments in some cad formats. That would allow a primitive form of restitution.
Regards! and congrats for my favourite

Pages: 1 [2] 3