Team DEMP

Is there a way a regular user can see the date & time for their logged caches?
Is GC still screwed up with sometimes passing dates in local time and sometimes not? 
They REALLY stink with consistently handling date/time/time zones
 

Good deal. I or someone else can update the wiki.

I added a number of tips for ways to use highlights to the How To section. I also added some more use case tips for people.

Good deal - added it and it seems to be working fine. 
http://www.cach.ly/help/index.php/Navigating_Around_the_App
 

See http://www.cach.ly/support/index.php?/topic/1070-how-to-use-coordinates-in-personal-cache-note/ for a similar discussion. 

An option until a more automated solution is considered, would be to go to https://project-gc.com/Profile/SolvedMysteries and add any filter you want such as filtering out found caches, and start updating the corrected coordinate data field. 

Another option, if you are a GSAK user, is to investigate if the corrected coords you have in the cache note are or can be put to another field in GSAK and then run one of several macros that would update the corrected coordinates on gc.com, which of course would then be reflected in Cachly. 
Now that GC has mostly resolved the corrected coordinate mash-up, folks should move to what should now be universally supported. The solutions used by GSAK, PGC and older apps are hacks implemented before things were a bit more consistent. GSAK, PGC and other apps are supporting the official method so folks just need to get that step done. 
 

Thank you for the education. I had forgotten about the logging features as I usually don't cache with the fervor one does at a Mega. For Power Trail like caching with the right setup, a cache is logged by: Log This Cache and Send Now. You can't beat that. 

I default my log type to Found which, if I'm correctly following your steps, would cut the clicks in half.

I can understand Cachly's desire to not assume/rely on non-standard fields to contain unstructured data that individuals want to be interpreted as structured data, especially when it's specific to a 3rd party site. 

I can understand Cachly's desire to not assume/rely on non-standard fields to contain unstructured data that individuals want to be interpreted as structured data, especially when it's specific to a 3rd party site. 

Yes - 20 requests in 60 seconds with each request covering 50 caches. That means 1000 caches per minute and then it needs to pause 1 minute before it can start the next batch. So with 10,000 caches it would be:
Min 1 - 1000
Min 2 - Pause
Min 3 - 2000
Min 4 - Pause
Min 5 - 3000
Min 6 - Pause
...
Min 17 - 9000
Min 18 - Pause
Min 19 - 10000
Min 20 - Pause
Min 21 - 11000

Assuming everything goes as planned. 

I just logged a series of trackables via the app and the 2 fields that are always required are at the bottom of the Log Trackables screen - Log Type and Message. For me, it requires scrolling to select those fields. Please consider moving those fields up on the log trackables screen similar to the order of fields in the Log Cache screen - Date, Log Type, Message, followed by the rest of the fields. 

Cachly 3.0.3, iOS 11.0.3 on an iPhone 7.  It happens with or without clustering.
http://www.falstad.com/zoombug.mp4
 
 

The logic behind the current solution is that full data is needed to display log info while lite data is used for the live map. I recall earlier discussions that it might be a nice enhancement to consider showing that info if available such as offline caches with log data downloaded.

@rragan - Are you also a GSAK user? I know GSAK now has a macro at http://gsak.net/board/index.php?showtopic=32407&st=0&#entry243426 that can update Geocaching.com with corrected coords if they come over from geosphere. Not sure where the wonkiness is or might be in that approach. 

Nic - Not sure of your GC profile so I used rragan (congrats on find #5000) as that should work for you and look the same for me when I describe it. Regarding this specific thread, I'm not interested in it being handled in Cachly but wanted to explain this. 
If you go to https://www.geocaching.com/p/default.aspx?guid=744a4c8e-9c58-4e68-bb57-62576570320a&tab=stats#profilepanel you should see rragan's profile & stats. When you view this page, scroll down to the Difficulty / Terrain grid which is 9x9. A goal is to fill the grid out by finding at least 1 of each of the 81 squares that cover every combination of difficulty/terrain ratings. 
The grid shows the # of caches found in each combination. Completing the "challenge" would show at least 1 cache in each square. "Looping" is finding all 81 x2, x3, x4, etc. If you look at the grid for rragan when I posted this response, you'd see that each square has at least a 2 in it, so he's found all 81 twice. To find all 81 x3, he'd need to log another cache in every square D/T combination that currently shows a 2.

You can easily see the next "loop" but what was requested in the initial post is to look beyond the next loop and look at ones that are in loop+1 & loop+2. 

@rustywa - if you were around a few months ago, some of the folks that replied in this thread were pretty tough on needed enhancements to replace their beloved Geosphere app functions they relied on. It's hard once you are used to an effective process to switch. I haven't popped over to the Geosphere forum lately to see how much complaining there is about Cachly not being Geosphere but I chuckle with how folks are sometimes whining about the tremendous effort the Cachly developer puts towards meeting their needs while they continue to complain. It got to the point where when a thread started here with "In Geosphere.." I just ignored it. :-D 
 
Anyway, it might be pretty tough to come up with an optimal solution for this for 2 reasons:
1) A source of info to use to determine the needed D/T combinations for each upcoming loop
2) Calling geocaching.com via the API for a series of D/T combinations which might not be a contiguous range. It might require calling geocaching with the lowest D/T combine through the highest D/T combo and then filtering out on the client end to limit to just what is needed on the nth loop.  This would cause a large number of cache requests to be made where possibly many are discarded.

