cache finds not displayed in order they were logged

[+caretaker5]

i started my day out hosting an event and logged that attendance before caching around the area. later when i looked at my homepage on the website at the top of that day's list was my hosted event, like it was the last thing i logged. it should have been at the bottom of that day's list of caches, as the first thing i did that day. i deleted and re-logged those caches and they still display out of the order i logged them, with that hosted event top of my daily activity when it should have been on the bottom. i know this is a little nit-picky but I'd like my activity to reflect my activity, and in the order i did it.

 

i had a similar occurrence a day before, but i only attended an event and found a virtual, basically in the same place, so my millage concerns weren't strong enough to delete and re-log, but i bet if i did they'd show up the same wrong order on my homepage that they are now.

 

any ideas?

[+caretaker5]

forgot to add I'm still using the old dashboard as i do not care for the new one.

[+The A-Team]

My guess is that you may have mixed logging methods. For example, maybe you logged the event via a mobile app (which uses the API) while you were on-site, but then logged the rest of the finds through the website. The two systems (API vs. website) use different methods for recording timestamps on the logs*, which can lead to logs being displayed out of order if you use both methods in a day. The best advice is to stick to one system for any given day to avoid this issue.

 

*IIRC, the API timestamps the log with the current time at the time of submission, whereas the website uses 7pm UTC for all logs

[+caretaker5]

i usually log from my mobile and when necessary will update later on my desktop, as i often treat those mobile logs as placeholders that lack details. thanks for the advice, I'll try it going forward.

[+barefootguru]

@The A-Team is correct about different methods storing different times, and one work around.

 

The time is ignored when displaying the log order (annoying design IMO), it's done solely on the order the logs are received in the GS database (Log ID).

 

e.g. if you first submit a log through the website, then submit a log through an app, it doesn't matter what time is on the app log, it will always appear after the website log on both the cache page and your finds.

[+caretaker5]

i went, back on my desktop, and deleted and re-log in the order that i found them and i still have that event which should have been my first find of the day as the last find of my day?

[Moun10Bike]

8 minutes ago, caretaker5 said:

i went, back on my desktop, and deleted and re-log in the order that i found them and i still have that event which should have been my first find of the day as the last find of my day?

 

This is a side-effect of a semi-recent change that forces events to be logged at the time of the event. Even though you logged the event first, the time of the event was at 12:45 PM, so the system writes that as the timestamp on the log. For the other caches you logged on that day, the web defaults to a log time of noon, so they are listed prior to the event.

[+The A-Team]

2 hours ago, Moun10Bike said:

This is a side-effect of a semi-recent change that forces events to be logged at the time of the event. Even though you logged the event first, the time of the event was at 12:45 PM, so the system writes that as the timestamp on the log. For the other caches you logged on that day, the web defaults to a log time of noon, so they are listed prior to the event.

 

Thanks, that would definitely explain the behaviour.

 

I would suggest that this is wrong, though. As mentioned above, prior to this change, the website used 1900Z for all logs, so the submission order wins for sorting. Forcing website Attended logs to use the event time when all other logs are timestamped 1900Z will almost always result in mis-ordered logs. I can't think of a way to work around this new behaviour without completely changing my workflow away from the website, so I may need to hold off on attending any events until this is sorted out.

 

What was the rationale behind making this change? Also, when was it made? I attended an event on May 9th and it still has a 1900Z timestamp.

[+werla]

8 hours ago, Moun10Bike said:

For the other caches you logged on that day, the web defaults to a log time of noon, so they are listed prior to the event.

I doubt that this is the explanation. Because:

I have attached a screenshot of my finds dated May 25th. A CCE is correctly entered as the 11th find of the day. The event time was 14:30. If all the other finds are entered with the same timestamp (12:00 noon or 00:00 midnight?), why are some of them placed before the event and some after? 

[+Chwiliwr]

I didn't look at them all just the ones either side of the event and it doesn't explain your problem if you entered them in a different order but the order shown in the image for the first eight are the order they were entered into the database going by their log ID.

[+werla]

2 minutes ago, Chwiliwr said:

 it doesn't explain your problem 

It wasn't supposed to explain "my"problem. It should show that the above explanation given by @Moun10Bike does not fit. He said: "For the other caches you logged on that day, the web defaults to a log time of noon, so they are listed prior to the event." As you can see from my screenshot, there are logs (all dated May 25th) sorted before and after the event log. According to @Moun10Bike's theory, all regular found logs should have beeen sorted before the event. 

