import camera accuracy

[JMR]

Hi: I'm working in some hardware hacks that have allowed me to write 2miliseconds accurate timestamp in my drone photos and do precise GPS postprocess calculations. This gives me a good estimation of accuracy of the image coordinates.
As long as this accuracy varies from one photo to another during the flight it could be a good idea to allow us to assign weight to each geo-tag according to its calculated accuracy.
So please enable import of a-priori individual precission for each photo and use them as weights in the adjustment. Thanks

[Alexey Pasumansky]

Hello JMR,

We'll try to add Accuracy column in the Import CSV dialog in the next updates for version 1.2 pre-release.

Currently in 1.2 individual accuracy for each camera can be modified manually or via Python using camera.reference.accuracy.

[JMR]

Great! Thanks a lot!
That was a fast response to a wish!

[Cytvill]

Good afternoon,
someone have an example of this script if I introduce a .txt file of coordinates?
I try to use this command (camera.reference.accuracy) in the Python console, but I obtained "'NameError: name 'camera' is not defined".
Thank you

[Alexey Pasumansky]

Hello Cytvill,

Have you assigned any value to camera variable?

[Cytvill]

No, honestly I only tried to introduce this command with the path-file in the console.
I am not familiar with Python language.
Thank you for your help.

[Alexey Pasumansky]

Hello Cytvill,

then you can try the following:
chunk = PhotoScan.app.document.chunk #assigns an active chunk to the variable
camera = chunk.cameras[0] #first camera in the active chunk in the workspace
camera.reference.accuracy = (1, 2, 3) #assigns individual accuracy in meters for each component