Jump to content

geo-knot

Members
  • Content count

    30
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by geo-knot

  1. On the screen when you are looking at the main map to choose which cache to find next... It would be cool if when you click on a cache and the information pops up about the cache, any additional waypoints for the cache would also pop up on the map. That way if there are parking coords, or other important locations, you know about it right away rather than when you navigate to the cache. I realize this won't guarantee that the waypoints won't be hidden by the info pop-up.
  2. geo-knot

    Edit and re-order the map list

    There are tons of map options available now which is awesome! My problem is having to hunt for the two or three that I use all the time has it gotten a little harder. It would be awesome if we could edit and re-order this list to put our favorite maps at the top, and hide ones that we never use
  3. It would be cool if when you were creating a waypoint if there was a default name filled in. The first one could be called “stage 2” the second one could be called “stage 3” etc. Note that the first waypoint. Created starts with the number 2, this is because when doing a multi, the listed coordinates are usually stage one. Of course if someone wanted to change it to a more meaningful name, they could.
  4. geo-knot

    A default name when creating a waypoint

    Ah! Much like elevators in Europe where the ground floor is zero. Interesting. In the states, when people say "oh, it's a 5 stage multi" it means that when you find the 5th thing, you have found the final. I know L4C starts it's numbering new waypoints with 1 which has always thrown me off.
  5. Perhaps this is by design... As the GPS gets a better (or worse) signal, the blue dot slowly drifts around as if it's position is an average of the last several readings. The red line on the other hand seems to update abruptly. The result is that the line and the dot sometimes don't line up which can result in a somewhat confusing situation. (see image)
  6. geo-knot

    on map: target line does not terminate at my position

    OK, just thought I'd give you a heads up. Incidentally, you probably saw in the screen recording where things start to move about half way through. The blue dot accurately reflected my location. The red line seemed to be doing its own thing which did not quite compute. So it's not totally clear to me that the map was off here.
  7. geo-knot

    refreshing offline list

    Is there a way to "refresh" an offline list all at once to pick up corrected coords, new logs, and anything else that could have changed? How about images? Thanks, Ben
  8. geo-knot

    on map: target line does not terminate at my position

    This happened again today. This time I took a screen recording of it. The line was going to a completely different place and just hanging out there. Really strange. It was on a google map when it happened. Then I changed to an apple map, and the problem went away. I switched back to google, and it was fine. I uploaded it to dropbox here: https://www.dropbox.com/s/mp6dg6ehnrskry0/ScreenRecording_03-14-2019 14-31-49.MP4?dl=0 I won't leave it there forever, so if you want it somewhere else, just let me know. Ben
  9. geo-knot

    refreshing offline list

    Thanks David, that's exactly what I was looking for. I was expecting it to be on the "..." next to the list name. Ben
  10. geo-knot

    show waypoints on main map screen

    I'm also coming from L4C, so I know exactly what PlasmaWave talking about. It's a nice feature. He is talking about the main (or first) map screen. Tapping on a cache will also show it's associated waypoints, and from there you can select a waypoint to say.... navigate to it. It cuts out a bunch of extra steps. Kinda what I was trying to say initially here. If you decide to implement this, you may like to make it so that when you click off the cache, and the call out goes away, the extra waypoints stay on the map until you click a different cache.
  11. geo-knot

    using the map while navigating

    I know I’ve touched on some of this in another post, but wanted to elaborate a little. Navigating to a cache while using the map screen could be improved… Sometimes navigating with the compass makes sense, and sometimes navigating with the map make sense. When the map makes sense, it is often hard to see the little red arrow that spins around your location on the map that shows your heading. I have good eyesight, but sometimes due to map details, that target line, or sun glare, it is hard to see or make out which way it is pointing without spinning your phone around. I’m also an advocate of having the phone orient the map when navigating to a cache. When this is done, the red target line clearly points to the cache and the little red arrow is not so important. I know cachly can do this, but unfortunately the implementation is not great. The problem is that in order for the map to stay oriented, the map has to be centered on you. That means if you zoom out so that you can see both yourself and the cache, you have 1/4th the detail on the map that you could have if you could manually scroll them map so that it was centered on your target line such that you are at the bottom of the screen, and your target is at the top. I was recently listening to “Inside Geocaching HQ podcast: episode 16: Geocaching app update”. In that episode they chronicle the way that they decided their maps need to orient themselves automatically by default. (also called track-up) Basically they went to a bunch of people, with all different exposure levels to caching. (including some with no exposure). They found that when navigating to a cache, having the map oriented was a big win. You can listen to the podcast for the full details. The end result is that if you try the geocaching app now, the initial map that shows all the caches around you defaults to North-up, but as soon as you start navigating to a cache, the default is track-up. (admitedly: the geocaching app also stops rotating when you are not centered) This setup feels ideal to me for some reason. north-up when choosing a cache to go to, and track up when navigating. Certainly there are some people who prefer north up all the time, but similarly, there are many (and I would argue more people) who would prefer it track-up. The other apps I’ve been using over the years all let you keep your map oriented if you like. Geosphere even let you automatically center the map on the target line in a way that kept you and the cache on the screen, and it slowly zoomed in as you got closer to the cache. I’m really liking cachly, but this is one spot I feel that the other apps I’ve used have a leg up. How would I improve things? I have a few ideas. -when you are navigating to a cache, and set the map to track-up, that it does not stop orienting just because your location in not in the center of the map. -remember that my “navigate to cache” map was north up last time I used it so that the next time I’m on that screen, it is still track-up -add a small compass or some other indicator in the upper right of the map that always points to the cache. This would help especially when you are using the map as north up and whenever using the map to navigate to the cache.
  12. Cachly v 5.0.3(2) iPhone X IOS 12.1.4 I think I found a bug... from the map, choose a cache, then navigate to the cache. On the resulting map, choose a different cache with a different owner, and click on the call out to view it's page. Hit the back arrow on the top left until you get back to the first cache and select "log geocache". at this point my template which contains *|owner_name|* will translate to the owner of the second cache, even though we are trying to log the first cache. Not sure which cache actually gets logged since I caught this before I hit send. Ben
  13. geo-knot

    on map: target line does not terminate at my position

    Interesting, I saw this one today. I was fairly zoomed in, but it did not self correct quickly as I was expecting. It seemed to stay like this for several seconds with little change.
  14. geo-knot

    Text templates and variables

    I love the variables in the log templates, but I sometimes run into a problem... I use the *|owner_name|* which uses the owner's name as listed on the cache page. The problem with this is that a significant part of the time, it comes back as someting like "user1 (adopted by user2)" which does not really fit into my sentence thanking the cache owner. When I used L4C, it would convert the templates when you begin to create your logs so that you could see if it was right, and correct it it it was not. Even better was Geosphere (back when it was the best thing going) It had two variables available. One for the cache owner as it was listed on the cache page, and a second for the cache owners username as it appears on their profile. This second option would be the best, because it calls out the current owner. But if the API no longer allows for that, perhaps there is another way... If you replace *|owner_name|* with the owners name at the time you click "Log Geocache", then you could easily see that there is someting that needs to be edited. I understand it may not make sense to convert all the variables at that time, especially ones relating to date and time since they can still be edited. I also understand that I can always click "Preview" to see how my log turned out, but that's a lot of effort for every cache when I'm using a feature that is supposed to make this part faster. Thanks, Ben
  15. geo-knot

    Text templates and variables

    here's one: GCXE6G . There are a lot of these around. It is a bit of a pain to have to check the preview for every cache.
  16. geo-knot

    can't set target to parking coords

    I started by navigating to GC217J4. Now I want to get driving directions to the parking coords, so I'm trying to set the target as the parking coords, by clicking on the parking pin on the map, then the "...", then "set as target", but nothing happens. It looks like the "set as target" button might be greyed out, not sure. I am able to set it as the target if I go to the list of waypoints, then select that parking waypoint. Note, on this resulting screen, the only pin on the map is the parking, no others, but this seems to be the current implementation. As a side note, maybe we could see other pins on this screen too.
  17. I think this may be a minor bug... When I start to edit my log text (pre filled with a template) the cursor starts at the beginning of the text. When I go to "..." and select "Insert Text Template", it inserts the text at the end of the text instead of where the cursor is. Incidentally, I'd rather that I had a button "Replace Text With Template" to wipe out the text that was there with one of my templates.
  18. Project-GC also recognizes {FTF} or (FTF) without the * . That may be the easiest solution.
  19. geo-knot

    on map: target line does not terminate at my position

    I would not say always, but I have noticed it before. And yes, it generally self correcting. Interesting, it seems that the map framework has some built in averaging.
  20. geo-knot

    can't set target to parking coords

    Ah! I was using Google Standard Maps. I just switched to Google Standard and tried it on GC26PZ5 and was able to reproduce the problem.
  21. geo-knot

    can't set target to parking coords

    Just tried it now without restarting, and it worked fine. I guess the problem is intermittent.
  22. (Cachly 5.0) I have a cache with several user waypoints, and two cache waypoints. The first time I navigated to the cache, the map showed all the waypoints as I would expect. However, if I navigate to it again, it only shows the cache waypoints. I can go into the list of user waypoints, click on the one I want, and it will navigate to that waypoint, but now none of the other waypoints are displayed. One way it seems I can get it to show all waypoints again is to quit the app, and restart it.
  23. geo-knot

    Waypoints on the map, sometimes there, sometimes not

    I guess there are two issues here now. - waypoints disappearing altogether - some or all waypoints show the apple default pin. I've seen both a few times. I'll see if I can figure out any patters. If I do, I'll report back.
  24. geo-knot

    big tip not working

    FYI, I selected the big tip when purchasing the premium maps access, but for some reason, when I got my email receipt, it looked like it did not add any tip.
  25. geo-knot

    big tip not working

    gee, I see I have the 5.0.1 version now, but I think it was just the 5.0 then. I did it right after the new version came out on Sunday, so it's probably all fixed.
×