First available date variance

General discussions about the website's layout and functionality

First available date variance

Postby afudc » December 14th, 2018, 8:12 am

Yesterday, December 13, I found two caches -- GC81ABR and GC81ARG. According to their respective web pages both were hidden and published on December 13. On LonelyCache it says one was first available on December 13 and the other on December 14. I know that this difference will have a negligble effect on the point values but if I understand it correctly it also will affect who gets credit for the FDF.
I am wondering why this happened.
afudc
 
Posts: 19
Joined: January 22nd, 2012, 10:22 pm

Re: First available date variance

Postby Corfman Clan » December 14th, 2018, 10:39 pm

I see there is a discrepancy like you point out. When I select the caches through the Geocaching API, the published dates are being returned like you say. Below is data I copied from the Geocaching API response. The API documentation states the dates are in the time zone of the cache itself. The best I can do now, is ask Geocaching HQ why the discrepancy exists. I imagine what both the website and API are doing don't quite match up.
Code: Select all
[
  {
    "referenceCode": "GC81ABR",
    "name": "Missing Windmill",
    "placedDate": "2018-12-13T00:00:00.000",
    "publishedDate": "2018-12-13T17:56:00.000",
  },
  {
    "referenceCode": "GC81ARG",
    "name": "PIF - Tilting Topless Windmills",
    "placedDate": "2018-12-13T00:00:00.000",
    "publishedDate": "2018-12-14T00:27:00.000",
  }
]
Image
User avatar
Corfman Clan
Global Moderator
 
Posts: 804
Joined: January 17th, 2012, 12:21 am
Location: Phoenix, AZ

Re: First available date variance

Postby Corfman Clan » December 14th, 2018, 11:12 pm

What I didn't look at above was the logs. Below is the cache data along with the published log. It appears that the date/time of the published log is in local time and the date/time of the published date field is in UTC. The API documentation states that the times, both for caches and for logs should be in the time zone of the cache. Here, this is obviously not the case. Again, I'll contact Geocaching HQ and see what they say. I do know they have had issues with this for years. Frankly, I think they should just yank the time component and all would be good, but what do I know?
Code: Select all
{
  "referenceCode": "GC81ARG",
  "name": "PIF - Tilting Topless Windmills",
  "placedDate": "2018-12-13T00:00:00.000",
  "publishedDate": "2018-12-14T00:27:00.000",
  "geocacheLogs": [
    {
      "referenceCode": "GLXM0QC7",
      "ownerCode": "PRJZHYC",
      "owner": {
        "username": "AZKokopelli"
      },
      "loggedDate": "2018-12-13T17:26:58.161",
      "geocacheCode": "GC81ARG",
      "geocacheLogType": {
        "id": 24
      }
    }
  ]
}
Image
User avatar
Corfman Clan
Global Moderator
 
Posts: 804
Joined: January 17th, 2012, 12:21 am
Location: Phoenix, AZ

Re: First available date variance

Postby Corfman Clan » December 14th, 2018, 11:43 pm

One more thing, the IANA time zone of the cache is available, so I can easily convert from UTC to the local date. Well not quite that easy since LonelyCache runs un a Windows server and Windows uses its own time zone scheme, not IANA. At least that's not difficult to overcome. I sent this question off to Geocaching HQ for the official take on how to handle this but in the interim I'll probably convert.
Code: Select all
{
  "referenceCode": "GC81ARG",
  "name": "PIF - Tilting Topless Windmills",
  "placedDate": "2018-12-13T00:00:00.000",
  "publishedDate": "2018-12-14T00:27:00.000",
  "ianaTimezoneId": "America/Phoenix"
}
Image
User avatar
Corfman Clan
Global Moderator
 
Posts: 804
Joined: January 17th, 2012, 12:21 am
Location: Phoenix, AZ

Re: First available date variance

Postby Corfman Clan » December 15th, 2018, 12:58 am

And just because... This is now fixed. We'll wait and see what Geocaching HQ says for sure, but for now things are good.
Image
User avatar
Corfman Clan
Global Moderator
 
Posts: 804
Joined: January 17th, 2012, 12:21 am
Location: Phoenix, AZ

Re: First available date variance

Postby Corfman Clan » December 15th, 2018, 3:00 pm

Corfman Clan wrote:And just because... This is now fixed. We'll wait and see what Geocaching HQ says for sure, but for now things are good.

Well, it fixed it for newer caches but broke it for older caches. That is, the fix broke it for caches that don't have a published log, so the cache's PublishedDate field is exactly the same as the PlacedDate field. So now, LonelyCache will only convert the PublishedDate from UTC to it's local time zone if it is not exactly the same as the PlacedDate field.
Image
User avatar
Corfman Clan
Global Moderator
 
Posts: 804
Joined: January 17th, 2012, 12:21 am
Location: Phoenix, AZ

Re: First available date variance

Postby Corfman Clan » January 5th, 2019, 12:33 am

Geocaching HQ, treated this as a bug that has now been corrected. I verified that the cache's published date is now being delivered in the cache's time zone. As such, I have backed out the changes I added since they were a stop gap solution.
Image
User avatar
Corfman Clan
Global Moderator
 
Posts: 804
Joined: January 17th, 2012, 12:21 am
Location: Phoenix, AZ


Return to General

Who is online

Users browsing this forum: No registered users and 2 guests

cron