Jump to content

benh57

+Premium Members
  • Posts

    807
  • Joined

  • Last visited

Everything posted by benh57

  1. What golden ammo can? Not sure where your friend got his, but this isn't something official.. maybe a local caching group? -Ben
  2. benh57

    Route PQ bugs

    You can select the "preview" option on that page to see the count. I suspect the reason this isn't done automatically is because route PQs can take much longer to run than "normal" PQs. Nah. I suspect it wasn't done because they just added the feature to the normal PQ page, and forgot to add it to the CaaR version. The feature actually saves a lot of queries on the DB since a simple 'count' is a much smaller DB operation than clicking 'preview' repeatedly to see whether you are under the 500 limit.
  3. benh57

    Route PQ bugs

    - 'Cache along a route' PQ page does not show number of results the query returned like normal PQs do. (at the top of the query page) - After editing the CaaR PQ, the "placed date" option keeps switching back to "within the past week" from whatever i have it set to. (actually appears to be no selection at all, but the effect is the system selects "within the past week").
  4. Just had this problem, but i figured out that deleting my cookies (clearing old session cookie) fixes the issue.
  5. True, but the site does work quite well with teh back button since it doesn't use much dynamic HTML at all. And there are actually a couple parts of the site that do have return links -- when entering field notes, for example, there is a link to go back to the field notes list once you have successfully logged a cache. If you decide to attach a photo to that note though, the return link is lost, which is really annoying.
  6. Generally, such caches made it past the reviewer accidentally or they weren't aware of it.
  7. Advice: Always buy GPSrs from REI. Not the cheapest, but you can return anytime -- even years later.
  8. http://www.urbandictionary.com/define.php?term=whore Definition #2 . Whore Someone who does something excessively. You camping whore!
  9. Localizing software is really not that difficult or expensive. In fact, i bet geocachers would gladly volunteer to translate Groundspeak's string tables, if they provided them. Now, reprogramming the entire site to be *localizable* (or internationalizable) can be difficult if it was not originally programmed with that in mind. However, that only has to be done once. Once that task is done, adding new languages can be done basically for free (see volunteers above)
  10. Thanks for clearly describing your issue, benh57. I'll investigate. I am not seeing this issue. If I upload the same field notes the last one in the file does reimport, but that's because it technically does not fall "before" the cut-off date (it falls precisely on the cut-off date). Do you have more info to help me repro what you are seeing? Could I perhaps get a copy of the field notes file you are using? Thanks! Here's some better steps. 1. Find a bunch of caches (recorded in oregon field notes txt file) 2. Upload the field notes file, but don't log the caches yet. 3. forget to delete the field notes txt file from oregon 4. Find some more caches -- they end up appended in field notes file with the older finds 5. Upload file again --> All the finds from the first list are duplicated. Expected behavior: Ignore the finds which were already uploaded. Basically don't let me duplicate finds, that's never something i'd want.
  11. I think you are misunderstanding the function of this microfeature. I'm not sure why you saw the date stick after you deleted what I uploaded (perhaps cached in your browser or a side-effect of my spoof of your login), but it is expected that If you delete field notes, it will reset your time back to 01-01-0001. However, if you instead use the field notes (i.e. post them), the date will stick. The date sticks, but the feature doesn't work... it still imports the logs even though it says it won't. To reproduce, upload a field notes, log them using the field notes feature, then upload the file again -- they are reimported.
  12. Android is already out. Droid uses the same apps and market and platform as the T-mobile G1. (Android market) There are a plethora of non-official apps for it already, but an official one would be great.
  13. What was the name /coords? Many here would consider it a fun challenge to find it online.
  14. As others noted that particular power trail looks a little widely spaced. There are some closer-together ones, check east of Denver international airport (where the 413/day record was set), or west of Lancaster,CA (Tarot Series) or east of Lancaster,CA (NOCLUE series) On-foot power trails, one example I was looking at today is northwest of Ojai, CA (those are hiking, though). 70+ caches in a few miles on one trail.
  15. Another good way is to use the new GSAK 'check email' macro. I set up a secondary gmail account which gets instant notifications of all geocaching archival/ un-archival notices within 100 miles. The GSAK macro can be set to check this email address and update your db's status fields. This is totally allowed since it doesn't touch Groundspeak's servers.
  16. I see some validity in allowing caches with older placed dates than the current date, but i think it's reasonable to limit that to a couple months. If it's some sort of pre-geocaching container being used as a geocache then the 'date it became a geocache' seems more appropriate anyway. It should also be impossible for owners to delete any reivewer notes (such as the published log).
  17. He's right in that it is kinda unreliable. Often after a few pans / zooms it will completely stop displaying caches. If he is doing a lot of panning and zooming around then it's possible that it looks like it never works. The search box is also unreliable, but was slightly improved recently. At least you can search for coords now to zoome there.
  18. It's been this way for a while, but when you view another cacher's list of finds, ie http://www.geocaching.com/seek/nearest.aspx?ul=benh57 , within each day the caches are in ascending order of 'placed date' of that cache which makes no sense. Ideally, they would be in descending logID order. Which is chronological in the order the cacher logged them. Any chance that could be resolved for the next build? thanks! -Ben
  19. I know of a website with plenty of free ammo cans. People just put them out there, free for the taking! Here: http://tinyurl.com/yupfd
  20. I do not see these options. Where are they?
  21. Wow, this is a really substantial update ! Some long standing issues fixed. "My Finds PQ no longer calculated in daily quota" Excellent! Let's hope it doesn't add more issues than it fixes
  22. Investigated with firebug, it seems http://www.geocaching.com/css/general.css was coming back totally blank, and the server was saying it was 'not modified'. Cleared cache and it's good now. This is probably related to the firefox crash i had the other day, must have corrupted my browser cache. So, false alarm! Thanks! -Ben
  23. Interesting. I'll debug it a bit. Perhaps some extension is messing with it.
×
×
  • Create New...