Dabremix

Hi, today I wanted to update the list of my GPS devices on my account details. Unfortunately the list for Samsung devices seems to be very outdated. Popular high-end smartphones like S4, S4active and S5 are not listed :-( When will this list being updated? Is there a way to report new devices to be added? Regards Dabremix

Back to topic... Whether challenge caches make sense or not is not the topic of this thread. And of course a D/T rating should be changeable by the owner with little efford according to new conditions. The thing that frustrates me (and others) is: All other statistics offered by Groundspeak seem to display correct values regarding my founds. Only the D/T matrix does not display the status of my found caches. Instead it displays the current state of caches that I've found months or years before. I think, that this behaviour could be corrected by a programmer with not so much efford (storing the D/T values at log time together with the log entry). And this would also have positive influence on statistic generation process. I would appreciate if this could be discussed further. PS: Only to hzoi: The original post was not inspired by the 5/3.5 gap in my matrix. (It was a 2/4 gap which is filled again.) But I would prefer that you omit such assumptions.

Of course it should be possible to change D/T values if necessary. (As well as owner, type, attributes, etc.) But I (and all other cachers that I know) don't want that the changed values affect our official statistics of our founds. Of course I can track the statistics by myself. I've written a program for that (similar to GSAK). But the produced statistics are not the official GC statistics and therefore not accepted for challenges. In my opinion it should be easy possible to store the current D/T values (and maybe other values like type, coordinates, or owners name) together with the log entry when logging the cache. The statistics build process should be then generate faster results because it doesn't has to lookup cache data for each found. Storing the D/T history at a cache (maybe created by an special log type) would be more precise, but would otherwise produce more lookups.

Even though it is commonly known: D/T changes of a cache affect statistics of cachers that have already found this cache. This is a severe misbehavior! For my found statistics it is important which d/t values the cache had when I've found it. Changes made afterwards should never change my found statistics. Please consider this in your data model! Thanks Dabremix