clubjuggle
+Premium Members-
Posts
18 -
Joined
-
Last visited
Everything posted by clubjuggle
-
'An Error Has Occurred' when previewing a CAaR PQ
clubjuggle replied to clubjuggle's topic in Website
I was able to duplicate the problem using the site-generated route with a radius of .1 miles, as well as a 7-mile long route that I created duplicating my commute to work. -
NOW we're getting somewhere! Not fixed yet, but at least we've given TPTB somewhere to look (that is, a consistently repeatable error condition). Is there a formal bug-reporting mechanism, or do we just wait for someone from Groundspeak to see this? (sorry, I'm new here).
-
'An Error Has Occurred' when previewing a CAaR PQ
clubjuggle replied to clubjuggle's topic in Website
Both are less than 500 miles. I also tried testing the Google Maps method you outlined with a short route (my daily commute, about 7 miles) and had the same problem. -
'An Error Has Occurred' when previewing a CAaR PQ
clubjuggle replied to clubjuggle's topic in Website
Perhaps the (original) problem is unique to longer routes. I just generated my route from home to work on-site and that query worked fine. My trip route is less than 500 miles. -
'An Error Has Occurred' when previewing a CAaR PQ
clubjuggle replied to clubjuggle's topic in Website
I tried that just now and I uploaded the KML, but it didn't see any routes in the file. Perhaps the format is slightly different? ~Terry -
Question: Is your problem with a CAaR PQ that you generated via the on-site Google map thingy? I had a similar problem with a PQ, and I seem to have isolated it to just the query I created with a site-generated route. It does not seem to affect standard PQs or CAaR's generated from a file I uploaded from Google Earth. Does this observation hold for you as well?
-
'An Error Has Occurred' when previewing a CAaR PQ
clubjuggle replied to clubjuggle's topic in Website
Ok, it does seem to work with the uploaded GPZ. So we know where the problem is. Now, the hard part (and this may be one for the Groundspeak peeps): What's the fix? -
'An Error Has Occurred' when previewing a CAaR PQ
clubjuggle replied to clubjuggle's topic in Website
I don't think that can be done in Google Earth... at least, it didn't seem to work the one time I ever tried it. Of course, I am by no means an expert in Google Earth. I don't use it except for this purpose. -
'An Error Has Occurred' when previewing a CAaR PQ
clubjuggle replied to clubjuggle's topic in Website
I can try that as a test to see if it's the problem, but I need to include an intermediate waypoint, so that can't be the solution (unless I create 2 routes and blow 2 PQs, I guess). Thanks, ~Terry -
Subject/description pretty much says it. I click the attribute icons and nothing happens (looks like I never clicked them). This only seems to be the case on my caches along a route queries. Is this by design? If it helps, I'm running Firefox under Linux (Ubuntu). Thanks.
-
I am leaving for a trip in a few hours and started last night trying to generate a PQ of the trip route. I am trying to preview the route with varying search radii (starting at 2 miles) to determine how much I need to narrow it down to get under 500 caches. Any time I try to preview, I get the following (rather unhelpful) error: An Error Has Occurred Your request has resulted in an error. You may choose to retry your previous request. Or you may tell us what you were doing when this error occurred. If anyone is interested in trying to duplicate the error, the route I am using is http://www.geocaching.com/my/userrouteedit...3f-28b28514e7d4 To start, I am starting with the following selections: Search 2 miles on either side of the route Show me 500 caches Of: Any cache type Any container type No filter options selected No attributes chosen to include/exclude (though this feature doesn't seem to work on Firefox in Linux) Output to this account's email address Compress files into zip format Any insight into why this preview is not working is appreciated. I also tried scheduling the query to run overnight, and so far it hasn't. Yes, I checked my spam folder. Thanks, ~Terry
-
I use it and like it. I've gotten questions from friends about Geocaching, but no one has complained yet. Of course, the most caches I've found in a day is 12, so if I was doing runs of 40 or 50 caches in a day, I might turn the feature off before starting.
-
Can't access Premium Caches - Upgraded this Morning
clubjuggle replied to MasterAlthalus's topic in Website
I just purchased a premium membership as a birthday gift for a friend of mine. He had to log out and back in before he could see premium caches. Have you tried that? -
I tend to use Wikipedia. Most articles on trees have photos. Google image search works well, too.
-
Ah, well that's slightly disappointing but at least it makes sense. The important thing is that it was a fun, interesting and memorable find. The statistics are secondary. Thanks for the replies!
-
Can't speak to anything else, but as to the lack of reply, consider that it is a holiday week. Perhaps the CO in on vacation, away from a computer? Has she logged in to GC.com recently?
-
Yesterday in my travels I found Smoke on the Horizon (GCAD5), which I expected would replace Capitol View (GCDE1) as my oldest cache found. When I looked at the listing for Smoke on the Horizon, however, I noticed that it is listed as having been hidden 22 Jan 2005, even though it has 557 log entries, going all the way back to 6 June 2001. The "oldest cache" thing will (hopefully) quickly become a moot point, as I'm heading to SC later this wiik and the trip will take me right past Octopus Garden (GC70). Still, I'm curious what the story is here. Can anyone offer any insight?
-
Other things found instead of the cache?
clubjuggle replied to Gryffyth's topic in General geocaching topics
A couple months ago I was hunting a micro on a walking trail over lunch. Thanks to heavy cloud cover, I never did find the micro, but in the process of searching I did find an unrelated letterbox (not a letterbox hybrid, but one listed on Letterboxing and not here) about 35' from where my GPS said the cache I was looking for should be. It was an otherwise unremarkable spot on the trail, so it's a pretty amazing coincidence that two different people would choose it as a hide location.