Nic Hubbard

Thank you. Please let me know if you have any questions.

This will be all fixed in Cachly 2.1. There are major performance updates and we have tested an offline list with 50k caches that loads in 2 seconds. Yes, clustering will be used when an offline list is a certain size, but will not be used if under that threshold. This will be a user definable setting.

No, this has not been added yet.

Thanks for this suggestion, will add it to our feature list to take into consideration. Has anyone else found this confusing?

Can you give me some coordinates for where this location is? Just tap on the current location indicator and it will tell you the coordinates. Also, have you made sure to tap reset in Search Options so that you are sure none are being used? ** Note: geocaching.com has been having server issues for the past 2 days, so it might be this issue causing the problem.

Bulk upload feature is coming in Cachly 2.1. You can currently export in bulk a .txt file for upload to geocaching.com or GSAK.

Will look into it.

I have considered using iCloud for features like this. They would be synced across all devices that use your iCloud account (if you login to iCloud). However, this would likely be a 2.2 or 3.0 feature.

Will see about getting this added into a future version.

This could be an easy feature to enhance.

It worked correctly for me. Are you using an iPad?

So sorry about that.

Cachly supports background downloading of offline maps. However sometimes iOS will pause a download and there will be missing data when it is resumed. Try downloading it again keeping your phone from locking and it should work.

Cachly is a third-part geocaching.com app and is therefore also bound by the terms and restrictions of the API that geocaching.com provides. This sadly means that they limit what Regular users see, e.g. only Traditional caches, limited searching, etc. To be clear, this is NOT a limitation of Cachly, but a limitation of the geocahing.com API for Regular users. ** Note: The Classic app used a modified API that we don't have access to. I wish there was a way to provide a better experience for Regular users.

Are you asking if it is possible to show the radius around all waypoints of a cache?

We don't force your phone to stay awake since as you mentioned, there is an iOS setting for this. If we forced the phone not to sleep, user might leave Cachly open expecting iOS to sleep their phone at the chosen interval, but instead it would just waste their battery keeping the screen on. However, adding this feature to the Navigate screen might be beneficial since this is likely the screen that users would be using a lot.

This is on our feature list, but I don't know if it will make it into 2.1.

Did you see the updated screenshot I posted?

So glad to hear it!

In Settings there is an option to "Rebuild DNF Database". This will gather your DNFs from geocaching.com again and should correct your issue.

This is key. It is the amount of caches/pins on the map, and doesn't really matter the map span. Clustering should solve this, as it can be turned on and off based on what zoom level the user is at, which should solve pretty much all the problems, including memory.

I think regardless of the viewing size, if it is a full country, state or even just a city that the solution I posted proves to be interesting, but not practical. It was fun to build, but as much as I would like to be able to implement a simple solution like this, I can see how it won't work.

I think that this solution, as pointed out, doesn't solve the problem in a good way. Back to the drawing board and working with clustering code...

Playing with an alternative to clustering. This loads x number of caches at a time, and tapping a button allows you to load the next x number of caches. It is really easy to cycle through 7543 caches in about 10 seconds. This also keeps memory low because all pins are never loaded on the map. Thoughts on this proof of concept?

Will reply to your email.