Platform(s), such as mobile, website, API, other: all platforms
URLs (aka web addresses) of any pages, if relevant: Discussion started here: https://forum.inaturalist.org/t/make-it-easier-to-distinguish-how-coordinates-were-created
Description of need:
The coordinates of observations are created in different ways:
- searching in the map in the uploader and accepting the searched location
- manually navigating the map in the uploader to select a point
- camera has built-in GPS
- mobile app automatically records coordinates
- geotagging via external app
- geotagging via external GPS device
Some of these methods are likely to result in less accurate and less precise locations than others - notably the first method (#1) in the list above. To give an example, if I search for “Denali”, the first result is a point with reasonable precision (< 1 km) but it’s highly unlikely that my observation is from the mountain peak itself - more likely from the vast national park of the same name.
My request is to ensure that the positioning method is being recorded in observations (as described by @jwidness here) and that it is available to users, who could, for example, filter out observations that were created through a simple google maps search that was not then modified by the observer moving the pin to a more accurate location. This would also be useful in diagnosing location errors.
Feature request details:
Verify that the fields positioning_method and positioning_device are being populated reliably, and make them available so that observations can be selected depending on the value of these fields. In the list of methods I’ve given above, I don’t think it’s important to distinguish items 3, 4, 5 and 6, but it would be useful to distinguish item 1, and items 1 and 2 should not be lumped together.
It would also be nice to record what text was used in the google maps search, but that might be more difficult and is not central to this request.