Jump to content

dirtisgood

+Premium Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by dirtisgood

  1. I know who Hobo is talking about... and it's all about the numbers. Look at his profile and it's all he can talk about, how he's the first this or that. First with triple digit hides, finds, TBs, events, whatever. I thought of spoofing it like first to find a cache with a migraine headache, or first male to find a cache while wearing a wedding veil, etc. Most of these hides are film canisters with torn paper logs, in uninteresting places like mileposts or lampposts. Some finds are also film canister replacements when he couldn't find the original, but that's just how he plays. Give him the numbers, let him brag. For the most part, I've ignored these since I first figured it out. I'll still grab one now and then, but I don't specifically seek them. However, I do wish people would place caches with the knowledge that their placement isn't a small dot on a map, but a large (.2mile dia) circle. To run through town on the side of the freeway stopping every .1 and tossing a film canister out the window is also a good way to blow some planning and researched cache placements. I have one I've been working on for a month now, waiting until the right time to submit it, because I want it done well, not quickly. I guess someone could come up and stick a bison tube in the brush while stepping on my well concealed container and submit that micro. Maybe that's the chance I take, but I'll have to take it.
  2. I know I'm slow on this reply, but I stopped at a fairly new local fishing hole one day to check it out. I talked to several guys who caught close to their limit and just as I was leaving, I realized I had this calendar. I went back and asked if the fishing was good for the two hours that ended just an hour before, and he recalled that the good luck they had did indeed end an hour before. Maybe a coincidence, maybe it's correct.
  3. Precisely.The PQ limits are in place to make it more difficult to create off-line databases. Jeremy has been quite clear about this. I stand corrected, although it doesn't seem very convenient.
  4. Hard enough writing down the cache code number to log it as a find. At least I can remember a name sometimes if I forget that. Besides, just how small do you think an evil nano hider could write that code down on a grain of rice hidden in a sagebrush or pinecone? That would just be torture. It's bad enough that I have to carry tweezers, I don't want a jeweler's loupe in my bag.
  5. My eXplorist holds significantly more than 1000 caches. I've only used about 12% of the available memory I had on the internal memory and I have about 1600 cahes loaded, several routes, track logs, etc. I have lots more room, and an emply SD card slot. I could theoretically load the entire GC database Not really, the system doesn't give me a nice chunk of info in the areas I want, without getting a simple radius filter... GSAK gives me polygon areas, arcs and lines, radius' to NOT include in the search, etc. Precisely. Just don't allow it to be run all the time! Set it up internally so that it is run only once per state, per week. (as opposed to once per state, per week, per user) When (and if) the file is requested, and you could set it up that it must be specifically requested, the file is emailed to the user. GSAK is not competition for GC.com, it is a wonderfully brilliant enhancement to an excellent site (GC.com) GSAK is what tipped me over the edge to subscribe to GC.com, and I doubt I'm alone.
  6. Some can get a query of every unfound cache in the state that they want with 1 PQ. If you're fairly new, it will take 15. The biggest thing to remember is the load on the database and email server. 15 or 16 PQs to get a full database by dates is a LOT more of a load on both of the above than a full state query run once (on the database server, then stored for the day/week and emailed to all requesting it. Run it on Thursday night, so all those requesting it have it by Friday and the weekend hunts. The overhead of the email server is lower, and the database server is not thrashed with PQs all week long by hundreds of people (do the math, that's thousands of database queries instead of one per state) Remember that the query is looking first for the state, (at this point in a state query, it is done.) then it looks for those caches meeting the date criteria. It does this multiple times per day, per person, each with slightly different dates it seems. Seems to me that a state query would save server time and money. A win-win situation. BTW, searching for Reg & Large, 4 or less T&D, traditional, unfound, active, etc, gives me 498 in a radius of only 32 miles. What if I want to go into the mountains? A PQ for each mountain range? Then we're just as well getting the whole 16PQ list for the state.
  7. Just a thought, but could it be the pocket queries slowing down the system? I hunt in a large area and like to have an up-to-date database of the area's caches. This takes 16 pocket queries to get all of them, because Utah is a big state with a lot of caches. Could these be done with just one query of the state in the future? That would clear up a lot of server time, and probably be a lot simpler of a search through the database. What about splitting larger states into multiple areas? I've never found a cache near St George, but I have a lot of them in my database. They're 300 miles away from me. I've found caches in Idaho just 150 miles away, but I have none in my database. I became a premium member for this reason mainly, but also because I found the hobby so fun I figured it was worth it. Thanks to all who started this site and made it so great.
  8. I may have the most basic of all units... Motorola i710 Nextel cell phone running Trimble Navigation Silver. No topo maps, just direction, speed, distance, and a track/waypoint map. Very challenging. Looking to buy Garmin etrex Venture soon. I just want to make sure I can hook it up to the computer for topo maps and easy downloading of geocaching.com cache data.
  9. Travel bugs with missions, such as one I saw recently with a mission to race several others from Maine to various destinations and back, should be tagged as such. I visited the bug log, and had a hard time figuring out if it had reached the first destination or not. I think a bug owner should put that mission on the bug, and perhaps a spot to use a hole punch on it to mark that it is on the way back to the owner. That way if I can move it closer to an interstate that will take it in the right direction, I could do so.
  10. I recently contacted an owner about a TB. It was dropped in some high mountains late last summer, and will likely be under snow until late May or early June. I told him I was planning a trip in June to the area and would attempt to retrieve it. He may not have known what the area is like.
  11. 1. I've seen some "pulled TB out and put it right back in" posts. What's the point of that? 2. Is there a general rule such as... if you remove a TB you must replace it with one, or is that only for certain caches?
×
×
  • Create New...