Re: Report Site Issues Here
Posted: 16 January 19 4:50 pm
Technical items are not senate issues. The senate has no say on how we code or configure the site.
Free and Open Geocaching
https://forum.geocaching.com.au/
This caused me some confusion so I made this: https://wiki.geocaching.com.au/wiki/Upl ... ate_IssuesRichary wrote:On a similar vein when I do imports to help keep the db up to date, I often see messages saying Updated date of log or similar. Whether this is because they have previously been imported and since amended by the finder on the other site I haven't been able to work out.
OK, I am probably almost as confused as I was before but is there a fix? Like a GSAK macro that will strip the time from the data before the GPX export or set it to something sensible so we don't have the mismatch in data?Laighside Legends wrote:This caused me some confusion so I made this: https://wiki.geocaching.com.au/wiki/Upl ... ate_Issues
It is caused by GC failing to fix some issues when they introduced dates being included as part of the description. Individual GPX files and anything done with their API has been fixed but not the PQ stuff but they are working on that. (The issue is only apparent for those in different timezones than GCHQ). Not much we can do when the source data is wrong.Laighside Legends wrote:The dates for most GC events are out by one day on GCA. Not exactly sure why this is, but possibly because Groundspeak are now including the event start time in the GPX file (in the <time> tag) whereas previously this was set to 00:00:00
The fix is at the source. Petition to GCHQ to fix their date/time which has been wrong for, well, ever. Anything we attempt to do will only ever be temporary and will not fix the root cause.Richary wrote:OK, I am probably almost as confused as I was before but is there a fix? Like a GSAK macro that will strip the time from the data before the GPX export or set it to something sensible so we don't have the mismatch in data?Laighside Legends wrote:This caused me some confusion so I made this: https://wiki.geocaching.com.au/wiki/Upl ... ate_Issues
This is the only reference to the problem I can find: https://forums.geocaching.com/GC/index. ... nt-5761155caughtatwork wrote:It is caused by GC failing to fix some issues when they introduced dates being included as part of the description. Individual GPX files and anything done with their API has been fixed but not the PQ stuff but they are working on that. (The issue is only apparent for those in different timezones than GCHQ). Not much we can do when the source data is wrong.Laighside Legends wrote:The dates for most GC events are out by one day on GCA. Not exactly sure why this is, but possibly because Groundspeak are now including the event start time in the GPX file (in the <time> tag) whereas previously this was set to 00:00:00
At the time GSAK users were told to update caches via the API after a PQ download as the API has been fixed and now doesn't have the problem.Laighside Legends wrote:This is the only reference to the problem I can find: https://forums.geocaching.com/GC/index. ... nt-5761155caughtatwork wrote:It is caused by GC failing to fix some issues when they introduced dates being included as part of the description. Individual GPX files and anything done with their API has been fixed but not the PQ stuff but they are working on that. (The issue is only apparent for those in different timezones than GCHQ). Not much we can do when the source data is wrong.Laighside Legends wrote:The dates for most GC events are out by one day on GCA. Not exactly sure why this is, but possibly because Groundspeak are now including the event start time in the GPX file (in the <time> tag) whereas previously this was set to 00:00:00
They were "looking into" the problem on Jan 31st and no updates since.
I would have thought this would cause problems for everyone that uses PQs and GSAK (not just GCA users)