Nic Hubbard

Thanks for all your quick support; unbelievably fast and greatly appreciated!
Although something I've never done with GSAK (only used for challenge cache verificatin prior to this), I made a small GPX file there and was able to successfully import it.  Since the individual geocaches have no common denomenator among them, I can't make a PQ to pull them.  I'll see if it's possible to make a list on the geocaching site, import that to GSAK, then export to GPX and import into cachly.  If the list option doesn't work, then I'll have to import each individual cache to GSAK as I did for the test file.  Same result, only slower. 

Oh vey! How did I miss this?! Well thank you for making me feel silly, and love this app (and the user forums) even more!! :-)) :-)) :-))

Thanx so far.
I send the GPX to the "Contact Support". :-)

Would you be able to provide a GPX file from GSAK that has only 1 cache that has GSAK corrected coordinates and note? This would greatly help in adding this feature. 
You could just email using the "Contact Support" option in Cachly. Thanks!

Agree. This will be fixed in 2.1.

I have not tried that as of yet.  I will try that out when I have a chance and report back here with the outcome.

Here's some snippets from the GSAK FAQ on Facebook related to corrected coordinates. Might just provide some perspective and the sometimes complex options/interactions...

3.4: What is the easiest way to enter corrected coordinates in GSAK?
A: There are correct and incorrect ways to enter corrected coordinates in GSAK. I will not point out the incorrect ways.
  1. Open the GSAK database with the cache you want to correct.
  2. Use one of the following methods to open the Corrected Coordinates window:
    a. Double click in the Corrected Coordinates Indicator column for desired cache.
    b. Right click cache and choose the Corrected Coordinates… menu item.
    c. Highlight cache then choose the Waypoint menu then the Corrected Coordinates... menu.
  3. The Corrected Coordinates window will appear with the corrected coordinates currently filled in the Lat/Lon box. If you have not corrected them in the past, the coordinates showing will be the original coordinates entered by the cache owner.
  4. In the Lat/Lon box enter the actual corrected coordinates.
  5. At the bottom of the window check the Force elevation refresh check box.
  6. Click the OK button to save the coordinates.
If you correct the coordinates with the steps above, those coordinates will NOT be overwritten by a PQ.

If you correct coordinates in GSAK by using the API to Refresh Cache Data and download corrected coordinates that you have entered on geocaching.com, these corrected coordinates WILL be overwritten by a pocket query and the yellow corrected coordinates indicator will be removed. By using the method above, you are ensuring that a pocket query will not ever overwrite your corrected coordinates. If you did enter your corrected coordinates on geocaching.com and then downloaded them using Refresh Cache Data, the corrected method will be shown in the bottom right corner of the Corrected Coordinates window as “Type: api”. Simply clicking the OK button on this window will now change it to “Type: gui” and protect it from being overwritten. If yours says “Type: api” then the coordinates are susceptible to being overwritten.

More information

3.5: What are the issues regarding the use of corrected coordinates from geocaching.com?
A: There are multiple ways to download caches from gc.com. For this question it is assumed the coordinates on the cache page were changed using the built in capability provided on gc.com for changing coordinates.
GPX based downloads treat the changed coordinates as the posted coordinates. The 'Refresh Cache Data..." API does recognize the concept of "corrected coordinates" and transfers both original and corrected. This is the case for:
  1) Downloading the GPX file for an individual cache directly using the GPX File button.
  2) Creating a PQ that contains caches with manually, online corrected coordinates.
    a) Downloading the PQ manually
     Downloading the PQ via the API
If you download a new PQ onto of your existing DB containing corrected coordinates, the corrected coordinates will revert back to posted coordinates. Doing a refresh of cache data will fix everything.
The short answer is, you can download caches containing corrected coordinates, but you need to run the refresh cache data API to get the corrected coordinates indicator.
Alternatively, you can just correct the coordinates in GSAK and they will not be overwritten by any download method.
To learn how to refresh cache data see question 5.1.

I did test this by importing into GSAK and then exporting from there and it displays properly. In my case my Offline imports come through GSAK at least 75% of the time, just not in when I first tried this TC import. The GSAK solution works for me, but I realize there may be other TC users who don't use GSAK. 

As a Geosphere refugee, who already lives Cachly, this will be a hugely welcome feature!

A little off topic, but I guess there are a lot of "refugees" using Cachly! Great to see an active developer again 

Cachly does have basic URL scheme support:
cachly:// Opens the app
cachly://?gccode=<code> to open a specific cache
Adding more is for sure on our radar.

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.

No Nic, not a excellent review, a excellent app.

The current text on trackables is confusing.  I looked at one in my inventory which was recently discovered by xnard.  The status message says "Last seen with xnard". This made me think somehow it was in her possession. Saying "Last discovered by xnard" would eliminate the confusion. 

Saying "seen with" does seem to imply that the cacher had the trackable in their possession. Using "seen by" would help a bit, but I agree with rragan that "discovered by" is better since it matches the term used for that trackable log type.

Cachly does have basic URL scheme support:
cachly:// Opens the app
cachly://?gccode=<code> to open a specific cache
Adding more is for sure on our radar.

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.

To expand a bit, Geosphere has the ability to display the proximity circles as an overlay on the map, and it's also set to only show on physical waypoints - posted coordinates for physical cache types, and multi-stage and final waypoints. (reference points, parking/trailhead/virtual etc are not relevant for proximity concerns and so don't show the circle).  It's a very useful feature, especially when planning for cache placement in a busier area.

Thanks - that worked

I was using an iPad. I tried it again this morning and it no longer does that. Focus goes to the pin and stays there. Gremlins. I'll keep an eye out for it. 

Thanks for such a swift response - I'm loving this app!
Yes that would certainly be the screen that I would like to see it on - as you say it would not be sensible for the other screens

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.

Posting this for more discussion. Thoughts?

P.S., this is starting to grow on me...
 

You sir, are amazing!  Thank you not only for your super fast response but for knowing just what to do.
Problem solved!
P.S.  Did I mention this already? I love Cachly!

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.