W3C home > Mailing lists > Public > public-geolocation@w3.org > May 2009

Re: renaming enableHighAccuracy

From: Angel Machín <angel.machin@gmail.com>
Date: Thu, 21 May 2009 16:47:38 +0200
Message-ID: <5562f69c0905210747k54135616re4379bd4f799eb5@mail.gmail.com>
To: "Allan Thomson (althomso)" <althomso@cisco.com>, Andrei Popescu <andreip@google.com>
Cc: public-geolocation <public-geolocation@w3.org>
Hi!

Just a comment related to this...
I was checking the Android SDK and I have realized that it defines two
separate attributes for accuracy  and battery:

criteria.setAccuracy(Criteria.ACCURACY_COARSE);  //fine or coarse
criteria.setPowerRequirement(Criteria.POWER_LOW);  //low, medium or high

According with the documentation:

"If more than one Location Provider matches your criteria, the one
with the greatest accuracy is
returned. If no Location Providers meet your requirements, the
criteria are loosened, in the following
order, until a provider is found:
- Power use
- Accuracy
- [others]"

Regards,
Angel
Received on Thursday, 21 May 2009 14:48:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 August 2009 20:54:11 GMT