search

lz1asl / CaveSurvey

Cave surveying application for Android devices
MIT License
44 stars 11 forks source link

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

Open LavaTiger99 opened 3 years ago

LavaTiger99 commented 3 years ago

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: 68747470733a2f2f7261772e6769746875622e636f6d2f6c7a3161736c2f436176655375727665792f6d61737465722f646f632f73637265656e732f506f696e742e706e67

LavaTiger99 commented 3 years ago

And length should not be required field in the backshot

lz1asl commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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