1
General / Re: Error - Too small max compute workgroup
« on: May 13, 2025, 12:54:06 PM »
Hi Olihar,
I am now. 2.2.1
I am now. 2.2.1
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.
2
General / Re: 2.2.1 issue? - Sparse Point Cloud not showing in Model view port
« on: May 13, 2025, 12:52:24 PM »
Hi Olihar,
Thanks for replying.
Nothing shows up.
Thanks for replying.
Nothing shows up.
3
General / Re: Error - Too small max compute workgroup
« on: May 10, 2025, 04:00:59 AM »
Hi Alexey,
Thanks for looking at this problem. But I seem to have fixed it.
Because my client was waiting on the data my first work around was to tick the "split into blocks" option when creating a model. This worked, I didn't get the error.
But my proper solution was to update all NVidia drivers. The fixed the problem and I was also able to create the model as a single entity.
Thanks again
Ben
P.S. if you could have a look at the other issue I posted yesterday that would be great
[size=78%]- [/size]Topic: 2.2.1 issue? - Sparse Point Cloud not showing in Model view port
Snapshot of my GPU preferences, attached as requested
Thanks for looking at this problem. But I seem to have fixed it.
Because my client was waiting on the data my first work around was to tick the "split into blocks" option when creating a model. This worked, I didn't get the error.
But my proper solution was to update all NVidia drivers. The fixed the problem and I was also able to create the model as a single entity.
Thanks again
Ben
P.S. if you could have a look at the other issue I posted yesterday that would be great
[size=78%]- [/size]Topic: 2.2.1 issue? - Sparse Point Cloud not showing in Model view port Snapshot of my GPU preferences, attached as requested
4
General / 2.2.1 issue? - Sparse Point Cloud not showing in Model view port
« on: May 09, 2025, 04:30:29 PM »
Hi,
I have replicated this issue twice now using 2.2.1. I have not seen it in previous versions.
I have create a sparse cloud from 6500 images. The sparse cloud has about 8.4 million tie points. I go to do a gradual selection clean (now called Clean Tie Point in 2.2.1). After selecting 200,000 points using the Project accuracy slider and deleting them, then running optimization, the sparse cloud disappears from the viewer. The tie point counter, in the bottom left of the screen, is showing me the correct number of points (8.1 million) but there is nothing on the screen. I have tried resetting the view, resetting the region but nothing shows the tie points. And obviously the tie point button is clicked to show tie points on.
Luckily i had duplicated the chunk before I started the gradual selection clean. The sparse cloud shows up perfectly in the first chunk
Would any one have any suggestions?
Regards
Ben
I have replicated this issue twice now using 2.2.1. I have not seen it in previous versions.
I have create a sparse cloud from 6500 images. The sparse cloud has about 8.4 million tie points. I go to do a gradual selection clean (now called Clean Tie Point in 2.2.1). After selecting 200,000 points using the Project accuracy slider and deleting them, then running optimization, the sparse cloud disappears from the viewer. The tie point counter, in the bottom left of the screen, is showing me the correct number of points (8.1 million) but there is nothing on the screen. I have tried resetting the view, resetting the region but nothing shows the tie points. And obviously the tie point button is clicked to show tie points on.
Luckily i had duplicated the chunk before I started the gradual selection clean. The sparse cloud shows up perfectly in the first chunk
Would any one have any suggestions?
Regards
Ben
5
Feature Requests / Smart Marker detections by Surveyed GCP Location
« on: May 09, 2025, 07:23:25 AM »
Hi,
Could you please consider adding this option to marker detection -
1. a csv or txt file (import reference command) is used to import the GCP locations.
2. Detect Marker command is run but with the option of only searching images within a nominated radius of the imported markers. The user would nominate the radius e,g 20 metres
Using this suggestion Metashape will only search images in the areas of the imported GCPs, which should speed up the process. Instead of every image or selected images
I have a project of 350 hectare area - 6500 images and 32 non-coded markers. I think if my suggestion was implemented the process of detecting markers would be very quick.
Thanks for reading
Kind Regards
Ben
Could you please consider adding this option to marker detection -
1. a csv or txt file (import reference command) is used to import the GCP locations.
2. Detect Marker command is run but with the option of only searching images within a nominated radius of the imported markers. The user would nominate the radius e,g 20 metres
Using this suggestion Metashape will only search images in the areas of the imported GCPs, which should speed up the process. Instead of every image or selected images
I have a project of 350 hectare area - 6500 images and 32 non-coded markers. I think if my suggestion was implemented the process of detecting markers would be very quick.
Thanks for reading
Kind Regards
Ben
6
Feature Requests / Re: Selection Toolset -> Add Polygon Tool
« on: May 09, 2025, 07:11:20 AM »
+1 - this is really needed
7
General / Error - Too small max compute workgroup
« on: May 08, 2025, 02:01:42 PM »
Hi,
When starting the "Build Model" command I get an error which stops the command. The problem is listed in the log file -
2025-05-08 20:45:23 Vulkan device Intel(R) UHD Graphics 770 skipped: too small max compute workgroup count 65536x65536x65536 (at least 524288x16384x16384 required)
2025-05-08 20:45:23 Found 2 GPUs in 0.016 sec (CUDA: 0 sec, OpenCL: 0 sec, Vulkan: 0.016 sec)
This job has only around 2000 photos. I have processed jobs many times bigger than that on this computer.
Could someone please tell me why this would happen - "too small max compute workgroup count 65536x65536x65536 (at least 524288x16384x16384 required) "
I am using professional version - 2.2.0 build 19890
Thanks
Ben
When starting the "Build Model" command I get an error which stops the command. The problem is listed in the log file -
2025-05-08 20:45:23 Vulkan device Intel(R) UHD Graphics 770 skipped: too small max compute workgroup count 65536x65536x65536 (at least 524288x16384x16384 required)
2025-05-08 20:45:23 Found 2 GPUs in 0.016 sec (CUDA: 0 sec, OpenCL: 0 sec, Vulkan: 0.016 sec)
This job has only around 2000 photos. I have processed jobs many times bigger than that on this computer.
Could someone please tell me why this would happen - "too small max compute workgroup count 65536x65536x65536 (at least 524288x16384x16384 required) "
I am using professional version - 2.2.0 build 19890
Thanks
Ben
9
General / Shifting Data from Assumed Coordinates to somewhere else
« on: November 15, 2024, 05:29:01 AM »
Hi All,
I have spent alot of time trying to work this specific requirement out, so thought I would share in case it may help others. I'm sure alot of MS users reading this will think this is obvious or have a better way. I would be very happy to hear from those users.
Problem - how do you shift a MS job from assumed coordinates (XYZ) to a either somewhere else in space or to a published coordinate system (E,N,ALT or lat,long,heigh). This solution is for when you have markers in your job that you can calculate the shift (XYZ and rotation) required to move them to required new coordinates.
By Assumed Coordinates, I mean where you have no exif location data and have just nominated a point in your MS job at any coordinate e.g. Point 1 has XYZ of 1000.000,2000.000,50.000. This example of "Assumed" coordinates could also be called "Local Coordinates" in metashape.
I have a project where I have captured the underside of a bridge with a handheld camera. These photos have no exif location data. This is a visual inspection job so actual true location and true dimensions are not critical but it would be handy if the job was roughly in a known CRS so I need to move it.
I did have a survey staff (3metres long) in some of the photos to act as a scale bar. That scaled the project to roughly actually size.
After aligning the photos, the sparse cloud is created. I rotated the sparse cloud using "rotate object" to put the z axis roughly "up" and also roughly rotated the sparse cloud alignment to match the real world bridge direction. I only did this so it visually looked close to the real world bridge look, making it easier to work on the data. During the photo alignment I had needed to create some markers to help it align. In the reference pane I gave one marker an assumed "source" coordinate ( x=40 y =25, z=10) by writing in the Reference / "View Source" / marker XYZ . After ticking one marker running the "optimize cameras" that meant all my other markers now had "estimated" x,y,z values - These are shown after clicking the Reference / "View Estimated" button. I copied (via click,drag,hightlight,copy) all the marker's "estimated" XYZ values and pasted those values into a Excel spreadsheet and saved as a csv file. I then imported them into MS using the "Import Reference" function. So now a have a project on "Local Co-ordinates" with all markers having "Source" values. I created two additional markers at each end of my bridge. I exported all the marker values to a csv.
I then used a external website that has a map viewer and shows location values for the cursor when over the map. The web site allows the user to extract location values in many different Coordinate Systems e.g. WGS 84, MGA2020 etc. From this I could get two very rough MGA2020 coordinates for either end of my bridge (at similar locations to the additional points I created in Metashape). I used some survey software to rotate and shift all my markers from assumed coordinate to MGA2020 based on these two common points. I exported out the MGA2020 coordinates of all markers from the survey software to a csv.
I then -
10. Using the "Import Reference" command - Re-imported markers (using the new csv - When the "Import csv" dialogue box opens, if needed, change the "Coordinate System" from Local Coordinates to the defined CRS you need. In the example I have attached I am going from Local Coordinates to MGA 2020 (EPSG 7856), click OK and import the data. This updated all my source marker values to MGA2020 values
11. Under the Reference Settings the "Coordinate System" should now be showing the CRS you want (not Local Coordinates)
12. Tick all your markers on and click " Update Transform"
13. In the Reference Tab / "View Source" list - your markers should have the correct coords and labels (e.g. E,N,Altitude or Lat,Long not XYZ)
14. The data should have moved. Also click View Menu/ Reset View to see your data.
15. If you get the error message" Error- vertical datum outside tolerance" you have a marker or markers that did not update and still on their original coords. Either delete or update these.
Notes
20. For Step 10 - if you are just moving your data from a "Assumed" CS to another "Assumed" CS to can just leave the "Coordinate System" as "Local Coordinates"
21. Obviously this method could be adopted if you have "accurate" marker values in both local and CRS. You would not have to use external software and resources.
I hope this may help someone with the same need.
Kind Regards,
Ben
I have spent alot of time trying to work this specific requirement out, so thought I would share in case it may help others. I'm sure alot of MS users reading this will think this is obvious or have a better way. I would be very happy to hear from those users.
Problem - how do you shift a MS job from assumed coordinates (XYZ) to a either somewhere else in space or to a published coordinate system (E,N,ALT or lat,long,heigh). This solution is for when you have markers in your job that you can calculate the shift (XYZ and rotation) required to move them to required new coordinates.
By Assumed Coordinates, I mean where you have no exif location data and have just nominated a point in your MS job at any coordinate e.g. Point 1 has XYZ of 1000.000,2000.000,50.000. This example of "Assumed" coordinates could also be called "Local Coordinates" in metashape.
I have a project where I have captured the underside of a bridge with a handheld camera. These photos have no exif location data. This is a visual inspection job so actual true location and true dimensions are not critical but it would be handy if the job was roughly in a known CRS so I need to move it.
I did have a survey staff (3metres long) in some of the photos to act as a scale bar. That scaled the project to roughly actually size.
After aligning the photos, the sparse cloud is created. I rotated the sparse cloud using "rotate object" to put the z axis roughly "up" and also roughly rotated the sparse cloud alignment to match the real world bridge direction. I only did this so it visually looked close to the real world bridge look, making it easier to work on the data. During the photo alignment I had needed to create some markers to help it align. In the reference pane I gave one marker an assumed "source" coordinate ( x=40 y =25, z=10) by writing in the Reference / "View Source" / marker XYZ . After ticking one marker running the "optimize cameras" that meant all my other markers now had "estimated" x,y,z values - These are shown after clicking the Reference / "View Estimated" button. I copied (via click,drag,hightlight,copy) all the marker's "estimated" XYZ values and pasted those values into a Excel spreadsheet and saved as a csv file. I then imported them into MS using the "Import Reference" function. So now a have a project on "Local Co-ordinates" with all markers having "Source" values. I created two additional markers at each end of my bridge. I exported all the marker values to a csv.
I then used a external website that has a map viewer and shows location values for the cursor when over the map. The web site allows the user to extract location values in many different Coordinate Systems e.g. WGS 84, MGA2020 etc. From this I could get two very rough MGA2020 coordinates for either end of my bridge (at similar locations to the additional points I created in Metashape). I used some survey software to rotate and shift all my markers from assumed coordinate to MGA2020 based on these two common points. I exported out the MGA2020 coordinates of all markers from the survey software to a csv.
I then -
10. Using the "Import Reference" command - Re-imported markers (using the new csv - When the "Import csv" dialogue box opens, if needed, change the "Coordinate System" from Local Coordinates to the defined CRS you need. In the example I have attached I am going from Local Coordinates to MGA 2020 (EPSG 7856), click OK and import the data. This updated all my source marker values to MGA2020 values
11. Under the Reference Settings the "Coordinate System" should now be showing the CRS you want (not Local Coordinates)
12. Tick all your markers on and click " Update Transform"
13. In the Reference Tab / "View Source" list - your markers should have the correct coords and labels (e.g. E,N,Altitude or Lat,Long not XYZ)
14. The data should have moved. Also click View Menu/ Reset View to see your data.
15. If you get the error message" Error- vertical datum outside tolerance" you have a marker or markers that did not update and still on their original coords. Either delete or update these.
Notes
20. For Step 10 - if you are just moving your data from a "Assumed" CS to another "Assumed" CS to can just leave the "Coordinate System" as "Local Coordinates"
21. Obviously this method could be adopted if you have "accurate" marker values in both local and CRS. You would not have to use external software and resources.
I hope this may help someone with the same need.
Kind Regards,
Ben
10
General / Re: Local to projected coordinate system of point cloud
« on: November 15, 2024, 05:11:58 AM »
Hi K,
I have just spent hours trying to do something similar (but different) and have got it to work. I thought I'd share it with you in the hope it may work for you. I'm sure a lot of MS users reading this will think this is obvious or have a better way. I would be very happy to hear from those users.
Your MS job has the Reference Settings set as "Local Co-ordinates" but you later find out your data (including Marker data) is actually on a known Coordinate System and you just want to change the Coordinate System setting of your job to the correct CRS in the Reference Settings. So, you are not actually shifting the data in space, only re-assigning the data to the correct CRS name in MS -
note - this assumes you have your markers in a coordinate file, e.g. csv or txt format -
1. Your MS job is currently defined as "local coordinates" in the Reference Settings.
2. Using the "Import Reference" command - Re-import your markers (using the same csv or txt file you originally used to import your markers) - When the "Import csv" dialogue box opens, change the "Coordinate System" from Local Coordinates to the defined CRS you need. In the example I have attached I am going from Local Coordinates to MGA 2020 (EPSG 7856), click OK and import the data.
3. Under the Reference Settings the "Coordinate System" should now be showing the CRS you want (not Local Coordinates). But in the Model viewer your data should not have moved.
4. In the Reference Tab / "View Source" list - your markers should have the correct Labels (e.g. E,N,Altitude or Lat,Long not XYZ)
5. The data should be in exactly the same place but, if needed, click the "Update Transform" button
Kind Regards,
Ben
I have just spent hours trying to do something similar (but different) and have got it to work. I thought I'd share it with you in the hope it may work for you. I'm sure a lot of MS users reading this will think this is obvious or have a better way. I would be very happy to hear from those users.
Your MS job has the Reference Settings set as "Local Co-ordinates" but you later find out your data (including Marker data) is actually on a known Coordinate System and you just want to change the Coordinate System setting of your job to the correct CRS in the Reference Settings. So, you are not actually shifting the data in space, only re-assigning the data to the correct CRS name in MS -
note - this assumes you have your markers in a coordinate file, e.g. csv or txt format -
1. Your MS job is currently defined as "local coordinates" in the Reference Settings.
2. Using the "Import Reference" command - Re-import your markers (using the same csv or txt file you originally used to import your markers) - When the "Import csv" dialogue box opens, change the "Coordinate System" from Local Coordinates to the defined CRS you need. In the example I have attached I am going from Local Coordinates to MGA 2020 (EPSG 7856), click OK and import the data.
3. Under the Reference Settings the "Coordinate System" should now be showing the CRS you want (not Local Coordinates). But in the Model viewer your data should not have moved.
4. In the Reference Tab / "View Source" list - your markers should have the correct Labels (e.g. E,N,Altitude or Lat,Long not XYZ)
5. The data should be in exactly the same place but, if needed, click the "Update Transform" button
Kind Regards,
Ben
11
General / Re: Local to projected coordinate system of point cloud
« on: November 14, 2024, 01:51:03 AM »
Hey K,
Did you ever find a solution to this?
Did you ever find a solution to this?
12
General / Re: Close Holes in Mesh - by selection
« on: November 04, 2024, 02:37:50 AM »
Hi Alexey and Tas,
I am finding the same result as you Tas - "I've tried it both with and without mesh filters applied. When I try to run the process without mesh filters, it quickly fails with an error that reads something like "Error - can't fill holes." I've tried this in v2.1.3
Kind Regards
Ben
I am finding the same result as you Tas - "I've tried it both with and without mesh filters applied. When I try to run the process without mesh filters, it quickly fails with an error that reads something like "Error - can't fill holes." I've tried this in v2.1.3
Kind Regards
Ben
13
Feature Requests / Be able to use FIND in camera list in Reference Tab using Wildcards
« on: November 02, 2024, 02:47:38 AM »
Hi,
I would like to suggest MS adds the functionality of FIND within the the Reference tab / Cameras list. This would work like any FIND function in programs like Notepad, Word, excel etc
I have projects with thousands of images (cameras). Sometimes i want to find an image or a several images within the list of thousands. I know the image name but instead of scrolling down the list, I just want to be able to chose "FIND" and enter the partial name of the image using wildcards e.g. *0170* for image name DJI_20241031120609_0170.JPG. MS would then automatically scroll down this list to the first occurrence of *0170*. if that wasn't the image I could then click "NEXT" and I would be taken to the next image satisfying the criteria in the list of images.
This would be a much faster way to find images that currently is possible.
I do know that in the Workspace Tab when right clicking on the Images Folder there is the option to "Select Items" and that allows wildcards. It selects the photos but it does scroll to them. But this functionality is not available for the Reference Tab.
Thanks for reading. I hope this suggest can be implemented in a future version
Kind regards,
Ben
I would like to suggest MS adds the functionality of FIND within the the Reference tab / Cameras list. This would work like any FIND function in programs like Notepad, Word, excel etc
I have projects with thousands of images (cameras). Sometimes i want to find an image or a several images within the list of thousands. I know the image name but instead of scrolling down the list, I just want to be able to chose "FIND" and enter the partial name of the image using wildcards e.g. *0170* for image name DJI_20241031120609_0170.JPG. MS would then automatically scroll down this list to the first occurrence of *0170*. if that wasn't the image I could then click "NEXT" and I would be taken to the next image satisfying the criteria in the list of images.
This would be a much faster way to find images that currently is possible.
I do know that in the Workspace Tab when right clicking on the Images Folder there is the option to "Select Items" and that allows wildcards. It selects the photos but it does scroll to them. But this functionality is not available for the Reference Tab.
Thanks for reading. I hope this suggest can be implemented in a future version
Kind regards,
Ben
14
General / Re: Misalignment between Laser Scan and Photogrammetry Point Cloud
« on: November 01, 2024, 05:07:12 AM »
Hi Tas,
Did you follow this methodology? - https://agisoft.freshdesk.com/support/solutions/articles/31000168474-terrestrial-laser-scans-processing-in-metashape-2-1
It explains how MS handles Scan alignment + Photos
Looks like photo misalignment in that area
Cheers
Ben
Did you follow this methodology? - https://agisoft.freshdesk.com/support/solutions/articles/31000168474-terrestrial-laser-scans-processing-in-metashape-2-1
It explains how MS handles Scan alignment + Photos
Looks like photo misalignment in that area
Cheers
Ben
15
General / Re: Detect Marker Issue or Tie Point Discrepancy issue?
« on: October 21, 2024, 03:57:54 AM »
Hi All,
I have had the same issue but with another project. Please see attached pdf.
Could anyone suggest why this is happening and give a possible solution?
Kind Regards
Ben
P.s. in my original post on the 12/10/24, the line "Marker 7 and Marker 11 are about 15cm apart." Should have said "Marker 6 and Marker 14 are about 15cm apart."
I have had the same issue but with another project. Please see attached pdf.
Could anyone suggest why this is happening and give a possible solution?
Kind Regards
Ben
P.s. in my original post on the 12/10/24, the line "Marker 7 and Marker 11 are about 15cm apart." Should have said "Marker 6 and Marker 14 are about 15cm apart."
