Hiking (and Sailing!) features

[email-creator]

Issue description

I find myself in different situations where I want to get access to specific info. I may want to find out my current location, the next upcoming intersection, my speed, my heading (based on direction of travel or compass heading depending on phone compass,) lat/long data, etc. This would be valuable in a variety of situations while walking, driving, or hiking. Perhaps the settings page could have a way for me to select the info that is provided by pressing an info button on the main screen, to avoid cluttering the main UI.

Use case

• As I'm hiking, and I am not near a road, I need to have a better way of tracking my position. Geocaching benefits as well. For this reason, having a way to announce lat/long coordinates, with possibly a way to set preferences for the type of announcement and the accuracy, could be very helpful. Compass heading is also crucial for this use case.
• While walking or driving, I often want to quickly know specific information such as next upcoming intersection, heading, city and neighborhood, etc.
• While on a bus, being able to know upcoming intersection if I don't have a mark set at a drop-off bus stop would be very helpful. Intersection announcements aren't provided with enough time to act, and often times aren't provided at all while driving, so the ability to determine next intersection in the UI is critical.

[davecraig]

We've had another request come in which is to aid people who are sailing. It's quite similar in that they'd like heading information and possibly location. A couple of things occurred to me:

1. We could enable an "outdoor sports" setting
2. Beacons could be set on a bearing e.g. 245 degrees. In practice we'd just set a beacon on a location >100 miles away in that direction. They would then be able to listen to how their travel direction was differing from the direction of the beacon. With a bearing beacon, instead of calling out how far from the beacon they are, the app could callout the current heading instead.
3. Whenever in outdoor sports mode, calling out the lat/lng, speed and travel heading would be the norm.
4. For dinghy sailing, just setting up a route of markers in standard soundscape might be very useful already.
5. I talked to a sailor that I know and he reckoned that using the travel direction of the boat rather than direction that the boat is pointing in for the heading calculations might be more useful than the direction that the boat is pointing in and so they could just put their phone away in a bag and use standard Soundscape.
6. We'd have to be more careful with the GPS error values that are coming in when in outdoor mode. For regular Soundscape we're map matching from the GPS location to nearby roads and paths. I need to check, but I think that the 'snapped' locations are what are used when calculating travel direction. This removes GPS error, though risks mapping error instead. In outdoor mode there would be no map matching, and so both Kalman filtering the GPS and discarding locations with large errors would be much more important.