Group: Super Administrators
Joined: Dec. 2001
||Posted: Nov. 27 2004,1:56 pm
|Quote (CoyoteRed @ Nov. 27 2004,9:17 am)|
|I've just retired my caches and I'm not shy about why. Pretty much it's just because they were all cross listed with gc.com. Really, there is little point in cross listing. I have a local copy of the listings and most of the logs are on gc.com. So, really, there is little reason. I've got enough on my plate keeping up with gc.com and my letterbox listings to have to worry about redundancy.|
Sorry to hear this, but I would tend to agree with Scout on this one and not just for the obvious reason.
I could give reasons for cross listing such as being able to have 2 legs of a multi (or even yours and anothers) cache within 528' of one another, open database for use by other sites like Buxley's Waypoints, No worry about getting that Virtual listed, No charge to access ANY part of our database... And the list goes on.
A bit of advise if you're looking for more traffic. Talk to ClydeE, the creator of GSAK, and try to get him to implement an open source GPX format to transfering cache data. You've got to make it easy for folks to get the data. The XML is a good start, but falls far short. I would be interested in an open format as I'm sure other alternative site developers would be. If we can show Clyde that there is a market--and I've already got Jeremy to commit to saying he doesn't care if GSAK imports an alternative--then that would be a major step.
As for traffic, while we appreciate the advice I must say that in comparison you can not get much easier for acquiring our data. Also the the simple fact that one would feel they needed the Frogs approval for GSAK to import 'an alternative' would be cause for concern in my book and tells me it GSAK is not so 'Open Format' after all.
Second, encourage unique listing. Designate a field to show it is a unique listing so dual users can come here and find just the caches not listed at gc.com. It's next to impossible as it is now.
Perhaps Jeremy would like to implement this over on GC.com. I mean considering WE support the open-caching database this would not be so hard for him to do. On the other-hand, with his very restrictive rules to cache data we can accomplish the same quite as easily.
Getting a little off topic for this 'How To' thread though, so further discussion on this would be best in a topic of its own.
Always welcome suggestions.