Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by DrDaffy

  1. Hi,

    some time ago I noticed a problem with the handling of decimal separators in Cachly for german users. One part seems fixed, but there are still issues:

    Coordinate projection:
    When entering bearing and distance you get the numeric keyboard and for german users the decimal separator will be the comma. The bearing seemed to be interpretated correctly now since 90,1 gave me neew coordinates in the east. But it looks like the decimal places ar ignored. I made another test with 180°, 180,1°, 180,9° and 181°. I would have expexted that 180° and 180,1° give nearly the same result and 180,9° and 181° give nearly the same result. But the resulting coordinates for 180°, 180,1° and 180,9° are all the same. This can't be right.
    And the distance is even worse. Giving a distance of 50,01 m the new coordinates were 5 km away instead of roundabout 50 m.

    Pasting coordinates:
    Similar probleme here. At this place I have a normal keyboard thus I have the possibility to use a dot and I can work around, but it is annoying. At this place both should work because german users will usually get coordinates with dot when using internet tools but coordinates with comma when using tools on their phone which respect the language settings. Since dot and comma won't appear together (N52° 28.123 E9° 50.123 OR N52° 28,123 E9° 50,123) this should be possible.


  2. Just tested with a new cache I never touched before. Going back to the offline cache while my phone is offline showed the same strange behaviour as before:
    the corrected coordinates show up in the list of user waypoints (normally the coordinate ovverride doesn't show up in the list of user waypoints) and in the list of cache waypoints the original coordinates show also the corrected coordinates.

    Go back online, switch to the main page of the cache, pull down to update and the waypoints are fixed: no user waypoint and original coordinates which are the original ones

  3. Thats right but the caches where I first encountered this problem were done 1 week ago and downloaded for the first time 2 weeks ago. By the way: what meens 'long time ago'. It's only half a year ago I started using Cachly.

    If it helps I will repeat this test with a cache I never touched before

  4. Just tested. What I did:

    • Create a test list
    • Go to live view
    • Select a cache with corrected coordinates
    • Selected 'Add to list' from the 'list actions' menu
    • Add to my list
    • Switch to list
    • Selected cache from list
    • Go to Waypoints

    Result: A user waypoint named 'Coordinate override' with corrected coordinates and a cache waypoint named 'Original coordinates' also with the corrected coordinates

    • Go back to the main screen of the cache and pull down
    • Return to waypoints

    Result: No user waypoint but a cache waypoint named 'Original coordinates' with the original coordinates (this is what I would expect)

    • Close Cachly
    • Go offline
    • Start Cachly
    • Select the test cache in the test list
    • Go to Waypoints

    Result: A user waypoint named 'Coordinate override' with corrected coordinates and a cache waypoint named 'Original coordinates' also with the corrected coordinates

    Hope this helps.


  5. Cachly 5.2.5 (1)
    iPhone 6
    iOS with iOS 12.4

    Yes, I can replicate this. Just switched my phone offline, took a Cache at random from one of my offline lists, looked at Waypoints\Cache\Original Coordinates and it showed the corrected coordinates instead of the original ones. Then I switch my phone back online, go back to the main screen of the cache, pull down for update, go back to the waypoints and the original coordinates are OK.


  6. Yesterday I was caching and had an issue with Cashly. At one point on our hiking tour in the mountains we had problems finding a cache and wanted to check our coordinate projection. Based on what Cashly showed as 'Original coordinats' in the list of cache waypoints we did the coordinate projection again. Unfortunately what Cashly showed as 'Original coordinates' were in fact the 'Corrected coordinates'. So I made a second projection on the already projected coordinates and ended at a completely wrong place.

    I attached three screenshots. They show a solved Mystery. You see the main screen of the cache with the corrected coordinates and two screenshots of the waypoints. Once it shows the 'Original coordinates' as they should be and once it shows 'Original coordinates' which are in fact the corrected coordinates.





  7. Hi,

    This morning I realized the handling of trackables stopped working. Whenever the inventory of trackables is accessed (trackables in bottom menu or while logging a cache) I get an error message:
    "kilometersTraveled is not a supported property Parameter name: currentProperty" (see screenshot)

    I restarted Cachly and also logged out and back in to my GC account - didn't help.


    TB Issue.png

  8. Markups for bold and italic text are lost when editing logs.

    This morning I created and posted a found log while I was at the cache. At home I edited this log to complete it. The screenshots illustrate what happened. The screenshot with the ** shows what I saw while editing the log. The screenshot with the bold text is what I saw in the preview. And the screenshot without ** and bold text is what is online after I posted my changes. 

    iPhone 6/iOS 12.3.1/Cachly 5.1.4 (2)






  9. A real tagging system, where several tags can be assigned to a cache instead of only one color marker (I know, we had this topic in another thread :-), might solve diorex problem. But yes, I know, this would be a major change that is not planned.

  10. On 6/3/2019 at 6:33 PM, Nic Hubbard said:

    I agree there is room for improvement. I will look at past a certain zoom level, only center the map and don't zoom in. Meaning, if you are looking at the whole world, tapping the location button would zoom and center. But, if you have already manually zoomed in to a certain level, Cachly would honor that level and just center the map.

    And this zoom level can be configured? Because different users willl probably have different ideas regarding the zoom level that should be the threshold between "preserve zoom level" and "zoom in".

  11. Hi,

    right now I make preparations for my vacation and that drew my attention to something. I have a lot of lists and sometimes it's hard to keep track of them. But they fall into certain cathegories:

    1. Some default PQ covering my home zone
    2. Several lists for different cache series I want to keep track of
    3. Lists of caches for completing some challanges
    4. Lists for vacation
    5. Misc

    It would be helpful if I could organize these lists in folders



  12. 4 hours ago, Nic Hubbard said:

    Since these are user definable label names it is up to the user to remember what custom names were given.

    To be honest I expected your answer to point 2 :-), but would it be so hard to implement point 1 and show the name of the marking color in the cache details? I think it’s a relativ small change with great effect. 

  13. 1.) Meaning of the markers
    Starting on the map I see a cache with a black marker, but have no clue what it means (Screenshot1). I open the cache details, see that it's marked with the black marker, but I still have no clue what it means (Screenshot2). In order to get this info I have to edit the marker of this cache (Screenshot3) and finally in the list where I choose the color for this cache I can see the meaning of this marker/color.
    At least that's the only way I found.

    2.) Multiple markers/tags
    I think it would be great if these markers were used like tags and you could assign several tags to a cache. I attached an edited screenshot (Screenshot5), which might make this clearer. On the one hand you can see what the markings/tags mean (see point 1) and on the other hand it shows a cache to which two tags have been assigned.

    I hope this make my ideas clearer.







  14. 13 hours ago, hidegoseek said:

    I'm not sure that percentage is the best metric when planning a trip and looking for favorited caches.  I have a cache with 100% favorites, but there have only been 4 finders so far.  I think cachers would rather look for my cache that has 67 favorite points (but only 26%).  

    You might prefer the absolute count of favs, but agree with Attila_G that for many cachers it would be great to have the % value available. I also prefer the % value.

  15. Hi,

    I just had a look on the new named markers. Great improvement, but it's a pity that I can't see the meaning of the color when looking at the marked cach. I have to edit the marker in order to see what the current marker means. That seems very awkward to me.

    Also it would be helpful to be able to assign more than one marker.


  16. Hi,

    when I discovered the new icon (and the updated app:-) I went straight to the waypoints to check if the duplication error is fixed. Great, that worked but there are new issues. I created a waypoint ‘Test’ which shows up in the list with the strange name ‘UW2W3EDM Test’ (see screenshots 1 and 2) and when I try to delete it I get an error message complaining about a missing reference code (see screenshot 3).





  17. Can't wait. I frequently have this problem. Once I thougt it was my fault because I created my drafts in the wrong order. But often this is not the case. I simply open Cachly start writing a log and the counting is one off. Sometimes it helps to go back to the map and then back to the pending logs. Sometimes I have to close Cachly and sometimes I fix it manually.

  18. Hi,

    any news to the feature discussed here. Recently I had a talk with a fellow Cacher. I had a question about a waypoint and a minute later he sent me a photo of what I was looking for. This was so fast, I was amazed and asked him if his Geocaching app was able to store photos related to the caches. He answered: No, unfortunately not. For some time he maintained a Evernote cache database, but finally he abondoned because the extra work of managing cache fotos in another app was too cumbersome and time consuming.

    This would be a great feature ...

    1. for those who like to document their caching
    2. for those who want to remember nice caches with photos they cannot store in the found log
    3. for stages of multis (always helpful to be able to look up again whether one has noted down the last coordinates correctly)

    Sure, you'd have to think it through. First step would be to store personal photos with the cache locally on the device with the possibility of a structured export (e.g. one dir with GC code and cache name per cache). This would ensure that nothing is lost and can be transferred to a personal photo starage location later.

    iCloud sync could be a secont step/improvement.