Nic Hubbard

This for sure is something I will take into account. My plan is to not even show clustering after a certain zoom level. Stay tuned for more details and testing.

It would crash Cachly.

It currently uses an iOS coordinate parser that, as you have seen, its't very friendly. Implementing the new parser hopefully will be in 2.1.

Clustering. This is a touchy subject. I too hate the idea of clustering pins on the map, and I know many do not love that the official app forces clustering of caches. The reason for this topic. In Cachly 2.1 there have been some major performance improvements. Some users use Cachly in different ways, and some might have 20,000 caches in an Offline List. I have tested 50,000 caches with no performance overhead when loading the Offline List in list view. However, how does one display 20-50k caches on a map? Currently trying to do this uses so much memory even an iPhone 7 crashes. Putting that many pins on a map just isn't feasible. This is where the idea of clustering come into play. Here is what I want feedback about for 2.1: Offline Lists will use clustering by default if the list has more than 1000 caches. Clustering can be turned off for ALL lists with a warning that it might not be possible to show all the caches you want on the map, and it might be very slow. Offline Lists will load in List View by default and not even load pins on the map if the user doesn't want to look at it, thus improving performance. Other alternatives to clustering? So far, I have not gotten far with this.

Can you add a comma between the coordinates and see if that helps?

I do think it would be a lot of fun to build. Working on seeing when we could fit in this development.

Great idea. This is something that we are working on for our 2.1 version. Stay tuned.

Are you meaning specifically the Hint, Cache Note and Attributes text since those are lighter grey?

True. But for the sake of simplicity we use that field for multiple functions.

Yes, this isn't possible because Groundspeak owns the coord.info domain, which is tied to their app, and only their app. Since that field takes GC Code, coordinates or a location search there isn't a way to do this.

These are two sections that have distinct functionality. Live is for live caches that you load while you have internet connection. Offline are caches you have saved offline for offline caching when you have no internet connection or just want to save caches as lists. Let me know if you have any additional questions.

Thanks for the suggestion. Are you meaning in Cachly or in the forums here?

Finally fix the parsing error in that cache. The problem was an invisible unicode character, 0x1f. Hooray for invisible things.

Maybe all users should vote?

That cache should be saved internally by Cachly. Let me log a bug report for this and do some testing.

I also am not 100% happy with the user experience on this screen. Considering having the ... always show, and making sort one of the menu options. Thoughts?

My take on this is to fix the errors as they come in from users so that it isn't an issue for all other users. There are many invalid characters that we currently clean before exporting to XML, so reports like this are extremely useful.

Are you meaning when viewing an Offline List?

Excellent suggestion about adding additional error information in the error message. Here is what it will look like: It wouldn't be easy to skip just that cache as the XML Parser is what bails on error. This is an XML spec error with invalid characters, so it only applies to XML and doesn't affect anything when normally viewing the cache in Cachly.

These options are not greyed out, that is just the text color of the "placeholder" text. Just tap the field and you will be able to type. Yes, sadly this is a limitation of the Groundspeak API.

Just swipe the row and it will show a Delete option. Is this what you meant?

Did you mean having this as a list of options to choose from?

Thanks. It looks like Cachly is using a slightly different version, so that must be the issue. Will get this fixed in 2.1!

In Geosphere, are you using a custom URL to open HERE? If so, what is the URL you are using?

Welcome to Cachly! Do you just mean a feature that zooms the map in the closer you get to the cache? If so, this isn't yet possible in Cachly, but we do have it on our feature list!