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

Pages: [1] 2
1
General / Re: Agisoft Metashape 2.0.0 pre-release
« on: October 19, 2022, 06:00:05 PM »
Dear bassistas,
It would be helpful, if you can share the sample data (your E57 file).
If you are able to share the data, please send the download link to support@agisoft.com

Here is a link to a sample e57 file https://drive.google.com/file/d/1KXlUsAUTf8BV-qOzeN3-cm3G11Q7WFNA/view?usp=sharing
Please let me know if you are able to reproduce the problem.

2
General / Re: Agisoft Metashape 2.0.0 pre-release
« on: October 19, 2022, 11:28:28 AM »
Hello bassistas,

Do you use Import Depth Images or Import Point Cloud for E57 files? Also can you share the processing log related to the file import (enable Write Log to File option in the General Preferences tab and try to reproduce the issue)?


I'm using the import point cloud option for the E57 files. Here is my log file, I don't see any errors, it just crashes:

2022-10-18 18:29:52 ImportPointCloud: path = D:/Faro scene projects/arnaia scans 1-10-2022/Faro scene Gerovasiliou/e57 export/gerovasiliou_Gerovasiliou000.e57, format = PointCloudFormatE57, crs = Local Coordinates (m), shift = [0, 0, 0], precision = default, point neighbors = 28, use trajectory (origin)
2022-10-18 18:29:52 Working in temporary directory D:/temp//import_points.tmp.11
2022-10-18 18:29:52 Importing point cloud in memory. Save project in .psx format for big file import.
2022-10-18 18:29:52 Importing point cloud...
2022-10-18 18:29:53 Analyzing points...
2022-10-18 18:29:53 processing 68983239 points...
2022-10-18 18:30:45 Calculating normals...
2022-10-18 18:30:45 Required 25.9399 GB RAM for extended block
2022-10-18 18:30:45 Available: 80.6923 GB
2022-10-18 18:30:45 Using extended block
2022-10-18 18:30:45 Using 32 threads
2022-10-18 18:30:45 Expected max memory usage: 25.9399 GB
2022-10-18 18:31:17 computed normals in 32.536 sec

I just tried to export the laser scans in another format (pts) and now they are loading without any errors but it takes a lot of time to load as the files are double the size now.
So maybe there is a bug with the e57 format.
Now I'm stuck on the "reset current alignment" option which is not active (greyed out) and if I proceed with the alignment it doesn't align the photos with the scans.

3
General / Re: Agisoft Metashape 2.0.0 pre-release
« on: October 18, 2022, 06:44:07 PM »
Hello bassistas,

Do you use Import Depth Images or Import Point Cloud for E57 files? Also can you share the processing log related to the file import (enable Write Log to File option in the General Preferences tab and try to reproduce the issue)?


I'm using the import point cloud option for the E57 files. Here is my log file, I don't see any errors, it just crashes:

2022-10-18 18:29:52 ImportPointCloud: path = D:/Faro scene projects/arnaia scans 1-10-2022/Faro scene Gerovasiliou/e57 export/gerovasiliou_Gerovasiliou000.e57, format = PointCloudFormatE57, crs = Local Coordinates (m), shift = [0, 0, 0], precision = default, point neighbors = 28, use trajectory (origin)
2022-10-18 18:29:52 Working in temporary directory D:/temp//import_points.tmp.11
2022-10-18 18:29:52 Importing point cloud in memory. Save project in .psx format for big file import.
2022-10-18 18:29:52 Importing point cloud...
2022-10-18 18:29:53 Analyzing points...
2022-10-18 18:29:53 processing 68983239 points...
2022-10-18 18:30:45 Calculating normals...
2022-10-18 18:30:45 Required 25.9399 GB RAM for extended block
2022-10-18 18:30:45 Available: 80.6923 GB
2022-10-18 18:30:45 Using extended block
2022-10-18 18:30:45 Using 32 threads
2022-10-18 18:30:45 Expected max memory usage: 25.9399 GB
2022-10-18 18:31:17 computed normals in 32.536 sec

4
General / Re: Agisoft Metashape 2.0.0 pre-release
« on: October 17, 2022, 07:40:46 AM »
Hello, I just tried this pre-release version and when I try to load any e57 laser scan the program crashes and closes after some minutes of loading without any error. The e57 files are structured and they are exported from the Faro Scene.  Does anyone know why this happens?

5
General / Re: TLS Laserscans - Registration incorrect
« on: October 11, 2022, 08:25:17 PM »
You must define the tls as fixed.

To do this, click the checkboxes for position and rotation (only tls) before the camera orientation.

Where do I find these checkboxes? Also do I need to run the quicklayout script first?

6
General / Re: TLS Laserscans - Registration incorrect
« on: October 10, 2022, 09:44:02 PM »
Hello Dieter,

In 1.8.4 release (published yesterday) when you add pre-processed laser scans from TIFF files (all at once) they will be added as multi-camera system, but during the alignment the relative orientation of the sensors in the system will be preserved (just to not enable adjust rotation/location for the slave cameras in the Camera Calibration dialog).

This approach is an intermediate solution, as in future major Metashape updates the concept of the laser scans will be revised. But I hope that it could at least partially work for your needs.

I've tried this method and I get a successful alignment but the orientation of the model is wrong. How Can I keep the orientation of the laser scans? (rotation/location for the slave cameras is unchecked)

