Jump to content

msrubble

+Premium Members
  • Posts

    717
  • Joined

  • Last visited

Everything posted by msrubble

  1. Thank you! Sometimes I can't see what's right in front of my nose. I was considering marking it missing, because I think there's an option to calculate mileage from last known location.
  2. Thanks for the suggestion, but, no, I'm in incognito mode on Chrome. I can see the trackable page. I can see the cache page. I cannot get to the trackable "in" the cache.
  3. I just logged my new trackable into a cache I own, to give it a starting location, and now I can't log it back out.
  4. The same query ran again this morning, and I was able to download it. I didn't want to chance waiting until tomorrow!
  5. A pocket query I ran yesterday was not available for download today when I clicked on it in the Pocket Queries Ready for Download list. I got an error message similar to the subject line. This was also reflected in the URL. The completed pocket query was then deleted from the list, which now shows 0 PQs ready for download. I have not seen this behavior before today, nor any announcement about a change in PQs. This is a query I have been running twice a week for years.
  6. I came here to report a similar problem. A "caches along a route" pocket query I set up years ago shows about 107 caches on the map, but only 31 in the preview list and the download. None of the caches in the download have additional waypoints (for additional stages, parking, trailhead, etc.). Maybe that is a clue. No puzzles or earthcaches are included in the download, although they are in the route.
  7. I see a Raef series out by Amarillo. They are on Raef Road. I don't know whether it has any other significance.
  8. OK, now I can see it. I tried mapping it, accidentally made the window wider when I went back, and there was the list. It seems to take several minutes to load even 100 or so caches. Now, I don't know how mobile-friendly it is, but on my laptop, it has way too much white space. If I maximize the browser window, which I do not like to do, I can see the difficulty rating, but not terrain, date last found, placement date, or trackables.
  9. I cannot see my own hides! Furthermore, when I click on "Filter," the entire browser window becomes overlaid with gray, and I cannot do anything. The gray overlay also takes over if I type a term in the search box and hit the magnifying glass icon. I can tell it to show me 200 results, and I still get zero. Chrome on Windows 10. This is from my profile.
  10. If you want to issue your own custom geocoin (or tag that can be tracked on geocaching.com), see this section in the Help Center: Mint geocoins and trackables.
  11. On one of my own hides, where I had visited the page earlier today. This time when I went to log Owner Maintenance, I get this in Google Chrome on Windows 10:
  12. Same here. Windows 10 and Chrome for a browser. If you hit the "back" button, the white space at the bottom goes away, and main menu is restored.
  13. That's because Groundspeak changed links from the profile and dashboard to act like the "new" search. See this thread in the Release Notes forum: Release Notes (Website: Links now point to new search results) - April 20, 2021.
  14. Do Not Like. I thought I had accidentally agreed to a "new" version of something. Not nearly as useful as the older way. When using a map-based view of caches nearby, say, a frustrating DNF or a challenge I can finally claim, it means an extra click to browse instead of being limited by the "new" view. When reviewing my finds, it is useless without pagination, and with the limit of 1000. Luckily, all of my finds are still sorted by date found at https://www.geocaching.com/my/logs.aspx?s=1&lt=2 , but that does not allow me to filter by type except for events ("attended" logs vs. "found" logs). The recently viewed list is similar to the way my "All geocache finds" list used to look, but way too short for seeing who may have found a geocache after me, and what their experience was. Using the new search results for "All geocache finds" from my profile does allow me to sort by the date I found it, but does not let me see if anyone has found a cache after me.
  15. They came out about the same time. The 64sx also has routable topo maps. It has a bigger screen but fewer pixels. Neither is touchscreen. Battery life on the 64sx is not advertised to be as long as on the 32x. Have you tried an eTrex model before? Do you have a preference between a joystick and buttons on the side (etrex) or rocker and buttons on the front (GPSmap)? Ultimately, it may come down to which you like more. If you liked the older model GPSMap a lot, perhaps you should go for the GPSMap 64x if you can afford it. That would be better than saving money but not getting something you liked as much.
  16. Adopt or transfer a cache Write to the owner and say you'd like to adopt the caches. You can't take over the caches without the owner's permission. If the caches are archived, you could hide new caches in the same locations.
  17. Chiming in late. I use two approaches to choosing a hiding spot. 1. Sometimes I find an area that I think would be a great place for a cache, if there's not a multicache or puzzle blocking it. That's the location, location, location approach. 2. Other times I have an idea for a container I want to hide, and I go looking for a spot that is suitable for it. For this, experience is valuable. As you find more caches by different hiders, keep an eye out for what containers do or don't keep the log dry. And sometimes when I am looking for a spot for a particular container, I find a location that would be terrific for a different type of hide, so the second approach leads to the first tactic. There are exceptions, but usually you want the container to be protected and not just out in the open. At the least, it should not be likely to be blown away, get washed downstream, or get moved to a different location by an animal. I rarely have a Difficulty or Terrain rating in mind ahead of time. One exception was when I wanted to hide a T1 cache that was not a micro.
  18. With chirp, there's a wireless beacon attribute, which I believe is required. Although it could be NFC. One cache I found actually broadcast a wireless signal. I used my ereader to read the message. And no, it doesn't fit "the original complaint exactly" because geocaching is not fundamentally a smartphone game reliant on a specific app. Geocaching was founded on selective availability being turned off and people using their GPS units to hide and find things.
  19. That's what I'm saying. You can exclude T4.5 or higher caches from a search. You can't exclude only the bonus caches that depend on an Adventure Lab. Nor, in your case, can you search for only the bonus caches that show that a new Adventure Lab popped up in a geographic area that interests you. You'd also get bonus caches that are "collect the codes from this series of caches," if the owner has set the attribute.
  20. You can exclude those. There is no way to know which bonus caches depend on an adventure lab. This is a smartphone game, not geocaching.
  21. It excludes people who use a GPS receiver to geocache. Remember those? To add insult to injury, the map of said users is littered with bonus caches that they can't get tied to "adventures" they can't see.
  22. 57 days of caching and 129 cache finds needed to complete the promotion.
  23. The blog mentions feedback in three steps of the process of harmonizing different versions of pages, but the profile page is being presented as a fait accompli.
×
×
  • Create New...