Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Posts posted by caderoux

  1. Scenario 1:  Bomb squad responds to report of suspicious object and detonates the cache.  Law enforcement learns it was a geocache and contacts geocaching.com, asking them to remove the listing immediately.


    Scenario 2:  Land manager learns about geocaching for the first time, does a search, and is shocked to learn that a geocache is placed in the middle of an ecologically sensitive wildflower preserve.  Geocaching.com receives a request to have the cache listing removed immediately.


    Scenario 3:  Geocacher obtains permission to hide a cache in a State Park, filling out a form that says the cache must be removed on X date.  Geocacher would like for the cache to remain available for hunting right up until and including X date.  Permit conditions also stipulate that the cache must be removed from the searchable listings on the listing site once the cache's expiration date arrives.

    Except archived cache listings still really remain on the site in all those cases and you can still view the pages (as you should) in no different way than whether they are included in a Pocket Query without data beyond the status.


    Which still leaves the question that if it's so important that we don't want people caching with stale data, why not provide a listing of archived cache waypoints - not the coordinates, not the full GPX schema?


    After all, we've now got an "All My Finds" GPX with only your own logs - and this includes archived caches.


    There are plenty of workarounds, but the time taken to answer this question in the forums over and over and over again for all the newer users plus the time for everyone to learn the workarounds and do their cleanup would seem to outweigh the implementation costs. But I guess that's too global a view. Let's just stick to the way things are and keep wasting our time answering these questions.


    Silly me, what am I doing prolonging the agony...

  2. I can't seem to figure out how to get archived listings.  I don't see anything in the Pocket Query form to indicate it.


    TIA for any help.

    Although the previous posters are correct, you have not mentioned your goal in getting a listing of archived caches, and so they have not been able to offer any path to resolve your issue.


    I assume your goal is to avoid hunting archived caches, and that you have a problem because you have stale data and you need to figure out a way to keep it up to date without reprinting a whole bunch of cache pages or checking through every cache in your binder before a hunt. You didn't say if you were fully paperless or just use the GPX file to load a GPS without any processing or what.


    Some ways to do that (depending on your method of making your hitlist) would be to:


    1. Purge (or mark up) your paper listings


    2. Update an offline database




    1. If you are attempting to purge paper listings, you are unfortunately out of luck, as even listings of caches archive have been opposed here. So you will have no way to go through your paper listing and purge out ones on an archive list.


    2. If you maintain an offline database in GSAK, you are in luck, as you can create a filter showing only caches which HAVE NOT come down in a GPX file within the last week, say, and then either:


    a. Pull down the individual GPXes (so you can have the last few logs which will show why it was archived etc - that's what I do)


    b. Delete them


    c. Change the status to archived


    If you do use GSAK, modify any filters you use to hunt from to ensure that only caches updated from GPX files recently are included in those filters, and you'll almost always avoid hunting an archived cache - and then the database maintenance is really just a failsafe in case you make a filter without an updated GPX criteria.


    And then obviously, you replace all your waypoints in the GPS with those from GSAK, so the archived ones aren't in your GPS - I don't have a traditional GPS, so I can't help there.


    Hope that helps a little.

  3. I've asked for the cache owner name (not a link - although we do get the name and link of the approver) in the notification, too - it is useful to see if a notification you've been waiting for is for the cache you are expecting or not.


    Other good suggestions were made at:




    regarding a more condensed format conducive to mobile devices, and terrain difficulty ratings.


    As it stands now, the notification is only useful as a notification to me to trigger my PQs to get all the new information, since there is not enough information in the notification to determine where the cache is and whether I should go read the listing and download it. i.e. the information in the notification does not inform any decision about whether or not to read the site - I always have to.

  4. Server Error in '/' Application.



    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    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.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.


    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:


    [sqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]

    System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) +742

    System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +45

    System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) +5

    System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304

    System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77

    System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) +38

    Groundspeak.Web.SqlData.SqlConnectionManager.FillDataSet(String sql, Database database, Int32 Timeout) +208

    Groundspeak.Web.SqlData.SqlGeocacheController.GetCacheDataByArray(String CacheList, Int64 UserID, Int64 AltUserID) +256

    Groundspeak.Web.CustomWpt.Geocache.GetCacheDataByArray(ArrayList CacheList, Int64 UserID, Int64 AltUserID) +345

    Geocaching.UI.geocaching_nearest.ProcessResults(OriginWpt OriginWpt) +1169

    Geocaching.UI.geocaching_nearest.Location_PQLoaded(Object sender, EventArgs e) +577

    Geocaching.LocationPanel.GetQueryParms() +4517

    Geocaching.LocationPanel.Page_Load(Object sender, EventArgs e) +108

    System.Web.UI.Control.OnLoad(EventArgs e) +67

    System.Web.UI.Control.LoadRecursive() +35

    System.Web.UI.Control.LoadRecursive() +98

    System.Web.UI.Control.LoadRecursive() +98

    System.Web.UI.Page.ProcessRequestMain() +750




    Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032

  5. There seem to be an increasing number of virtual coins and travel bugs which get dropped in caches and then grabbed back by the owner. People are using them to track all kinds of things, from distance between caches to favorite caches to friends. I've thought of using my FTF geocoin to track my FTFs.


    Right or wrong, it's happening. Just like waymarks, it might be that travel bugs and coins need to be generalized and categorized to limit what can be done with them.

  6. You should talk to your IT guys. There's no reason to block zip files...they aren't dangerous by themselves. My IT department blocks exe files, but if we really need to get one they tell us to have them zipped before they are sent.

    The blocking software (even updated) can be buggy, so more simplistic rules (like blocking all ZIPs and EXEs) can be more reliable.


    Just the other day we found malware which got through. EXE inside a ZIP file (which is still supposed to be scanned), but it had a long name with extra periods inside the ZIP file.

  7. I don't think so. However, assuming you are parked at a cache, you can always select the current cache and make it the center point.


    Here's how I do cache runs of 20 caches or so.


    GSAK database up to date with PQs

    Local filter of all unfound caches

    Check off the ones I want to attempt with the user flag

    Switch to hitlist filter of all user flagged caches

    Export GPX for GPX Sonar on PDA

    GPXtoMaplet for Mapopolis on PDA.

    Export CSV to Microsoft Mappoint

    Import into Mappoint

    Optimize route in Mappoint


    Then I follow the laptop route, but use street routing in Mapopolis, selecting the next cache after completing the previous cache. I never actually connect my BlueTooth GPS to my laptop, however if I have a BlueTooth transceiver, that would probably be a good idea. However, I would probably have to have it disconnect it from the PDA first.

  8. We built our own.


    One of the features most useful is that users can submit requests for other users (like if their computer is down, or their account is locked out).


    In addition, requests for new hardware or software is automatically copied to their boss for approval.


    Prioritization is not allowed by users, since they are not able to balance the workload across departmental needs.


    We also use it for security authorizations, equipment loans, and new user account requests.

  9. It wasn't so long ago that you couldn't just go online here because the site had stability problems. Having the regular PQ in your mailbox means you have a good chance at having up to date information (when the site is down, you've got 0 chance to have that on-demand PQ run). Whether you put it into a database or just keep them, at least you've got something.


    In fact, just on Sunday afternoon I was out and I called my wife because it looked like every cache I was going to had already been found that morning. I wanted to see if there were going to be any FTFs possible (did get 2 eventually). Site was down, so no info. Noticed that a lot of people logged much later (I think they saw my logs going through and started their logging). Didn't see a notice here about any downtime, though.


    Having it automatic does mean less prep time with the computer and more time making sure you have water and everything ready for the trip.

  • Create New...