Messages

16

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.

17

General / Re: Hovermap SLAM normals

« on: November 02, 2022, 03:49:50 PM »

Dear Chani,
Thank you, we downloaded your data.

Thank you, Elizaveta. I await your response to see if anything can be done to import/calculate clean normals.

18

General / Re: Hovermap SLAM normals

« on: November 01, 2022, 06:46:24 PM »

Dear Chani,

Could you please send an example of your data set (point cloud and trajectory file) to support@agisoft.com?

I have sent the data by WeTransfer. You should have a link in your email (might be in spam folder).

19

General / Hovermap SLAM normals

« on: November 01, 2022, 05:53:38 PM »

Hi, I have some SLAM data that I have captured using Emesent Hovermap and I am trying to take them into Metashape so that I can colour the data using a set of spherical images I have captured at the same time. The problem I am having is that the SLAM data does not have normals and Metashape calculates them with a LOT of inverted normals. This is a capture of an oil and gas facility so there are a lot of pipes, walls and other multi-shape objects.

I have created a chunk and imported our spherical images and aligned them perfectly, then I take the SLAM data in and want to colour it based on the following tutorial: https://agisoft.freshdesk.com/support/solutions/articles/31000157888-colorization-of-the-external-dense-cloud-lidar-based-on-images

The colourisation process works great, it is just the SLAM data that is proving a real headache to generate correct normals for.

I have tried to up the setting to over 200 on 'Generic' during import but this does not help too much. I noticed that there is an option to use a trajectory file (which I have from the Hovermap scan). When I select this option, it just appears to create the normals from the origin of the scan and not along the trajectory. I have tried to strip the trajectory xyz file so that it only contains the fields mentioned in the importer (time,x,y,z) but again, this does not help. I'm guessing the trajectory file must be a specific file and not just any trajectory file.


Can anyone offer any advice on how to get the point normals created correctly or a script that would flip all inverted (black) normals in Metashape? It is seriously frustrating. I have tried to create normals in Cloudcompare but that is also all out of whack.

20

General / Re: Export Tiled Model - Cesium

« on: January 24, 2022, 02:46:02 PM »

I have the same issue, the cesium 3d tiles don't work and i don't know why. If i upload the obj to cesium, the converted 3d tiled works fine, but if i use the 3D tiled from metashape something is wrong. This is an issue as the storage is limited on cesium...

If you revert back to version 1.7.0 then the Cesium export works correctly since it defaults to the correct WGS 84 coordinate system and not the local coordinates that the later versions seem to default to on export.

It's a bit of a pain having to switch versions all the time but it is the only way I have found to get Cesium tiles working again.

21

General / Re: Export Tiled Model - Cesium

« on: January 14, 2022, 05:08:03 PM »

I want it to be in the correct coordinates system but when I go to export (since quite a few versions ago), it shows the coordinate system as 'Local Coordinates' and it is greyed out so we cannot change it to WGS84. It does not appear to default to that as when I export it, it is not where it should be. It has moved and when I pan, rotate or zoom in Cesium, the model vanishes.

My workflow involves importing a 3d model into a blank chunk and then converting that to 3D tiles and manually geolocating it in WGS84 with the basemap active.
As I say, this workflow used to work. Now I have to install an old version when I need to do this process.

22

General / Re: Export Tiled Model - Cesium

« on: January 14, 2022, 02:19:49 PM »

I have also noticed this and can only assume it is a bug as it ruins the exported models' position. This is also still greyed out in version 1.8

I have to go back quite a few versions to get one where the 3D tiles export works correctly (1.6.6 or 1.7 maybe).

23

General / Re: Keep Server jobs on Server quitting

« on: October 14, 2021, 02:14:19 PM »

Thanks for the reply Alexey. This does not solve our problem though

Once again we have lost over 4 days of a job that was processing due to windows automatically restarting the server PC while it was processing. This PC is configured to not automatically restart when a user is logged on but Windows seems to override this for certain updates.

Is there no way for the server jobs and progress to be automatically saved so that if the computer does crash or restart, we don't lose days and days of processing?
It is extremely frustrating and costing a lot of time and money for us to have to restart jobs after days of processing is lost.

24

General / Re: Keep Server jobs on Server quitting

« on: September 09, 2021, 01:21:26 AM »

OK, I'm guessing that this is not possible to do with the way the server works as nobody seems to have a solution for it.

25

General / Keep Server jobs on Server quitting

« on: August 11, 2021, 10:18:38 AM »

I there any way for the Metashaoe server to keep the progress and list of jobs it is working on when it quits/closes?

Every time our PC that the server is running on has to restart, or if it crashes, we lose all the progress of the network processing and all jobs have to be re-submitted from the start again.
This has lost days of work sometimes.

All other server/node setups that I have used in the past have a folder where the network jobs are stored and they will just pick up processing from where they left off If there is any hardware faults/crashes etc.