- From: Jack Farley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Sep 2022 12:48:03 +0000
- To: public-device-apis-log@w3.org
I've just been looking at implementing a generic app to workaround that this isn't possible in the browser ATM. I think it would be good to have [options like those of @nativescript/geolocation](https://docs.nativescript.org/plugins/geolocation.html#options). `frequency` could be equivalent to `updateTime` and then have a option for `updateDistance`, resulting in a logic of a new position is emitted if the position change is more than `updateDistance` meters (dependent on accuracy), otherwise every `frequency` ms. My use cases are position tracking during surveys (eg litter surveys) and position tracking of responders/first-aiders during events. Having played with watchPosition, this was the logic I implemented in the code. Having the option to pass these options the the sensor constructor would mean the logic could be implemented at a lower level (it must already be implemented[ish] if it is in NativeScript) to save power. -- GitHub Notification of comment by bytesnz Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/13#issuecomment-1243691625 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 September 2022 12:48:05 UTC