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

Pages: [1] 2 3 ... 6
1
General / Re: Black point cloud
« on: April 21, 2026, 07:00:11 PM »
You might try to uncheck the Enable VBO support in the advanced tab of preferences.

Tom

2
Bug Reports / Re: Vertical datum out of range
« on: February 20, 2026, 08:37:45 PM »
I have attached screenshots and the log.

3
Bug Reports / Vertical datum out of range
« on: February 19, 2026, 01:30:33 AM »
I am trying to build an orthomosaic using the Model as the surface and am getting the Vertical datum out of range error

Using version 2.3.0 build 21954 on MacOS

I have a compound coordinate system set and have the appropriate geoid being used.

Tom

4
General / Re: Surface from polygon shape
« on: July 23, 2025, 08:19:29 PM »
Hello Alexey,

Thank You. Script works perfectly.

Tom

5
General / Re: Surface from polygon shape
« on: July 23, 2025, 02:19:00 AM »
Hello Alexey,

I thought and hoped it could be accomplished with a script but I don't see what method or function that I would use to create the mesh surface using the shape. Any code snippet that you could share would be most helpful.

Thanks,

Tom

6
General / Surface from polygon shape
« on: July 19, 2025, 08:46:14 PM »
If I select tie points and make a drawing plane then draw a polygon shape, can I turn that shape into a surface?

Any insight welcomed.

Tom

7
General / Re: Batch Export Point Cloud Vertical Datum out of range error
« on: February 14, 2025, 05:06:08 PM »
Hello Alexey,

The problem still exist with 2.2.1 pre-release

Tom

8
General / Re: Batch Export Point Cloud Vertical Datum out of range error
« on: February 13, 2025, 08:41:58 PM »
Another oddity that I found with version 2.2 build 19890 regarding Vertical Datum out of range error.

The vertical datum with geoid us_noaa_g2018u0.tif in this case is honored for everything until I try to create an orthomosaic using the Model as the surface AND try to transfer model texture. I then get the Vertical datum out of range error.

As I said, everything else seems to be fine.

Tom

9
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

10
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

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


12
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

13
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

14
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

15
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

Pages: [1] 2 3 ... 6