Pasting here from @BobTorgerson's 2021-10-1 email. This is something we'll want to add 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.
Pasting here from @BobTorgerson's 2021-10-1 email. This is something we'll want to add to the CSO data harvester (
importAPI) 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_accuracyandlocation_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.