Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by Falach-fead

  1. I started having the same error using Safari on an iPhone and still haven't resolved it, but have resorted to a work around: 1. Select the drop down menu list "the three horizontal bars in top right corner of screen" 2. Scroll down to "View Browser Map" and select it. 3. Expand the map by selecting "<" if not visible 4. Map can then be quickly resized/panned from home point to desired caching location. Note: the "View Map" selection on the drop down list gives the same error as seen why selecting "View Larger Map" on a cache page. Tested on a newer iPhone with Safari and "View Lager Map" feature works. Uncertain what the exact difference in the versions is, both appear to have the same Safari setup.
  2. There is an inconsistent issue with the the correct coordinates function. It repeatedly hyperlinks to the following page: https://www.geocaching.com/seek/# while waiting for logs to open. It appears to be directly related to the number of logs that a cache has and the inability to use the proper hyperlink until the page completely loads (in Mozilla). Other links seem to work fine except the cache logs link, which is expected. The solution would be to allow this link to load first like the others on the page and not after all the logs are loaded. In the meantime, expect to wait until logs load before you can link to the correct coordinates function.
  3. Using the PQ for routes very infrequently, I found that I had filtered for "I own" instead of "I don't own" on two Route PQs. The "I own" is on the second line first column for Route PQ filter...on a normal PQ, the "I don't own" is in that location. I suggest that those filter layouts should be the same for both a regular PQ and a route PQ. The two route PQs generated no caches due to the error in picking the correct filter. Instructions said to look for an error and fix it, which I did. The e-mail link I received now opens to indicate there are several hundred caches along the route, but only displays them 20 at a time. Nothing showed up the in the PQ download list to download the entire ZIP file. It would seem that the queries ran, but if you don't change the name of the PQ then it will not create a ZIP file even if the PQ was corrected and it contains hundreds of caches. To add to the frustration, the PQs that generated no caches due to errors count as 2 PQs towards the 5 PQs per day. The two corrected PQs also counted as 2 PQs for the day but created nothing in the download list. Since I had already ran 2 normal PQs earlier in the day, I still expected the first corrected route PQ to run and create a download file. Ideally, a PQ that creates no caches should not count against the five per day; maybe asking too much. A fifth PQ for the day that generates caches but does not provide a download file should definitely not be counted against the five per day. There is a bug in the creation of the PQ download file if you don't change the name. The only workaround that I have used is to change the name during corrections (usually simply adding an extra letter or number at the end) and resubmitting. The instructions to look for errors regarding PQs should include a note to change the PQ name before resubmitting.
  4. Wow, that's an awesome milestone for 24 hrs of power caching. To take a shot at the question of "why - dunno" In four years of caching, I have tried it twice along with my brother, a fellow cacher. Yes, it is partly about the numbers, but it was also about the personal challenge (planning, preparing, driving, biking, hiking, bushwacking for 24 hours). The caches found during those 24 hr days leave long lasting memories...give it a try some time. PS Bring at least 1 of those 5 hr power drinks!
  5. Yes you log a found as well if that is the case. A needs maintenance does not indicate that a cache was found. Often a needs maintenance log is entered by someone after getting a DNF if it is one of several in a row on a historically easy find that is most likely missing.
  6. Lost Blackberry as well and drove 1/2 hr back to area and retraced GPSr track for 20 minutes to find it. Lost GPSMAP60CX in a stream under the ice after it fell into an open pool at the base of a waterfall in March a few years back. The GPSr was returned 2-1/2 months later by a fellow cacher who found it under water just down stream from the waterfall...new batteries and it worked fine ever since.
  7. Many thanks to the developers for taking up the challenge and designing a new version that will retain much if not all the previous functionality and mitigate the stability concerns of the old version. Many thanks to all those that shared their take on the issue in the previous forum, I would like to believe our words did not go unnoticed. I look forward to trying out the new version.
  8. This has been answered several times, by several different people already. Run a Pocket Query, and drop it into Google Earth. Time required to perform the task beforehand: About 20 seconds. Time required to perform the task today: About 10 minutes. And yet the KML was dropped because it was slowing down GC.com. I haven't noticed that GC.com is 30 times faster without those "200" cachers accessing the GE KML feature. Yes, I know how the 200 was determined. I was not one of those 200 that used all 500 mouse movements on any given day. It would be interesting to recalculate as suggested by a previous post to see how many use 1-50 GE refresh movements though. I have not counted but suspect this thread will exceed 200 unique users if it hasn't already.
  9. I am sure this was possible to "duplicate" in one minute since the GC number is posted in the picture above! However Google maps does not duplicate Google Earth.
  10. I estimate that this took 5 to 10 times longer to create than if the KML feature was working. Not only slows down the process for me but perhaps the extra time on GC.com will contribute to slowing down the entire site. Without GE, many will never happen upon this unique series in their searches. (Of course, with the GC# taken from the image above anyone should be able to find the area quickly and display in Google maps.)
  11. I have already posted my request to bring back the KML link and I sure hope it does, but until then, any ideas to QUICKLY scope out new areas is welcome. Panning the google map on a cache page 1000 kms to locate some new location you may be going on vacation is painfully slow. I always did PQs centred from a GC# picked off a location in Google Earth and swept with the ruler to pick a distance for the PQ. Haven't found a fast method to do that. Once the PQs are in though, for Garmin users with MapSource, there is the View - View in Google Earth feature which duplicates the GE KML feature (with solid coordinates) for the 500 caches in a PQ or you can paste in as many as you want into MapSource (at least 3000) and then view them in Google Earth. It may be possible to run several 500 cache PQs to cover a large area and save them to one MapSource format file and then just run update PQs for the time period since the BIG download that you need. A few other notes: Loss of the feature also limits being able to search the world QUICKY for puzzle caches which provide great ideas for cachers in other areas that are putting out puzzles. It was also interesting to zoom in on other areas to see where in the world caching is taking place. I have seen it mentioned that GE was slowing down GC.com and that was the reason/part of the reason for dropping it. Without a doubt, I have found all the alterative methods required to "replace" the functionality provided by GE to be slower, require more steps and may only be available to those that use software such as MapSource.
  12. Yes, Bring Back Google Earth KML I use(d) Google Earth feature almost every time I wanted to look for new caches or do pocket queries for an area I was planning to travel to. How else can you quickly center on a cache in a location you are not familiar with and display the nearby caches quickly? How else can you quicklyopen, copy and paste a cache number into a query and search for the nearest 500 caches? How else can you quickly assess the terrain around a cache in 3D? I am sure there are many other advantages others have found as well. GC.Com, it was a mistake to drop the KML...maybe we can convince Dave Carroll to write a song and produce a video for YouTube..."GC.com Breaks Links"
  13. I just upgraded to Google Earth 4.3.7204.0836 (beta) and had the same problem. Even tried some different versions and they used push pin or switched after one time. The fix was when I downloaded the geocache browser in Google Earth the last time, I switched the Open With selection from Google Earth.exe to Google Earth.kmlfile(default) and the caches all appeared with the correct icons. The original push pin version was still in My Places list so both sets of icons were there. I deleted the one generating push pins and saved the changes to My Places when exiting Google Earth. So far it works when I open Google Earth for a new session. Hope this helps others F-f
  14. I had the same trouble with my legend. There are instructions on-line on how to take the GPSr apart. You should only need to take off the two outer wraps of rubber and adhesive strip that covers the buttons. I found the plastic button broken inside and was able to cut a piece of plastic into a "T" shape which would fit into the hole and activate the on-off switch. I re-used all the wrapping that was carefully removed during disassembly. I found that a glue stick was good for holding the rubber band in place.
  15. My Paperless downloads usually goes like this: 1. Check out the caching area using Google Earth and Geocaching.com Google Maps 2. Use Google Earth to select a centre cache to do a pocket query around and select a search radius that will not exceed the 500 cache limit of a Pocket Query or whatever the maximum limit is that I will chose. 3. Do the Pocket Query (try to get a PQ that will return less than the maximum requested so you dont miss any by mistake) 4. Download the Pocket Query zip file from the e-mail and unzip it. 5. Open the Cache and Cache Waypoint files with EasyGPS and save to GPSr 6. Open the Cache and Cache Waypoint files with CMConvert (converts the EasyGPS format to Cachemate format). 7. Select the waypoints desired in CMConvert and export as a Palm database file (*.PBD) which will automatically load into the Palm Cachmate program on the next sync. 8. Sync with Palm to load Cache and Cache Waypoints, so far there are 4000 caches loaded...not sure the maximum if there is one. Note: 1. If space is required, waypoints and tracks currently on the GPSr are downloaded and saved to MapSource and then the GPSr is cleared to make room for the new download. 2. I have Mobipocket on the Palm as well but don't use it anymore. The interface is cumbersome compared to Cachemate. Files for Mobipocket can be requested during the PQ and can be sync'd easily to the Palm if desired
  • Create New...