As an example of #2, if you needed a 1/5 and a 5/1 as the remaining D/T combos for loop 12, the request would either need to be each unique combination or 1/1 through 5/5 and filter out the 79 D/T combos that didn't matter. if you go with unique calls for each D/T needed in the nth loop, you could make between 0 or 1 or 81 requests per loop. 

Maybe there's a sexier way to do it but these seem the obvious approaches. 

The issue is the geocaching service is unavailable. The web site and any apps that rely on it are not currently working.  See http://status.geocaching.com/ 

Even though API is green, it should be red. I posted about that on their forums. 

Please review  http://www.cach.ly/support/index.php?/topic/652-multiple-logs-for-you-and-your-friends/ for a similar request. 
 

Were you using the c:geo app on Android? If so, that is not an official app and they circumvent the restrictions that official apps need to abide by. What you see in Cachly is what you'd see in the official geocaching app for caches. A basic membership is unfortunately very limited when it comes to the app - traditional caches only with a difficulty/terrain of 1.5/1.5 or lower. In addition, the absurd limit of detail on 3 caches per day as you ran into.You'd see the same thing with the official (and free) geocaching app on android or iphone. It's limited by Groundspeak/Geocaching and not Cachly. 

As for full access, you can continue to use Android/c:geo or get a premium membership which runs $30/year. c:geo breaks from time to time as it is tied to the web pages on the site and not the official API, so that app needs to constantly adjust as the geocaching site changes. 
Again - it's not Cachly creating these limits any of this but Groundspeak/Geocaching.  

I'd start with a guess there is a filter applied that is limiting the search. On the main cachly screen that is displayed when you launch, to the right of the field near the type that shows "Location, GC Codes, coordinates" is a small circle with a gear icon. When you click that, it shows your search options/filters. You can go through that and see if there's anything set you want to adjust or click "Reset" in the top left and go back to the defaults which should display all caches.

Geocaching.com provides an official app and it's free. Cachly is a 3rd party application that costs $4.99 and for those of us that use it, we find it far superior to the free app.
In order to get the most from either application, you need to have the Premium subscription on geocaching.com and that costs $30/year. If you haven't purchased the premium membership you will be limited by what you do in either app because geocaching.com limits your visibility to caches.
 
Do you have the premium subscription yet? Have you found any caches yet? 

First off, welcome to Geocaching and to the Cachly forums. 
 
Cachly is an iPhone application that would provide you a terrific experience when caching. What Cachly would display as available caches is the same as you would see when using the official Geocaching application.

I tried looking up your cache name on the site to see if you were a basic (free) or premium (paid) geocaching.com member but didn't find a match. The reason that is relevant is that the company that runs geocaching.com and provides the data that Cachly can show you, limits the caches based on the membership type (basic or premium).  If you are premium, you have nearly unlimited access to all caches. If you are basic, the official iPhone app and Cachly would limit you to seeing live only caches with a difficulty and terrain rating of 1.5 or less. There are work arounds to get around some of the geocaching.com limitations, but no need to go into that for now.

You can of see all the caches in your area (Maryland) by going to https://www.geocaching.com/map/default.aspx?lat=39.44371&lng=-77.54471&asq=QD0zOS40NDM3MSwtNzcuNTQ0NzEmb3JpZ2luPU1pZGRsZXRvd24sIE1hcnlsYW5kJm90PTMmZz0zMDk0NzkmcmFkaXVzPTEwbWk=#?ll=39.44468,-77.54322&z=11 . I'm not 100% sure if you'll see *all* caches or just the 1.5/1.5 Difficulty/Terrain caches if you are a basic member.  I can't recall if the map filters out the higher difficulty/terrain caches. If it doesn't, this link https://www.geocaching.com/play/search/@39.44371,-77.54471?origin=Middletown,+Maryland&ot=3&g=309479&t=1-1.5&d=1-1.5 might bring them up and click the Map these Geocaches button on the page to display in a map format.

This link would show you the caches with a Difficulty/Terrain (D/t) of 1.5/1.5 or less and have a few favorite points which means other cachers have frequently liked these - https://www.geocaching.com/play/search/@39.44371,-77.54471?origin=Middletown,+Maryland&ot=3&g=309479&t=1-1.5&d=1-1.5&fav=10&e=1

There's a functioning macro on the GSAK site that should properly update the geocaching website with the GSAK approach to corrected coordinates. Apparently in the past, the geocaching website/API didn't function properly in this area but it seems to be fine now and is the preferred approach, at least to accomplish what the original poster was looking for. In the original poster's case, the geocaching site wasn't updated so it was refreshing with the original coords. It seems the original poster would like the updated coords when refreshed which would be accomplished with the GSAK macro. 

See http://gsak.net/board/index.php?showtopic=32407&st=0&#entry243426 on the Gsak site. 

The logging behavior you are looking for is the reason I switched all logging to local Cachly phone drafts and then uploaded as drafts (aka field notes) to the web site. It allows me to edit locally until I upload and then look at the logs on a real computer before I submit them. I was making too many typos and not writing out everything I wanted from my phone and this approach addressed that. Even if I have a full cell signal I still log it locally as a draft and submit it after I'm back home as a draft to the geocaching site.

The logging behavior you are looking for is the reason I switched all logging to local Cachly phone drafts and then uploaded as drafts (aka field notes) to the web site. It allows me to edit locally until I upload and then look at the logs on a real computer before I submit them. I was making too many typos and not writing out everything I wanted from my phone and this approach addressed that. Even if I have a full cell signal I still log it locally as a draft and submit it after I'm back home as a draft to the geocaching site.