On Wednesday, December 18, 2013 9:44:53 AM UTC+2, gjs wrote: > > Hi, > > Not I, but you could guess that these relate in a device, cost &/or > technology independant manner about what (Location) accuracy is desired by > your app. > > The current technologies that the OS might choose from based on your > settings include GPS (fine or high accuracy), Wifi access point (medium > accuracy), Cell Tower (low accuracy) & Barometer (for medium vertical > acurracy ?), public IP address (low accuracy?) where those technologies > are supported by the end users device. > > By presenting the Location accuracy options in a technology independant > manner Android also leaves open the possibility of supporting other > Location based techniques in future, such as Bluetooth, RFID, NFC, and > other passive wireless techiques, using sensors etc. And to do this with > you needing to update your app. > > Regards > > Great - my question as stated in the OP is _why have 2 methods with different set of integer parameters (why not an enum btw) doing the exact same thing_ not why I do not ask for GPS or wifi by name. Please read more carefully before posting
> On Wednesday, December 18, 2013 8:25:58 AM UTC+11, Mr&Mrs D wrote: >> >> As internally accuracy just >> sets<http://androidxref.com/4.4_r1/xref/frameworks/base/location/java/android/location/Criteria.java>`mHorizontalAccuracy` >> I wonder why both setHorizontalAccuracy() and >> setAccuracy() - and no less than 6 constants - are provided. >> >> Anyone knows ? >> >> On Tuesday, November 5, 2013 12:48:54 PM UTC+2, Mr&Mrs D wrote: >>> >>> setAccuracy<http://developer.android.com/reference/android/location/Criteria.html#setAccuracy%28int%29> >>> >>> > Indicates the desired accuracy for latitude and longitude. Accuracy >>> may be ACCURACY_FINE if desired location is fine, else it can be >>> ACCURACY_COARSE. More accurate location may consume more power and may take >>> longer. >>> >>> setHorizontalAccuracy<http://developer.android.com/reference/android/location/Criteria.html#setHorizontalAccuracy%28int%29> >>> >>> > Indicates the desired horizontal accuracy (latitude and longitude). >>> Accuracy may be ACCURACY_LOW, ACCURACY_MEDIUM, ACCURACY_HIGH or >>> NO_REQUIREMENT. More accurate location may consume more power and may take >>> longer. >>> >>> Another example of the pristine android docs. So what is the difference >>> ? Notice they take different constants - is it possible/desirable to >>> specify both with some combination of constants ? >>> >>> asked also >>> here<http://stackoverflow.com/questions/17599719/setaccuracy-vs-sethorizontalaccuracy> >>> >>> -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
