[Can't import caches into Garmin Oregon 450]

I know this is a separate thread but I haven't actually done a pocket query yet... going off to search for instructions.

 

Thanks, all, for your help and information.

 

I think the specs were changed to 2000 gpx files, but that includes all of your routes, tracks, and waypoints, which are stored separately from geocaches.

 

The reason I say "irresponsible" is that by using the "send to GPS" button, you never have to open your GPS in a file window and look at what you have stored on there. Your found caches get hidden from searches on the device, but the .gpx file still takes up space in the memory. I learned this the hard way back when the file limit was 200 .gpx files, and caches I had loaded for an area didn't show up when I got to the trailhead. I immediately started setting up pocket queries that evening and haven't looked back since. Here are some reasons why pocket queries are superior to loading using the "Send to GPS" feature:

 

1. 5000 cache listings loaded in as few as 5 files.

2. Keep your cache listings up to date with the latest logs by running the PQ weekly.

3. Clean found listings off your GPS by selecting "I have not found" as part of your PQ.

4. Keep disabled listings off your GPS by selecting "are enabled" ensuring that you don't go after a cache that isn't there at the time.

5. Never miss a cache. You'll always have caches loaded for the area you are heading.

 

Yes, it seems like overkill to keep thousands of caches on hand, but it means you can make a find on a whim and you're not limited to the few you've added one at a time.

 

That's not to say that the "Send to GPS" function isn't useless. But I use it sparingly, mostly when I've run my PQ recently and then a new cache is posted that I want to run out for the FTF.

[Can't import caches into Garmin Oregon 450]

I didn't know that. Why is it "irresponsible"--could it harm your GPS? It does sound like the best way to do things.

 

 

The Garmin Communicator plugin is built on an old platform that Chrome is no longer supporting. Other browsers still support it, but might disable these plugins by default.

 

Regardless, adding caches one at a time using the "Send to GPS" is at best burdensome and at most irresponsible. That's because your Oregon can only read a maximum number of .gpx files, and the way you go about it, you load 1 file per cache. Meanwhile, with pocket queries, you can load up to 1000 cache listings at a time per file and have all of the caches in an area with you when you go out, which means choosing your caches while you're out instead of choosing them before you leave.

[Can't import caches into Garmin Oregon 450]

Oh, thanks! I had been using Chrome, and I switched to Safari first to try it because I already had it downloaded (was going to try Firefox after that). Safari did the trick. It made me download some software (Chrome had also asked me to download this software but it still didn't work when I did that). SO happy the GPS wasn't broken. Thanks again.

[Can't import caches into Garmin Oregon 450]

I am wondering if anyone has had a similar problem and if they know of a solution. I have a PC and recently I can't get caches to import to my Garmin Oregon 450. It was working fine before. The computer recognizes it as being plugged in but Geocaching.com isn't finding the device. Any suggestions?