Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ortho + plugin (step 4) generates a Null Point Cloud error when using the latest version of Metashape Pro for linux (2.0.1) #2

Open
Runge123 opened this issue Apr 19, 2023 · 1 comment

Comments

@Runge123
Copy link

Dear Chris,

I used the Ortho+ plugin to process a set of RGB images over a forest using the latest version of Metashape Pro for linux (2.0.1). Specifically, I used the Best Practices workflow using GCPs to georeference the images. Steps 1, 2 and 3 (from image alignment, manual marking of GCPs to optimisation of the sparse cloud) all work fine, however, when I want to run step 4 I get the error "Null point cloud", this means that the system does not recognise or detect the sparse cloud.

Log error
Agisoft Metashape Professional Version: 2.0.1 build 16069 (64 bit)
Platform: Linux
BuildModel: source data = Point cloud, surface type = Height field, face count = High, OOC version, interpolation = Enabled, vertex colors = 1
Finished processing in 0.010364 sec (exit code 0)
Error: Null point cloud

So I tried to install new Python3 dependencies but the error remained.

Then, I uninstalled the Linux version of metashape pro 2.1.0 and installed the previous version 1.8.5 and when I ran step 4 to create the mesh and the orthomosaic it worked.

So, maybe the error derives from some incompatibility of Ortho + with the latest version of metashape pro version 2.0.1 for Linux

Best
Christian

@gisma
Copy link
Owner

gisma commented May 14, 2023

Typically this means that the bounding box is not covering the point cloud . You can manually try to rest the bounding box. It som,etimes also occurs if the GPS data of the images is faulty. Check for outlier.

Otherwise keep the 1.8 if you are not using Lidar data this is fine. I try to fix the downward breaches asap.
Please check the updated version.

best Chris

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants