Messages

1

General / Re: Orthomosaik in greyscale

« on: September 06, 2024, 06:40:52 AM »

Metascape takes the output channels from the input with the fewest channels at least for texture and vertex coloring. So you need to disable all single-channel input  (scans and black-and-white panoramas) before building texture or colorize vertices. I'm not totally sure it the same applies also for the orthomosaic... I would just duplicate the chunk and remove any source data with just 1 channel.

Regards,
Geobit

2

Feature Requests / Re: Some suggestions for ergonomic changes

« on: July 16, 2024, 02:47:43 AM »

About decimals. This has to do with windows regional settings for numbers and decimal format. You can modify win to your taste without turning Metashape into a mess.
I personally dislike . as thousand separator and , as decimal point. So every time I'm on a new computer I change thousands to blank and decimal point to a point . which sounds very consistent to me.
Personally, I would prescribe some pills to those who prefer to use comma instead of point, and yes, I would also directly send those who prefer units outside the international system to a mental health institution.
I suspect that more than one proud Englishman privately admits that this exotic system they call imperial is a blot on the normal development of life in the world (even on their own English lives). I don't understand why the hell we have mostly gladly adopted their language to understand each other, and they have never been able to adopt one of the most sound decisions that a sane part of humanity has ever made.
- Delete GCP or not to delete... I could agree it's annoying, it looks like the delete key has a more general scope than our desire sometimes. However, if you use the X button, the action will not kill your GCP but only selected key points, dense points or triangles, ignoring other selected items. If you want you can create a shortcut for the "kind" delete by assigning shift+del to delete just model selection, and it will do the same as the X button on the toolbar.

Loving Photoscan since very early years too.
Regards,

José Martínez
Geobit & Accupixel

3

General / Re: Control strip at lower altitude results in 10m shift

« on: May 21, 2024, 10:13:26 AM »

2. Per image accuracy override the general setting.
3. The error (m) given is an amalgamation of x/y/z, is there a way in Metashape to see the error per dimension?
errors per dimension are shown in the ref pane when you are in errors view mode.
There could be something wrong either in the processing method or in your source references. Otherwise it is hard to explain 10m

4

Feature Requests / Align chunks by laser scans

« on: April 30, 2024, 11:33:49 AM »

I think it would be useful and I'd love to see this added to the methods. If I have two chunks connected by a common laser scan or point cloud, it would be super easy and fast to use it as reference source for transforming one chunk to the other.
Cheers

GEOBIT

5

General / Re: Found oblique cameras without specified capture distance. Continue?

« on: February 17, 2024, 01:12:03 PM »

Hi Costas:
When Metashape finds oblique tilt angles in metadata, it can estimate overlap only when capture distance is entered in reference settings. In previous versions no warning mentioned this.
If object distance is empty, some overlaps would be wrongly estimated. See this drawing to understand.

6

General / Re: No option to create normal maps

« on: February 08, 2024, 12:50:08 PM »

Hi Sleis:
Normal maps are generally intended to attribute complexity to low poly meshes. Apply decimation to your current mesh to produce a lighter copy, and you will get the ability to build a normal map for it based on the high poly mesh.

Regards,
José Martínez CTO
Accupixel Ltd & Geobit Consulting SL
Photogrammetry training

7

General / Re: Import coordinates for laserscans

« on: January 28, 2024, 09:51:05 PM »

Sorry, but the patch does not work at all for me as it should. The reference scan is loaded and nothing changes, the scans continue looking up side down. Am I supposed to do anything to tell the group of scans and the linked images to adopt the transform inherited from the reference scan?

What am I doing wrong?

8

General / Re: Linear scan using video frames and RTK images instead of GCP's

« on: January 28, 2024, 07:40:57 PM »

Is there a way to increase the 'weight' of RTK images in this workflow?
Any advice greatly appreciated!

regards,
Wim

Hi Wim:
Maybe is worth to mention that the weight of camera locations can be set according to the quality of the RTK fix solution.
If your drone with RTK on board can write this tags to the images, then you must tell Metashape to read them from metadata or alternatively you can enter all manually by selecting all cameras on ref pane, right click and choose modify accuracy, then enter the estimated accuracy.
a single value is assigned to xyz
two values sepparated by / are assigned to xy/z
three values are assigned independently to all axis x/y/z
To tell Metashape to gather the values from metadata, goto tools/preferences the got advanced tab and make sure that "Load camera location accuracy from XMP meta data" is enabled.
If it was not enabled for your project, just re-read metadata by means of the button with a camera, (third from the left) to "Import Reference from EXIF"

