Accuracy - Allow input of altitude in feet

[gb-dursley]

Bug Description
In the ACCURACY window, the Your... (position) continues to use decimal degrees and metres when the user sets degrees & decimal minutes and feet in Settings, even though the accuracy data at the bottom of the window is expressed in feet.

To Reproduce
In Settings:

1. change the Coordinate format from decimal degrees to degrees decimal minutes
2. change Preferred distance units to Feet
3. change Preferred speed units to Miles per hour

Expected behaviour
The users settings to be used throughout the App

Observed behaviour
As above

App, Device and Android version:
GPSTest Version 3.8.3
Acer Iconia One 10 B3-A40
Android 7.0 (Nougat)
Google Play (and Gmail) not used

[barbeau]

@gb-dursley Thanks for the feedback! I've split this into two separate issues, with the input of Accuracy location in DMS/DDM in #444, and this issue focusing on altitude in feet. I agree it's not currently clear that the coordinate format settings only apply to Status, especially for altitude. Supporting Accuracy altitude in feet should be easier to implement than input in DMS/DDM, so that would likely come first.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[barbeau]

Note that following #529, the hint text for altitude is "Meters above WGS84 ellipsoid (Optional)", so we need to update that if feet is selected and supported as an input unit.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

[barbeau]

Not stale