Team DEMP

It seems appropriate that what is downloaded under 1 logged in user account isn't visible to a different user account on the same device. Are these users individuals that used a different program prior to cachly that treated the files as application and not user specific? They just need to learn how it works under Cachly. I don't feel it should change.

bcuadrado - This restriction by Groundspeak is also why they were so keen on decommissioning the "old" official application that didn't impose the same limit on basic/non-premium subscribers.

Any GPS in NYC as well as other areas with tall buildings will struggle with what they call multi-path signals. I don't think a phone is any more susceptible to it than a traditional GPS but I'm not a GPS expert. In my informal use of both an iPhone and a traditional GPS (Oregon 700), being used at the same time is the accuracy difference between the 2 is no different from the accuracy difference between 2 folks using a traditional GPS standing side by side.

Nic might have a different perspective, but those are the 2 options that are allowed over the API. I don't think the API provides a way to respect specific data elements so if you get the full cache, any filtering would need to occur on your iPhone and by then, it's already been transferred. So just download the info when you have a decent enough connection before going offline.

When you are typing your log entry, there's a + in the bottom left of the screen surrounded by a dashed box. Click that and you'll be prompted to choose a photo from your camera library or take a new photo. Is that what you are looking for?

No worries and no shame at all !!! There's an annual or monthly recurring member ship option. Once you subscribe on the geocaching.com website, if after a couple of minutes it still doesnt show you are are premium on the site, log out and log back in. Once the Geocaching.com site shows as premium, I suggest logging out in the Cachly app and logging back in there too. Good luck!

There is no Cachly membership, only a geocaching.com membership. There's no Cachly user account in the app, only a geocaching.com account. If you purchased a premium membership on geocaching.com, you will have full access on the site and be able to view unlimited caches through Cachly. Did you buy a membership on geocaching.com and provide your credit card info or Paypal info? If not, you still have a basic free account. If you paid, then log out and log back into your account on geocaching.com and see if it shows you as Premium at https://www.geocaching.com/my/ . On the top right where it shows your Finds and Hides, above that it will show Premium Member. If geocaching.com shows you as a premium member, log out of your account in Cachly and then log back in and you will have full access to caches from within Cachly.

Try this... Go to settings of the main map screen by clicking the ... in the bottom right and selecting Settings from the next page. In Settings scroll to where it shows Fit to Map and uncheck it so it doesn't show any green. Click the back arrow in the top right. And then click Live in the bottom left. Now taking an action on the main screen shouldn't try to fit you and everything loaded on the map into the screen view.

I was able to replicate this situation. Here's what I experienced regarding GC code GCRYD9. Cachly shows 2 waypoints under the Waypoints Cache tab and 1 waypoint under the Waypoint User tab. Unfortunately, I can't attach the GPX or ZIP of the GPX files used to test but if Nic wants him I can email them to him. Test 1: I exported GPX of this file from Cachly and loaded into GSAK. There was a warning message on GSAK loading that the GPX file is in an old format (1.0) and in order to import attributes, etc you need to be 1.0.1. This seems do specifically to the GPX line at the top of the Cachly exported GPX so maybe an adjustment for this, unrelated to child waypoints, needs to be done in a future update. No child waypoint was imported. Test 2: I modified the Cachly exported GPX file from Test 1 changing just the GPX value at the top with what Geocaching.com exports. This suppressed the warning message but no child waypoint was imported. Test 3: I exported a GPX of this cache from geocaching.com for me that has a child waypoint added. I imported this GPX into GSAK and it shows a child waypoint. The differences are the GPX header and that Cachly didn't export the child < wpt > into the GPX, at least from what I can see. Cachly Export GPX Header: <gpx xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0" creator="Cachly" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.groundspeak.com/cache/1/0 http://www.groundspeak.com/cache/1/0/cache.xsd" xmlns="http://www.topografix.com/GPX/1/0"> Geocaching GPX Header: <gpx xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0" creator="Groundspeak, Inc. All Rights Reserved. http://www.groundspeak.com" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.groundspeak.com/cache/1/0/1 http://www.groundspeak.com/cache/1/0/1/cache.xsd" xmlns="http://www.topografix.com/GPX/1/0"> Missing GPX Waypoint included in GC GPX export but not Cachly GPX export: <wpt lat="41.046467" lon="-74.20315"> <time>2009-03-24T18:49:13.37</time> <name>S2RYD9</name> <cmt /> <desc>GCRYD9 Stage 2</desc> <url>https://www.geocaching.com/seek/wpt.aspx?WID=7eb638d3-8249-43f1-9c0a-68aec82154d6</url> <urlname>GCRYD9 Stage 2</urlname> <sym>Physical Stage</sym> <type>Waypoint|Physical Stage</type> </wpt>

Saw this over in the GSAK forum posted by Clyde last night. Not sure of the impact of this change on those using the recently added time zone adjustment option in Cachly. Time zone changes:In order to address long-standing inconsistencies in time zone handling between our website, our apps, and partner applications, we will be implementing a new system for handling time on geocache logs.Currently, geocache logs submitted through the API are converted from UTC to PST. With the upcoming changes, our API will stop the conversion from UTC to PST. The API will pass through the utcDateLogged without conversion and an underlying service will then convert those UTC timestamps to the time zone where the cache is located. Due to the above changes, utcDateLogged timestamps on geocache logs submitted through the API should generally be submitted in UTC without offsets. Additionally, the API will return geocache logs with timestamps converted to the timezone of the cache.Although we understand that not all logs are submitted in the time zone of the cache, we believe that this change will result in many more logs with the date intended by the player.

The GSAK forum post didn't indicate when it might take effect. Was that included in what you received?

Normally if I don't feel I have a need for an enhancement request, I just don't respond as the requestor or others might have a real need that inhibits use or effectiveness of the experience. Aren't there viable alternative workflows that provide the same or better results for the steps you outlined? Couldn't the selected caches be added to a list and the list accessed and saved offline in Cachly with the full cache details? Is there another reason the minimal Loc file needs to be imported? If Geocaching.com provided a GPX to download, would this functionality still be needed? I know I've seen these requests on their forums.

Turn off Search by Cache Name from the top of your last screenshot and try again.

Might you possibly have a filter enabled limiting the caches that would display? As an example, if I only allow Earthcaches and then search for 75238, I get the message you posted. If I have all cache types enabled (or whatever your filters are set to), it goes to the zip and displays caches.

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.

Super quick review, and I have nothing to do with Cachly, is that Terracache outputs GPX 1.1 while Geocaching.com outputs GPX 1.0. This difference causes the structure of the XML GPX files to be very different. I don't know if it's possible to request Terracache GPX output as 1.0 format or if GPSBabel would convert the necessary data effecively. No idea how Cachly is coded for parsing and if it is using a set of routines that know GPX 1.0 and/or 1.1 or if the program is handling via custom XML parsing.

Can you attach the GPX for 1 cache - TC9NH - that you imported? The site requires someone to register to get an example to compare what the differences are. Do you use GSAK? Could it handle the transformation by importing into GSAK and exporting a Cachly readable GPX in the interim?

Sounds great! If we have a cache with info, updated coords, etc loaded from the unified database and you access a cache in the "live" portion of the app, is it using data from the unified database, data provided in real-time via the API or some combination? Or is the unified "offline" database just used when offline and anything "live" isn't referencing the unified database?

Try again, hopefully on Wifi. Also, every few seconds, touch the screen so the phone stays active. Might just be a blip between continents.

I didn't make my point well. I was suggesting that maybe there are options for large areas being displayed, medium areas being displayed, and smaller closeup areas being displayed and the approach could be different. What might work for a country view covering 200 miles x 200 miles might be different from say 25 miles x 25 miles and different from say 5 miles x 5 miles. Or maybe it's less the display area then # of map points/caches. Of course if there was 1 solution that covered all, no worries. But if not, maybe pick a target to shoot for delivering the optimal experience and let the larger areas have a different experience.

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?

At the zoom level in the video, if all caches couldn't be loaded I might rather see clustering as it could provide an overview of the entire displayed map vs no idea about the areas in the video. But at the zoom level you were at I'm not sure clustering would be very beneficial either. What about a map display area that's maybe 50 miles by 50 miles with a few thousand caches? The zoom level in the video, if showing all of Ireland is about 300x171 miles and I'm not sure the use case and how practical it is to show an area that large within Cachly populated with all possible caches.

I seemed to be able to replicate this. I opened a multi cache in live view and put my phone in airplane mode. I went into waypoints and added a new one called stage 3. Cachly seemed to save the waypoint but when I went back out to the live map screen and back into the cache from the map, the waypoint I added was no longer listed. Then I selected an offline list (downloaded PQ) and a multi cache from that list, performed the same steps as above, and when I went out and back into the offline list multi cache, the waypoint WAS there and saved. Still in airplane mode, went back to the live map, selected a different multi cache, performed the above steps saving a new waypoint and it wasn't saved when going out and back into the cache. What I see from the above little test is if you are offline and working in an offline list, Cachly seemed to save the waypoints but not if offline when loaded from the Live map screen.

I usually operate with offline OSM maps regardless of signal. I might temp switch to Google satellite view but then back to offline. I can have full 4G LTE and in usually use offline maps. Not sure the above approach would work for me or what the downside is as I normally Send Now while caching and might not launch Cachly after I'm home and back on wifi.

Is clustering something that is determined by the total number of possible map points in the set of possible map points or is it something that is more accurately discussed within any given map display window on the device at a given time? As an example, if a list has 2000 caches, but only 64 might be displayed at the current zoom level of the map and what is displayed, will clustering of those 64 possibly kick in or might they display the 64 individual map points like we see today? I ask because if I use the official geocaching app, the clustering seems to remain even at a zoom level that Cachly has no issue displaying individual caches. So is the constraint the total number of map points (caches) on the map or total number of map points (caches) loaded that might display even if not on the active screen? And if the clustering would still be there, do you have control over when it unclusters as the geocaching.com app seems to still cluster when it shouldn't. Here's about the 2 same screens showing the clustering behavior in the official app vs what we see today in Cachly. Of course I prefer the Cachly screen because I can see much more info.