Messages

1

Feature Requests / Constraining lidar geometric tie point matching to spatial neighbourhood

« on: January 05, 2025, 01:36:08 AM »

Problem: The current method of registration of unordered point clouds works well for distinctive spaces, but is error prone due to high repetitiveness in projects with scans of multiple similar spaces.

Proposed solution: Many sources of point cloud data deliver the data pre-registered. It should be possible to constrain the geometric tie point matches to a spatial neighbourhood from the pre-registration. This would constrain the matching process greatly, both speeding it up immensily and preventing matches across for example multiple floors.

2

General / Re: Metashape in space, example with comet 67P Churyumov-Gerasimenko

« on: October 27, 2024, 10:12:16 PM »

Hi David,

Id just like to reach out and thank you sincerely for writing this up. Its really interesting. Keep up the good work, and please give us a heads up on the forum going forwards with your research.

3

Feature Requests / Re: Export COLMAP in standard

« on: September 11, 2024, 11:24:24 PM »

Hello! Great work with the export function!

Id like to chime in and agree with PLAN8 that exporting dense cloud instead of tie points would be really useful. The usecase is that we could then generate a really nice and dense point cloud, do all the usual cleaning, filter it somewhat, which would really increase coverage in areas which otherwise are almost empty.

4

General / Re: Can't change cursor depth height

« on: January 25, 2024, 03:50:21 PM »

Did you solve this? I cant change cursor depth either in 2.1.0, windows 11.

update: tried it on a mac using 2.0 as well. Cant get it working there either.


update 2: the beavhiour seems extremely flaky. I get it working by holding ctrl + shift + left mousebutton, although as soon as try drawing something it stops working after two vertices.

5

General / Re: Agisoft Metashape 2.1.0 pre-release

« on: November 21, 2023, 09:30:20 AM »

Ive been trying out the geometric matching with good results. Heres a few features which might improve it. I assume youre working on many of them already. Considering were treating the clouds as images in a sense (extract tie points for bundle adjust), they should be treated in a similar manner in the gui, for great simplicity when were used to Metashape with images.

- Allow multi-scanner rigs similar to multi-camera setups. Use case is for throwing together a few lidars for a poor mans laser scanner and joint optimizing their internal relation at the same time as were optimizing the large scene.
- Have some symbol for a laser scan, similar to cameras that shows up in model space.
- Allow us to use the matching graph to see the scan relations.
- Allow editing of the matching graph. Right click on link > Remove factor. Right click two or more selected scans > Add factor.
- Choose cloud markers. Right click in a scan and add marker, simple as that.
- View laser scan orientation data in reference.
- Distinguishing the optimization results from photograph tie points when right clicking tie points - show info. Right  now, its reported in same units/manner as photos.
- Allow estimated prior positions in reference, just as with images, with known offset.
- The number of strong points extracted seem fixed regardless of point cloud size or quality or number of allowed tie points. Allow more!

6

General / Re: Agisoft Metashape 2.1.0 pre-release

« on: October 10, 2023, 04:07:36 PM »

Hey Dmitry, can you elaborate somewhat on the algorithms of the geometric based alignment? Is it a traditional pairwise fine registration or is it some bundle adjustment co-aligning multiple clouds simultaneously?

7

Feature Requests / Re: COPC .laz support for exporting point cloud

« on: October 10, 2023, 09:44:35 AM »

Amazing. Just read the changelog. This will be a game changer for us. Keep up the good work!

8

General / Re: Agisoft Metashape 2.0.0 pre-release

« on: December 14, 2022, 12:24:53 AM »

I am noticing a significant slowdown between 1.8.4 and 2.0, latest version, as well. (Imac Prop, 3.2 GHz 8-Core Intel Xeon W, Radeon Pro Vega 56 8 GB, Montery). Alexey or RHenriques, do you mind sharing that small dataset so we have someting similar to test on? Alexey, is it the logs that would be of best help, or can we do something else to troubleshoot?

