Nic Hubbard

No, those two things are not related. What I meant was, some caches might have 500 photos available for them, especially very popular historic caches. Cachly does not download all these images, it only checks the last 30 or so logs to see if images were included in those logs.

When using the "Download Images" option Cachly looks through the log data that comes from the API for each cache. If the logs that are included (normally 30 logs) include images, those will be downloaded. So likely you will only get the last few images for a cache. We don't download all images for caches because that would require a API call for each cache to find out what images are available (then downloading all images available). If we did try to do that it would quickly exhaust the available API calls that a user is allowed per minute. For example, if you were downloading 300 caches offline, we would have to make 300 requests to geocaching.com, and because we are limited to 30 requests per 60 seconds, this entire action would take over 10 minutes.

Thanks!

I had talked to one of the geocaching.com developers about something very similar (Field Notes) and from what he said, it made it sound like it works now. And that submitting from Cachly we set the UTC time, and it will show the time in your geocaching.com account based on your time zone settings in your user account there.

Do you mean as a .txt file that you would import into a program like GSAK? This is a feature that is in our 2.0 version, although it is for exporting Pending Logs. But, many of our users will create Pending Logs, then export as a .txt for GSAK. Then they will just delete the logs from Cachly.

Can you zip the file and send to support@cach.ly? If not, could you share the file URL through dropbox to that same email address?

Could you contact Support through the app and send the GPX file so we can make sure to test it in 2.0?

When is this crash happening? Any particular action you are doing that invokes the crash?

Thanks for reporting this. It is for sure a bug, and we will get it fixed.

Groundspeak limits users to downloading 6000 "full" caches per day (caches with description, hint, waypoints, logs). And 10,000 "lite" caches per day (basic info like location, difficulty, terrain, etc). Once a user uses these caches up you have to wait 24 hours to load more caches. Unfortunately this isn't a limitation of Cachly, but a limitation of geocaching.com. I wish that there was a way to fix this issue, but the good news is that most users will never even get close to that limit.

Yes, this option is in our 2.0 version that will be released in November.

You can use Cachly on the iPad, as many of our users do. But we do not have a dedicated iPad app that makes use of the screen size at this time. It isn't something that will be in the 2.0 version.

This is a feature in our upcoming 2.0 version. It will allow you to send the .txt in a number of ways including email, Dropbox, local save, etc. This export option will be available from the Pending Logs screen.

This is a feature that we wanted to get into 2.0 but it looks like it will go in 2.0.1. Stay tuned!

I just realized that for some reason that option isn't showing up for GC Regular users. Sorry about that. Will fix!

Looks like you need to upgrade. What version are you using? Current is 1.1.7.

Hi Alex, tap on the more tab and you will see an option for Saved Locations.

Thanks for letting me know. I think it is just a layout issue, and will get fixed in 2.0.

This has been fixed in 2.0 and there is also a new HTML option to view that version.

This isn't currently possible to export as GPX, but I will add it to our feature list. Thanks!

Good to know. Will add this to our feature list.

Like you suspected, this isn't possible with the current API. Hopefully in the future!

It all depends on what advantages it can give us for caching. With the series 1 watch, it was little more than a novelty to build a watch app, as it would have just been better for users to pull out their phone to cache. If the series 2 provides a better caching experience than series 1, then I will for sure develop it. But, if it doesn't, I would rather spend the time to build better features into the iOS app than make a watch app that doesn't really help anyone.

I bought one of the new Series 2 watches as well, so I for sure will be seeing how we can integrate it with Cachly. I hope it will be more than a novelty like the Series 1 one, and I did't see any real value in developing for that one. Stay tuned!

Yes, this is due to memory. This will be fixed in 2.0. Sorry about that!