Hi @OET_Production,
Format id=“{00000000-0000-0000-0000-000000000000}” should be a unique identifier of your template. For your personal purposes, it is completely sufficient to change few zeros to a number, e.g. {00000000-0000-0000-0000-000000000001}. However, if you want to share your template, then this value should be unique and you should use an online GUID generator. Please also note that the body string is also substituted and it just includes your template file.
Also, the descID should be unique and not used in any other XML file. Basically you can add +1000 to the number you see now.
So, I got this working now, but I have a few questions:
A) On the “prior pose” section of a selected input, it shows “Pitch / Elevation”. Pitch and elevation are very different things. I am trying to define to RC that the camera is pointed 50 degrees down, so I input a value of -50. Is this correct?
B) What are the units of Yaw? Is it a degree of 360, with 0 being north?
How would you advise I proceed in the case of this bug?
I have three cameras that are taking simultaneous pictures every three seconds. Each camera has a different pitch and heading, and focal length. Each camera has the same origin point. The photos (because of the type of camera used) do not have embedded exif data for me to read - hence why I need to use the FlightLog.
I am trying to figure out how to most efficiently group these cameras for processing.
You will need to set it manually for now.
Are you sure with the same origin point? I suppose the principal points for the cameras won’t be the same. At least there needs to be some difference.
I believe that the functionality to use FlightLog to indicate camera offsets from the origin is also bugged. I submitted this bug on the old ticket system.
To be honest, I do not know how to set FocalLength manually for a batch of images. I don’t see the ability to do this. What do you suggest?
I am also open to setting camera offsets, but I do not know how this could be accomplished with the flightlog offset functionality broken.
I am not sure if this will work. Also, for zero values, they will be consider as zeros, which could mess the calculation.
It would be better not to use such info.