Nic Hubbard

I will do some additional debugging tonight and post my findings here.

Yes, I can capture the API requests. That is what is puzzling. I submitted a log at basically the exact same time in Geosphere and Cachly, and captured both requests. Comparing them, they are almost identical, but the log on geocaching.com is different.

Thanks, I will use that time zone for testing. I did check when there were the two logs, and I looked using the API and the dates were very similar, see post above. This is why it is a bit confusing. I am not get convinced that the GPX from GSAK isn't doing some sort of conversion on the UTC date. Still investigating...

The part that is so far a mystery to me is that I can submit a log (on Sydney time) in both Cachly and Geosphere, and both show an almost identical UTC date being sent using the API. However, when viewing those logs on geocaching.com the dates are not the same. Cachly's is wrong.

Here is a bit more detail of what I get from the geocaching API: Log 1 (Cachly): Date(1481664900000-0800) http://www.epochconverter.com/timezones?q=1481664900000&tz=Australia%2FSydney Using the converter of that timestamp, it does show December 14, 8:35am. Going to geocaching.com shows the wrong date: https://www.geocaching.com/seek/log.aspx?LUID=f2b8cbbf-c491-46ff-a04b-acddcdbaeebf Log 2 (Geosphere): Date(1481704200000-0800) http://www.epochconverter.com/timezones?q=1481664900&tz=Australia%2FSydney This also shows December 14, 8:35am. Attached screenshot from Cachly where it shows both of the logs on the 14th: Another test I did was to submit a log (on Sydney time/date) in both Cachly and Geosphere. Both of them submitted the same UTC date, which when converted is correct: http://www.epochconverter.com/timezones?q=1481671920000&tz=Australia%2FSydney I think my conclusion of this whole situation is that geocaching.com is displaying the dates incorrectly. It seems that the API is displaying and sending the log dates correctly, and Cachly should be showing the correct log dates as well. geocaching.com does save the dates in the correct non-converted format, but the way they display them is incorrect. As I mentioned before, one of the developers at Groundspeak is aware of this issue, and I hope they can get it fixed ASAP.

As always, I am happy to help. Welcome to Cachly.

I think there is a bit of confusion here. Cachly is exporting a GSAK Note TXT file (same type and format that Geosphere exports). It creates a Field Notes .txt file that is very similar to the .txt format that GPSr units save. This file is to be used in the Geocaching.com access -> Publish Logs menu. Does this help clear things up?

Currently this isn't possible in 2.0, but it will be a new option in 2.0.1 to clear these.

That amount of caches is currently too large for Cachly, as the memory it takes to load that will likely overwhelm your phone. The size limit really depends on your phones memory. We are working on our 2.1 update which will include changes to the database structure which will allow large lists like this with low memory and fast speeds. Stay tuned.

This isn't currently possible. This filtering feature will be added in our 2.1 version.

Great idea. Will get this fixed!

If you aren't already a beta tester then send me an email using the Contact Support option within Cachly and I will get you setup.

I have done some additional testing on this. I have set my iPhone to be on Sydney timezone. I created a log and viewed that created log (and submitted to geocaching.com) and the date was correct everywhere, so I think within Cachly everything has been fixed. Have done this quite a few times in different ways and it all seems to be fixed. However, viewing that same log on geocaching.com has an incorrect date, for the reasons stated in the previous post...

I have been doing some more testing with this and I think I have found a way for Cachly to show everything correctly. However, geocaching.com will continue to show things incorrectly because it seems they do the conversion. The correct data is stored, but they are seeming to convert it. Would anyone want to test these changes in Cachly? UPDATE: I was just told by one of the developers at Groundspeak that they are looking into the date issue on geocaching.com.

The rendering speed on a 5s is currently pretty slow for high zoom levels. We are working to fix the performance of offline maps for older and newer devices.

Thanks everyone for fielding questions when I was gone on Sunday. As stated, downloading offline maps is the way to go. Then you never have to worry about pre-loading tiles, you can just save your caches offline and go!

We really want to put users first. With that as our #1 goal we can make the best Geocaching app possible and provide the best support.

From what I understand about Geosphere is that it back dates the time that you logged it, based on your time zone. I have not yet concluded that this is the best way to do it, because if in fact geocaching.com does fix it on their end, all of those dates would end up being incorrect. I will look into this further today.

Downloading PQs don't have any options because it will automatically download "Full" caches which do not count toward the users daily download count. So that is a good thing. In 2.0.1 it will also automatically download images, but there will be a new option in Settings to turn that off if you don't want that to happen.

Yes, the sorting by distance issue has been fixed in 2.0.1, but thank you for pointing it out.

This feature can be used to upload the .txt file to the Field Notes page on geocaching.com: https://www.geocaching.com/my/uploadfieldnotes.aspx As for GSAK, I don't use it all that often. The feature was developed in conjunction with a GSAK beta tester of mine and did all the testing of this feature. You should be able to import that file and then publish those as finds using GSAK. There isn't currently a way to convert these to a GPX file.

Thank you.

The green dot shows the list that is currently loaded into memory. This can help speed things up if you have a huge list and you want to navigate away and then return to it.

This feature isn't gone and hasn't changed. It is just only available when you are in the Navigate to Cache screen.

I think this might come down to a distance sorting bug we have fixed and will be in 2.0.1, but I will look into this on Monday. Thanks for reporting!