Jump to content

alanfreed

+Premium Members
  • Posts

    132
  • Joined

  • Last visited

Posts posted by alanfreed

  1. Sounds good? It's not. Here are the problems.

    1. The calendar is totally useless.

    2. I rarely ever wanted the next nearest cache, so it just added time trying to be "helpful".

    3. Added no value. The things you anticipated, like hints, past logs etc aren't there

    4. You have to use a single caching icon for unfound. This means you can't use customized icons for different cache types. I like to show multi's, micros etc.

     

    Just to present a differing opinion... I use the Geocaching mode all the time on my 60csx. I would argue that the calendar is not "totally useless" for caching purposes. I wouldn't use the calendar for much of anything else, but if I've done a number of caches in a day, when I get home and start logging them, it is EXTREMELY convenient to have a list of all my day's finds in the calendar. When you click "Found" on the compass screen, it automatically saves the cache ID into the calendar... so I have a very nice list of the codes for logging purposes.

     

    I don't *always* use the "next nearest cache" feature, but I quite often do. It's a pretty handy feature for my purposes. If I'm not going to search for the next one, all I have to do is click "Stop," and that's that. No biggie.

     

    You can indeed load the hints into the "Note" field, if you have a little savvy with GSAK. It restricts you to 30 characters, I believe, but more often than not, it's enough of the hint that you can figure out what it's saying.

     

    Anyway... I find this mode quite useful, personally.

  2. It would probably be helpful to have a real address from you to be able to test it out...

     

    My parents' address changed a few years ago for the same reason here in Pennsylvania. Their address used to be "RD2 Box 115" in their community, but is now a standard street address. Their new address does work correctly in CN 2008, for what it's worth.

  3. Ooooh... it would be nice if they added a bookmark list like that!

     

    It is pretty easy to separate the caches by keyword in GSAK, as an alternate method.

     

    Unfortunately, the pocket query generator doesn't have a keyword feature.

     

    The best solution is for one of the AGT project organizers to create a master shared bookmark list of all the AGT caches, and then keep it up to date by adding the new ones as they're published. Any premium member can then run their own pocket query for that bookmark list.

  4. I don't know whether there are maps available or not... but I have definitely enjoyed having the GPS along for cruises! Just having the basemap will be good enough to be able to get a good idea how far you are from land and so forth.

     

    And you can normally find coordinates for various ports of call that you can enter ahead of time... it's fun to be able to see where you are in relation to the next port.

     

    And naturally, I'd do a bunch of pocket queries to load up all the caches at each port!

  5. I'm guessing that you're only using the basemap, and you haven't uploaded detailed maps to the unit?

     

    The map that comes built-in on the 60CSx isn't nearly as accurate as what you'll get with the optional maps, like City Navigator, etc.

     

    The basemap is meant to be very basic, includes main highways and major lakes, etc., but isn't very reliable and is not very detailed. As a result, you could indeed appear to be standing in a lake on the map while you're on shore.

     

    Hi, im new to gps and geocaching and have just bought a garmin gpsmap 60csx. It seems that when it draws a track on the map that it is slightly off. for example driving along a road it shows that im slightly paralell to the road and standing on the shore the trail drawn shows that i was slightly in the lake. Am i doing something wrong, or is there a way to correct this?

     

    thank you for any suggestions!

  6. I have a Palm TX, and I've been very happy with Cachemate and GSAK, too. It's great to have all of those details along without messing with paper all the time. Plus with the WiFI capabilities, it's nice to be able to stop at a hotspot and look up more current information if need be, also!

  7. You read my mind with that comment! It's an awesome feature, and setting it so that this icon automatically appeared would be wonderful.

     

    It really needs the closed chest geocache icon so it works with the geocache functions of most Garmins. Otherwise - looks great!!

  8. It would be very nice if the Custom POI feature would simply work just like additional waypoints. I'd definitely use it much more if that was the case. I'd be great if you could just specify that the unit writes any waypoints to the microSD card instead of its own memory, and just treat those as waypoints.

     

    The bummer about the Custom POIs is the fact that you can't use the caching features, as you mentioned... and that they won't show up on the screen unless you are zoomed in really close, bringing up every other POI in the area.

     

    As it stands, waypoints. GC number as it's name, and the title of the cache as the note. I doubt you'd want to click this link more than 1000 times though. Pocket Queries are still the way to go.

     

    It's not so much the 1000 waypoint limit that is annoying it is the fact that if I am going to use this feature with GSAK and the Garmin POI loader it will put the caches in 2 different locations. This is something Garmin needs to straigten out. As it stands right now the geocaching features on the units are useless if you use GSAK and the POI Loader as it puts them in as custom POI's and does not offer the geocaching features of the unit to custom POI's. In my opinion a massive oversight especially as I have to use GSAK and POI loader due to the fact that I travel to so many different areas I need to store well over 1000 caches in my unit.

     

    Thanks for the info.

  9. To give you an idea of the difference the SIRF chip makes...

     

    I sat in the middle of our high school auditorium (no windows to be found... in the middle of the school), and I was getting a signal of +-20 feet.

     

    The difference is simply remarkable. I bought this unit because I was tired of losing a signal under tree cover. So far, the only time I've seen "Lost GPS Signal" has been in a tunnel.

  10. I picked up a cheap Zire 21 (if I remember correctly) on eBay last year, and it really works just fine for caching. With Cachemate, you can upload a good 3,000-ish caches (including descriptions, hints, recent logs, etc.).

     

    Like most things in life, this made me hungry for a newer Palm, so I got a Palm TX. It has wireless Internet capabilities, so that's cool... plus expandable memory, so I can really load tons and tons of cache information into it.

     

    The paperless caching thing has really been nice -- it certainly beats printing stuff out all the time!

  11. I love my 60CSx, too. I can't imagine using anything other than NiMH batteries, personally. If I'm doing any serious numbers of caches, I just charge 'em up ahead of time (or while I'm en route with a cigarette lighter charger), and I'm good for the day.

     

    Some folks don't realize that there's a setting on the unit to specify that you're using NiMH batteries -- you get a better indication of the amount of charge remaining if you choose that option.

  12. I know for certain it was reading 200+ feet off the mark... that's not the issue.

     

    My home waypoint is set to a specific point in my driveway, and standing at that point (with +-10 accuracy) it was telling me I was 225 feet away. It has always shown my home properly on the map every other time, so it's not as if the map data is off. Plus I have two other GPS units, so I was able to compare numbers.

     

     

    You can isolate the problem by setting a waypoint when you observe the error. Then, when you get home, plot the waypoint on Google Earth or a topo program like ExpertGPS. If you see the same error on the photo or topo, then you know your fix is off. If you don't, you know your GPS unit's map is off.

     

    I just did a cache with my 60 Csx where the map was 60' off. Hasn't happened often, but then, I just got the unit. In my neighborhood, the GPS map is about 20' off (the normal margin of error of the unit). Google Earth is spot on.

  13. My error was at around 5:30 PM PDT. How about yours?

     

    I was having the problem initially at 2:30 (ET) today. We went out to see a movie and had dinner, and I was still having the problem when we got home after 6:00. I dunno... very odd. I wasn't a happy camper there for a while.

     

    If anyone happens to find the previous thread about it, I'd definitely like to read more about it.

  14. I had a weird problem with my 60CSx today... just curious to see if anyone else has experienced something similar.

     

    I did a cache this afternoon, and on the way home, suddenly it was showing me consistently 200+ feet off the road. My tracks paralleled the tracks from my earlier ride on the same road. At home, after turning it off, turning it on several times, changing batteries and so forth, same deal... it would show me more than 200 feet off, even while showing a very strong signal.

     

    I was using my "home" waypoint as a benchmark since I know right where it normally zeroes out.

     

    I eventually took the MicroSD card out, and turned it on, and the coordinates were back to reading normally. And thankfully, they continued reading normally once I put the card back in.

     

    Very weird... and it certainly had me a bit concerned for a bit. I'm just wondering if anyone else has seen this happen before, and whether this is a symptom of worse things to come...

     

    Thanks in advance!

     

    -- Alan

  15. Only 1G for all of North America. That is less than I thought. Cool!

     

    I'm not sure which program you were using, but CN8 takes 1633.8MB for all of North America (including the route calculation data). Without the route calculation data, it's still 1165.4MB.

     

    Some of the older maps are likely smaller, I'd imagine.

×
×
  • Create New...