Jump to content

gse1986

+Premium Members
  • Posts

    102
  • Joined

  • Last visited

Posts posted by gse1986

  1. Just guessing... but if you do not check-mark the delete and leave the PQ active (just not set to run repeatedly), wouldn't this solve that problem? You can later delete it as you will.

     

    On a sidenote -- We find that a PQ over a week old is "stale" and you are liable to go out caching, only to find (rather, NOT FIND) a cache or two that have been disabled, archived or just plain missing during the interim.

    If we run a PQ for a caching outing, it is always a "fresh" one.

     

    Not quite...my first post wasn't very clear. the 7 days bit is the automatic deletion of results Groundspeak impose, which i completely agree with.

     

    And yes I could just wait until i've downloaded the results before deleting the query, i was merely trying to remove one step from what i do. :ph34r:

  2. Ok probably a confusing title. Basically I run a lot of queries as one off, and had them set to auto delete (since that's all I did once they'd run anyway). I've found now, that since I now have to manually download them rather than pick them up via email, that once the query has been deleted from the "active pocket queries" list, it gets deleted from the ready for download list.

     

    This hasn't been a problem until I didnt manage to download my queries last night, so once the 24 hrs since it ran was up this am, the queries (and thus results) from yesterday got deleted.

     

    Can this be changed, or at least be an option for the 1 day old results to not be deleted?

     

    I perfectly understand deleting after 7 days....but could the deleted from queries ready to run not be linked to the results?

  3. Because in the world of databases and geocaching, there is no need to maintain information on or to go look for something that does not exist.

    that's exactly the reason why we do want archived caches in PQs, at least as stub entries. we don't want them so we can keep information about them, we want them so we can delete those caches off the GPS. because without that, those cache entries would sit there on the GPS, effectively doing what you mentioned (maintaining information about something that's not there), they'd never get updated with the information that they've been archived, and we may end up going looking for them because we don't know any better. we want to know about archived caches so we don't go looking for them.

     

    You may want to try GSAK out. It is free to download and after 21 days you will receive a nag message asking you to donate a one time $25.00 fee. It is well worth your time to at least try this product, it's free.

    GSAK isn't the solution to everyone's problems. particularly, not everybody can use it as not everybody uses windows.

    Exactly. That's why I suggested merely having, for an "Archived Caches PQ" to list a GC number and the archived flag. Thus to anyone wanting to search for the item it's relatively useless, and requires the user to find the cache by logging in and looking at archived data anyway, but for users of GSAK it would allow old caches to be archived in the database (and then deleted).

     

    GSAK currently does have the ability to filter out, and subsequently delete, archived caches.

     

    Since I do run GSAK on an Ubuntu desktop as well as my Windows laptop, not sure what you are using unless you are referring to Apple or Wii. In which case, you're right, it only runs on computers.

     

    Whatever database you are using, if it does not show the last GPX date, then it is a shortcoming of the database you are using not the data being presented as all the information you need to accomplish this is included. Otherwise it is a simple matter of filtering out all records that were not updated during your last PQ cycle. i.e. Many people run a series of PQs over a week, so it is a simple matter of anything not updated in the last seven days and deleting the results.

     

    You can keep pushing for or resisting the methods that have been suggested, however it will only result in frustration. Aside from being a very small segment of cachers that want or could/would use this, the issues it would create just make it not very desirable, probably not even feasible, for GC to offer it.

     

    You're right it doesn't have the ability to do that automatically, however simply being able to apply a filter for archived caches(whose flag has been set by an "archived query" and then deleting the waypoints in that filter is only a very quick task.

     

    I can see that you don't feel the archived query would be beneficial to how you use the pocket queries, however i believe that others would be able to benefit from it.

     

    The alternative is to run the same query over and over again, and then delete any waypoints not updated in the most recent query. This can cause issues if for example a huge series appears nearby, thus the slightly further away caches would not appear in a nearest 1000 query, but would not be archived.

     

    :)

  4. Because in the world of databases and geocaching, there is no need to maintain information on or to go look for something that does not exist.

    that's exactly the reason why we do want archived caches in PQs, at least as stub entries. we don't want them so we can keep information about them, we want them so we can delete those caches off the GPS. because without that, those cache entries would sit there on the GPS, effectively doing what you mentioned (maintaining information about something that's not there), they'd never get updated with the information that they've been archived, and we may end up going looking for them because we don't know any better. we want to know about archived caches so we don't go looking for them.

     

    You may want to try GSAK out. It is free to download and after 21 days you will receive a nag message asking you to donate a one time $25.00 fee. It is well worth your time to at least try this product, it's free.

    GSAK isn't the solution to everyone's problems. particularly, not everybody can use it as not everybody uses windows.

     

    Exactly. That's why I suggested merely having, for an "Archived Caches PQ" to list a GC number and the archived flag. Thus to anyone wanting to search for the item it's relatively useless, and requires the user to find the cache by logging in and looking at archived data anyway, but for users of GSAK it would allow old caches to be archived in the database (and then deleted).

     

    :)

  5. Excellent solution. Works just fine.

     

    But again, it brings us back to the axioms on my page:

    1. GC.com didn't create PQs for users to maintain offline databases. They were created as a means for querying against the database and downloading sets of caches for quick upload to your GPS.
    2. Any offline database created by a user is - by definition - instantly out of date with the most current version, which resides on Groundspeak's server.
    3. GC.com takes a hard-line stance that while caches are in the database for archival purposes, they do not send out data on archived caches. As far as the PQs are concerned, they do not exist expect in the "All My Finds."
    4. Since offline databases are stored and maintained in third party software, the onus is on third party software to weed out archived caches.

    I think it falls under #4...

     

    What about the option to simply download a PQ which contains the GC number and the archived flag? The data is then useless to anyone wanting to search for archived caches (as there's no coords) but would help those wanting to remove archived caches from their database?

  6. Of course script a login / cookie is a violation of the TOS, so now I'll be watching your account :):)

     

    -Raine

     

    We'll also be able to tell when a person doesn't download a PQ that they generated, so we can selectivity turn them off and get PQ's out the door even faster to people who do use them! (really excited exclamation mark)

     

    -Raine

     

    I might have missed the reply, but I don't think it's been answered explicitly. Will the download URL require logging in? If yes could it be made so you don't, to enable an alternative script (that is not blocked by the TOS) to grab the file and import into GSAK. Surely since that's a legitimate use of the data it will be allowed?

  7. I've used OpenGPX on Android (which is what the Legend runs) which seems to work quite well, another option would be (reference to unauthorized application removed by Groundspeak). This makes use and offers naviation as well, which i know you said you weren't interested in but is simply an extra feature. (reference to unauthorized application removed by Groundspeak) also lets you download caches on the fly, so quite useful if you find an opportunity for caching you weren't prepared for.

     

    This program also ties directly into the new Google Navigation app which offers satnav, simply find a cache u like and click Navigate and then program will give you the driving directions to the cache (or a parking child waypoint if you so choose).

  8. Danke für die Hilfe, habe jetzt eine genauere Karte auf meinem Gerät, aber es scheint nicht Routing fähig zu sein...in Mapsource kann ich mir zwischen 2 Wegpunkten eine Route vorschlagen lassen, wnn ich diese aber ans Gerät übertrage, zeigt es mir nur die Fluglinie zwischen den beiden Punkten an...

    Der Verkäufer meinte, dass das das Venture HC routingfähig ist.

    Kann mir da bitte einer weiterhelfen? Ist es nun routingfähig oder nicht? Wenn ja, wie kann ich mir eine Route anzeigen lassen?

     

    Gruß

    Benjamin

     

    Translation : Asking if the device is can create routes automatically, the seller informed him that the device could perform this task.

     

    I've got the Venture HC as well and as far as i'm aware the device can not create routes on roads itself, it only supports "as the bird flys". I think it's the higher models (vista etc) which can route along roads automatically.

     

    Ich hab auch Venture HC und soweit dass ich weiss, ist es nicht Routingfähig. Man kann die Routes selbst eingeben, aber nicht automatisch - das ist aber auf andere GPS (Vista usw) verfügbar.

     

    MFG,

     

    GSE1986

  9. Whilst I can see the thought behind this idea, in practice it wouldn't work. As others have mentioned some difficult caches (I believe that there's one in america somewhere that's not been found after having been out for 2 years odd?) There's a load of DNF's on that but cache is still there and confirmed by owner.

     

    It would result in either

     

    a) the owner getting fed up of keep reactivating it so cache would be archived (and perhaps moved to a different listing site)

     

    :D A culture of posting note rather than DNF would start and completely stop the "auto disable" function you suggest

  10. The PQ processors stopped sometime overnight. They were restarted this morning after 8:00AM Seattle time, but there is still a backlog of queries to generate. Keep patient; they are on their way (I'm waiting for mine, too)!

     

    We are underway on an overhaul of the PQ system that should finally put issues like these to rest in the future.

     

    Cheers for letting us know :)

  11. I've got a problem with one of my 5 pocket queries today. I was due to have 4 "new" pocket queries run and one recurring one. The 4 new ran this morning - 830ish GMT but the recurring one which normally runs 930ish still hasn't come through. I've tried unticking and ticking it to run today but no luck :)

  12. I'd suggest using an iframe, although this still wouldn't really work for how most people use the site.

     

    Pocket queries, iphone app, geocaching live, send to gps etc would (I assume) show the iframe html rather than the text that should be there. :D

  13. Just wondering if anyone knows where/if it is possible to get:

    1. mapping of Italy (Tivoli and Rome area) for my windows mobile 6 gps/pda, preferably of a scale suitable for walking rather than a road atlas. I use memorymap in the uk, but there don't seem to be any Italian maps available. I don't want to spend a lot of money on it though, its only a week!

    2. Italy maps for "Route 66 navigate 7" sat nav software, which I also use on my Windows mob6

     

    We're off to Tivoli soon, and I'm hoping to find a cache or two whilst there, and also slightly terrified at the idea of driving in Italy, so being able to use the satnav would be a big help. I've never driven on the wrong side before, and my Insignificant Other has already chickened out altogether :unsure:

     

    Thanks :blink:

     

    I visited italy hiking during the summer and proper mapping was a problem. I've found around cities there are some OK paper maps, but only the city - as soon as you get out of a city it goes to 1:250000 as a minimum.

     

    Unfortunately because of this the similar goes for electronic mapping. I found some maps for garmin but that's about all - nothing for windows mobile.

     

    an option may be geocaching live. You can pre download maps (using desktop companion) and then import your pocket queries. Works quite well in the UK but I wasn't organised enough to set it up before I went to Italy!

     

    Good luck!

  14. Hallo,

    seit einem Tag bekommen wir an mehreren Geräten diese Fehlermeldung beim uploadversuch von Geocaches, Geräte werden aber erkannt.

    Woran könnte das liegen?

    Is das ein Problem der geocaching Site selbst, das sich von selbst wieder löst die nächsten tage?

     

    Fehlermeldung :

    Fatal Error: File Path: String Stream, line: 1, char: 3 Message: processing instruction name expected

     

    Ich nehme an das es vielliecht am besten ist, auf Englisch zu schreiben, dann koennen mehr Leute helfen. Wenn Sie kein Englisch koennen, werde ich übersetzen :anibad:

     

    Translation:

    Hello, yesterday we started getting an error on a number of devices when trying to upload gecaches. The devices are recognised (by the computer). What could be causing this problem? Is it a problem of the geocaching site itself which will correct itself?

    Error report:

    Fatal Error: File Path: String Stream, line: 1, char: 3 Message: processing instruction name expected

  15. The reason for the slowness is how the caches are displayed (which I don't believe can be changed).

     

     

    Basically you call up google maps as you would when visiting maps.google.com. Once all this is loaded the caches get called via java script. The computer sends the limits for the map you're looking at and the server returns the caches there if there is less than 500. If there's more then it returns nothing. The filters premium members can apply simply filter the results received (ie any filtering is performed client side rather than server side).

     

     

    Because of this if the site (or possibly the server which deals with the map information - i don't know if this is a seperate server to the rest of the site) is under some stress, for example in peak times or if you're on a relatively slow connection you may find yourself waiting for a bit longer to get the results. I believe it's how the java works in browsers that it waits until it is completed before anything else can happen, different to when you're loading a few web pages in different tabs etc.

     

     

    It could possibly be something that GS implement that filtering is performed server side or maybe allowing a user to limit the number of caches to 100/200/500 etc caches from the centre?

     

     

    Obviously this solution then moves the stress to the server rather than the client.

     

     

    I usually use Chrome and haven't had that sort of problem - well, maybe waiting 5 seconds or so for results to come down. I know chrome has a different VM that is built into the browser, not sure if this may improve things for you?

     

     

    :unsure:

  16. I think it's one of the things that people can do as they like.

     

     

    As i mentioned before different people do geocaching for different reasons and it's everyone's game so I don't think you can say it's wrong you should do it that way.

     

     

    On the same note though just because you enjoy Geocaching for a certain reason doesn't mean others enjoy it for that reason. If you find someone's cache chances are they put the cache out for people to enjoy finding, and since noone gets paid for putting caches out saying thank you in the log is a way of showing gratitude.

     

     

    Likewise some people enjoy to find the odd FTF (myself included). Although it doesn't make the slightest bit of difference really it can be (and was) annoying to find a cache that hadn't been logged as found on the website but had been found a few days before.

     

     

    So i think since noone can do geocaching on their own (ie there has to be someone else to place the cache before you find it! - well for it to be a challenge anyway!) it's nice to thnink of other players. If you think they may take some joy from you commenting on their cache, like the joy you took when you found it then do it!

     

     

    :unsure:

  17. I currently use GeocachingLive on Windows Mobile to type quick logs and then submit them to geocaching live server. Once home I login to the live webpage and send them to field notes and expand the logs before submitting.,

     

     

    Sounds like a lot of work but it's not too bad, as it also makes it a bit easier remembering which cache's i've done! I'm thinking of developing an application on Windows Mobile where it'll store the cache info (from a PQ) and then allow you to store all the info before copying over to pc when you get home. Similar idea to live but it hopefully won't suck up the battery power as quickly AND it won't require you to have signal like live does (PQ import doesn't currently work - all caches end up just off the coast near Hull!)

     

     

    :unsure:

  18.  

     

    ???

     

    It's only a game..............

     

     

    Nice constructive comments...

     

     

    As i said it doesn't really matter but since I was going out expecting an FTF when I got to the cache and found it was found a few days before was a little annoying that the cacher hadn't bothered to log their find online.

     

     

    Some cachers race after FTF's all the time - it's their game and what they like doing, isn't any problem with that - and I can imagine finding out that it had been found some time ago could be annoying to them to.

  19. I feel so computer illiterate this morning, as I am trying to set up my first Earth Cache and in the process of sending an email to the gentleman that runs the highway dept., I would like to include a link to several Earth Caches that I have visited....I tried to copy the link on the URL, but it's not the GC# highlighted that I am looking for. Any suggestions would be greatly appreciated. :ph34r:

     

     

    Bit confused why it isn't linking to the right cache but you can simply make your own by....

     

     

    http://coord.info/GC CODE HERE ie,

     

    http://coord.info/GC12345

     

     

    :lol:

  20. Apart from itsnotaboutthenumbers

    Do any other websites use the My Finds PQ for anything?

     

     

     

    Thank you

    Mark

     

     

    There's also mygeocachingprofile.com - it's not as indepth as itsnotaboutthenumbers but does give some nice information that can easily be imbedded into the profile. Also there's one with a weather map and michael fish :ph34r: - check my profile out

  21. Hi all,

     

    I've recently found logs that various cachers have made in the logbooks in my caches, but they haven't bothered to log their finds on the website. I guess this isn't really a problem, but I'm worried in case these people are also picking up travel bugs and not bothering to log those either, so they go missing from the caches they're supposed to be in, turn up unexpectedly in other caches, etc. Does this happen a lot, and is it a problem?

     

    Cheers,

    Toni xx

     

     

    I think generally people who take TBs will log on the website too thanks to the information on the tags etc. Obviously there will be a few people who pick them up without realising they have to log them etc. I don't have any problem with people not logging on the website if they don't move TBs apart from people who go for first to finds and then not log them for a few days. FTF doesn't really mean much anyway as it shouldn't matter if anyones found it before, but a few times when I've been out for an FTF and got to the cache to find it'd been found a few days before but they hadn't logged it on the website annoyed me a bit. Each to their own though :ph34r:

×
×
  • Create New...