Jump to content

Team DEMP

Members
  • Posts

    582
  • Joined

  • Last visited

  • Days Won

    55

Posts posted by Team DEMP

  1. Just an idea to consider. What I do for challenge caches which I qualify is I update the posted coord on GC.com with the same coord. GC, Project GC and Cachly treated is corrected coords. This trick shows a triangle in Cachly even though the coords are the original. 

    I use Project-GC for seeing what challenges as I qualify for and then update the coordinates on the gc.com site for the challenge cache.

    There's no distinction between a solved mystery and a qualified challenge, but the indication would show it might be worth going after.   Just a thought you could do in the interim if a more permanent solution was coming. 

  2. Why use UTM on your GPS as the standard for Geocaching is WGS84? If you create a cache on geocaching.com aren't the coordinates provided in WGS84 format?

    Anyway, you can more easily get to the geocaching.com page from Cachly without having to separately launch a browser, go to geocaching.com and search on the GC code. Instead, with the cache selected, click the 3 ... in the top right and select View on Geocaching.com and it should launch that cache in your browser.

  3. 14 minutes ago, Vividrogers said:

    is it possible to add to a log a bit of text that is always the same and always there (just like an email signature)

    for eg "logbook signed as VR because I'm lazy"

    Yes you can! On the main screen click the 3 ... in the bottom right and go into Settings. Scroll in settings until you find Log Text. Click into that and whatever you write here will be posted to your log.  You can also click the 3 ... in the top right of the Log Text screen, select Insert Keyword and you'll see a list of shortcuts to add. 

    I'm not a "trackable" guy but I think what you want is ... when you are creating your log, scroll to & click Trackable Drop/Visit. On that screen, click the 3 ... in the top right and select All Visted. 

    Those work for you?

  4. My Finds is not accessible/downloadable via the API. It's not a Cachly restriction but a restriction through Groundspeak. You can download it on your own and transfer it if you want though it is a little bit of an oddball PQ file. 

  5. 14 minutes ago, BAMBI11 said:

    from my understanding some users have two nicknames / accounts. Perhaps they go Geocaching in a group or want to log the same Caches. Not everybody is using an iPhone and they want to log all together. Then it makes sense to have multiple users in Cachly at the same time. That means that all accounts are logged in Cachly. Then you can choose what you are doing with the accounts.  There is another Geocaching app in the App Store that already is doing that. That makes sense. 

    When you have to log out and log in with another account the user dates should not be accessible from the other user. So it is fine as it is at the moment.

     

    Through the API you can only be logged in to one geocaching.com account in any application I've used. I can understand supporting multiple users - one logged in at a time. I don't see a need or priority to have 1 Cachly app supporting teams (2+) of individuals. 

    What app is supporting multiple users logging concurrently?

  6. 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. 

  7. 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. 

  8. 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!

  9. 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. 

  10. 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.

  11. 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>

     

  12. 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.

  13. 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.

  14. 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
        B) 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.

  15. 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. 

  16. 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?

  17. 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?

  18. 2 hours ago, Nic Hubbard said:

    I think regardless of the viewing size, if it is a full country, state or even just a city that the solution I posted proves to be interesting, but not practical. It was fun to build, but as much as I would like to be able to implement a simple solution like this, I can see how it won't work.

    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. 

×
×
  • Create New...