José Martínez
Accupixel
https://accupixel.co.uk/courses/metashape-professional-edition-for-forensics-surveying/

9

General / Re: Dense cloud artifact

« on: January 09, 2024, 08:07:58 PM »

I can not see whatever you call an artifact, can you elaborate a bit more? (add a close-up, please)
The first question is why dense cloud and not a mesh directly after alignment?
Have you refined the alignment by any recursive cleanup method?

Regards

José Martínez
Accupixel Ltd

10

General / Re: Insta360 double Fisheye DNG's

« on: December 21, 2023, 10:30:30 PM »

Not sure with insta dng's but I've had some success with ricoh Theta and photoshop.
Import DNGfile, crop to the left fisheye half extent and save as jpg, then import again and crop to the right half to save as new jpg
just make sure the left and right cameras are always exported into different folders and you let Metashape know they are different cameras. Use the photos as multicamera or as single camera files, its up to you.
Regards
José Martínez
Geobit & Accupixel CTO
Metashape training providers

11

General / Re: How to make image orientations fixed before alignment ?

« on: December 21, 2023, 10:23:16 PM »

Hy Cyril
If you know camera positions you can import them as reference.
You say you also can have prior rotations with really high accuracy... that sounds good, but I think this is harder to achieve even for a robot, so my suggestion would be to set camera locations accuracy to a very tight value (for exampe 0.00001m) and let rotations accuracy set to say 1degree
that should be enough of a constraint and would provide enough freedom to estimate rotations and interior orientation during alignment and refinement wile your initial camera posioions would be leaft almost untouched.
But if you are 100% positive that your encoder-estimated locations and rotations have negligible error, you can import them and apply "quick layout" script. After that you can build the tie points and if you are right and your orientations are good, Metashape will create a sparse cloud without modifying your reference priors.

Regards,
José Martínez
Geobit & Accupixel CTO

12

General / Re: How to remove the "snow" at the edges of the point cloud

« on: December 21, 2023, 10:09:23 PM »

(Currently I am only interested in the point clouds, which I like very much from an estetically, and not the meshes. I hope that's all right.)

Hello rowild:
I just wanted to add that sometimes building a mesh and then sampling a dense cloud on the mesh leads to a much cleaner and pleasant dense cloud and it does not necessarily add processing time.
Workglow: align - build mesh from depth maps - build point cloud from mesh
Moreover, you gain the ability to choose the dense cloud density to your taste.

Regards
José Martínez
Geobit & Accupixel CTO

13

General / Re: improve quality of dem

« on: December 17, 2023, 12:13:37 AM »

Overall...yeah it's strange when you remove bad points from dense cloud and then you naturally expect that you'll get better mesh, or in this case DEM...but in fact you get same result.

Hi, jkova96. when I clean the dense cloud and build then a DEM from dense cloud, what I get is what I'd expect: a clean DEM.
Share some screenshots and let us see what is going wrong with yours.

14

Bug Reports / invisible boundary shapes

« on: December 01, 2023, 10:24:19 PM »

Dear Agisoft team.
Boundary shapes remain active in spite of the layer status. I wished to be able to keep different sets of boundaries stored in layers with different purposes, and thought I would be allowed to choose the active set of boundaries to produce desired deliverables with different extents according to the active layer while the remaining layers were disabled... but nope, it does not work. Boundary action override the layer status and the clipping was always the same. I think this is not the right behaviour.
Regards

Geobit

15

Bug Reports / Snaps...

« on: November 29, 2023, 02:56:08 AM »

Snap tool was eagerly welcome, but after a few years it's still terrible, one can hardly see what is snapping to the tiny red dot and the snapped feature is not highlighted at all. It is the subtlest snap feedback I have ever seen. It is truely hard to notice when not even totally invisible if one is trying to snap to some vertex under another feature. The two modes available are not enough (what you call axis snap, I would not call it a snap mode, ibut rather ortho drawing mode)

When we are editing a shape A and we drag a vertex that was created with a snap on another vertex of a shape B, they move together even if we are not necesarily wanting to edit both features. is there a way to prevent this behavior?  can we de-snap a node on a feature so it can be dragged alone?

I have reported by mail that snap isn't working at all during rectangle creation... the bug remains the same in latest stable release and so in the 2.1 beta. Please solve.

By the way if you give us a rectangle tool, please let us have persistent rectangles. Allow us to draw them rotated, let us modify height and width with a gizmo in the midpoint of each side, or let us drag two adjacent sides consistently orthogonal when we drag a corner.

Best regards.
Geobit & Accupixel