This topic contains 17 replies, has 10 voices, and was last updated by 
-
Posts
-
I notice a lot of people post the GC waypoint ID of a cache in the forums instead of a URL. Not sure this is doable, but it would be pretty cool if those IDs were automatically converted to a hyperlinke by the forum software. So if someone typed in GCGEPY it would automatcially get converted to GCGEPY when it was posted. Just a thought, not a big deal.
If you happen to be using Firefox for a web browser….. Check out this little linkie… You could certainly copy the GC&(() code and paste it into the firefox quick search….
See it here: http://xca.auscstrike.com/modules.php?op=modload&name=GQS&file=index
Load the thingie up and enter this… “new:50” It gives you the newest caches in Wisconsin… Nice…
Cache On!!!!
Cool idea… I never would have thought of providing this feature, but it definitely seems useful, especially for folks who haven’t figured out BBCode yet (or are just lazy ;)).
After about 15 minutes of regular expression building, I have something that I think works pretty well.
Here are the rules for the auto-linking to work:
– Waypoint code must start with GC in capital letters
– Waypoint code must have a space before it, and either be “naked” like GCHZKB, or enclosed in parenthesis like (GC65B). Jamming it next to another character or word like MyFavoriteCacheGCABCD, and enclosing it in anything else like [GC1234] will not work.If there are any other conditions under which folks think the waypoint auto-linking should work, let me know. I intentionally limited things by requiring the space in front of the GC to prevent false positives (bogus links).
On a somewhat related note, does anyone know what geocaching.com is going to do when all the waypoint codes starting with GC are used up? (It looks like all these waypoint codes may be used up by the end of the year.) Hopefully they have a plan for dealing with this rollover and it isn’t a Y2K-like situation…
@flushingrouse wrote:
If you happen to be using Firefox for a web browser….. Check out this little linkie… You could certainly copy the GC&(() code and paste it into the firefox quick search….
See it here: http://xca.auscstrike.com/modules.php?op=modload&name=GQS&file=index
Load the thingie up and enter this… “new:50” It gives you the newest caches in Wisconsin… Nice…
Cache On!!!!
Did it. Cool!
@jeremy wrote:
On a somewhat related note, does anyone know what geocaching.com is going to do when all the waypoint codes starting with GC are used up?
According to Jeremy Irish (the other Jeremy), when they reach {GCZZZZ}, they move to 5 characters. He mentioned this in the reviewer chat session just last week.
@flushingrouse wrote:
If you happen to be using Firefox for a web browser….. Check out this little linkie… You could certainly copy the GC&(() code and paste it into the firefox quick search….
See it here: http://xca.auscstrike.com/modules.php?op=modload&name=GQS&file=index
Very cool. In fact, it is so cool that I shamelessly ripped off most of the features of this Geocaching Quick Search module to create a Geocaching.com Search block for the WGA site. More than 70% of visitors to the WGA site are not using Firefox, so this feature will allow these folks to have access to a similar “super” search facility. (But having the search always visible in the Firefox title bar is definitely more convenient though… maybe someday I’ll put together a WGA Firefox search module.)
On the left hand side of all pages on the website you should now see green and yellow block titled Geocaching.com Search. Most of the commands and search types supported by the Geocaching Quick Search are also supported here… click on the View Search Syntax link for a complete list.
Note that I did add a couple new commands. My favorite is getting the nearest caches by Wisconsin location name (like city name)… if you find yourself in a town and want to know what caches are around, you can just type loc: and then the name of the town (like loc:Portage). This is much easier than trying to find out what zip code you are in, navigating on a map, etc.
Wow that was quick! Thanks for 2 great new features.
Those are two GREAT additions Jeremy!
I just had fun with the “loc” function. 😀 Very neat!
I switched to Firefox about a month or so ago. Opera was just lacking in it’s abilities and IE.. well forget it!! Tired of all the spyware. Now I have more fun stuff to play with….Thanks!!
@jeremy wrote:
Very cool. In fact, it is so cool that I shamelessly ripped off most of the features of this Geocaching Quick Search module to create a Geocaching.com Search block for the WGA site.
I’ve been using the geocaching quick search for over a year and love it, though there is one thing I find different with the new search added to the WGA site. when searching a zipcode with the firefox quicksearch, if you are also logged into geocaching.com the only results you get are new/unfound caches. I find I use the FF quick search this way almost everytime I’m about to head out, that way I only am seeing the caches I haven’t done.
I’m not trying to complain about the newly added WGA search, I think its a great addition to the site. I just wanted to point out one thing I really like about the FF quicksearch.
@buy_the_tie wrote:
According to Jeremy Irish (the other Jeremy), when they reach {GCZZZZ}, they move to 5 characters. He mentioned this in the reviewer chat session just last week.
Are they going to drop the ‘C’ (Ex. G12345)? Or are they adding the 5th digit? (Ex. GC12345)? I don’t think my GPSr can handle more than 6 characters. I’ll have to check it out.
@Johnny Cache wrote:
@buy_the_tie wrote:
According to Jeremy Irish (the other Jeremy), when they reach {GCZZZZ}, they move to 5 characters. He mentioned this in the reviewer chat session just last week.
Are they going to drop the ‘C’ (Ex. G12345)? Or are they adding the 5th digit? (Ex. GC12345)? I don’t think my GPSr can handle more than 6 characters. I’ll have to check it out.
I assume they reuse GC numbers once a cache or event is archived, too?????
I doubt they’ll reuse digits …. after all “closed” events or old caches never really disappear … you can still get to their pages, if you go about it the right way.
@hogrod wrote:
I’ve been using the geocaching quick search for over a year and love it, though there is one thing I find different with the new search added to the WGA site. when searching a zipcode with the firefox quicksearch, if you are also logged into geocaching.com the only results you get are new/unfound caches. I find I use the FF quick search this way almost everytime I’m about to head out, that way I only am seeing the caches I haven’t done.
You caught me on this one… I actually removed this “feature” because I wanted to see all the caches in a particular location or zip code. But I can see how having the filter applied would also be useful in some cases.
So to make things as close to the FF GQS as possible, now when you search by zip code or location on the WGA site, caches found by you or hidden by you are filtered out. To see all caches, simply append a + (plus sign) to the end of the zip code or location.
@cache_boppin_bunnyfufu wrote:
I assume they reuse GC numbers once a cache or event is archived, too?????
Nope, they are definitely not reused. In fact, a unique waypoint code is assigned as soon as a cache is submitted, so even caches that never get approved or published are “holding” codes forever (there are probably tens of thousands of these).
You must be logged in to reply to this topic.