lonepetrel

I was just looking around for GPSr prices, just curious and not really shopping for one, and stumbled across this. The former Radio Shack, now The Source by Circuit City (www.thesourcecc.com) advertises a Garmin Etrex Legend C for CAD$149.99 and on the same page, a Garmin Etrex Legend for CAD$179.99 Hmmm, which should I get? As I mentioned, I was just looking, but after looking at this same unit at different places, I knew that was a deal (or an error?). Well, I didn't wait until they fix the error, if it is an error, an ordered online right away, don't care about shipping costs, just want to get the deal... Oh! it's free shipping on items over 25$, now that's a deal! So, is it a deal (it's not advertised as being a sale price) or an error?

This is what I get when trying to upload images to attach to a log: Server Error in '/' Application. -------------------------------------------------------------------------------- There is not enough space on the disk. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.IO.IOException: There is not enough space on the disk. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [iOException: There is not enough space on the disk. ] WebSupergoo.ABCUpload5.UploadedFile.SaveAs(String path) +180 Geocaching.UI.ImageUploadPanel.ProcessFile() +480 Geocaching.UI.ImageUploadPanel.btnUpload_Click(Object sender, EventArgs e) +7 System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain() +1277

Oh, and it was also impossible for me to edit my pq's. I had to delete them and create new ones. Anyone else having this problem?

OK, I figured out the problem I was having. I had all the countries selected for my pq search for caches I've found. I created a new one that searches in all the states/provinces and got the missing "found" caches. For some reason, the system seems to think that some geocaches located in Nova Scotia don't fit the criteria for geocaches in Canada. Hmmm.... Now I have to use 2 pq's for 1 search filter. Same thing for the locationless search filter. Searching for all states/provinces yields to more results than searching for all countries. Now I have to use 4 pq's for 2 search filters. I realize that the United States aren't included in the countries list, which might explain my problem with the missing locationless entries. However, Canada is in the countries list, but a search within Canada returns less results than a search for all provinces.

Different problem now... Only caches I've found are returned by my "Found" pq, but not all of them; about a third are missing. My pq for locationless caches is also missing entries.

Call me too lazy or too cheap, I just don't like to spend a lot of time planning before going on the hunt. I take my pq's and send them directly to the gps, select one within the radius I'm willing to travel to on this day and wait to see where it will take me. I like the game for the adventure, not the race for the number of finds. I did, however, spend the time to read the posts in this topic and I quickly realized that a limiting rule would greatly affect those who are in it for the numbers, therefore not quite the easy fix I thought it could have been. Different people, different opinions, not everyone is ever going to agree on something. I could start doing more planning, analyse cache descriptions, read the logs, pinpoint the location a map, etc. in an attempt to avoid bad surprises, but that would defy the purpose of the game, the way I play it. I'll just have to accept the fact that most people play the game differently than I do and be prepared for the odd "that was a waste of time" kind of cache.

I think you illustrate exactly what the problem is in this discussion. Some people hunt because they like to discover nice places, for the adventure and the pleasure of a visit to a place that is worth it. Some other people are out there simply to rack up the numbers, whether it's for the number of caches they place or the ones they find, or both. There is nothing wrong with this, and I can see why this type of geocacher has nothing to complain about finding many caches in the same area, even if they don't have anything particularly attractive. However, for someone who takes geocaching as an excuse to travel and enjoy nice scenery, it's a different story. I'm not saying that ALL caches should be in places appearing on the cover of National Geographic, I also like to go out for a quick one.

I wish there was a limit imposed on the number of geocaches placed by a single member, other than simply keeping the caches 528ft. apart. It's really frustrating to plan for a day of geocaching thinking that you're going to see nice scenery, learn interesting facts, find places of special significance, discover the history of an area etc., only to end up nowhere special and find a trash container that was placed there by someone simply because they wanted to have one more cache added to their statistics. It should be quite safe to assume that someone who has placed over 102 caches over a 3 month period, with over 40 in one single month, hasn't put much thought into it and doesn't really care what visitors are going to find once they get there. I think this is far from what geocaching is all about. I have a really hard time believing that a single person can come up with over 200 caches that are worth a visit, especially all in one province. With the growing popularity of this sport, I really think it's time the rules were more specific about how many caches can be placed in a particular area, by a single member and in a defined time span. I don't want to waste my time and energy on crappy caches anymore; let's keep this sport about the quality, not the quantity.

Exact same problem here. My PQ for "Cache I Have Found" is maxed at 500 results from caches I've never visited. I tried to delete it and create a new one, no joy. The PQ# of the first one was 55784. I don't know the # of the new cuz it hadn't been emailed to me yet. Is there any other way to find out the # than to wait for the file to appear in my inbox? Can't have it sent today, already maxed at 5 for the day.

In addition to the terrain and difficulty level of a cache, wouldn't it be useful to also have cache authors provide hunters with an approximate of the time required to complete the cache from a nearby parking location?