- From: Dean Jackson <dino@apple.com>
- Date: Mon, 14 Feb 2011 11:04:04 -0800
- To: public-geolocation@w3.org
Hi, One of the engineers who worked on Apple's Core Motion API passed on some feedback related to compassCalibrated. He suggests that a float property called "accuracy" would be better suited - taking a value between 0 and 1. The reasoning is that a developer shouldn't really be concerned with calibration. All they really need to know is the accuracy of the data they are seeing. Also, future hardware may not need calibration, but will still have variance in accuracy. A value of 0 for accuracy could still trigger a dialog by the system asking for compass calibration (on iOS this prompts the user to do a figure-8 movement with the device). A value of 1 would mean that your data is as accurate as possible. Anything in between could be used in the UI to suggest you're not getting perfect data. I don't want to hold up FPWD for this comment. Please consider it simply feedback on the draft. Dean
Received on Monday, 14 February 2011 19:05:06 UTC