General discussion on the "services/caches/search/all" method.

[GoogleCodeExporter]

General discussion on the "services/caches/search/all" method.

Original issue reported on code.google.com by rygielski on 19 Aug 2011 at 8:25

[bubski]

I'm wondering, what the reason is for rating parameter to be a range of integers, while Cache's rating property is a float. Wouldn't it make more sense to be able to specify 1.5-2.5 range in a query?

[following5]

I think that these ratings are pretty useless, because there are very different perceptions on what is a good geocache. When averaged, the result will just meet the taste of some geocachers who's taste acciendtially meets the average value.

But as they are implemented on some OC sites and exposed through OKAPI, I agree that it would make sense to keep the data type consistent - i.e. float for all rating parameters / options.

[wrygiel]

Floats in services/caches/geocache's rating field were introduced for forward compatibility - because OC sites could decide to publish non-integer data in the future, I just wanted the existing applications to be compatible with that possibility. However, currently these floats will always be integer-ish.

In services/caches/search/* methods we didn't (yet?) include such "forward-compatibility". I guess, we could do that too (if developers want us to), but - as long as ratings are expressed by integers - it wouldn't make much "functional" sense.

[ztNFny]

date_hidden (in addition to modified_since) would be a nice addition to search parameters