Pole distance and bearing, where to aim the cameras, and the survey written into cameras.local.yaml. Everything is computed in this page; nothing is uploaded.
1. Points
Points surveyed on this channel - in the web console or the Android app, on any device - arrive here by themselves: origin, camera_a, camera_b, and any other name as a reference point for north alignment.
Reference points (for aiming / north alignment)
2. cameras.local.yaml
Open the tracker's settings file, write the survey into it, save. Only the site origin, each camera's origin_e/n/u and pole_distance_m: 0.0 change; you see every changed line first.
or paste it
No file at hand? Values to type in by hand
Compare with a planned layout (optional)
The tape-measure layout: poles pole_distance_m apart, camera_b at pole_line_bearing_deg from camera_a, origin halfway. Shows how far each pole is from it.
Between the poles
Load or enter both poles.
Imagery is typically 1-3 m off; the exact plot and numbers are survey-grade.
Corrections vs plan
Aim the cameras (north alignment)
Where each camera must point to see each reference point, in the tracker's own frame. For calibrate_ptz.py sight, replace <lat>,<lon>,<alt_m> with the copied value. Points further away give a better alignment.
Needs the origin and a camera.
Live rover - walk to a spot
Any rover surveying on this channel - web console or Android app, on any device - shows here live, with directions to the target.