Jump to content

MariettaGecko

+Premium Members
  • Posts

    84
  • Joined

  • Last visited

Everything posted by MariettaGecko

  1. Awesome! Thanks! I didn't know about Project-GC. I'll have to investigate this.
  2. I hate to resurrect this one again, but I'm running into this problem, too. In my case, I am working on setting GSAK back up after having been out of things for a long time due to stuff. The result is that I have downloaded the My Finds PQ from the site and imported it, but after doing so the website currently shows one more find than GSAK did. It did show five more finds than GSAK, but I found four of the five caches that appear to have been logged twice. Problem is, despite having been through the pocket query a couple of times, I can't seem to find the last dupe. Any thoughts on how best to do this?
  3. So I'm not sure if this is something going on within the iPhone app, something related to the Geocaching website, or if the issue is somewhere else. I have recently been trying to make sure that I find at least one cache every day, and it has been somewhat of a challenge. However, when I recently downloaded my "My Finds" PQ and ran it through the findstatsgen macro in GSAK, I was dismayed to see that it was saying that I hadn't found any cache on the 8th, even though I *KNEW* I had. Here's what I found after digging into the XML file for the cache in question: <wpt lat="" lon=""> <time>2009-03-08T00:00:00</time> <name>GC1NF8V</name> <desc>Up Above by vallarryH, Traditional Cache (2/2)</desc> <url>http://www.geocaching.com/seek/cache_details.aspx?guid=d001e7ef-21c8-4e64-aa9e-dde968962759</url> <urlname>Up Above</urlname> <sym>Geocache Found</sym> <snip unnecessary details> <Groundspeak:logs> <Groundspeak:log id="83729174"> <Groundspeak:date>2009-09-09T00:31:18</Groundspeak:date> <Groundspeak:type>Found it</Groundspeak:type> <Groundspeak:finder id="125250">MariettaGecko</Groundspeak:finder> <Groundspeak:text encoded="False">Amazing. This one was really easy, despite the fact that it was dark out by the time I got here. I only had one issue with the cache, but that was easily solved. Thanks!</Groundspeak:text> </Groundspeak:log> </Groundspeak:logs> <Groundspeak:travelbugs /> </Groundspeak:cache> </wpt> Now when I looked at this, the date of my log popped out at me: 2009-09-09T00:31:18 Now, don't get me wrong... I will frequently go out caching in the middle of the night or whenever. However, this night, I had to be at work the following morning, so I needed to be in bed, asleep, by that time. As a matter of fact, that's exactly where I was. So you can imagine my surprise when I saw this. How is it that I could be out finding this cache at 12:31 in the morning when I was in bed, asleep? Thinking about it, however, it seems that the time mentioned here is almost exactly four hours *AFTER* the time I *ACTUALLY* signed the physical logbook. Since it is currently Daylight Saving Time, USET happens to be exactly 4 hours behind GMT... Maybe I'm onto something here. I think that what is happening is that the system is saving all the logs posted directly from the iPhone app with the time it comes in, but converting from the time zone to GMT (correctly). However, when the logs are exported in the My Finds query, it DOESN'T tag the log with the time zone, and GSAK assumes that the time zone is the same as the one it is configured to be. Incidentally, I found the same problem with several other tools, so I suspect that the problem is not GSAK, but rather the export utility. Is there any way that the PQ generation utility could reconvert the time zone back to the user's time zone, and tag the time zone information into the date of the log? I'll probably also address this with GSAK and see if Clyde can somehow address the issue as well, but since I think it is erroneous behaviour.
  4. I don't know for sure, but my guess would be that the OPs reason is similar to mine: I like to have a good selection of caches loaded in my GPS whenever I go somewhere. Sometimes I go various places with short notice, and therefore like to have the data all available already in my GPS, or else just a sync to my PC away. Additionally, I have helped maintain a "Lonliest caches" list for my state. Both of these would be good reasons, IMHO.
  5. Incidentally, I would recommend that you be somewhat careful with this cache anyway. It should be relatively safe, but it might be a good idea to post something to the effect that people shouldn't search for the cache after dark. I imagine your neighbors might get rather perturbed finding that someone was out rummaging around in your yard searching for the cache at night with a flashlight, and I wouldn't want you or another cacher to have to deal with law enforcement showing up and harassing anyone needlessly. As for the ALR, I would drop it altogether and, instead, invite people to come up and say hi. It would probably make the cache much more inviting.
  6. I should look it up. What is an ALR? (Associate of Lame Retrocaches?) See I'm so newbie. Additional Logging Requirement (emphasis mine): That's what they're referencing...
  7. I have found another simple way to get around this issue: Set up your PQ(s) to show you only caches which are available. Set up GSAK so that it clears all user flags before loading your PQ, then sets the user flag for each cache loaded by the PQ. Now all you need to do is go through the caches which aren't user flagged and check the status on them, and delete them if they are archived (or mark them temp unavailable, if that's the case). Problem solved!
  8. So, maybe Groundspeak should outlaw such caches! Ummm. Unless I misread the guidelines, they already are outlawed. The chances that the hider would be able to obtain permission to place such a cache are less than 0. That said, I do note that the above post was rather tongue-in-cheek, but I just thought I had to respond to it anyway ;-) Personally, micros in the woods (particularly where there are dozens or hundreds of places such could be hidden) are annoying to me, especially when there is no reason a small, regular, or perhaps even large cache couldn't be placed at or near the same location.
  9. Personally, I prefer to cache using the coffee method. Usually if we are caching under that rule set for the find, I'll step away and comment about having found the cache. Unfortunately, most of the time, when I'm out caching, I'm caching with a group which prefers the Three Musketeers method. That said, on one occasion, I managed to get to the cache before the rest of the group (I was coming up from the bottom of the hill, the rest of the group was coming down from the top), and managed to get it open, sign the log, and return it, then resume searching. It was awesome to be able to make random comments about having found the cache and having the group frustrated at me for it.
  10. Getting back to the OP's comment, however, I can't see any reason to care why the hider archived his caches. I suppose you can get all sorts of upset if you like. I suppose you can rant and rave if that makes you happy. I mean, the rules state no agendas, but there is an agenda in EVERY cache out there. The agenda for every cache is to get someone to go someplace and find something hidden there. Additionally, unless the cache owner trims/whatever logs on their cache, people can post logs with an agenda anytime. In the end, what do you figure that Groundspeak is going to do about it, archive his caches? Oh, wait, he already did that for them. And since I assume that he has removed his caches from their hiding places, they can't very well make the caches active again...
  11. Having just recently bought an iPhone, and the Groundspeak Geocaching app, I have to say that I am both pleasantly surprised and mildly dissapointed. It's really nice to be able to pull up cache data in the field on the fly. I love the fact that, if I happen to be on a 3G network, I can pull that list of caches, select one of them, and enter the coords into my GPS while someone else is driving along. On the other hand, I am slightly disappointed: 1. The GPS unit built into the phone is less than stellar. It works, but it's only really good in flat, open terrain. Get into mountains or under the tree canopy or into the urban jungle, and your reception (and accuracy) goes right down the tubes. 2. You cannot use the Groundspeak app to log the cache once you have found it. If that option were available, I'd be loving it. 3. Use of the Geocaching app requires that the screen be turned on and doing stuff, and the more time the screen is on, the more battery gets used. The battery in the iPhone seems to be relatively short-lived, so this can be a problem as well. So, can the iPhone be used for geocaching? Absolutely. Would I recommend doing it? Not without also having a regular hand-help GPS for the actual routing to/from the cache.
  12. This makes me a sad puppy, although it also makes me seriously tempted to re-learn how to write this code so that I can support this thing and build it out more. I just loaded v1.5, and it's awesome. I love some of the new features. I'll look into the possibility. I believe that there are other people who might be interested in having this software maintained. That said, would anyone be interested in seeing this software maintained and upgraded over time? Or is everyone abandoning this software for Cachemate (or something else)?
  13. Please note, however, that in order to use this feature, you cannot use alternate icons depending on the type of cache. The Garmin GPSMap 60 series and the Colorado series come with a "Geocaching Mode" but it ONLY has two icons to use. The first is a closed cache box, the second is the same thing, open. I know that you can add custom icons on the 60Cx, and so I have done so to use the Geocaching.com icons for the various cache types. The problem with this is that you cannot tell Geocaching Mode that all these icons are geocaches. You can only select one unfound icon, and there's one found icon. While this seems to be a nice idea, it's a little lacking in my opinion. For those who might not understand why this is an issue, I usually keep my GPS loaded with ~900 caches around my home. As I am going about my daily business, I go through and pick up caches as they are convenient for me. The result is that I want to have different images so that, as I'm going by, I can see on the map that this cache is a traditional cache, so I have time to get it, whereas this other one nearby is a mystery cache, so it may actually be no-where near. On another trip, where I have a lot more time, I might be interested in going back after that mystery cache. Or the multi right down the road. Thus, I want different cache icons so that I can tell what's available. Depending on how you cache, this may be a good thing, or it may be a nearly useless feature. That is for you to decide.
  14. Is anyone else having trouble trying to access the site? I've been trying to check for a newer version than v1.4.0, and the only thing I can find is a mirror site which carries v1.3.x. Has the link changed?
  15. Careful... Say things like that, and you'll have someone go log your cache with exactly that phrasing just to get to you... I considered doing exactly that just now, but decided not to.
  16. See, this is kinda reaching the point of silly. By the definition posted here, I could spend the next year logging every cache in existance (except those I have found, or which are mine) with a DNF log. I haven't found it yet, right? Therefore, I did not find it. That's just silly talk. If you didn't even look, how could you have found it? Personally, unless there's some sort of external reason beyond my control which precludes me from looking for a cache, if I don't look for the cache, I'm not going to log it. Such external reasons could include (but aren't limited to): Construction in the area Poison ivy/oak in the area Dangerous insects (wasps, yellow jackets, etc.) in the area. Dangerous animals (snakes, bears, etc.) present semi-permanently closed parking area Basically, if there's something which I feel other cachers need to know about so that they can plan their hunt accordingly, I'll go ahead and post a DNF. However, if I drive along the road and pass a cache just because I missed my turn into the parking lot, I'm not going to DNF that. If I pull into the parking lot and start to search, but have to leave due to rain or lack of time, I'm not (normally) going to DNF that, since I don't feel like I have performed a thorough search yet. To me, a DNF log means I performed a thorough search for the cache and was unable to locate it. In all other cases, I MIGHT decide to post a note, but it depends a lot on how I feel that day.
  17. I personally must disagree with the concept that all micros where the GPS leads you to a parking lot somewhere are bad. I have found a good number of nicely done micros in parking lots. As a matter of fact, I have placed one cache (Gecko Meets Oldschool, in Alpharetta Georgia) which was nominated by the cachers in the GGA for a "best of" award last year. I consider myself lucky to have been nominated, but I'm sure that the cacher who placed the winning cache had a nicely-done cache as well, and apparently, theirs was even better than the one I did. Therefore, I would recommend that just because you find yourself in a parking lot does not mean you should instantly judge the cache as being bad.
  18. So, I understand that we've had this problem before. Originally, geocache numbers were based upon a hexadecimal GC#. At some point, TPTB determined that there simply weren't enough hexadecimal numbers that could be made with GC and 4 characters, so they changed the way the caches were numbered so that each character could be made up from one of nearly 36 characters (yes, I know that there are some which aren't used, but I don't recall precisely which ones... I'm sure it's been mentioned here before, and would appreciate if someone would markwell me). Anyway, my point is that I have recently resumed caching after an extended absence due to Real Life (or some reasonable facsimile thereof) and have noticed that since I had to stop caching for a while, we've gone from GCN or GCP all the way to GCWxxx. I understand that the reason a six character code (GC +4 alphanumerics) was selected is that some GPSs would only handle a four character name when this game first started. Thus my question comes about... what happens when we reach GCZZZZ and someone wants to create a new cache? Have TPTB said what they plan to do?
  19. The question seems to be at what point a DNF is appropriate. I think most people would agree that if you perform a thorough search for a cache and fail to find that cache, it constitutes a DNF. However, this is where the grey area begins to appear. Is it a DNF if you get to ground zero but don't have enough time to perform a thorough search, so you abandon it to return when you have some more time to spend? I believe that the answer to this is "maybe". I won't burden the discussion with why I think it's a maybe. Is it a DNF if you decide to go after a string of caches, and when you get to the parking lot nearest the cache you decide that you're not going to go after the cache for one reason or another? Again, I think this is a "maybe". Is it a DNF if you decide to go after a cache but change your mind before arriving at the parking lot nearest the cache? In my opinion, it could be, but usually isn't. Is it a DNF if you decide to go caching in a general area, but you didn't go to the location of a particular cache? I would say no. If anyone would like me to elaborate on my "maybe" responses, I'll be happy to. However, I feel that most people can answer that question themselves.
  20. I hope I didn't come off as rude. I didn't mean to. I'm sorry if that is how it was interpreted. I am not 100% sure, but I believe it does work with GPX filels natively. I export out of my GSAK into a folder (I named my caches) and then I sync with my Pocket PC. Then I open Cachemate and import the GPX file from the folder that it sync'ed from. I hope this makes sense and I didn't confuse anyone. Again, if my reply earlier seemed harsh, I did not intend for it to. Sharnie Not at all. As a matter of fact, with some of the recent threads going on around here, you came off as downright civil. Sorry I made it seem like you were not. As to the Cachemate, it sounds like it does handle the GPX file natively. That's definitely new. When I last used Cachemate on my Palm (LONG time ago) it was necessary to run the GPX through a tool called CacheMate Convert (CMConvert). Once that was done, it would automatically sync the data to the palm. While this did do SOME nice things, this also caused a few problems... Specifically, it meant that when I powered on my palm, I then had to import the database into Cachemate, and usually ran out of memory. About that time, another cacher introduced me to the Pocket PC and GPXSonar (http://gpxsonar.homeip.net/cs/Default.aspx) and I found that GPXSonar was MUCH easier to use than Cachemate was. Some or all of these things MAY have changed since I last used Cachemate, but I suspect that I will not go back to Cachemate at this point. Perhaps if there's some significant reason for me to do so.
  21. Actually, Cachemate DOES have a version that works on PPC. You can get it from www.smittyware.com. It works great for me. I really like having Cachemate on my handheld. Hope this helps someone. Sharnie I stand corrected. I was not aware that they had released a version for the pocketPC. However, this version, as far as I can tell from their webpage, still does not work with GPX files natively, which GPXSonar does.
  22. Cachemate will only work on the Palm. It does not work on the PPC. However, there is another program you can use on your PPC device. That program is called GPXSonar. This program takes the raw GPX data and renders the cache pages itself. There's no need to do any fancy re-parsing of the GPX that you get through a pocket query from Groundspeak.
  23. As a second example of when an owner might legitimately claim a "found" log on their cache, I have had one experience where I felt that it was reasonable to do so. When I placed one of my caches, I had placed it in a particular location (obviously). Some time later, it was found by the local children who used that park, and left sitting out in the open, along with a log in the logbook indicating that they had known all along where it was. A well-meaning cacher moved the cache to another location in the park for me and provided me(via email) the new coordinates of the cache, as well as some instructions on how to get there. As I wouldwith any other cache, I attempted to use the coords to find the cache. Only when I failed to do so due to the heavy tree cover did I resort to the instructions. I personally feel that since I had to find my own cache, that cache is reasonable to claim as a find. Incidentally, on the topic of moving caches, I would suggest that if someone placed a moving cache (back when they were legal) and said cache is still "alive", and they find it's hidden(by someone else) nearby, I think they should be able to log a find on it if they choose to do so.
  24. I am finally getting a chance to post the things I have in here. I have the following geocoins. Coin names with a number next to them indicate how many of that coin I have available for trade. If you would like any of the coins which have a number by them, please let me know via email through my profile. 2005 Georgia Geocoin (3) 2005 GGA 4th anniversary Geocoin (1) 2005 Georgia Wanna Go! Geocoin (1) Trez's Pirate Trezure Geocoin Today's Cacher squashed nickel (1) Geopirat's squashed coin Canada Geocoin(I believe this is a 2005 series coin, but I am not certain) I am interested in obtaining anything I don't yet have.
×
×
  • Create New...