Maintaining the sequence of caches found in a single day

[+healing_beam]

For purposes of a challenge cache that is based on elevation change between sequential found caches, I need to make certain that the found order sequence is maintained for multiple caches found in a single day, but the order does not seem to be maintained, even if the caches are logged hours apart.  Is there a way to maintain the sequential order of found logs in a daily list?  Thanks!

[+hzoi]

Well, if you need two specific caches in sequence, perhaps just log the two, then post your qualifications to the challenge. Then, log the rest of your finds (if any) later.

[+healing_beam]

I appreciate the suggestion, but it's an ongoing challenge that will require many, many sequential caches in order.  If I am limited to only logging two per day to maintain the logged sequence, it will take a very long time.  It is GC74X6Y in Turin, Italy, "Stairway to heaven challenge", if you want to take a look.

[+Max and 99]

What a headache!

[+The_Jumping_Pig]

For me, as an android user on the official app, I log drafts right when I find the cache, which saves the time in the system. I then make sure to fully write my logs (edit the draft from the empty text) on either the app or the website and submit them in the order in which they were found. This works for me to keep my caches in the correct order.

[+Smitherington]

I log mine in the field too so they stay in order for my personal trackable map. Keeps the cache to cache distance correct.

 

I found one out of order once and was able to correct the time found on Cachly.

[+cerberus1]

Maybe it's too simple, but I still keep a small notepad with me.  We've marked the time of every cache we've found...

[+peter-tvm]

Unless you find a cache on Mt Everest and at the dead Sea on the same day I would continue to log caches as I found them. The differences in altitude where you live is probably to small to make a huge impact on the result. 

 

If you want to have as many positive difference included as possible use drafts and mark the lowest cache of the day as found first and then highest followed by the second lowest, the second highest and so on. 

[+JL_HSTRE]

On 5/31/2024 at 10:17 AM, healing_beam said:

For purposes of a challenge cache that is based on elevation change between sequential found caches, I need to make certain that the found order sequence is maintained for multiple caches found in a single day, but the order does not seem to be maintained, even if the caches are logged hours apart.  Is there a way to maintain the sequential order of found logs in a daily list? 

 

I've never seen logs end up in a different order than they were submitted. What method are you using to log caches and are you using the same method for all caches?

 

A challenge where the order of the logs matters seems like a terrible idea. Find a bunch of high elevation caches one day, find a bunch of low elevation caches the next day, log all of the the same day but alternating low-high.

[+_dxd_]

Regarding the Challenge, have you run the check to see if you already qualify?   I have fewer finds than you, but I qualify without trying. 

 

That doesn't answer your question of log order of course.  I go old school, list them on a notepad and log when I'm at home so I can use a computer. 

[+healing_beam]

On 6/2/2024 at 7:10 AM, JL_HSTRE said:

 

I've never seen logs end up in a different order than they were submitted. What method are you using to log caches and are you using the same method for all caches?

 

A challenge where the order of the logs matters seems like a terrible idea. Find a bunch of high elevation caches one day, find a bunch of low elevation caches the next day, log all of the the same day but alternating low-high.

I am in the process of doing what you suggested, but the elevation spread between the high and low caches is only about 1000 feet, so it will take many caches to get to 100,000 meters of elevation change.  I'm only at 30,000 meters presently...

[+barefootguru]

15 hours ago, healing_beam said:

I am in the process of doing what you suggested, but the elevation spread between the high and low caches is only about 1000 feet, so it will take many caches to get to 100,000 meters of elevation change.  I'm only at 30,000 meters presently...

What an unsatisfying way to 'pass' the challenge.  This is like people who sign 7 caches on one day, log them through the week, and call it a 'streak'.

[+Goldenwattle]

My logs stay in the order I log them. I have never had a problem with this. I mostly log on my computer, as then it's easier to type the experience. I don't do just TFTC. I can also load a photograph then if I want, which has been run though Photoshop to crop and fix any problems. I can easily edit logs on the computer too. Rarely log on the phone. That's clumsy and slow compared to typing on a computer keyboard.

 

Where are you logging?

[+Smitherington]

I log mostly on my phone right after finding the cache. I usually upload a photo of the log. I sometimes edit the log later on my computer. I never write TFTC. 

[+fizzymagic]

On 6/2/2024 at 5:10 AM, JL_HSTRE said:

I've never seen logs end up in a different order than they were submitted. What method are you using to log caches and are you using the same method for all caches?

 

