Add interpolating-coordinates to GUI for observations without location

Add a button in the detailed observation view for observations without location to edit the observation with a default location based on observations of the same observer just before and after this observation.

This feature is already available in the edit of an observation: ?interpolate_coordinates=true

Description of this feature and the suggestion to create a feature request can be found in this forum topic:

Platform(s): website

This is based on a weird URL hack, but I’d be pretty wary of making it an official and easily accessible functionality unless it had some massive accuracy circles or somehow had some extensive testing to verify accuracy. I also feel like for one point, it’s not that helpful (it’s easy enough to just drop that in between some of your other points on the map). I can see it being useful for multiple points, but then I start to worry about accuracy. I guess I’m just wary of any situation in which data is added to an observation that doesn’t really require human input/verification. I also wonder what data repositories/data users would think of it. I personally wouldn’t want to use interpolated data and would want a way to filter them out.

One potential issue that I can think of that would need to be screened out if implemented was if a user tries to interpolate multiple points from the same “trip” or day. You could end up with interpolations based on interpolations unless you explicitly track and exclude which points have been interpolated. Depending on how it’s implemented you could have some nonsensical locations generated if a user went to multiple discrete locations (like interpolated points in the middle where they definitely weren’t).

There could also be some weird interactions with ongoing time zone issues I guess.


See a feature request about wrong locations in stead of no location:

How would you handle the first or last observation in a series since there is not a before or after. What if you visited multiple locations in one day.

The alorithm is already implemented. The only thing to do is to integrate it in the GUI of the apps and the web and add the possibility to correct the location and accuracy if the algorithm makes a wrong decission.

When using this feature the location as well as the accuracy should be possible to be manually adapted.
In the end it is the user who adds a location and accuracy, not the algorithm.