Messages

1

General / Re: Agisoft Network Processing - Correct way to specify the STORAGE PATH?

« on: November 06, 2023, 10:57:51 AM »

You may be using forward slashes instead of back slashes in your path.

On Windows, Agisoft have it on their manual as the following:
metashape.exe --node --dispatch 333.333.333.333 --root //Storage/FOLDER/

You need to change it to back slashes instead.

metashape.exe --node --dispatch 333.333.333.333 --root \\Storage\FOLDER\


See if that fixes your issue.

Hello


We are trying to get the Network Processing working between 3 machines. We have used the instructions on the following link:

https://agisoft.freshdesk.com/support/solutions/articles/31000145918-how-to-configure-the-network-processing

The machines connect to the server, however, when we start processing, we keep getting an error:

"The system cannot find the path specified (3)"

What is the correct way to specify the location of the project files on Windows:
Do I use the \\PC-Name\Folder syntax, or should I use the IP address, should I map a network drive and use that?

Can someone please advise what we could be doing wrong?

Thank you!

2

General / Re: Align images using SLAM data/trajectory and images - V2.0.2

« on: October 31, 2023, 01:10:17 PM »

I'm just bumping this to see if anyone new may be able to throw a solution for this. I'm guessing it's not currently possible to align images using a SLAM trajectory file. Maybe some way to script this? I'm not a coder so it is beyond my understanding of where to begin with it.

We also cannot get our SLAM data set to automatically assist with aligning the images, we still have to do it all manually with markers. Very time-consuming and I'm hoping I've overlooked something in the process.

Is there a way in Metashape V2.0.2 to use the point cloud and trajectory file to automatically align the cameras more accurately?

We are seeking a method to leverage point clouds (SLAM data) to aid in aligning images captured simultaneously from a fixed point on the SLAM device.

Typically, our SLAM files are aligned to control points (GCPs) during processing, ensuring that the SLAM Lidar data serves as the reference.

Currently, we use Metashape for image alignment, but the initial results are not accurate enough to colourise the SLAM point cloud effectively. We import the SLAM point cloud and its trajectory, then manually add markers throughout the image sequence to achieve better alignment with the point cloud.

I had hoped that we could employ the point cloud and trajectory file to automate the camera alignment process, achieving greater accuracy.

A similar workflow exists for TLS (Terrestrial Laser Scanning) scans, which appears to use embedded images to assist in alignment. However, when attempting to align our data, it seems this method does not work effectively with our non-TLS data, likely because we don't have embedded images.

Is there a specific approach or feature in Metashape 2.02 that allows us to harness the point cloud and trajectory file for more precise camera alignment?

3

Bug Reports / Re: Colourise Laser Scan bug / odd behaviour

« on: September 12, 2023, 03:38:51 PM »

Hello Chani,

What version of Metashape you are using?

 
Currently using version: 2.0.2 build 16404 (64 bit)

This has been happening since back when V2 was just an initial beta version.

4

Bug Reports / Colourise Laser Scan bug / odd behaviour

« on: September 11, 2023, 10:31:47 AM »

As part of my ongoing effort to find a solution to the question I posted here: https://www.agisoft.com/forum/index.php?topic=15820.0, I have found an odd and frustrating issue with colourising imported LIDAR (SLAM) point clouds.

When we set the point cloud to 'use as laser scan' and then try and colourise this from our images that we have manually aligned to the scan, Metashape seems to duplicate the LIDAR to make a regular point cloud copy and colours that, moving the point cloud somewhere else as it colours it. This is frustrating as most of our SLAM data has been aligned to a control network using GCP's.

Our only workaround for this is to remember to change all the 'laser scans' back to regular point cloud objects prior to running the colourisation.

Is this a bug or is this the expected behaviour?

5

General / Align images using SLAM data/trajectory and images - V2.0.2

« on: September 07, 2023, 01:33:28 PM »

Is there a way in Metashape V2.0.2 to use the point cloud and trajectory file to automatically align the cameras more accurately?

We are seeking a method to leverage point clouds (SLAM data) to aid in aligning images captured simultaneously from a fixed point on the SLAM device.

Typically, our SLAM files are aligned to control points (GCPs) during processing, ensuring that the SLAM Lidar data serves as the reference.

Currently, we use Metashape for image alignment, but the initial results are not accurate enough to colourise the SLAM point cloud effectively. We import the SLAM point cloud and its trajectory, then manually add markers throughout the image sequence to achieve better alignment with the point cloud.

I had hoped that we could employ the point cloud and trajectory file to automate the camera alignment process, achieving greater accuracy.

A similar workflow exists for TLS (Terrestrial Laser Scanning) scans, which appears to use embedded images to assist in alignment. However, when attempting to align our data, it seems this method does not work effectively with our non-TLS data, likely because we don't have embedded images.

