Metashape Processing Script: "Cameras" may contain elements that are not cameras, and therefore no "labels" tag #2611
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
This probably isn't worth a PR, but we use Metashape (and now NeRFs 😎) for underwater reconstructions. Because we already use Metashape, the processing script is very useful, which allows us to skip the redundant step of using colmap.
We use Metashape 2.0.X, and when exporting cameras as an XML file, "cameras" may contain elements (children) that are not really cameras, and therefore they will not have a "label" tag. This results in the processing script to throw an error which checking:
Simple fix is just to check if the value returned in the previous line (
camera_label
) isNone
, since iflabels
does not exists it will returnNone
; ifNone
that iteration is the looped is skipped. This worked for us.Below is the end portion of the xml file exported from Metashape 2.0.X: