Team DEMP

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.

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.

I came back to thread when I was notified Nic replied and I see what I thought was a comment I made earlier this morning not posted to the thread. I guess it's sitting unsubmitted on my ipad at home. 

My comment had to do with the display window in your video. I'm not sure I'd look at (approx) a 300 mi x 175 mi area like the screen covers and try to find caches. For me, I'd say a 25x25 square mile area is probably the absolute biggest I'd look at on a cachly screen. Maybe others have a *need* to see all of a country like in the video but I definitely don't. I don't see myself needing to see an entire US state at one time. But if there is a need or a viable solution could allow for it, then great. If not, maybe a smaller coverage area should be the target to come up with the best solution?
 

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 use the Cache Note on the cache page screen that shows Description, Hint, etc. The cache note two-way syncs to Geocaching.com with the Personal notes.

Darn that lame API. I should have known! 

Wherever the official app had the advantage (really a feature that Cachly couldn't provide) it's where Groundspeak doesn't  provide a viable mechanism for apps like Cachly that must conform to their API to provide the feature - messaging, "live" view as you drive, etc. 

I would personally prefer the current sort order over alpha. It matches what I've been recently doing with those most recently used bookmarks at the top of the Cachly list.  Putting them in Alpha wouldn't kill me but it would be less productive for me in how many I have and how I work with them.  Just one person's opinion.

The 27k cache GPX file is too large for the current version of Cachly. The developer is working on supporting larger GPX files in an upcoming release. Until then, you can load multiple GPX files so split the GPX you have if you really need 27k caches loaded on the device at the same time.

Another approach when logging is to enable the Save As Field Note option. You can then edit all your logs as field notes on the Geocaching.Com site vs directly uploading to the respective cache pages.

After you log a cache where it's not sent immediately, it will show under your pending logs list. At the bottom of the main window on the right is an icon for More. Click More and in the screen that opens is an option near the top for Pending Geocache Logs. When you click into that all your pending logs are displayed. You can edit any pending log by clicking it in the list. You can change it there from Found to Not Found. 
In the list of Pending Logs, if you slide one to the left in the list, you will see a standard iOS Delete option to completely remove the pending log.
I hope that helps.

I can almost guarantee you that Nick will reply saying this is a great idea (which it is) but not possible. I doubt it's part of the API because it's not in any app that I know of. In fact there is a current discussion in the GSAK forum where a user is writing a SQL query to get this information from their GSAK database. This wouldn't be necessary if either the GPX file or the API provided this information. 
While it's possible that I'm wrong I know I won't be wrong about Nick replying because Cachly support is phenomenal as you know. 

Or you can load up caches in the Live tab, then tap the ... and choose to save those to an Offline List. Or, you could import a GPX of caches. Many ways to have caches offline.

Absolutely. This is something that I have already added in for 2.0.3. Here are some screenshots:
 

See http://www.cach.ly/support/index.php?/topic/227-multi-cache-experience-trackables/#comment-885 where a similar request for waypoint & projections was requested and discussed.
 
 
 

On the main map page that is displayed when you launch Cachly, click on the map icon displayed at the bottom. It's the icon with 3 stacked squares.
In the map window that opens, the top option is Download Offline Maps. Click Download Offline Maps, then Europe and then Belgium or whatever countries you want to have offline.
I hope that helps.

Thank you!  I had checked all the Safari options in Settings but did not realize the Private button in the browser was sticky. Setting it to off remedied the problem. 

On the main map page that is displayed when you launch Cachly, click on the map icon displayed at the bottom. It's the icon with 3 stacked squares.
In the map window that opens, the top option is Download Offline Maps. Click Download Offline Maps, then Europe and then Belgium or whatever countries you want to have offline.
I hope that helps.

I often do something similar and that would be a handy feature added in the future. 

I wonder if you need to reconsider/alter your workflow.
Right now you have an offline view of data in GSAK with corrected coordinates. 
You don't seem to be updating geocaching.com with that info for some reason.

You also have 2 downloads you are doing to Cachly - 1 from GSAK and 1 from Geocaching.com
So I see the following options...
a ) have 2 different downloads to Cachly and select one to view at any given time
b ) Update geocaching.com with the coords you are entering in GSAK and just download the PQ from geocaching.com to Cachly
c ) Update GSAK from geocaching.com where GSAK retains the corrected coords. You load Cachly from GSAK
d) Possibly, a way to merge within Cachly but not sure if the expected results will be reliably obtained.

Just my 2 cents.
 

Nice catch!

I would appreciate to have this feature for the online-profile-link, too. ;-)

Hi @Nic Hubbard
I tested it this morning and it seemed to work fine. I created a cache note for a cache at 6:00am my time which would have previously shown incorrectly and it appeared on the correct date on geocaching.com. So far so good. I'll do some more logging with Cachly at various times over the weekend and see how it goes. Thanks for all the work you've put in to this. 

Works well in the 2.0.2 beta . Woot!!!

The filtering was just added into 2.0.1 which was just released to the App Store. Update Cachly on your phone and see if the new feature is now available for you. 
It's not an advanced field search as far as I know but a generic keyword search/filter across the offline caches.