A challenge where the order of the logs matters seems like a terrible idea. Find a bunch of high elevation caches one day, find a bunch of low elevation caches the next day, log all of the the same day but alternating low-high.

 

There are a large number of such challenges out there.  Any "distance you've traveled" challenge requires the correct order.  Of course, those don't use actual locations anyway so there is no point in even trying to be accurate.

 

And geocaching.com does not let you change the order of your finds.  If for any reason you delete a log or have one deleted, it will forever show up at the end of that day. Not possible to put it back in order.  Sorry.  The database contains a date and time but you can't change the time.

 

So those advocating that you just log your finds in order are sort of right, as long as you never ever make any mistakes.

[+Mausebiber]

Can you please give me the GC Number of this challenge, I only find one "100,000 Foot Challenge" and not 100.000m

 

Thanks.

[+jmirish1]

I log them in the field on my phone and put a sequence number 1, 2, 3, ... then go back and edit them on the computer, add more details, overall stats, etc. I think sometimes I have had them go out of order, but mostly they stay where they belong. Even if I miss logging one in the field until the next day (usually due to lost connectivity) I can correct the found date in the log and it seems to show up (more or less) correctly.

[+Max and 99]

On 6/9/2024 at 3:26 PM, Mausebiber said:

Can you please give me the GC Number of this challenge, I only find one "100,000 Foot Challenge" and not 100.000m

 

Thanks.

100km. 

The geocache mentioned is in post # 3.

[+Mausebiber]

6 hours ago, Max and 99 said:

The geocache mentioned is in post # 3.

Found, thanks.

[+Viajero Perdido]

Why can't Groundspeak sort by date of the find, then by time log was submitted?!?

 

It appears to sort by date, then by [unknown or random].  I see this on the finds list (both new and old code), also GPX downloads.  It's annoying when you've logged the finds in sequence, then later want to review your diary.  It jumps all over the place within the day.

 

(I'm logging with Locus Map in Android, and it does have a time field, which defaults to the time you open the logging screen.  It's fair to assume the app passes that time to the API.)

 

Only in the last year or so has this been a problem.  I seem to remember it working properly for years and years:  Order logged = order reported back.  Can you restore this please?

 

Edited March 4 by Viajero Perdido

[+barefootjeff]

1 hour ago, Viajero Perdido said:

Why can't Groundspeak sort by date of the find, then by time log was submitted?!?

 

It appears to sort by date, then by [unknown or random].  I see this on the finds list (both new and old code), also GPX downloads.  It's annoying when you've logged the finds in sequence, then later want to review your diary.  It jumps all over the place within the day.

 

(I'm logging with Locus Map in Android, and it does have a time field, which defaults to the time you open the logging screen.  It's fair to assume the app passes that time to the API.)

 

I log pretty much exclusively on the website and my logs stay in the order in which I've created them. The only exception is on a FTF when I'll post a field log using the official app as a courtesy to other searchers. Those logs look to appear ahead of website logs but, since I generally don't post the website logs until I get home, I don't know if that's always the case or if it's still following the order created.

[+CAVinoGal]

23 hours ago, barefootjeff said:

I log pretty much exclusively on the website and my logs stay in the order in which I've created them. The only exception is on a FTF when I'll post a field log using the official app as a courtesy to other searchers.

 I do this as well - in addition, somewhere around 100 or 200 finds in, both hubby and I started adding Find # and a timestamp to each log; our son got us started on that, and after 3000+ finds now, 7, nearly 8 years later, it's fun to look back, remember a cache in an area, and see it was our Find #3xx - early on!

 

Adventure labs make this a bit of a challenge - especially if we intermix Ad labs and other cache types, so I keep a notebook with when we found each stage of the lab cache and all the other caches we may have logged that day.  Since Ad labs add to your find count immediately, the numbering gets confusing, but it's a good double check to be sure we logged everything correctly, and the numbers work out properly.

[+Viajero Perdido]

Update:  I just logged a full day of finds using only the website, and it works as expected.

 

As above:  Having logged a full day of finds using an API app (Locus), the results were scrambled.

 

Long known:  Mixing the use of website and an app for the same day, gives scrambled order.

 

I wonder:  What about other API apps, such as "the" app (by Groundspeak), or Geooh Go, or ...?

[+barefootguru]

On 3/6/2025 at 8:06 AM, Viajero Perdido said:

I wonder:  What about other API apps, such as "the" app (by Groundspeak), or Geooh Go, or ...?

Cachly uses the official API and the finds always appear in the order I upload them.