Jump to content

wigoweb

+Premium Members
  • Posts

    348
  • Joined

  • Last visited

Everything posted by wigoweb

  1. A search for postal code did turn up comments and questions about zip code problems. My problem seems to be one that other folks have encountered with other zip codes. I guess as long as I can come up with a four letter synonym or near synonym for my three letter-word searches, that four letter or longer restriction on search terms won't be a problem. I still think we should have the ability to search for words that are only three letters long, though.
  2. We are planning a trip to the northern part of our state and did a zip code search for several communities. Most worked just find. When we searched for 08530, all of the results were for Glendale, Arizona. Since we live in NJ where the 08 prefix for zip codes also resides, we wonder what happened for this zip code. By the way, I tried searching for the term zip code search and received the message that at least one of my search terms was less than four characters long. Why do we have to have four characters in our search terms. Zip is probably not the only three letter word that visitors to the forums might want to search. Seems like an arbitrary restriction to me. So, if the zip code search topic has already been explained somewhere, the restrictions on the length of my search term prevent me from finding it. I doubt that postal code search would yield any results, but I admit I just thought of that and did not try it. I will try it after I post this comment.
  3. Why do people cache? Probably as many reasons as there are cachers. We currently are involved in three challenge caches here in NJ. Our state has long had a north/south divide politically, culturally and geographically. A while back a central section became part of the state's awareness. Central Jersey Geocachers started a Central Jersey Checkpoint Challenge. Soon that spread to South Jersey Checkpoint Challenge and then to North Jersey Checkpoint Challenge. Search for keywords, CJCC, SJCC or NJCC to see examples. Each group had volunteers place a cache with a name matching a letter of the alphabet. Each group had a different theme for the alphabetic names. We are "crossing over" into other parts of the state to complete each of the three challenges. We have met cachers face to face on the trail and at informal social events as we planned the series. We might not have met these nice folks otherwise. South Jersey (our section) is relatively flat. I think the highest point in our county is about 30 feet. Central and North Jersey are quite different. We've learned that a terrain of three in North Jersey might be a six at home. We cache to hike. We cache to eat. We cache for the fun of socializing with other folks who like to cache. We cache because our Elkhound likes to get outside, too. All of the caches in these challenges, a total of 82 caches with not one micro or skirt lifter, are there for anyone to find whether that cacher plans on fulfilling the challenge requirements or not. Is this a game open to the public, or is it a game open only to other cachers with similar goals to a particular cacher who only wants people who "appreciate" the cache in the same manner as the cacher who hid the cache? I don't really understand the fuss.
  4. Thanks. I wrote to all three of the cachers who logged the discoveries. If I receive a response, I will post here.
  5. Barry & Jolanda, the cachers who organized the event in the Netherlands just sent us a note that they had not seen the coin. They hope that it shows up in a cache soon, too.
  6. We have put out a few coins to travel knowing that some would disappear. A coin we placed with our granddaughters at our 1400th find last fall traveled about 350 miles to a cache in Massachusetts where it was logged in last January. Logs for Wigoweb 1400 During the past week, we received three "Discovered It" logs for our coin at an event in the Netherlands.*BaJo's* Geocoin Event We have posted notes asking that the person who is sharing our coin please log it in so the mileage gets recorded. We are pleased to see some activity with the coin, but having someone share the coin for discovery without logging the coin takes away some of the fun we get by releasing coins. We have used Babel Fish to try and get a translation of our notes so that we could post them in Dutch as well as in English. After receiving the third discovery log today, we grabbed the coin from the Massachusetts cache and dropped it in the Event cache in the Netherlands. We're hoping someone will tell the person with the coin to read our notes and that the cacher will then update the logs. We would like to see the coin dropped off in another cache and moved along. Has anyone else had coins shared for discovery without having them logged in and out of the caches they were placed into or attended?
  7. We cast a vote in favor of this feature. Some of our coins have scattered to many states and even to Europe.
  8. This morning we submitted a new PQ and had it in our mailbox in less than 2 minutes. That is what usually happens for us. Yesterday was a bit frustrating, but we survived.
  9. Downloading waypoints from Preview. After submitting a Pocket Query: Go to My Profile, click on Build Pocket Queries. Find the Pocket Query that you want to use in the list of your PQs. The second column, named Preview has two icons. Click the first icon. Your list of caches will open. Scroll down and find the button named Check All at the bottom right. Click Check All. Under Check All you will see a button named Download Waypoints. Click that button. When you click Download Waypoints, the caches on that page of the preview will appear in GSAK. Continue on, page by page, until you have downloaded all of your waypoints in the PQ Preview. This requires repeated steps for each page. If you have 500 waypoints in your PQ, you will have to do this about 25 times to get them all. It takes us about 5 minutes to get 500 waypoints using the Preview pages. At least this way we have our data to put into the GPSr with GSAK. Hope this is helpful.
  10. During the past week we submitted several pocket queries which were returned within a few mintues. This morning we submitted two PQs at about 4:22 am PST. We received responses at about 7:22 am PST. These were plain vanilla, run-of-the-mill PQs. One had 99 caches and the other had 100 caches. We were hoping to have them to download into GSAK before going out this morning. We resorted to using the Preview and downloading from the Preview. This work-around worked and our caching trip was not postponed. We really didn't expect to have to use a work-around, though. Thanks.
  11. We're waiting for a PQ since yesterday, too. But, even without the PQ, we wouldn't waste anytime looking for a cache that isn't there. It really doesn't take long to run through the list of caches we are going to visit and determine when they were last found or if they have been archived. No doubt that this will be fixed. It's really a minor inconvenience. I'm always amused at those who paid the $30 annual fee and seem to think that they deserve 24/7 tech support 365 or so days a year. Given the services we do get, $30 is a bargain.
  12. Nice instructions. Cleared up some confusion for me. It seems we have many choices when we work with our GPS units and our computers. The two most obvious are keep everything just like it is and ignore any possible changes (improvements) that become available because software like browsers and operating systems are updated or adapt to the changes and accept that some features we really like will no longer work in the new environment. It's a pain to change, but that may be one of the costs of moving forward.
  13. Sorry for the multiple posts - got a message about a fatal error and a time out. Decided it hadn't posted, so tried again.
  14. Sorry for the multiple posts - got a message about a fatal error and a time out. Decided it hadn't posted, so tried again.
  15. We finally had a chance to do some caching where we located a regular sized container so that we could drop off BrierPatch's geocoin proxy. It is now awaiting a cacher in Hoyt's Quarry near Saratoga Springs, NY. GC141TZ If you're in the area, maybe you can pick it up, see the quality of this proxy, move it along to another cache. We've enjoyed this thread and taking part in moving the new proxy geocoin.
  16. We've been watching for these since they were first announced. We have cache with a Matryoshka nesting theme, so these will be a really nice adjunct to that cache. We ordered four sets. One for each granddaughter, one for our collection, and one that we will activate and use for folks who find our cache to discover. Limited editions are nice; various finishes are nice; our granddaughters wouldn't notice the difference. Some coins we have purchased in various finishes were difficult to distinguish after we had them in hand. If they hadn't been labeled, we might not have known which was antique silver or antique nickel. We just hope for an attractive coin in the standard finish. Anyway, we're tickled that these are available now. Looking forward to receiving them.
  17. Don't know where they went, but I don't see them either.
  18. We have one coin that I was working with this morning which violates the rule suggested in the quote. It is a GeoElement coin and has letters for the first two followed by a digit and three more letters for the remaining four.
  19. For us, trackable is definitely preferable. We have some really nice non-trackable coins, but we like to follow a coin after we have put it out to travel. Of course, only trackables allow us to follow the coin's route. We have coins that have found their way to Europe, Australia, New Zealand, Mexico and Canada. We enjoy the emails we receive when a cacher moves one of the coins. We don't keep all of the coins we acquire. If we were not setting them out to travel, perhaps the trackable option wouldn't be an issue.
  20. We just returned from a trip to Maine and New Brunswick, Canada that took us through several New England states. We found and moved a replicoin on this trip, too. Our mail box was overflowing with coins from trades, but we also had a really nice package from BrierPatch with his "professional" proxy for an Inept Geocoin. Here is a link so you can view the coin/replicoin page: TB2GK6G, a well done replicoin. We would say that this one is definitely not "lame," but we doubt that most cachers would go to quite this much effort. When we place the replicoin, we will post some photos here and on the coin's page. Nice work, BrierPatch
  21. Wigoweb went caching in Lubec, ME and New Brunswick, CA in early August, so we weren't home on Mrs. Wigoweb's birthday. When we returned home yesterday, we found a nice package with some very nice coins and other geocaching goodies. There was a pin, an Atocha coin and a Turtletoes coin plus some swag. Very nice! Thanks for all the work and for all the stuff.
  22. I found a paper coin today described as "ersatz" (an artificial or inferior substitute or imitation). The listing said that the original coin had been stolen and this paper proxy was being sent out as a replacement. I grabbed the paper coin and logged my find. In a few days I will release it to continue its travels. Why should the coin's owner lose the fun of watching the coin travel because of a poor sport who has picked up the original and not moved it along for others to enjoy? This paper copy obviously can't compete with the original, but I believe that by continuing to move the copy along I am thwarting the coin thief if the coin is truly stolen and not just neglected.
  23. Quote: [forthferalz] PS fixed your picture up ( nice coin!) and there is also a trade only category if you want to list your coin in that End quote Thank you. That is so much nicer than just a link. Will give the icon a try a little later.
  24. Added a page for the wigoweb coin with a link to the photo. How do we get the icon to show, too? Thanks
  25. We have tried printing with Firefox 2.0.0.14 and Safari 3.1 with Mac OS 10.4 We also tried with IE 6 and Firefox 3.0 with Windows XP. None of the results was really satisfactory. Somebody at gc.com is doing a lot of work, but we hope the printing functionality will return so that we can print both maps and logs. Thank you
×
×
  • Create New...