W3C home > Mailing lists > Public > public-device-apis-log@w3.org > April 2020

Re: [dap-charter] Any new sensor API? (#4)

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Wed, 01 Apr 2020 09:01:26 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-607127271-1585731685-sysbot+gh@w3.org>

>For some background, the hinge angle sensor as described in the Android documentation.

Fold Angle Sensor is added to the [draft charter proposal](https://w3c.github.io/dap-charter/DASCharter-2020.html).

> Barometer altitude (if the device has barometer) https://github.com/w3c/geolocation-sensor/issues/43#issuecomment-604911855

Here's how I unpack this, clarifications welcome:

Using GPS the method to measure altitude is called [trilateration](https://en.wikipedia.org/wiki/True_range_multilateration). This method has restrictions as outlined in the article. To get more precise altitude readings, some (or most modern mobile?) devices include [barometric altimeter](https://en.wikipedia.org/wiki/Altimeter) that measures the atmospheric pressure.

I think the proposal is to allow web developers to request "high precision altitude". This could be addressed by allowing developers to pass a flag upon instantiation of the GeolocationSensor, for example (note: this approach has caused interop issues in the past, see PositionOptions.enableHighAccuracy in Geolocation API). This would be already in scope, no changes required in the charter to pick up this work.

If, OTOH, there are reasonably mainstream use cases for requesting altitude _alone_ without lat/long, it'd make sense to split that feature into a separate sensor type to enable better privacy protections (users could grant access to altitude alone, and not lat/long). Also we need to understand  implementability (i.e. do platforms allow requesting just altitude), initial assessment https://github.com/w3c/geolocation-sensor/issues/43#issuecomment-604911855 suggests some platforms do expose this sensor type separately.

cc @karianpour

GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/4#issuecomment-607127271 using your GitHub account
Received on Wednesday, 1 April 2020 09:01:32 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:57 UTC