Jump to content

ThePropers

+Premium Members
  • Posts

    891
  • Joined

  • Last visited

Everything posted by ThePropers

  1. The defaults work fine for geocaching, but if you want to take a look at how I have mine set up, feel free to read this page I made. I find the system works well for me, and I promote it often, because after all, my way is the best way
  2. Since the GPX file doesn't contain the attribute info (see this thread) it appears that might be an option (perhaps the only option). Of course, I don't know how to accomplish this in GSAK, but I'm sure it's possible since my knowledge of that is only slightly above beginner. The other option is to post a feature request and hope everyone doesn't shoot it down and TPTB think it's something that would be useful. Of course, I would like to see them fix the preview logic.
  3. 450 miles, but I opted to take my total number of finds and divide it by 2 instead I think that's probably high. While I've done tons of caches more than .5 miles round trip, I've probably done too many park and grabs, and that 10 foot distance would really drag it down.
  4. I use a 60CSx with this: %Dif/%Ter C:%con1 TB:%bug=YN %last4 %By That gives me difficulty/Terrain, container size, TBs, last 4 logs, and who hid it. I don't put the hint in it since I don't want to accidentally read it. See my Custom Symbols Page for more info on what it looks like
  5. Nope, but they all have at least one of the three, which is how I believe it should work. However, it should not be previewing as 101 found if the PQ file only returns 58. EDIT: Just checked the preview further, and even though it says 101, it's really returning 63, but with 5 repeats, which makes 58 caches, which is what the PQ file contains. So it appears that the PQ is generating correctly, but the preview count is all screwed up (maybe it's counting how many of those 3 attributes it found, rather than the unique caches?) and it's also returning a few repeats in the preview. I do think the PQ itself is generating the correct file though. Every cache in it has at least one of the attributes I selected, and I don't think it's supposed to only include those caches with all 3 of those attributes. At least I don't believe so. It seems like the problem lies with the preview logic to me.
  6. Just wanted to follow up: I just set up a PQ similar to yours: No Attributes: 74 24/7: 17 Winter: 34 Parking: 50 24/7, Winter, AND Parking: 101 Those are all previewed numbers. However, when I actually ran the pocket query (with all 3) and opened the file, I only got 58 (despite the preview showing 101). Maybe it's only the preview functionality that's broken? I haven't gone through the PQ results to verify that I have what I need, nor did I go through the preview to see what was in there that's not in the PQ. My first guess is that the preview is returning stuff it should not, and the PQ results are probably correct. That's of course based off my experience that selecting no attributes usually results with the preview matching the results.
  7. These options are "AND"... So checking the I Haven't Found should never return anything thats been found.. My thought would be that (its been stated before, don't know if its still true) that the PQ's run off a backup of the main database and if the caches were very recently found, that may not be reflected in the backup database. Remember here about two or three months ago that PQ's weren't returning new caches?? Same type of problem. That's true and I should've realized that. Weird behavior, but with the finds being a month+ old, I don't have any ideas. Have you tried to run the PQ again (or preview it) to see if they show up again?
  8. If its working fine, then can you explain why selecting multiple attributes would return MORE than selecting NO attributes?? In any case, selecting NO attributes should return the maximum number of caches, however, selecting multiple attributes (setting aside the OR vs AND argument) should always return fewer (unless all the caches just happen to have the selected attributes, unlikely, but still would never return more). I just reread the original post and apologize for the confusion. I must've missed the "selecting no attributes" section of it.
  9. I take any that I can help along. Sometimes I'll even take some taht I can't really help, other than to move them to a busier cache. TBs are NOT trade items.
  10. You don't also have some other additional criteria selected do you? Such as "caches on my watchlist" or "updated in the last 7 days" or something else that might cause it?
  11. Then explain how selecting multiple attributes returns MORE than selecting no attributes... Its broken... Uhm, that's not what I was saying. It's working fine, but your understanding of how it should be working is wrong. However, that's not to say how you WANT it to work is wrong, but that's not how it does work or should work. The point is it's working how it's supposed to, and is not "broken." I think if you want an additional functionality (to only return those caches that include ALL the attributes you selected), a request should be made. Personally I don't use the attributes anyways because I find only about 5% of caches actually use them, and of those, about 0% include everything they should. For instance a cache may be dog-friendly, but someone only selected the 24/7 attribute.
  12. It's not much over 125K. I never worry about or even reference width/height in pixels - just try to keep the file at ~ 125K. The site will accept files that are somewhat larger than that. Well, it's nearly 186, which is about 61k over which is nearly 49% too large. That's hardly "not much over 125k" It's also 1615 pixels wide, which is 1015 pixels too wide. I am not pointing fingers, I just want to know how that was able to be uploaded so I make sure I understand what the limits really are.
  13. LOL. And congrats to you on 1170 on Dizz-Knee Challenge! Ok, not really a milestone, but congrats anyways.
  14. I'd throw my vote in for archiving all virtuals and webcams if it would stop people constantly asking for them to come back. Wait, what was this topic about again?
  15. I like it, and wish each region had a sticky for congratulations. While I'm all for congratulating milestones, with the NE section covering 7 states + DC, it always seemed pointless to post a separate topic for each one (where maybe a couple dozen people might know the cacher in question). For instance, right now there are about nine threads congratulating people (I don't know any of them, not that it matters). Not that it really affects me of course, but I think a sticky would be well-served.
  16. Actually, I think that's exactly how it's supposed to work. It's kindof an "or" rather than an "and" clause. For instance, it's saying give me anything that's 24/7 OR winter OR dog friendly. I think what you're asking for is another option that will give you anything that includes ALL the attributes you selected. Regardless, I think it's working as designed, just not how you want it to.
  17. As mentioned above, that's probably because it's now a NEW pocket query, which jumps to the top of the queue above everything else. It doesn't matter WHEN you schedule it, but it matters when the last time it ran was. Maybe you should be patient and see if the other ones show up after they go through the queue.
  18. So no puzzle caches then, right? Nothing that would require a calculator? Nothing that might require a quick google search? Nothing from wikipedia for sure. What about having to do some simple math in the field....or might need a pencil and paper? Nothing that would say "go read this sign and then..." Canoes and climbing gear aren't part of every geoacher's bag either, so we should eliminate any cache that might need those too, right? I completely disagree. 100%.
  19. There are quite a bit of confusion around pocket queries, but maybe this will help (quoted from the bottom of the build PQ page): My understanding is that just because you add your PQ to the queue, doesn't mean you're special and your PQ automatically jumps to the top and processes before the other 500,000 that need to run that day. However, I guess if it's a new PQ it does. So in your case, it last ran on the 20th, so it's behind every other PQ that last ran before the 20th, and yours will run after all of those. At least that's my understanding. So if you need it right away (and I don't condone this of course) you can copy a PQ, and then schedule the new one. That way it's a new PQ and it jumps ahead of everyone else. Cheating? Probably. As for why you're not receiving them, check your spam/junk mail folders. If you're getting it sent to a work address, make sure they're not being stripped out (for instance, I cannot receive anything with a .zip extension at work, so I can't have my PQs sent there if I want the zipped version)
  20. I definitely agree here. If a needed website or phone number is down, then it's the owner's responsibility, and others can use the needs maintenance or SBA logic already built in. It's the same thing as if a needed stage goes missing...a piece needed to complete the cache isn't working, so it needs maintenance. I would really hate if we're suddenly limited to just text descriptions. Besides there's already a built in "associated web page" box when you go to submit a cache.
  21. My experience is that they each have a custom-fitted connector (admittedly limited experience) Ditto. Although my 60CSx just uses a standard connector (I don't know what it's called, but I use the same cord for the GPS, my PDA, and my camera). The eTrex though has a custom connector. In fact, I still have my old one around here somewhere. I guess I should give the cord to someone who needs it, considering the yellow eTrex doesn't come with it.
  22. I don't see a problem with it. I have a couple caches that might require more than one trip, and many puzzle caches do (heck, Choreographed Chaos is requiring me to make the 2 hour trip to New Jersey about 10 times). I've done caches that give you a phone number to call. If you don't have a cell phone on you, you'd have to leave and go find a payphone or go home to call. Same difference in my opinion. However, you should mention something about it in your writeup.
  23. I may or may not have done the same thing with another cacher. I don't see anything wrong with it, as they give you two licenses. If you're that worried about it, have your friend give his GPS to you, then they are both yours to do with as you please. After you install it on YOUR two gps units, be a good friend and decide you don't want two units after all, and give it back.
×
×
  • Create New...