Messages

1

General / Re: Error increasing after inputting marker accuracy

« on: January 12, 2024, 02:59:38 AM »

Hi Megan

It appears to me that your error estimates for marker pixel error is probably too loose in 2022 and way too tight in 2023. 2022 marker pixel errors is over 1 pixel which isn’t good. 2023 shows marker pixel errors far far below 0.1 pixel which is way too tight. Is that perhaps a typo that you meant say 0.15 but put in 0.015? Such an error estimate will force any mis marking error into the control values.

Tom

2

General / Re: Calibrate Colors - restrict calibration to enabled photos

« on: November 10, 2023, 12:31:20 AM »

Color calibration tries to minimize the differences in photos that are analyzed.

When running the color calibration tool, the console shows how many images are being analyzed and only enabled images are analyzed. What happens after that is not real clear.

If you run color calibration with some images disabled, in the photos pane, right click on one of the enabled photos and choose Adjust Color Levels… You should see level percentages other than 100 for the bands.

Do the same thing to one of the disabled photos. You should see all bands with 100 percent.

Basically this means that photos that you DON’T want corrected, or changed, they can be disabled. I don’t think that is a very useful solution. It seems to me that it is more likely that one would like to have some photos corrected to better match the photos you don’t want changed or changed very little.

What I would love to see is the ability to assign weights to photos or groups of photos. If I could weight photos that have better color and exposure higher, and photos that need more correction lower, then I think color correction would be more useful.

Tom

3

General / Re: Switching local coordinates from meters to feet not working

« on: August 22, 2023, 12:48:02 AM »

You can go to Preferences->General, Units: and set to Coordinate system units. That will make the Reference pane display feet.

4

General / Re: Millimeter paper drawing to project on a mesh

« on: June 11, 2023, 05:02:11 PM »

Quite a few years ago, I documented several petroglyphs that had Mylar tracings done in years prior to photogrammetry captures. I laid out the Mylar tracings and photographed them from multiple perspectives and convergent angles so I could align the images and make a photogrammetric project of the tracing. I could then pick points on the actual petroglyph project at real world scale and pick the same feature in the tracing and call them “control points” to reference the drawing in real world coordinates. You need at least 4 points. A single scan of the drawing doesn’t work as well and also, perhaps the detail, or lack thereof on the drawing may make it difficult to find common points but that is up to you to determine. Perhaps this technique will work for you.

Tom

5

Agisoft Viewer / Re: How to import TLS files - Agisoft Viewer

« on: March 26, 2022, 11:03:57 PM »

Instead of File->Open use File->Add Layer

6

Agisoft Viewer / Re: Latest 1.8.0 Viewer - continuous renderer_qgl.cpp error

« on: January 11, 2022, 02:51:43 AM »

I am using an iMac running macOS Monterey version 12.1 with Radeon Pro 580 8 GB graphics

Not sure if I see separate driver version?

Tom

7

Agisoft Viewer / Latest 1.8.0 Viewer - continuous renderer_qgl.cpp error

« on: January 05, 2022, 11:26:36 PM »

2022-01-05 13:20:57 Agisoft Viewer Version: 1.8.0 build 13794 (64 bit)
2022-01-05 13:20:57 Platform: Mac OS
2022-01-05 13:20:57 CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (desktop)
2022-01-05 13:20:57 CPU family: 6 model: 158 signature: 906E9h
2022-01-05 13:20:57 RAM: 64.0 GB
2022-01-05 13:20:57 OpenGL Vendor: ATI Technologies Inc.
2022-01-05 13:20:57 OpenGL Renderer: AMD Radeon Pro 580 OpenGL Engine
2022-01-05 13:20:57 OpenGL Version: 2.1 ATI-4.7.101
2022-01-05 13:20:57 Maximum Texture Size: 16384
2022-01-05 13:20:57 Quad Buffered Stereo: not enabled
2022-01-05 13:20:57 ARB_vertex_buffer_object: supported
2022-01-05 13:20:57 ARB_texture_non_power_of_two: supported
2022-01-05 13:20:57 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:20:57 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:20:57 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:20:57 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:04 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:04 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286

