Incorporate new location information elements from the MH server API response

[emiliom]

Pasting here from @BobTorgerson's 2021-10-1 email. This is something we'll want to add to the mountainhub-api client API, which should be fairly straightforward. In addition, we'll want to add them to the CSO data harvester (import API) and to the CSO database.

we are adding a couple of new fields for every new observation added to Mountain Hub along with our bug fixes and feature additions in mid-October.

These two fields will be returned in the https://api.mountainhub.com/timeline for each observation as location_accuracy and location_changed. These two fields are as follows:

• location_accuracy: The accuracy that was accepted by the user upon creation of the observation. This will be an integer of the number of meters for GPS accuracy.
• location_changed: This is a boolean value that will be True only if the user manually changes the location of their observation. In that case, you will be made aware that the user did not use the GPS accuracy of their current location for the created observation.

We wanted to give you time to incorporate this into your backend database and we expect that this will be something useful for the snow-based observations coming this winter.

[emiliom]

From Craig Stephenson, UAF/SNAP:

A new version (3.1.0) of the Mountain Hub iOS and Android apps was released last week that adds new location_accuracy and location_changed fields to observations:

location_accuracy: The GPS accuracy (in meters) of the observation. Users are able to set their desired GPS accuracy and timeout values to improve the accuracy if necessary.

location_changed: This is set to true if the user chose their location manually, in which case the GPS accuracy is no longer relevant to the observation. If the user did not choose their location manually, this is set to false.

These new fields are starting to show up in the Mountain Hub timeline API for users who have updated their app: https://api.mountainhub.com/timeline