16
Bug Reports / Cylindrical orthomosaic fails
« on: October 15, 2019, 08:05:47 PM »
Cylindrical ortho fails even if cylindrical DEM has been built correctly.
Regards
GEOBIT
Regards
GEOBIT
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.
17
Bug Reports / Drag view changes model orientation
« on: October 22, 2018, 01:09:50 AM »
Yes, this sounds imposible, but if you have a scaled model that has been rotated manually so scene XYZ axis are coherent with object principal directions, if you drag the view, your axis will rotate about Z. This unexpected behaviour has driven me crazy for quite a while... and is totally nonsense from my point of view.
As well, it is annoying that if one rotates object, then sets a scale bar and updates... Photoscan will on its own modify model rotations instaid of just scale it
Why without my permission? WHY?
EDIT: This odd behaviour can be reproduced, however it seems not to be a general case. In my particular case, I'm processing photos that had geotags. I cleared them before alignment, but still the coordinate system remains as wgs84. I have noticed that resetting transform and changing to "local coordinates" makes things work as they should.
Regards
As well, it is annoying that if one rotates object, then sets a scale bar and updates... Photoscan will on its own modify model rotations instaid of just scale it
Why without my permission? WHY?
EDIT: This odd behaviour can be reproduced, however it seems not to be a general case. In my particular case, I'm processing photos that had geotags. I cleared them before alignment, but still the coordinate system remains as wgs84. I have noticed that resetting transform and changing to "local coordinates" makes things work as they should.
Regards
18
Feature Requests / filter photos by doble click
« on: October 03, 2018, 03:21:12 PM »
It would be nice to speed-up the "filter photos by marker" by doble click on a marker in the list.
1. if done on the project tree
2. if doble click is done in the ref pane, currently one enters rename mode for marker name. In my experience renaming a marker operation is done more rarely than the filtering by marker, so I would prioritize the filter by... and put rename as a context menu option only
Alternatively, you could make the flag symbols of each gcp in the ref pane list (currently they are just esthetic), behave as a "filter by..." button by single click.
Kind regards
1. if done on the project tree
2. if doble click is done in the ref pane, currently one enters rename mode for marker name. In my experience renaming a marker operation is done more rarely than the filtering by marker, so I would prioritize the filter by... and put rename as a context menu option only
Alternatively, you could make the flag symbols of each gcp in the ref pane list (currently they are just esthetic), behave as a "filter by..." button by single click.
Kind regards
19
Bug Reports / Issue with OPK angles
« on: September 25, 2018, 08:01:04 PM »
Hello friends. I've found what seems to me a bit of a bug:
Have a project with photos having lat, lon, alt, yaw, pitch, roll, already aligned.
Now have a GCP text file with names,X,Y,Z
When you import this file with OPK as rotation format option selected in the dialog, even with rotations import check disabled, it will force change project to OPK mode causing problems with the camera rotations.
In my opinion this dropdown option in the import dialog should be disabled unless the rotation import is checked.
Regards,
GEOBIT
Have a project with photos having lat, lon, alt, yaw, pitch, roll, already aligned.
Now have a GCP text file with names,X,Y,Z
When you import this file with OPK as rotation format option selected in the dialog, even with rotations import check disabled, it will force change project to OPK mode causing problems with the camera rotations.
In my opinion this dropdown option in the import dialog should be disabled unless the rotation import is checked.
Regards,
GEOBIT
20
General / Using Dji Gimbal angles.
« on: June 19, 2018, 04:49:15 PM »
This an old issue but not fully understood by me.
the topic http://www.agisoft.com/forum/index.php?topic=7286.msg35063#msg35063 included some useful code to list gimbal angles and aircraft angles as well. By using it, one can notice that none of them correspond to what one could wish (something close to the estimated angles after a successful alignment with ground control)
Extracting angles from XMP data by means of the built-in funciton will lead user to wrong input data because it imports the so called flight angles rather than the gimbal ones... so it is useless. But even if it had read the right metadata, one would find that when camera is looking nadir, the gimbal pitch is stored as -90.0 while if used agisoft's convention it should be something close to 0 degrees. So it is likely DJI uses NED (north-east-down, typical for aerial vehicles) rather than ENU (east-north-up) convention.
Alexey: could you please modify the "read xmp" function so that when reading camera angles from dji, it can pick the right entries and convert them to the same convention used in photoscan?, if you do not consider this modification to be a good idea at all, could you please modify the py code in the related post so it can work as desired and filled photo angles to the ref pane?
Thank you!
GEOBIT
the topic http://www.agisoft.com/forum/index.php?topic=7286.msg35063#msg35063 included some useful code to list gimbal angles and aircraft angles as well. By using it, one can notice that none of them correspond to what one could wish (something close to the estimated angles after a successful alignment with ground control)
Extracting angles from XMP data by means of the built-in funciton will lead user to wrong input data because it imports the so called flight angles rather than the gimbal ones... so it is useless. But even if it had read the right metadata, one would find that when camera is looking nadir, the gimbal pitch is stored as -90.0 while if used agisoft's convention it should be something close to 0 degrees. So it is likely DJI uses NED (north-east-down, typical for aerial vehicles) rather than ENU (east-north-up) convention.
Alexey: could you please modify the "read xmp" function so that when reading camera angles from dji, it can pick the right entries and convert them to the same convention used in photoscan?, if you do not consider this modification to be a good idea at all, could you please modify the py code in the related post so it can work as desired and filled photo angles to the ref pane?
Thank you!
GEOBIT
21
Agisoft Viewer / Agisoft Viewer dedicated installer.
« on: May 29, 2017, 11:58:10 AM »
Agisoft view installer.
I'd like that agisoft Viewer had a dedicated installer, even a portable build. Is there anybody wanting the same?
regards
I'd like that agisoft Viewer had a dedicated installer, even a portable build. Is there anybody wanting the same?
regards
22
Bug Reports / orthomosaic edition odd behaviour
« on: April 18, 2017, 02:30:46 AM »
I have a buiding model and created orthomosaic for façade A, did some edition by assigning different images to pollygons with no problem, then exported the ortho.
Now moved to façade B, still the same chunk referenced just the new ortho is created from a new point of view. And now I cannot create shapes on the ortho?. To be more exact, I can start drawing a shape but when closed it disappears at the last clic.
this bug had been reported happening in previous version too so please, do something asap!
best regards
GEOBIT
Now moved to façade B, still the same chunk referenced just the new ortho is created from a new point of view. And now I cannot create shapes on the ortho?. To be more exact, I can start drawing a shape but when closed it disappears at the last clic.
this bug had been reported happening in previous version too so please, do something asap!
best regards
GEOBIT
23
Bug Reports / Trackball
« on: March 07, 2017, 08:17:46 PM »
Hello, Alexey:
Set trackball item to hidden
choose rotate object tool and the object trackball is shown but user is not allowed to use constrained rotations. This behaviour is not very consistent in my opinion. If the rotate object tools overrides scene trackball visibility setting (nothing to complain here) then it should work as usual when user picks its main circles.
I wish one day the GUI will offer better feedback of the active tool by means of differentiated cursors.
Best
Set trackball item to hidden
choose rotate object tool and the object trackball is shown but user is not allowed to use constrained rotations. This behaviour is not very consistent in my opinion. If the rotate object tools overrides scene trackball visibility setting (nothing to complain here) then it should work as usual when user picks its main circles.
I wish one day the GUI will offer better feedback of the active tool by means of differentiated cursors.
Best
24
Bug Reports / Wrong roll estimation in 1.3
« on: February 06, 2017, 10:25:11 PM »
Hi, Alexey:
There must be a bug in the roll estimation because in a project composed of 790photos hand held, 545 show 0.000 as estimated roll value... others show values close to -180 or to 180 but they alternate with no reason. Apparently all photos have been well oriented and pixel errors look fine.
I also have noticed that automated marker propagation stops functioning without reason after having merged two chunks.
Look carefully attached images and tell if selected images explain the shown roll estimated values in each case.
Yaw doe not seem consitent either. the last example with three images that were taken sensibly perpendicular to the façade, appear to have very diferent yaw angles.
Best regards!
GEOBIT
There must be a bug in the roll estimation because in a project composed of 790photos hand held, 545 show 0.000 as estimated roll value... others show values close to -180 or to 180 but they alternate with no reason. Apparently all photos have been well oriented and pixel errors look fine.
I also have noticed that automated marker propagation stops functioning without reason after having merged two chunks.
Look carefully attached images and tell if selected images explain the shown roll estimated values in each case.
Yaw doe not seem consitent either. the last example with three images that were taken sensibly perpendicular to the façade, appear to have very diferent yaw angles.
Best regards!
GEOBIT
25
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
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
26
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.
Regards!
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.
Regards!
27
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.
Best
José
Best
José
28
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,
José
kind regards,
José
29
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
GEOBIT
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
GEOBIT
30
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
www.geobit.es (Agisoft Reseller)
Enjoy our Point cloud publication service at www.pointbox.xyz
https://www.youtube.com/playlist?list=PL_cDdjQPbX1GXV4AC3Y3dYVwTPh4kxnk-
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
www.geobit.es (Agisoft Reseller)
Enjoy our Point cloud publication service at www.pointbox.xyz
https://www.youtube.com/playlist?list=PL_cDdjQPbX1GXV4AC3Y3dYVwTPh4kxnk-
