Jump to content

ZSteve

+Premium Members
  • Posts

    31
  • Joined

  • Last visited

Everything posted by ZSteve

  1. On a related note - For some reason the app will only let me scroll back through the first 20 or so Activity Logs. If I try to scroll past that to see earlier logs, it just spins as if it's trying to pull in more logs. I'm on version 1.3.11 build 2618, although I first noticed it prior to updating to this version.
  2. I'm finding this to be a very frustrating tool to use so far - hoping that some updates can be made soon. Here are some thoughts based on what I've seen so far: 1) The defaults should be set to the most logical search parameters - All Cache Types, Sizes, and DT Ratings should be set on. Why would the defaults be set to a combination that yields no caches? - If I input coords into the search field on the main page, I get everything within 10 miles (which is what I would expect). But, if go to the filters to make my search, I have to the turn on all the settings for Cache Types, Sizes, D and T Ratings. - When one resets the filter parameters, all of the above settings are removed rather than everything reset back on. 2) The integration between a quick search from the main screen (where one inputs coords or GC#, etc and gets a 10 mile radius return) and the filter does not appear to work. - If I input coords into the box on the main page, I get everything within 10 miles (which is what I would expect). But, if I then go to the filters to adjust something (usually the distance), even if I turn on all the settings for Cache Types, Sizes, D and T Ratings, the filter crashes and I get all 3+ million caches centered around my home coordinates. - It's only when I do all of the above AND delete and then reenter the coords in Location Search field that I get a good filter of caches. - In fact, it appears that every time I want to adjust the filters on my search, I have to delete and then reinput my search coordinates even though the filter already shows my old search coordinates in that field. 3) There is no memory to the filters. - If I go straight to the filter to do my search and input coords, set the distance, and turn on all of the parameters, I get the results that reflect the parameters that I input. But if I then go back into the filter to change something, some of the settings have been changed (for example, Cache Type and Size settings have been cleared). The filter should remember the parameters being used until one hits reset. (Also see note in (2) above about having to repeatedly reinput search coordinates) - Anytime the filter crashes and results in a response of all 3+ million caches centered around my home coordinates, the filter clears any parameters that I set. The old filter would return zero caches, but remember the settings so that one could go make changes as needed to get what I'm looking for. The penalty for making a mistake or changing your mind as to what you're looking for shouldn't be starting over. 4) The Search routine no longer allows one to search archived caches. There are lots of reasons to search for an archived cache and one doesn't always know if a cache has been archived when they start the search. I don't understand why this functionality would be removed. And while there are work-arounds, expecting the general caching community to use those work-arounds will discourage people (in my opinion). 5) When I do a search by coordinates, those coordinates are then "frozen" as a selection in the filter - which makes them un-editable. When I do a search by coordinates, I usually want to edit them most (90%?) of the time. Being able to retain the ability to edit the location/search input would be very helpful whether it be coordinates, names, GC codes, etc. Having to redo work is never fun. (Of course as noted in #2 above, one currently has to completely reinput them every time, so this comment really applies once that issue has been fixed.)
  3. So....How to do I find an archived cache? Pretty important feature, so I must be missing something basic. We used to be able to input the GC# and have the option to select that one cache. I don't see anything in the search settings that lets me select that as an option. I guess one can edit the URL to go to a specific archived cache, but that seems like a pretty inefficient way to get there.
  4. Hi Rui! Hope all is well! Yes - It's there. I was simply pointing out that I didn't receive an email notification and also that emails for events in my notification areas weren't consistent in case that's not what HQ intended. If I wasn't supposed to receive an email as the Owner/Host of an upcoming event, then no worries. It doesn't matter in my case since I received other notices. But, I was simply pointing out that there may be Event Hosts that didn't receive the HQ message.
  5. Yes - Nothing in spam. If it matters, mine is a regular event, not a CCE. As noted, I received messages for other events, so am obviously aware of the notice. Just simply pointing out my observations in case the notification process didn't go as intended.
  6. Thank you HQ for doing this! Oddly though, I received a notice for events in some (but not all) of my notification areas, any regular event that I had logged a WA for, and any regular event that I am watching, but I didn't receive a notice for my own event. I did check and one was posted. I wonder why the owners of events don't receive this announcement? Or why I didn't receive a notice for events in all of my notification areas (even though they were also posted)?
  7. Not sure #6 will be available that early. It's inside a building. I believe that 17-22 will be on foot (or bicycle) and a parking permit is now required. I believe the permit can be purchased online for $10 for the day.
  8. With the combination of the DNF icons obscuring the cache type icons on the map, and the cache health score counting even a single DNF as a negative mark against the cache, people may start using DNF logs even less than they did before. This exactly is what I fear, too. And I'm the best proof for it... Converted most of my DNFs without later find to notes already. Just the DNF icon doesn't help me at all I personally don't care for this feature either and will probably delete my DNFs and stop logging them in the future. If there's something important that I want to tell the CO, I'll probably use a note. I want to see what's out there to find by cache type. Additionally, for some reason seeing a DNF cache on the map gives me the impression that it's a cache that's missing and I shouldn't bother with it. I know that's not how it really works, but that's the natural reaction that I have.
  9. I think this is universal and probably relates to the map change. When I try to create a route query, there is no map showing in the block provided and several of the query parameters are missing. Pretty sure it's a bug and I'm sure there are lots of users waiting for the fix. Not sure where in these forums one goes to find out if anyone is addressing the issue.
  10. If the e-mail of the 500 cache gpx files is working, maybe an interim work-around would be for Groundspeak to waive the 5 query daily limit and we could run smaller queries. We'd still have to spend time changing queries, but at least we'd get the information.
  11. It's kinda working for me, but incredibly slow. Looks like the servers can't keep up with handing out those tiles. It does take a few seconds, but then the caches show up. However, when I click the personalize box, the caches that I've found turn into smileys (which is good). But, when I then click the smiley box (to get those to disappear from the map), all caches disappear - not just the one's that I've already found. Oh wait - I just looked again and it looks ok. Just took a LOT longer than a few seconds for them to reappear.
  12. Had some queries run 15 minutes ago. Got the email notifications and the Active Pocket Query tab shows that they have run. However, they are not in the Pocket Queries Ready For Download Tab.
  13. If you would, please send me a copy of any picture you are having trouble with (my email address is shown on my profile page) as well as where you are trying to upload it (specific log or specific cache). Hopefully we can pin down where the problem is occurring. email sent...
  14. It looks like 74-79 gets you the coords for GC1JD8E. Does anyone know if this cache is convenient to the route at that point?
  15. Yeah - Unfortunately, I've run mine at 1000 and can't download them and since the limit is 5 per day, I can't rerun them at 500. I love the 1000 limit though, just have to be able to download them.
  16. Me too - Hope it gets fixed soon as I need these for tomorrow.
  17. I noticed that this feature is now active, so I gave it a try. It worked great from my perspective. I'm sure that there will be ideas on how to make improvements, but I really appreciate the upgrade. Thanks!
  18. I'm really excited by the increase to 1000 and can't wait to see it happen even if it means that I might have to change the way I currently handle PQs. For me, it will be a big benefit. Thank you!
  19. This is a known issue and we hope to have it corrected for the next release. The logic behind it being if you log your caches from a multi-day trip then you only have to change the date once for each day of the trip that you found caches on. you don't realize the benefit of it keeping the last date. Emphasis added. I'm guessing it's timezone-related instead. I wonder if this discussion isn't mixing two separate items. I read Tsegi Mike's post to identify an issue with the default log date when he first went in to log a cache in his session - it should default to the current date, not a different date. The other posts are expressing a desire to make sure that fixing that issue does not impact the different feature that defaults the log date for subsequent logs to the most recent log date in the current session. I agree - That's a very valuable feature if one is not using field notes.
  20. Yes. It is Groundspeak that interprets the time incorrectly. I've uploaded some screen shots, it may help get my point across better. What is your time zone in your profile set to? Is it set to Mountain time? Let's assume it is. Let's say, you go out at night of Jan 19, and found a geocache at 12:30 a.m. (after midnight so local time is now Jan 20). You press "Found" on your GPSr. The field notes record "Found it" with time stamp of 2010-01-20T07:30Z since MST is UTC-7. You upload it, and it shows in the Field Notes page as 2010-01-19, because it converts it to PST. Time, not shown, is 23:30 You click "Compose Log", and the date it filled in automatically is 2010-01-19. Time, not shown, is 16:30 (23:30 - 7 hours). Now, let's say you found a cache at 5 a.m. in the morning of Jan 20. The field notes record "Found it" with time stamp of 2010-01-20T12:30Z since MST is UTC-7. You upload it, and it shows in the Field Notes page as 2010-01-20, because it converts it to PST. Time, not shown, is 4:30Z You click "Compose Log", and the date it filled in automatically is 2010-01-19. Time, not shown, is 21:30 (04:30 - 7 hours). Give it a try. That's exactly what I saw which led me to make my post (#2). I just didn't know why. It is the same issue - the caches that I had problems with, I had found early in the morning. Thanks for clearing that up. I'll have to watch future logs until this one has been fixed.
  21. Worse than that here . . . can't get cache listings to display at all, so can't see co-ordinates and can't even log maintenance on my own caches to keep them running for others. Had a brief go in local library, no joy, library also runs XP/IE6. I would agree with this - this 2000/IE6 user has many issues. - Maps don't work - Can't read many cache pages due to information flowing off the page to the left with no scroll bar - The nav menu isn't on a number of screens - When sending an e-mail, the text box resizes twice with every key stroke - Date issues with some field notes - etc The site really is unusable now where it was very usable before. At least if I'm patient, I can still run PQs, so I'm able to get the data offline and work with it there.
  22. I'm having problems with dates too, although I think I have a different issue. I've just noticed this issue, so maybe it's a result of the latest site release issues. On my field notes page, I had a few caches listed with a date of 01/17/10 and a couple dated 01/18/10. Since I wasn't ready to log the 01/17/10 caches yet, I decided to go ahead and get the 01/18/10 caches logged. When I went in to compose my log, the date had been changed to 01/17/10. This happened on both caches.
  23. I have to think that what you are experiencing is unrelated to the site update. We are not seeing widespread reports of site slowdowns, and no changes have been made to the servers that I can imagine would affect their performance. The changes to the site infrastructure made by the redesign should actually have sped things up if anything. It crawls for me too - I can't think of anything else that has changed other than the update.
  24. Boy - just sent and e-mail to another user. That was awful...
×
×
  • Create New...