Allow backwards shots, averaging, and alerting if there is a large variation

[LavaTiger99]

Allow optional backshot between stations, calculate the average, and alert if the compass or incline degrees is >2° (or a user defined amout in settings). This average # is what will be used for the final survey numbers
See mockup:

[LavaTiger99]

And length should not be required field in the backshot

[lz1asl]

The idea is good (#73) and can be debated. You offer to allow back shots, validate against the straigh one and use the averaged ones as final values? Do we need separate tresholds for azimuth/distance/inclination? Do we only display both shots and export only the averaged? Or use the back shot only for error checking? What should happen in case of validation?
Let me think more about this one...

[LavaTiger99]

I supposed it should be user specific, so in Settings > Backshots:
Which measurement from backshots to use? (Forward/backward/average, default: forward)
How much tolerance in direction? (0.0-90.0 degrees, default: 2)
How much tolerance in inclination? (0.0-90.0 degrees, default 2)
How much tolerance in distance? (0.01-1.00 meters, default 0.10)

[LavaTiger99]

I think it should allow you to save it regardless of variation/validation, but only notify in red of a variation beyond the threshold.

[lz1asl]

Can combine this feature with device reported errors(e.g. BRIC4 has accuracy reporting that is not yet implemented) and averaging error report