[Moun10Bike]

11 hours ago, The A-Team said:

 

Thanks, that would definitely explain the behaviour.

 

I would suggest that this is wrong, though. As mentioned above, prior to this change, the website used 1900Z for all logs, so the submission order wins for sorting. Forcing website Attended logs to use the event time when all other logs are timestamped 1900Z will almost always result in mis-ordered logs. I can't think of a way to work around this new behaviour without completely changing my workflow away from the website, so I may need to hold off on attending any events until this is sorted out.

 

What was the rationale behind making this change? Also, when was it made? I attended an event on May 9th and it still has a 1900Z timestamp.

 

There is definitely something strange going on. The time stamp for logs posted on the web has always been noon, with the time zone interpreted as Pacific (Seattle) time. I always log via drafts, and when I look at the time stamps for my own events, the start time of the event was being written as the log time starting in 2020, but this reverted back to noon sometime around the latter half of 2022.

Looking at caretaker5's event logs, however, the log time is very inconsistent of late. The last two events match the start time of the events (GCB7JEK and GCB72MA), but are not adjusted for the events' time zone. The two event logs prior to that are set to noon (GCB680V and GCB5TJJ), then the next is again set to the event's start time and not adjusted for time zone (GCANXX1). Things settle down to a consistent noon timestamp in April and before. @caretaker5, do you know if you by any chance used different methods for logging these last few events?

 

I'll need to involve the devs on this and see if they can determine what might be causing these inconsistencies.

[+Viajero Perdido]

I'm watching this thread with interest.

 

I've noticed my sequence of finds scrambled too, while browsing the "diary" output from a GSAK macro, where I sort by clicking the Found Date column before exporting.  I know I've avoided mixing web- and app logging on the same date.  But I've made things more difficult by sometimes caching many time zones away from Seattle and/or London, eg across the Date Line.

 

Some, just some, of my logs end up on the wrong date, eg my log says "last cache of the year", but it shows as Jan 1* whereas the adjacent caches from the same walk show Dec 31, oops.  This example, however, I traced to the fact I back-logged later (on vacation) using the tablet and Locus Map, which has a field for date and time on the logging screen.  I recently figured out that Locus defaults the time to right now, the moment you opened the logging screen, even if you're doing this days later.  I believe I logged those late in the evening, say 12:30am ("logged from a darkened patio in Puerto Vallarta"), and it might've still been yesterday in Seattle.  I need to keep an eye on the time field, and fudge it if necessary.

 

Long-winded, sorry, but in case it helps...

 

* Aha, the web page shows it correctly, but GSAK via all-finds PQ saw it as Jan 1.  I can't brain all this.

 

Edited June 4 by Viajero Perdido
linky

[+caretaker5]

10 hours ago, Moun10Bike said:

 

There is definitely something strange going on. The time stamp for logs posted on the web has always been noon, with the time zone interpreted as Pacific (Seattle) time. I always log via drafts, and when I look at the time stamps for my own events, the start time of the event was being written as the log time starting in 2020, but this reverted back to noon sometime around the latter half of 2022.

Looking at caretaker5's event logs, however, the log time is very inconsistent of late. The last two events match the start time of the events (GCB7JEK and GCB72MA), but are not adjusted for the events' time zone. The two event logs prior to that are set to noon (GCB680V and GCB5TJJ), then the next is again set to the event's start time and not adjusted for time zone (GCANXX1). Things settle down to a consistent noon timestamp in April and before. @caretaker5, do you know if you by any chance used different methods for logging these last few events?

 

I'll need to involve the devs on this and see if they can determine what might be causing these inconsistencies.

I've posted a field log for those events from a mobile device, and then went back and edited additional details about my experience at said event on my desktop at a later time, sometimes even a later date, when i had time. in my most recent attempt to fix my timeline i deleted and re-logged from my desktop one after the next, but just form GCB72MA which was my first event of the day with a start time of 12:45 PM local time through GCB680V which was my last of the day with a start time of 4:30 PM, and GCB680V still shows up in my attempted to fix timeline as before GCB72MA. i also have a similar problem with GeoWoodstock, GCANXX1, on that date/event the event was the first thing i logged. in my timeline the adventure maze, GCANAAA, shows up as the first thing i logged that day. that one wasn't a big deal as the order was just barely off, and they were feet apart.