1
Feature Requests / Re: Select mesh by shapes
« on: March 08, 2025, 03:49:43 AM »
+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 / 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
3
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
4
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?
5
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
6
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
7
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
8
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."
9
General / Re: Tie Point Misalignment
« on: October 16, 2024, 12:24:44 AM »
Hi DSmapping,
What verison of Metashape are you using? This is the third alignment issue posted recently.
One post was mine (https://www.agisoft.com/forum/index.php?topic=16791.0). I'm using MS Pro v2.1.3
The other post was https://www.agisoft.com/forum/index.php?topic=16788.0
Just wondering if you are using MS Pro v2.1.3 and maybe there is an issue with it?
Cheers
Ben
What verison of Metashape are you using? This is the third alignment issue posted recently.
One post was mine (https://www.agisoft.com/forum/index.php?topic=16791.0). I'm using MS Pro v2.1.3
The other post was https://www.agisoft.com/forum/index.php?topic=16788.0
Just wondering if you are using MS Pro v2.1.3 and maybe there is an issue with it?
Cheers
Ben
10
General / Detect Marker Issue or Tie Point Discrepancy issue?
« on: October 12, 2024, 11:10:06 AM »
Hi All,
I'm using MS Pro v2.1.3.
I have carried out a UAV flight with a DJI M300 and P1 camera of a pedestrian foot bridge. I have flown nadir and oblique flights and also captured images with a Canon hand held camera. Prior to the flight we placed many black and white targets on the bridge.
After aligning the images using highest accuracy setting and then running the detect targets command, Metashape has picked the centre of many targets correctly. Metashape allocated Marker numbers for those targets. I have noticed that Marker No 6 has been correctly identified (center of target correctly picked) in 36 images. I also notice that Marker No 14 has been correctly identified in 13 images. The problem is the target is the same target! Marker 7 and Marker 11 are about 15cm apart.
The images Metashape has picked the centre for Marker 6 are different to the images Metashape has picked the centre of Marker 14. So for Marker 6, the marker is centered on the target in its images. And the Marker 14, the marker is centered on the target in its images. How can this be?
In the Reference Tab Markers list the difference is shown "View Estimated" Table -
point 14 355681.7410382535 6308320.882072767 3.6456287776534353 13
point 6 355681.8124383928 6308320.808663793 3.7618934840380938 36
Does this mean the photos have not aligned correctly and Metashape thinks there a two targets in that area even though there is only one target there? The detect marker settings were "Tolerance" = 1 and " Maximum Residual (pix)" = 5.
Does this also mean there is Tie Point Discrepancy in the sparse cloud in that area? If that is the case, I would have never have found this if I didn't have a target there. How could I have identify this issue with no target? It would also suggest there could be issues in other areas but I would not know until I have created a model or point cloud and could see the issue.
Please see attachment showing the issue
Any help appreciated
Kind Regards
Ben
I'm using MS Pro v2.1.3.
I have carried out a UAV flight with a DJI M300 and P1 camera of a pedestrian foot bridge. I have flown nadir and oblique flights and also captured images with a Canon hand held camera. Prior to the flight we placed many black and white targets on the bridge.
After aligning the images using highest accuracy setting and then running the detect targets command, Metashape has picked the centre of many targets correctly. Metashape allocated Marker numbers for those targets. I have noticed that Marker No 6 has been correctly identified (center of target correctly picked) in 36 images. I also notice that Marker No 14 has been correctly identified in 13 images. The problem is the target is the same target! Marker 7 and Marker 11 are about 15cm apart.
The images Metashape has picked the centre for Marker 6 are different to the images Metashape has picked the centre of Marker 14. So for Marker 6, the marker is centered on the target in its images. And the Marker 14, the marker is centered on the target in its images. How can this be?
In the Reference Tab Markers list the difference is shown "View Estimated" Table -
point 14 355681.7410382535 6308320.882072767 3.6456287776534353 13
point 6 355681.8124383928 6308320.808663793 3.7618934840380938 36
Does this mean the photos have not aligned correctly and Metashape thinks there a two targets in that area even though there is only one target there? The detect marker settings were "Tolerance" = 1 and " Maximum Residual (pix)" = 5.
Does this also mean there is Tie Point Discrepancy in the sparse cloud in that area? If that is the case, I would have never have found this if I didn't have a target there. How could I have identify this issue with no target? It would also suggest there could be issues in other areas but I would not know until I have created a model or point cloud and could see the issue.
Please see attachment showing the issue
Any help appreciated
Kind Regards
Ben
11
General / Issue with "automatically placed" blue flag markers
« on: September 29, 2024, 09:15:50 AM »
Hi All,
I'm using the latest version of Metashape Pro (v2.1.3) for mainly processing UAV M300 / Zenmuse P1 or Phantom 4 pro data. This issue has arisen when flight subject was a Building.
I aligned the photos with no problem. From 490 images the average cammera error results were - X Err (m) 0.004, Y Err (m) 0.004, Z Err (m) 0.013
After the initial photo alignment, I had to add some more photos and needed to manually pin some targets (these are green flagged) in the photos to get these to align. As i pinned the same marker, in different photos, Metashape started to create Blue flag markers (as expected). The issue is - these blue flag marks are nowhere near the actual marker in the photo. Metashape should be predicting very close to the correct position but it is not. They are metres out of location,
What is strange is if I delete the projections of a blue flag marker, a new grey marker is automatically created, but it is automatically created exactly over the target in the photo. As soon as I pin that grey marker, turning it green, Metashape goes and creates more incorrect blue markers in other photos . I then have to delete those blue markers (I use python code for this) and keep pinning the gray markers.
Also, you can see the marker error (pix) get worse when there are blue flags for that marker. As soon as I delete the blue flags the marker error (pix) is good again.
I have now seen this in two projects.
Would anyone have a suggestion on what is going wrong. Could it a bug in the new version?
I am using the following python code delete all the blue flags in the project. It works very well.
It was found here - https://www.agisoft.com/forum/index.php?topic=10969.0
import Metashape
chunk = Metashape.app.document.chunk
for marker in chunk.markers:
for camera in list(marker.projections.keys()):
if not marker.projections[camera].pinned:
marker.projections[camera] = None
Any help appreciated
Regards
Ben
I'm using the latest version of Metashape Pro (v2.1.3) for mainly processing UAV M300 / Zenmuse P1 or Phantom 4 pro data. This issue has arisen when flight subject was a Building.
I aligned the photos with no problem. From 490 images the average cammera error results were - X Err (m) 0.004, Y Err (m) 0.004, Z Err (m) 0.013
After the initial photo alignment, I had to add some more photos and needed to manually pin some targets (these are green flagged) in the photos to get these to align. As i pinned the same marker, in different photos, Metashape started to create Blue flag markers (as expected). The issue is - these blue flag marks are nowhere near the actual marker in the photo. Metashape should be predicting very close to the correct position but it is not. They are metres out of location,
What is strange is if I delete the projections of a blue flag marker, a new grey marker is automatically created, but it is automatically created exactly over the target in the photo. As soon as I pin that grey marker, turning it green, Metashape goes and creates more incorrect blue markers in other photos . I then have to delete those blue markers (I use python code for this) and keep pinning the gray markers.
Also, you can see the marker error (pix) get worse when there are blue flags for that marker. As soon as I delete the blue flags the marker error (pix) is good again.
I have now seen this in two projects.
Would anyone have a suggestion on what is going wrong. Could it a bug in the new version?
I am using the following python code delete all the blue flags in the project. It works very well.
It was found here - https://www.agisoft.com/forum/index.php?topic=10969.0
import Metashape
chunk = Metashape.app.document.chunk
for marker in chunk.markers:
for camera in list(marker.projections.keys()):
if not marker.projections[camera].pinned:
marker.projections[camera] = None
Any help appreciated
Regards
Ben
12
General / Re: Can't set coordinate system when importing mesh in Agisoft Metashape
« on: September 29, 2024, 06:45:11 AM »
Hi Jkova96
I had a problem importing a mesh into Metashape. The mesh was in the format of 3d triangles (AutoCAD 3d faces). The triangle vertices coords were large values in X Y Z
What Alexi found was metashape was rounding the decimal places off the triangle vertices' coordinates when it was imported. This was because of their length of the coordinate values. Metashape has a maximum coordinate value length for each X,Y and Z when using Local Coordinates. So the mesh in Metashape was wrong - different to the mesh i was trying to import!
Once the shifts were applied when importing the mesh, the vertice coordinates value length were shorter and Metashape could then recreate my mesh vertices correctly (only shifted X and Y)
I know this is not your issue but the information below many help importing your mesh -
Alexi found the rounding issue and created this console input for me- Note the X and Y shifts are for my job. You would change these to your job, if a shift is needed.
- execute the following line in the Console pane: Metashape.app.document.chunk.transform.matrix=Metashape.app.document.chunk.transform.matrix
- use File Menu -> Import -> Import Model command, select Local Coordinates system option and input the following shift offsets: X = 365000, Y = 6326000, Z = 0
Hopefully this may stop your coords being greyed out.
These are the full instructions Alexi sent me and they worked for me -
Meanwhile you can also try another workaround. Using "local coordinates" system directly is not possible due to the rounding issue that will appear for the large coordinate values, but it should be possible to use Shift offests on import and export:
- create new chunk in Metashape project and make it active,
- execute the following line in the Console pane: Metashape.app.document.chunk.transform.matrix=Metashape.app.document.chunk.transform.matrix
- use File Menu -> Import -> Import Model command, select Local Coordinates system option and input the following shift offsets: X = -365000, Y = -6326000, Z = 0
- then export model using Local Coordinates option again and same shift offsets (X = 365000, Y = 6326000, Z = 0 ). You can use precision=6 that is similar to the input file.
Hopefully it should work according to your expectation: model will be loaded to Metashape in Cartesian coordinate system shifted by XYZ vector and on export the same vector will be added to all the vertices.
Let me know, if this approach works, while I am checking, why you are not getting the same results using geographic/projected coordinate system.
Kind Regards
Ben
I had a problem importing a mesh into Metashape. The mesh was in the format of 3d triangles (AutoCAD 3d faces). The triangle vertices coords were large values in X Y Z
What Alexi found was metashape was rounding the decimal places off the triangle vertices' coordinates when it was imported. This was because of their length of the coordinate values. Metashape has a maximum coordinate value length for each X,Y and Z when using Local Coordinates. So the mesh in Metashape was wrong - different to the mesh i was trying to import!
Once the shifts were applied when importing the mesh, the vertice coordinates value length were shorter and Metashape could then recreate my mesh vertices correctly (only shifted X and Y)
I know this is not your issue but the information below many help importing your mesh -
Alexi found the rounding issue and created this console input for me- Note the X and Y shifts are for my job. You would change these to your job, if a shift is needed.
- execute the following line in the Console pane: Metashape.app.document.chunk.transform.matrix=Metashape.app.document.chunk.transform.matrix
- use File Menu -> Import -> Import Model command, select Local Coordinates system option and input the following shift offsets: X = 365000, Y = 6326000, Z = 0
Hopefully this may stop your coords being greyed out.
These are the full instructions Alexi sent me and they worked for me -
Meanwhile you can also try another workaround. Using "local coordinates" system directly is not possible due to the rounding issue that will appear for the large coordinate values, but it should be possible to use Shift offests on import and export:
- create new chunk in Metashape project and make it active,
- execute the following line in the Console pane: Metashape.app.document.chunk.transform.matrix=Metashape.app.document.chunk.transform.matrix
- use File Menu -> Import -> Import Model command, select Local Coordinates system option and input the following shift offsets: X = -365000, Y = -6326000, Z = 0
- then export model using Local Coordinates option again and same shift offsets (X = 365000, Y = 6326000, Z = 0 ). You can use precision=6 that is similar to the input file.
Hopefully it should work according to your expectation: model will be loaded to Metashape in Cartesian coordinate system shifted by XYZ vector and on export the same vector will be added to all the vertices.
Let me know, if this approach works, while I am checking, why you are not getting the same results using geographic/projected coordinate system.
Kind Regards
Ben
13
General / Re: Local to projected coordinate system of point cloud
« on: September 18, 2024, 04:16:28 AM »
Hey K,
Yep we use the term Assumed coordinates for when we have no connection to a known coordinate system. I have also thought in Metashape Local = Assumed
Yep we use the term Assumed coordinates for when we have no connection to a known coordinate system. I have also thought in Metashape Local = Assumed
14
Bug Reports / Re: After "Build Tiled Model" Texture resolution is substantially degraded.
« on: September 15, 2024, 11:36:01 PM »
Mr Miyagi,
I know this is and old post but could you tell me how you created this OBJ? And after you fixed the problem in Metashape did the tiles model look exactly the same??
I have tried Tiled Models in Metashape (created from depth maps) but can never create anything as realistic as your example.
Any suggestions would be welcome.
Regards
Ben
I know this is and old post but could you tell me how you created this OBJ? And after you fixed the problem in Metashape did the tiles model look exactly the same??
I have tried Tiled Models in Metashape (created from depth maps) but can never create anything as realistic as your example.
Any suggestions would be welcome.
Regards
Ben
15
General / Re: Align imported point cloud file
« on: September 15, 2024, 02:38:05 PM »
Hi,
Does this document help? https://agisoft.freshdesk.com/support/solutions/articles/31000168474
I know it is talking about Laser Scans. But near the end of the document, it talks about aligning, could you use the same method for point clouds?
Cheers
Ben
Does this document help? https://agisoft.freshdesk.com/support/solutions/articles/31000168474
I know it is talking about Laser Scans. But near the end of the document, it talks about aligning, could you use the same method for point clouds?
Cheers
Ben
