Round all mileage to tenths place

[danrademacher]

So instead of 2.33 we'd have 2.3. This would apply to the following:

• Cue Sheet
• Cue+Map view
• Nearness to ECG on search for start and end.

That final one presents a small issue:

This would round to 0.0. In this instance, seems like we'd need to either:

• not round or
• set the tolerance for nearness to ECG to consider anything less than 0.05 to be on the Greenway.

The latter is preferable, but not sure if that then presents problems with actually using that point as a starting point for the router.

[clhenrick]

@danrademacher the tolerance for how far a searched location is to the ECG route would be a separate issue that should be opened in the ecg-map-router repo.

[clhenrick]

Actually there's no case for when someone is already on the Greenway, it would just say you're 0 miles from the ECG. So in that case it would be a UI update.

[danrademacher]

Let's call this lowest priority. Not worth causing other problems in the app for the sake of extra decimal place