After looking at my results, I noticed a few important points.
The results from this macro are only as good as the logs in your database. I have a number of caches where my log is the only entry in GSAK...thus an empty set is returned for those caches. Also, there are may caches where I already had the logs in my DB, then months later when I found the cache, I had never updated the GSAK logs between those two times....this will lead to a highly inflated result. The only way to make sure this macro give you exact results, is to make sure each of your cache finds has the correct previous find as well...not a simple task.
That would be another cool macro, get via the API, the last x number of logs before my find...or for that matter, x number of logs after my find.
Thanks again, this is a very helpful macro nonetheless!!
-Mike
The results from this macro are only as good as the logs in your database. I have a number of caches where my log is the only entry in GSAK...thus an empty set is returned for those caches. Also, there are may caches where I already had the logs in my DB, then months later when I found the cache, I had never updated the GSAK logs between those two times....this will lead to a highly inflated result. The only way to make sure this macro give you exact results, is to make sure each of your cache finds has the correct previous find as well...not a simple task.
That would be another cool macro, get via the API, the last x number of logs before my find...or for that matter, x number of logs after my find.
Thanks again, this is a very helpful macro nonetheless!!
-Mike