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 - nola

Pages: [1]
1
Feature Requests / Port zoom from Agisoft Viewer to Agisoft Pro
« on: October 15, 2021, 01:12:00 PM »
Hi,

I find that the zoom feature in Agisoft pro can be difficult to use when I zoom in very close to the model as the mouse controls (rotate, pan) seem to have a center of rotation that is not within the viewframe (hope you can understand what I mean). This results in the model 'disappearing' from the view frame with small rotations of the model.

I just tried Agisoft Viewer as I needed to share a model and was really happy to find that the zoom in controls work wonderfully! So my request is, could you port the Viewer Zoom controls over to Agisoft Pro?

2
Thanks for the tips and suggestions!
We will test with different types of targets on a smaller area to see which ones will work best with our workflow.

Now if only the weather was better here in Sweden!

3
Our test case is to see if the coded target can help us identify the locations of potentially hundreds of markers. These of course would not be used in the traditional gcp method of correcting the model.

Basically we have to go out and survey castre boundaries that are marked with a small pipe in the ground. Each property has min of 4 pins and we have about 300 properties to survey. An idea was to see if we could place the coded markers on the property pins and use Agisoft to auto detect these.

The question we want to answer is:
If we were to say only survey about 50 % of the pins, could we get the positioning of the remainder with a decent accuracy from the 3d model and locate them with the help of coded targets.


4
Thanks for the suggestion!

I ended up adjusting the size so it fills the A4 page and then printing it to A3 by scaling up in the printer settings.

I do wish there could be more than 161 coded targets though.

We are looking to place them out along different administrative boundaries to see if they could be used to minimize GPS work so we want to put out hundreds of targets.

5
I am trying to print relatively large (30-35cm) coded markers but when I have a center point radius value of say 50mm, the coded target becomes much larger then the default paper size (A4 i assume). It would be nice to be able to set a custom page size or that Agisoft changes the page size automatically.

The other request would be to allow the numbering of the coded target to have a custom location, especially useful for larger target size. When the font is increased (ex. 90) the number is inside the coded target.

I am trying to follow the guidelines in this post for using coded targets in drone surveys.
https://www.agisoft.com/forum/index.php?topic=2768.msg32898#msg32898

6
Feature Requests / Re: Export point confidence greyed out?
« on: October 15, 2020, 02:14:35 PM »
nevermind, i see that i had selected to export point normals :)

I do hope that export of confidence values can be included for .txt file export in the future as I am using matlab to classify points based on RGB values and the confidence would help out as I am classifying water from land.

7
Feature Requests / Re: Export point confidence greyed out?
« on: October 15, 2020, 02:04:47 PM »
Thanks for the reply!
Would you happen to know where in the las file it is stored? is it intensity?

Also, does anyone know what the columns are when the point cloud is exported as .txt file?
I see x,y,z,r,g,b but what are the last 3 columns?

I looked in the manual but couldnt find the answer anywhere.

thanks,
Norris

8
I would also like to know where the point confidence is stored in a las file :)

9
Feature Requests / Export point confidence greyed out?
« on: October 14, 2020, 03:49:42 PM »
I am trying to export my dense cloud as xyz with the point confidence but the option is greyed out.
I can filter the point cloud by confidence so the values have been calculated with the dense cloud, it is just the exporting that does not seem available.

Is this normal? or a bug?

Pages: [1]