Yes, Kai Team is correct.
My plugin (FSGPlugin_AddtitionalPlacedChacheStats) uses the tables generated by FSG.
It seems that FSG does not correct the PlacedLogs table for the issue with the geocaching.com date. This can be seen from the "Owned Statistics" section of FSG.
There, the cache "U turn at Horseshoe" is listed as havig a Last find on 22/12/2013, where according geocaching.co, it is indeed 21/12/2013.
Lignuaqua can easily fix this in his FindStatsGen3.gsk macro by changing line 12961 to:
This fix corrects both the last find date in the "Owned Statistics" and results in the "Placed caches found by Found Date " table of my plugin matching the dates on geocaching.com![biggrin.gif]()
My plugin (FSGPlugin_AddtitionalPlacedChacheStats) uses the tables generated by FSG.
It seems that FSG does not correct the PlacedLogs table for the issue with the geocaching.com date. This can be seen from the "Owned Statistics" section of FSG.
There, the cache "U turn at Horseshoe" is listed as havig a Last find on 22/12/2013, where according geocaching.co, it is indeed 21/12/2013.
Lignuaqua can easily fix this in his FindStatsGen3.gsk macro by changing line 12961 to:
| GSK |
$_sql = "CREATE TABLE placedlogs AS select lParent,lType,lText,lBy,g_gcdate(lDate,lTime) as lDate,lLogid,lOwnerID from gsakdb.LogsAll WHERE (lparent IN (SELECT code FROM gsakdb.caches where $_Where)) AND (SUBSTR(lType,1,5)='Found' OR SUBSTR(lType,1,5)='Atten' OR SUBSTR(lType,1,5)= 'Webca' OR SUBSTR(lType,1,5)= 'Archi') AND lDate<='$Today' AND lDate>='$SQLStart'" |
This fix corrects both the last find date in the "Owned Statistics" and results in the "Placed caches found by Found Date " table of my plugin matching the dates on geocaching.com
