[PATCH] geoclue: clarify accuracy values are ordered

[Luis R. Rodriguez]

GeoClue accuracy enums are ordered from least accurate
to highest accurate possible. Clarify this so that consumer
applications that are accuracy dependent can discard address
queries which are not suitable to the application's desired
accuracy thresholds.

---
 geoclue/geoclue-types.h |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/geoclue/geoclue-types.h b/geoclue/geoclue-types.h
index 9ecbc40..c28862a 100644
--- a/geoclue/geoclue-types.h
+++ b/geoclue/geoclue-types.h
@@ -49,7 +49,11 @@ typedef enum {
  * GeoclueAccuracyLevel:
  *
  * Enum values used to define the approximate accuracy of 
- * Position or Address information.
+ * Position or Address information. These are ordered in
+ * from lowest accuracy possible to highest accuracy possible.
+ * geoclue_accuracy_get_details() can be used to get get the
+ * current accuracy. It is up to the provider to set the
+ * accuracy based on analysis of its queries.
  **/
 typedef enum {
 	GEOCLUE_ACCURACY_LEVEL_NONE = 0,
-- 
1.7.0.4