These errors continue if my mouse is over the viewer window.

Tom

8

General / Re: Temporal comparison in an urban environment - best way to align two sets?

« on: October 03, 2021, 05:17:56 PM »

Delete isn't the right word - I removed them. Isn't disabling them essentially the same thing in terms of data? Though disabling allows me to reenable them later if I need to (which if all goes well I won't...)?
[/quote]

Removing photos is not the same as disabling them. Removing photos removes tie points and can affect the results of the alignment and optimization and will affect future products. The images should be disabled.

Tom

9

General / Re: Temporal comparison in an urban environment - best way to align two sets?

« on: October 02, 2021, 05:56:03 PM »

I don't think you should delete photos from the duplicated chunks. It would be much better to disable the photos you don't want to use in each of the duplicated chunks. Any products going forward will only use the enabled photos in each chunk.

Tom

10

General / Re: 1.6.5 align/optimize more accurate than 1.7.2 (aerial survey with PPK/RTK & GCP)

« on: July 08, 2021, 06:48:03 PM »

Andy,

Interesting.

Do you have differences between just GCP checkpoints - results just from the alignment and optimizations? Since the surfaces from depth maps is a different process, as I understand it, from 1.6.5 and 1.7.x I am wondering if the difference is because of the DEMs and how they are created.

Tom

11

General / Re: Agisoft Metashape 1.7.0 pre-release

« on: December 18, 2020, 06:47:09 PM »

Hello Alexey,

I ran a couple of tests on smaller projects and the results are very good with build 11637. The resulting mesh is superior to any I have seen in previous versions.

It is interesting that the depth maps look very different than previous versions but when I choose Export depth, the exported images look basically identical. Not sure what that means, just curious.

I am running a much more complex project now will report any issues, but I am not expecting any.

Excellent progress!

Tom

12

General / Re: Agisoft Metashape 1.7.0 pre-release

« on: December 04, 2020, 01:37:50 AM »

1.7.0 11539

I built a mesh on a project with 371 photos and only had 10 depth maps produced. I then tried a smaller project with only 10 photos and ended up with only 1 depth map.

I reran the 10 photo project using 1.6.5 just to be sure, and have 10 good depth maps. I tried 1.7.0 on medium and on high with the same result - 1 depth map.

My computer

macOS  11.0.1
iMac (Retina 5K, 27-inch, 2017)
4.2 GHz Quad-Core Intel Core i7
64 GB 2400 MHz DDR4
Radeon Pro 580 8 GB

Tom

13

General / GPU tweak

« on: September 29, 2020, 09:27:27 PM »

I am using an iMac with a AMD Radeon Pro 580 with 8 GB. When creating some complex meshes I get the console message

device AMD Radeon Pro 580 Compute Engine ignored because it has 2048 MB limit on allocations, but 2580 MB allocation required

Is there a tweak that can be set to allow more memory to be allocated or is it just a limitation of the system?

Thanks for any advice

Tom

14

General / Re: Agisoft Metashape 1.6.3 pre-release

« on: May 20, 2020, 01:06:27 AM »

Hello Tom,

The signature of Mac OS packages should be fixed in Metashape 1.6.3 build 10638. Can you please try the updated version?

Hello Dmitry,

Everything works now as expected. Thank you.

Tom

15

General / Re: Agisoft Metashape 1.6.3 pre-release

« on: May 17, 2020, 06:07:33 PM »

Hello Alexey,

I have done so in the past but in the recent past, that has actually caused the issue so no, I did not do so with 1.6.3.

I have tried rebooting and a few other things and finally tried using the terminal command "xattr -cr /Applications/MetaBeta/MetashapePro.app" and that has worked.

I am not sure I want to have to continue to do so, but perhaps it helps troubleshoot what may be going on.

Tom