In this transformation we have preserved the original metadata.
When processing these images we see that the results are very bad.
So we decided to study the content of the image metadata.
This image contains fields that are specific to the PIX4D software and Micasense camera.
Example of metadata image: metadata.txt - Google Drive
Any way to treat metadata to make it valid in ODM?
Information about the environment:
Installation: docker
Execution: docker run -it --rm -v /geo:/code/odm_georeferencing -v /images:/code/images -v /orto:/code/odm_orthophoto odm_image
HI, I’m working with @DCB on that… we saw that focal is not present (nor camera model) in the exif of the image but only inside XMP metadata tagged with pix4d!
workaround is to setup manually the focal lenght and check if it’s enough
add code in ODM to manage XMPs depending on camera model => some registry/plugin architecture to add dynamically support to different sensors (or simply a DB of models)
About XMPI found the best way to manage is through GDAL just because they are managed in elegant way, instead of direct XML parsing.
any opinion?