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.


Topics - Dieter

Pages: [1] 2
1
General / GPU GTX 3060 is low on memory at 12 GB
« on: February 23, 2024, 01:36:34 PM »
No matter what I try, Metashape doesn't manage to compute the mesh with high resolution in a project with photos and laser scans.

See error message at the end of the log:
2024-02-23 11:25:10 device NVIDIA GeForce RTX 3060 ignored because it has 11020/12287 MB available, but 11489 MB required.

What can I do?


Dieter

2
Bug Reports / Wrong Coordinates in Laserscan Export as E57
« on: February 06, 2024, 07:47:56 PM »
If I export a laser scan aligned in metashape as an e57 file, which coordinates are then output as the scan location coordinates of the laser scan?

The newly calculated values should then also be output in the E57 File.

At the moment, the height is always output as 0.


Dieter

3
Bug Reports / Crash with Metashape 2.02 and Windows 11
« on: September 09, 2023, 12:19:21 PM »
Hi, my System is Windows 11 with Metashape 2.02. I want to align 66 Scans and 6200 Fotos. With Cuda activated there is an error. Only with CPU its working.

See Error atached.

Any Hints?

4
Bug Reports / Masks for laserscans not working
« on: May 11, 2023, 03:11:35 PM »
If i mask out areas in a laserscan, it will not aply changes to the mesh i build. I work bis 2.02 beta.

Dieter

5
General / Referencing laserscans
« on: May 09, 2023, 11:00:37 AM »
What am I doing wrong?

I have a registration with GCP and aligned photos.
In addition, I read in a laser scan, set the scan's transformation to off, and align this scan over the photos.

Metashape finds identical points and aligns the scan to the photos, so far so good.

After this step I have 20 cm deviation in all GCP, my registration is no longer correct. I didn't tap a GCP in the scan, how can that be?


Dieter

6
General / Import coordinates for laserscans
« on: April 18, 2023, 11:53:26 AM »
Is there a way to import the coordinates for laser scans?
You can calculate everything well now, but in my opinion this possibility is missing.

Dieter

7
I want to build a cylindrical Orthomosaik with three markers. Axis is marker 1 to 2. Projection origin is marker 3.

After starting the procedure, a failure "Location of marker 1 is undefined." expires.


I´ve done this several times, why is there a failure? Version is 1.8.1 build 14671.


See screenshot!

8
General / TLS Laserscans - Registration incorrect
« on: March 04, 2022, 12:03:39 PM »
Dear Agisoft team, I have now tried the procedure with TLS scans and photos several times and each time I get a different result. There is now version 18, no one knows which script is correct or which one to use, no one knows exactly how I can add registered scans to an existing project without destroying the registration, all in all I can say for myself that the function "Reading in registered laser scans" DOES NOT WORK CORRECTLY.

I ask again to firmly integrate all these scripts into Metashape to make the whole thing a little more transparent.

There are now many entries here in the forum where almost all users say it doesn't work, how will the Agisoft team react to this?

For me and our office, I can say that we urgently need this function.

dieter

9
Bug Reports / Geoid heights and tiled model
« on: September 30, 2021, 12:42:37 PM »
In Metashape 1.74, when I work with a custom fixed height geoid and then export a tiled model and don't change the coordinate system, the output is ellipsoidal heights.

lg
Dieter

10
General / Import German Geoid Model into Metashape
« on: September 13, 2021, 07:33:12 PM »
I have now tried to import a geoid for 3 hours. Every time I get the message "vertical date out of range" when I convert data into the new format. I have original data from the German institute BKG for
the quasigeoid in Germany.

There are several formats in the ascii, trimble topcon, leica etc.

Despite the exact instructions in the freshdesk "https://agisoft.freshdesk.com/support/solutions/articles/31000148332-how-to-use-height-above-geoid- for-the-coordinate-system "
And yes, I called Metashape as admin and my project is within the geoid boundaries.

I can't get it to work,


It's just frustrating! Who can help and has done something like this before?


thanks
Dieter

11
General / Not enough memory on GPU
« on: August 31, 2021, 07:14:54 PM »
I want to texture and/or building tiled modell.

I always have this message in my console:


Estimated required video memory: XXXXX MB
Estimated device memory: total 4043 MB, used 65 MB, available 3437 MB
Cannot use GPU. Reason: Not enough memory on device


I always thought that metashape divides the model  according to the GPU?

Tested with GTX 1060 and GTX 970, my nvidia driver is 471.68 working on Metashabe 17.4

What can I do to calculate textures on the GPU?

Thanks

12
General / Heights in agisoft viewer
« on: April 14, 2021, 11:44:07 AM »
A question about the Agisoft viewer.

I have created a project with my own height system. It is the UTM coordinate system with DHHN2016 heights for Germany. When I output this project as a tiled model, the ellipsoid heights appear in the viewer, my DHHN2016 heights are gone. Is that what you intended?

And if so, how can I then output the project with the correct heights for me and the client in the DHHN2016 format?



Dieter

13
Bug Reports / Photoassignment Orthophoto is bad
« on: August 28, 2020, 11:03:30 AM »
Because I don't get an answer in the general forum, I'll post my request here again:


I would ask you to check the image assignment for the orthophotos again.

The optimal photo of the surface is not assigned, as can easily be seen from the attached example. Example 1 is the automatic Ortophoto, example 2 the post-processed version.

In this example, all photos had to be exchanged to get an acceptable surface.

I have often pointed out this problem without any change on the part of agisoft. I like to work with Agisoft a lot, but I have to exchange hundreds of photos for every project, which in the long run becomes too much for me and is unproductive for our office.

I am happy to help and offer my support.

Dieter



I may have found the solution.

The previous examples are cylindrical developments.

It looks like in this case the software determines the ranks of the images in exactly the opposite way.

I noticed this when I exchanged the pictures, Rank 1 means good for normal orthophotos, for my cylindrical developments it means bad.

That means the worst pictures are used for the orthophoto, very bad.

Dear Agisoft team, please check this !!


Dieter

14
General / Photoassignment Orthophoto is bad
« on: July 28, 2020, 10:23:10 AM »
I would ask you to check the image assignment for the orthophotos again.

The optimal photo of the surface is not assigned, as can easily be seen from the attached example. Example 1 is the automatic Ortophoto, example 2 the post-processed version.

In this example, all photos had to be exchanged to get an acceptable surface.

I have often pointed out this problem without any change on the part of agisoft. I like to work with Agisoft a lot, but I have to exchange hundreds of photos for every project, which in the long run becomes too much for me and is unproductive for our office.

I am happy to help and offer my support.

Dieter

15
Feature Requests / detailed orthofotos
« on: May 20, 2020, 09:34:50 AM »
Hi,

We very often process large orthophotos and are not always satisfied with the assignment of the images.

Please note the attached document, which shows a typical situation that often occurs.

Green is the object to be measured, blue is the individual photos taken, red is the direction of the orthophoto.

Metashape uses the images of "2" in the side areas because they are parallel to the direction of the orthophoto.

The photos from "1" would deliver much better results because they are closer to the object, have a vertical direction of exposure to the object and are therefore sharper than the photos from "2".

As a result, our office has a considerable additional effort to create "better" orthophotos from the orthophotos from Metashape. Hundreds of image areas are changed for better single shots.

As a solution, I could set priorities that the user could freely define. My priority list would then be:

1) Angle to the object (vertical recording direction if possible)

2) Distance to the object (photos as detailed as possible)

3) Fill the remaining areas with other photos that do not meet 1 and 2 to fill the areas.

Are there ways to do this or are there other solutions for "better" orthophotos?

Thanks
Dieter

Pages: [1] 2