Is there a specific approach or feature in Metashape 2.02 that allows us to harness the point cloud and trajectory file for more precise camera alignment?

6

Bug Reports / Re: Space mouse in Agisoft Metashape

« on: May 17, 2023, 10:34:47 AM »

Have to upvote this again...
It's such a pity to be confronted with this problem, as the controller was working fine for years.
Alexey, please, can you investigate?

I have just started using my (original) Sapcemouse again, and it works perfectly for me. I did have to change the settings in Metashape to get it to work on the correct axis. This was simply a case of inverting all the axis in Metashape.

7

Bug Reports / Re: Normals not being created from Trajectory

« on: March 14, 2023, 08:04:43 PM »

Hello Chani,

Thank you for additional information.

I was able to reproduce the same problem that you are observing, if the trajectory is imported without skipping the first row (with the headed information). Please try to perform the same steps, but using Skip Rows = 1 in the import trajectory dialog.

Ok I can confirm that that was the problem. I was almost certain that I was skipping the first row as that is how I have always taken my trajectory files in previously.

 It does work now that I have double-checked and made sure that I am skipping that first row.

Thanks for your help with this!

8

Bug Reports / Re: Normals not being created from Trajectory

« on: March 14, 2023, 07:00:54 PM »

Hello Chani,

Can you please confirm, that you have imported the trajectory (with properly specified column order) and only after that imported the point cloud with "trajectory" option selected in "scanner position" field?

With your data and the described steps we have properly generated normals in the project.

Your screenshot from 2.0 version looks like the point cloud has been imported using "origin" option for the normals generation and trajectory has been imported only afterwards, when the normals have been already generated.

"Can you please confirm, that you have imported the trajectory (with properly specified column order) and only after that imported the point cloud with "trajectory" option selected in "scanner position" field?"

Yes, this is correct. Start Metashape, import trajectory file into blank chunk using the correct column headings, import laz file specifying to use the trajectory. The result does indeed look like it's using origin rather than trajectory. Could it be anything to do with installing over the top of 1.8.4? Maybe some settings are being left behind?

9

Bug Reports / Re: Normals not being created from Trajectory

« on: March 14, 2023, 02:26:44 PM »

Hello Chani,

Can you please share the source point cloud and related trajectory to support@agisoft.com, so that we could analyze the issue?

Sent via WeTransfer

10

Bug Reports / Normals not being created from Trajectory

« on: March 14, 2023, 11:47:03 AM »

I have been testing out Metashape 2.0.1 for importing SLAM point clouds and it looks like the create normals from Trajectory is not working anymore.

I noticed that the workflow has also changed. It seems that you now have to import a trajectory file before you import your LIDAR (SLAM) point cloud, which is then supposed to get used for creating the normals on the imported cloud (unless I am missing something).

The following images are screenshots from Metashape 1.8.4 where the trajectory import generates correct normals. The second image is from Metashape 2.0.1 where the normals are showing as incorrect.

11

General / Enable/Disable cameras by distance from each other

« on: December 21, 2022, 02:36:48 PM »

I have some projects that have been created by creating stills from a 360 video. To allow us to get an accurate alignment, I have been using a frame every 2 seconds. This is way too many images for my final requirement so what I was hoping for was a script or an easy way to only have camera's enabled every nth meter from another enabled camera and all the rest to be disabled.

Does anyone know of a way to achieve this?

12

Feature Requests / Re: Paint Masks with Brush

« on: December 16, 2022, 01:41:13 PM »

The intelligent scissors can follow contrasted edges if you hold down the ctrl key while clicking, just FYI.

Thanks for that, I did not actually about that. It is still a very slow method to mask a lot of images though.

Even the free form selection from the Ortho or Model tab would be much better than the slow 'click, click, click....' method of masking in the images.

13

Feature Requests / Re: Paint Masks with Brush

« on: December 05, 2022, 10:19:11 AM »

This topic does not seem to have the attention it deserves, so I am also requesting masking with a size-adjustable brush. This would save a ton of time in many of my workflows too.

14

General / Re: Hovermap SLAM normals

« on: November 06, 2022, 11:31:08 AM »

Elizaveta, many thanks for this fix. It definitely appears to work now and most of my normals are the correct way. The ones that are still incorrect might be due to some other factor in how they are created but I can accept that.

This has helped a great deal in dealing with these data sets.

Thank you very much for taking the time to assist and resolve this issue.

15

General / Re: Agisoft Metashape 2.0.0 pre-release

« on: November 02, 2022, 04:30:03 PM »

I did some testing with this and one of the things I found was that when importing a point cloud, it does not replace the existing point cloud even if you have that option checked.
It just seems to add the newly imported cloud as a new point cloud and keeps the old one too.