7
General / mesh generation extremely low cpu and gpu usage
« on: August 03, 2022, 05:44:24 PM »
Hi guys,
I'm trying to create a mesh from 50 laser scans and 2788 (50mpixel) photos but after the generation of the depth maps the CPU and GPU usage is dropping to almost 0-3% and only the disk usage activity hovers around 30-40mb/sec as you can see in this screenshot. If I leave it like that the estimated time starts to explode and shows 8 to 10 days or more which is extreme for such an amount of data and the hardware I use. Is this a metashape bug? I'm using the latest 1.8.4 build.

8
General / Re: overexposed textures problem
« on: May 16, 2022, 06:27:36 PM »
Also I just tried now to disable the 8bit jpeg photos and try to create textures again with just the grayscale 32bit laser scans and it still produces the "overexposed" effect. So it seems there is some kind of a bug unless there is an option to adjust this somewhere.

9
General / Re: overexposed textures problem
« on: May 16, 2022, 04:15:46 PM »
I expect just 8bit output. So is there a problem if you combine 8bit images with 32bit laser scans tiff images? Should I convert my 8bit jpegs also to 32bit in order to avoid this "overexposed" effect?

10
General / Re: overexposed textures problem
« on: May 16, 2022, 04:03:36 PM »
Hello bassistas,

What color range (bit depth) the input photos and laser scans have?

As for the blank spots, I would suggest to mask out no-data regions on the images related to the laser scans prior to the texture generation stage.

Hello, the jpegs are 8bit and the grayscale laser scans are 32bit. Could this be the problem? and what can I do?

I also tried to mask out the no-data regions from the laser scans and it solved the black hole issue but as this black area has the same height in the lower part of the image in all of my laser scans is it possible to mask out this automatically from all the scans with a script rather than doing it by hand for every single scan?

regards

11
General / overexposed textures problem
« on: May 16, 2022, 01:26:52 AM »
Does anyone know why I'm getting such overexposed textures when I have grayscale laser scans imported in my project? If I disable the laser scans and create the texture with just the jpeg photos the texture is ok.
Also even if I import coloured laser scans I still get this black hole from each scan position which should not be there as there is texture information to cover that from the jpeg photos.

12
General / Re: Import Laserscan data -registration lost
« on: February 22, 2022, 09:50:19 AM »
My approach:

1) Import scans
2) Quick layout script
3) Import photos
4) mark only the scans as reference with an accuracy of 0.001 meters
5) allign scans and photos

Tie points are determined in the scans and the photos and compared with each other. The coordinates of the scans are held as a reference system.

Dieter

I had some success with this workflow but in the case I already have a project with imported laser scans and photos with markers attached, if I disable all the photos and leave just the laser scans enabled after the execution of the quick layout script , I go to Tools-> Tie points -> build point cloud and it messes up the position of the scans for some reason. It brings all the scans to the same center like a ball.
If I create a new project and add just the scans first then this is working as it should but how can I make it work on an existing project in which I have more than 150 markers already placed on photos and laser scans and is a pain to place all of them from the begining?

13
General / orthographic projection
« on: February 17, 2022, 03:18:51 AM »
Hi guys, is there any way to create orthographic projections with the use of a clipping box in metashape as in other softwares like Faro Scene? I am working on a big project with a lot of buildings and I want to create an orthographic projection/section along the road but it's very difficult to do this with markers, not all building facades are parallel to the road and I just want to do a section in the middle of the road exactly. If there is a way with the clipping box this would make the process easy. Also if any other software that can do this by importing the metashape model please let me know.
thanks

14
General / Re: Change images names after Align photos
« on: February 12, 2022, 05:17:22 AM »
THis one should also update the image paths:
Code: [Select]
import PhotoScan

chunk = PhotoScan.app.document.chunk

string = PhotoScan.app.getString("Input prefix to be added to the selected camera labels:")
index = PhotoScan.app.getInt("Input starting index:")

for camera in chunk.cameras:
if camera.selected:
if camera.label[-4] == ".":
camera.label = "_".join([string,"{:04d}".format(index)]) + camera.label[-4:]
else:
camera.label = "_".join([string,"{:04d}".format(index)])
camera.photo.path = camera.photo.path.rsplit("/",1)[0] + "/" + camera.label
index += 1

print("Script finished")

Hello,
I just tried this script and it renamed successfully all my photos but it does remove also the jpeg extension from the file names. Can anyone fix this problem on the script? thanks

15
General / Re: Import Laserscan data -registration lost
« on: January 05, 2022, 10:44:09 AM »
Hello Bassistas,

running the quick layout scrit will assign Estimated EO from the source values but not generate tie points. So to generate the tie points you should use Tools > Tie Points > Build Poind Cloud command (assuring that you set Keep Key Points option in Preferences settings). Then you can import photos and do alignment in incremental fashion. However, if you wnt to keep the Laser scan registration, give them a very high accuracy in m and degrees....

The other alternative is to measure a few well identifiables features in the laser scans, and use these feature points as GCPs to align the images in separate chunk as specified by Dieter...then merge chunks...

Hope this helpful,

Thank you, I'll give it a try, but what do you mean by "give them a very high accuracy in m and degrees"? Is there any setting for that?
I also tried to follow this tutorial I found here https://agisoft.freshdesk.com/support/solutions/articles/31000159101-terrestrial-laser-scanning-data-processing which at the bottom it says:
"If the project contains also the common digital images to be aligned, it is recommended to align such image set first and then load the TLS data to the same chunk and run the mentioned script. Note that the digital images alignment should be referenced in the same coordinate space as laser scanning data in order to be properly processed together."
But how this can work if you try to import registered scans on top of already aligned photos that are probably out of scale already? In my case a drone like the standard phantom 4 pro without RTK




Pages: [1] 2