Capping of erronous HR values

Sometimes when cycling down long fast down hills or cycling into a cold headwind my HRM starts to give incorrect values due to the strap drying on my skin. The HR values suddenly jump to max of 225-240bpm. It would be nice if oruxmaps could 'cap' or filter these incorrect values and just insert the last known 'good' value until the HRM values return back to normal. It should be easy to identify the incorrect reading as they jump in large increments, e.g. from 160bpm to 225bpm in one step which would be impossible. When the skin starts to sweat again the HR values will suddenly drop from 225bpm to 140bpm for example so at this point oruxmaps can start using the actual data again.

It's probably not an easy feature to integrate but would be very useful and prevent the incorrect high readings from messing up the stats and masking the true max HR achieved.