Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131)

alvinjiooo left a comment (w3ctag/design-reviews#1131)

@jyasskin Thank you for that excellent point regarding "accuracy" vs. "precision." You're right that "precision" (or granularity). 

While investigating this, I found that the platform-level APIs we'd be building on are also inconsistent, which makes the choice difficult.
- Apple's CoreLocation API uses desiredAccuracy (e.g., kCLLocationAccuracyBest, kCLLocationAccuracyKilometer).
- Android's GMS Location API uses Granularity (e.g., GRANULARITY_FINE, GRANULARITY_COARSE).
- Microsoft (WinRT): DesiredAccuracy (using enum values Default, High)

Since this is a new enum for the web platform and the underlying ecosystem is fragmented, perhaps this naming decision warrants a wider discussion. We will have this noted and see if we can discuss the final name of it in TPAC this year and see what it best way moving forward.

Also copying @nondebug here.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1131#issuecomment-3293410570
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1131/3293410570@github.com>