Jump to content

Teddy2k

+Premium Members
  • Posts

    113
  • Joined

  • Last visited

Everything posted by Teddy2k

  1. A friend of mine has a swimming cache series... he started with otterboxes, but found that they either kept getting muggled or in fact leaked (weather it actually leaked or one of the finders let water into it is unknown). He ended up switching to preforms for the caches, which are significantly less in price and surprisingly waterproof. He now swears by them for any cache that will be in or around water. The latest cache in his series can be viewed at http://coord.info/GC2DHV5 You can check out (or buy) preforms at http://www.cachingcontainers.com/sfp/Large...cache_Container
  2. To add to this... if you don't want to mess around with a bunch of programs, you could give this a try. http://garmin.na1400.info/routable.php Granted, they're not topo maps, but you know the roads will be accurate since it's based off the OpenStreetMaps.
  3. The 3 PQ's that I outlined in detail in this thread no longer pick up the errant caches on the map preview, however the number of caches is still inaccurate between the map preview and the list preview. #1 - Map shows 728, list shows 793 #2 - Map shows 726, list shows 853 #3 - Map shows 726, list shows 851
  4. Check your subscriptions under "My Controls". If any of the subscriptions indicate "Type: Immediate Email Notification", then you'll get an email every time someone posts a new post in the subscribed thread. If you'd rather have less frequent emails, you can change the subscription type to "Delayed Email Notification", "Daily Digest" or "Weekly Digest".
  5. Chrome, by default, saves all downloads to the default download folder (usually "My Documents\Downloads\"). You can either browse to that folder and move the zip files to a folder of your choice or in the Chrome options, put a check mark beside "Ask where to save each file before downloading". You can then tell Chrome to put the zip file(s) in the folder of your choice.
  6. Since the release yesterday, I started re-doing my old PQ's to take advantage of the new 1,000 cache limit. In doing so, I came across an odd issue where the PQ's seem to be picking up caches that are far outside of the set radius area (including archived and unpublished caches) when previewing the PQ in Google Maps view. For TPTB, if you want to look at the PQ's in question, I have named them "WEIRD 1", "WEIRD 2" and "WEIRD 3". They are all brand new and have never been run before. #1 picks up GCB "Geocache", which was archived long ago and is 300km away from my home coordinates. #2 picks up GC6DD3 "For Whom the Bell Tolls", which is almost 2,200km away from my home coordinates. #3 picks up GC3096 "TD's Chilton County Cache", which was archived long ago and is 3,400km away from my home coordinates. All of the PQ's are configured the same way, except for the Placed between dates: "Any type" "Any container" "That 'I haven't found' and that 'I don't own'" No terrain or difficulty restrictions "Within 'British Columbia'" "From origin 'My Home Coordinates'" "Within a radius of '120km'" "Placed between 'January 1, 1995' and 'SEE BELOW'" No attribute restrictions For the date ranges: #1 is between "January 1, 1995" and "January 31, 2007" #2 is between "January 1, 1995" and "March 31, 2007" #3 is between "January 1, 1995" and "March 30, 2007" NOTE: The only reason that they all start in 1995 is because that's the oldest year selectable in the PQ configuration screen and since I do my PQ's based on date, it only makes sense to start from the earliest possible date. Additionally, I also tried manually setting the coordinates in case it was an issue with the "My Home Coordinates" selection, but I got the same results. The key here is that each of the 3 listed caches above only show in that respective PQ and none of the other ones. If I change the end date even by 1 day on any of them, that cache will disappear and a different one will appear. For example, if I change the end date on #3 to April 1, 2007, GC3096 no longer appears, however GCB723 "Living Pond" does (which looks like it's actually unpublished). As I said before, this appears to only be an issue when previewing the PQ in Google Maps mode. These mysterious caches do not appear when previewing in List mode, so it could conceivably be an issue with the Google Maps programming or something.
  7. BC's First Cache - GC1DD Treehugger
  8. Garmin Dakota 10 Bike & Hike Bundle - $289.99 @ Costco.ca This is definitely a deal and a half at $79.96 off regular price. Most other stores have this bundle for sale for $369.95. http://www.costco.ca/Browse/Product.aspx?P...-_-GarminDakota
  9. I use Markwell's method of setting up my PQ's... I have multiple PQ's that have different date ranges and span over multiple days each week. I also ensure that none of my PQ's reach the current 500 cache limit. Today, when I downloaded them, GSAK notified me that one of my PQ's had hit the 500 limit. Upon investigation, I found that 2 of the settings for that specific PQ had been modified (without my knowledge). 1) The date range used to be set to Jan. 1, 1998 - September 30, 2005. It had been changed to January 1, 2011 - September 30, 2005. 2) Under "That (And)", I used to have "I haven't found" and "I don't own" checked, but this morning, only "I haven't found" was checked. First off, yes, I know there aren't any caches from 1998, but that was the oldest year in the drop down menu and this is for my PQ that catches all the oldest caches in my area. I now notice that 1995 is the oldest year in the drop down menu. As for the checkboxes, I began checking the rest of my PQ's and 74% of the rest of my PQ's had also had the "I don't own" box unchecked. The PQ's that were not affected seemed to be the ones that grab the newest caches in my area. So, I'm wondering if this happened to anyone else? Since the year drop down now goes to 1995, I'm thinking that perhaps one of the developers made a change that had some unintended side effects. It's not a huge deal for me, but I do have to go back to all my PQ's now to correct these changes. You might want to check yours as well, just in case.
  10. Interesting... I just realized when I posted the field notes that the dates ARE on March 14 when in UTC time. This definitely appears to be a site issue... it's converting the UTC times to the local timezone for the list of field notes, but apparently doesn't do it when composing the log for each field note.
  11. I'm also noticing this behaviour, but I don't think it's a Garmin issue because the fields notes are simply stored in UTC time and hence, time zones are irrelevant (at least until the field notes are uploaded to geocaching.com). After uploading my field notes, I find that the list of field notes has the correct date and time, but when I click the Compose Log link, the Date Logged changes to the next day. Exhibit A - Fields notes list with correct date: Exhibit B - Post a New Log with incorrect date: Exhibit C - The original field notes file from my Colorado 300: GC22EZE,2010-03-14T00:01Z,Found it,"" GC22BCY,2010-03-14T00:11Z,Found it,"" GC24D5D,2010-03-14T00:27Z,Found it,"" GC24EY3,2010-03-14T00:43Z,Found it,"" GC22BD6,2010-03-14T01:13Z,Found it,""
  12. Just a reminder that this sale goes until Feb. 28, 2010. Here is the updated link. (link)
  13. EDIT: Disregard, I just noticed that this was bumped from 2006, but the "Geo Fashion Blog" is pretty funny.
  14. Teddy2k

    PQ problems?

    I ran a CAAR PQ this morning and got it fine, but the normal PQ's that I created have not run yet.
  15. Welcome lornix! Glad to hear that you've enjoyed yourself so far. If you ever need any help or advice, feel free visit the BCGA forums where you can pose questions to our members. I'm sure there are quite a few members in the Surrey area that would be willing to meet up with you for a day of caching as well. http://www.bcgeocaching.com/ Teddy2k -- BCGA Vice President
  16. The website throws up the 500 error every time you click the Groundspeak Goodies link from the Resources page. http://www.geocaching.com/goodies/default.aspx
  17. Groundspeak just posted this to their Twitter account... great news!! For all those who have been asking, the geocaching app for Android will be available sometime in Q1 2010 http://twitter.com/GoGeocaching/statuses/7450369044
  18. Awesome, thx ibycus! I'll continue seeding for a long time after it's done downloading to help with the distribution.
  19. Indeed, the Great Coal Rush event in Tulameen last year was one of the best events of the year and this year's event should be even better! If there's one BC event that you should be attending this year, this is the one!
  20. 90%Angel, I look forward to meeting you at the event on Saturday! I live in Bridal Falls, so nice to see another new local cacher!
  21. I haven't had any issues with my scheduled PQ's in a long, long time. All of them seem to arrive around 3am at the latest, including today's.
  22. Zero returns for me as well. Bought it in December 2008.
  23. Forgive me for being brash, but the quoted comment is very ignorant. The site is designed to log you out automatically for security reasons. That way, if you leave your account logged in on a public computer, the next person can't hijack your account. You are the one that chose not to use the "Remember Me" function and hence, you need to accept the consequences. WRASTRO said it best..... "save early, save often". What an immature reaction to something that has affected the logging of 1 cache out of your 2,177 finds. Let's grow up and move along.
  24. Teddy2k

    Fire danger

    That seems pretty broad.... isn't most of North America under a high level of danger due to fire in the summer??
  25. I have submitted several reports to Navteq for missing/incorrect POI's and they have all been acknowledged/corrected. Some took a LONG time to be corrected, but it was done. I also just checked the POI's in question on the CityNav 2010.20 update and they have in fact been corrected.
×
×
  • Create New...