9

Feature Requests / COPC .laz support for exporting point cloud

« on: April 13, 2022, 12:17:28 PM »

There is a push in the open source community for a new, backwards-compatible way of formatting tiled .laz files called COPC. The result is a single laz file that can be streamed/has LOD etc etc, which previously were restricted to potree/entwine exports which consists of thousands of files. At the same time it can be opened using all the standard laz reading methods, as it is "just a laz", in a manner similar to a cloud optimized geotiff is "just a tiff".

If Metashape would add support for exporting point clouds directly this would be really beneficial, since this would significantly reduce the overhead of using/showing others the billion-points large point clouds we routinely produce.

QGIS will support simple drag-and-drop copc laz in 3.26, and potree 2.0 will support copc as well. PDAL supports reading/writing copc as of 2.4.0. I am not sure about Cloudcompare, but I hope it will support copc.

A couple of helpful links:
https://copc.io
https://pdal.io/stages/writers.copc.html
https://www.lutraconsulting.co.uk/crowdfunding/elevation-pointcloud-enhancements-qgis/

10

Feature Requests / Re: 360 Panorama alignment to world

« on: December 05, 2021, 11:44:53 AM »

The  1.8.0 build 13597 was released since my last post, with the excellent addition of "Added Build Panorama command with seamline editing support". This is great news! As panoramas are apparently being worked on at this moment, I would like to add a few more thoughts on how its usability could be improved.

Suggestion #2: Allow for precise angular alignment of a 360 using markers in an image with n projections = 1. Lets say you have a group of images marked as a station and nothing else in a chunk. The images are aligned, and the tie points appear as the classical spere. My suggestion is this: allow adding markers with known reference in a single image. Then the direction of that ray is known. Then add a few more markers with known coordinates, yielding more rays. Optimizing with multiple rays should lead to that the orientation of the spherical panorama should be pretty precise, as well as yielding some scaffolding to avoid drift.

Use case:  we have a drone pano shot above a city. Mark three or more house corners, and get their reference XY positions from a typical map service.  Optimize. Build Panorama. The direction that this resulting panorama looks in should now be in relation to the world, for example that the middle of the equirectangular image point straight north.

Suggestion #3: Assume that we have multiple previously created 360 images using the Build Panorama. These are loaded as single images into a chunk, and their projection set to spherical. Allow for a common alignment without calculatin tie points by simply marking common points. Then allow export with exif tags as suggested in #4.

Suggestion #4: Export the correct exif tags of the spherical image. Approximate the center of the spherical image from ingoing image coordinates and use it as exif coordinates. Do the same for yaw/pitch/roll.

Why is this, and my last suggested feature, useful? 360 images are increasingly used for VR/AR/BIM use cases. Being able to precisely align these panoramas to world, in an overfit manner, either by themselves or in combination with others, is critical for this use case. We can get a good enough approximation of the camera position using PPK or RTK, but the use case critically need a bit more robustness and precision in relating the image alignment to the world system.

11

Feature Requests / 360 Panorama alignment to world

« on: November 11, 2021, 05:10:42 PM »

The panoramic results from MS are great, but lacks automatic horizon alignment. Aligning the horizon has to be done manually, and as far as I can see, can only be done on on single-image chunks. The same holds for aligning images to north.

If, on the other hand, we use multiple camera stations that are aligned with eac hother and perhaps a few GCPS, then it it is not possible to rotate object as is suggested in the tutorial at https://agisoft.freshdesk.com/support/solutions/articles/31000148830. It is currently possible to align multiple camera stations with each other, and thus also with GCPs. Therefore, the exterior orientation of the panorama should be known. Yet, when I try to output the results, the panorama is randomly rotated.

I thus suggest the following feature. If the ingoing spherical panorama has a known exterior orientation, then allow us to export the panorama perfectly levelled and with the equirectangular center pointing exactly north. This would allow usage of Metashape for perfectly georeferenced 360 dataset generation.