MorrisonHiker

If you click on the Compatibility View button to the right of the address bar, it will fix the issue. I've noticed a few other minor things that don't work in IE9 and the Compatibility View button fixes them all. Eventually Groundspeak will fix these issues, I'm sure. Until then, use the Compatibility View if you see something that isn't working.

It's working fine for me in IE8. Have you logged out/in and cleared your browser cache? I'm still getting the old Seattle map for both links and my home location has been in the system for over a year now. Maybe they forgot to actually merge this bug fix into the release build? http://www.geocaching.com/map/default.aspx http://www.geocaching.com/map/beta/default.aspx?lat=47.67784251720985&lng=-122.34113216400146&z=15 These coordinates are NOT my home coordinates.

Probably the most fun that I've had geocaching was a night cache that I did earlier this month just south of Flaming Gorge. If you are in the area at night, check out Johns' Wild Animal Forest Cache. It is a large sized cache...but be sure to bring your headlamp or a good flashlight along. We found several other great caches in the Flaming Gorge/Vernal area...so don't give up just yet!

I finally found the duplicate entry. Instead of opening the GPX file as an XML document in Excel, I opened it as a read-only worksheet. This allowed me to see multiple entries for each cache location...and see the duplicate log. I removed it and that reduced my Found count. I'm chatted with Groundspeak and they are aware of the bug which prevents 20 caches from appearing at a time. A fix is on its way.

I did a little more checking and found that page 17 (of my 18 pages) only has 19 finds listed and the last page has 6. The 17th page should be showing 20 finds (20*17)+6 = 346. Looks like it's really only showing 20*16 + 19 + 6 = 345. I'm guessing I had an incorrect entry at one time...and now the counts are off...and the pagination is incorrect on that page. I guess I'll be reporting a bug to Groundspeak.

I've noticed a similar discrepancy with my cache counts for some time. Right now, Geocaching.com shows I have 346 finds. However, when I view the GPX file, there are only 345 finds. When I generate my stats on MyGeocachingProfile.com, it shows Total Caches 346 (345 distinct caches). Where is the other cache coming from? I believe when I first started caching that I accidentally logged a find twice...but I believe I later removed that found log. I've tried many times over the past few months to review the GPX file...but since I'm "short" a record, I don't know how I'm going to find what's missing. Any ideas?

I just did this one in Utah last week. It was my first night cache and was really fun. When I got home, I was disappointed to find the closest night cache in my area is about 90 minutes away...and that's the ONLY one nearby. John's Wild Animal Forest Cache: GC2C4AF http://www.geocaching.com/seek/cache_detai...88-6ba9af1ce2bb

Two weeks ago, I was preparing to place a cache at a historical point of interest only to find that the last stage of a multi had been placed nearby but had yet to be published. I was disappointed at first but forum members pointed out that I could place an offset multi instead. You could place your first stage virtually at your desired location and have the finder use a hint to find the physical cache a tenth of a mile away. Virtual stages aren't subject to the minimum distance from another cache rule. You could start your cache on that bridge, have them read a number off the bridge or count the number of bolts to determine where the physical cache is located nearby. Even though you are in a small town, I bet you could still fit a few caches in this way. I managed to find room for mine. Good luck!

Yep...the reviewer wrote back and said he'd missed the part about the first stage being a non-physical stage. GC2DC8G Mt. Falcon's Summer Home for the Presidents has been published. Thanks for everyone's comments!

The unpublished cache was finally published in the middle of last week. I resubmitted my cache using your suggestion. I made the actual historical plaque the first stage (non-physical) of an offset multicache. The physical cache was placed about 550 feet away. The reviewer rejected it again saying that it was withing 128 feet of a stage of the other cache. I'm hoping that this reviewer just didn't notice the note which indicates the first stage is non-physical. The reviewer quoted the entire Cache Saturation rule...but must not've realized this was a non-physical stage. Non-physical caches or stages including reference points, trailhead/parking coordinates and question to answer waypoints are exempt from this guideline. Additionally, within a single multi-cache or mystery/puzzle cache, there is no minimum required distance between physical elements. I forwarded it back to the other local reviewer and hope they will approve it. Am I understanding the rules correctly? Non-physical stages shouldn't be subject to the 528 foot rule. Is the other cache a traditional or a multi? It is possible that your virtual stage is not the one that is too close. Sorry I didn't make that clear in my last post. The other cache is the final stage of a multi-cache. That stage is 128 feet from the non-physical stage of my cache. When they rejected my cache (again), they again mentioned the cache by name...so I know that's the cache that's causing the problem. Theirs is a physical location...but from what I understand of the rules, non-physical stages (even for unrelated caches) don't have to follow the 528 foot rule. I agree, non-physical caches should not be subject to the saturation restrictions by the current guidelines. Being as the cache you are said to be too close to is a multi it is possible that one of the intermediate stages is near your final location. You will need to either check with your reviewer or find all stages of the other cache. I spent over 4 hours yesterday and hiked 9+ miles finding all other caches in the area and the other 7 stages of this multicache. The other caches and stages are far away from where I've placed my non-physical initial stage and the final physical stage of the cache. Again, I think the reviewer just didn't read the note that I left to indicate the first stage is non-physical. Hopefully they will review it in detail and realize their mistake. BTW...the reason I can't move my non-physical stage is because it is a historical site. I want to bring users to the location and teach them about the site by having them read the plaque there. Once there, they can use a number on the plaque to decode the final coordinates. The multicache that is placed nearby doesn't mention the historical site at all.

The unpublished cache was finally published in the middle of last week. I resubmitted my cache using your suggestion. I made the actual historical plaque the first stage (non-physical) of an offset multicache. The physical cache was placed about 550 feet away. The reviewer rejected it again saying that it was withing 128 feet of a stage of the other cache. I'm hoping that this reviewer just didn't notice the note which indicates the first stage is non-physical. The reviewer quoted the entire Cache Saturation rule...but must not've realized this was a non-physical stage. Non-physical caches or stages including reference points, trailhead/parking coordinates and question to answer waypoints are exempt from this guideline. Additionally, within a single multi-cache or mystery/puzzle cache, there is no minimum required distance between physical elements. I forwarded it back to the other local reviewer and hope they will approve it. Am I understanding the rules correctly? Non-physical stages shouldn't be subject to the 528 foot rule. Is the other cache a traditional or a multi? It is possible that your virtual stage is not the one that is too close. Sorry I didn't make that clear in my last post. The other cache is the final stage of a multi-cache. That stage is 128 feet from the non-physical stage of my cache. When they rejected my cache (again), they again mentioned the cache by name...so I know that's the cache that's causing the problem. Theirs is a physical location...but from what I understand of the rules, non-physical stages (even for unrelated caches) don't have to follow the 528 foot rule.

The unpublished cache was finally published in the middle of last week. I resubmitted my cache using your suggestion. I made the actual historical plaque the first stage (non-physical) of an offset multicache. The physical cache was placed about 550 feet away. The reviewer rejected it again saying that it was withing 128 feet of a stage of the other cache. I'm hoping that this reviewer just didn't notice the note which indicates the first stage is non-physical. The reviewer quoted the entire Cache Saturation rule...but must not've realized this was a non-physical stage. Non-physical caches or stages including reference points, trailhead/parking coordinates and question to answer waypoints are exempt from this guideline. Additionally, within a single multi-cache or mystery/puzzle cache, there is no minimum required distance between physical elements. I forwarded it back to the other local reviewer and hope they will approve it. Am I understanding the rules correctly? Non-physical stages shouldn't be subject to the 528 foot rule.

Now that's an idea. I had planned on a multi on a nearby mountain...but maybe I could start a multi or puzzle cache at this spot instead. There is a year etched in stone that could be used as part of a multi or puzzle cache.

Probably more than a few weeks, probably less than a year, probably a few months. I don't believe a reviewer will allow the claim to be held forever if there is pressure to publish another cache. Your choices seem to be find another location that does not have proximity issues, or wait a couple months and if the cache is still not published drop the reviewer a line and ask how much longer, your ready to go. But then if it is published you will need to find another location anyway. Seems the best strategy is go for a second location and publish. Yeah, I have other caches in the area...but this location is of historical importance so I was hoping to place a cache there and give details about the history. Hopefully the other cache owner will do that...and not just set up a micro cache with no description. There are other places on the mountain that will work...but this spot would be the best.

Is there a time limit on how long a user can have an unpublished cache? I'm asking because I've been watching a certain location for months and finally decided to place a cache there last weekend. I got the cache ready but before making the arduous hike up the mountain, I emailed the local cache reviewer to check on the coordinates. The reviewer said that the coordinates were within 200 feet of another cache...but the cache they mentioned is unpublished. Since the cache numbers are sequential, I believe the other cache was created within the past 9 days (since the other GC code came after one I created 9 days ago and before the one I created 2 days ago). How long does the other cacher have to place the cache? Weeks? Months? Years? Is there anything to prevent someone from "staking a claim" and never actually placing a cache in that location?

I went to Hawaii in May and took a list of over 50 caches that all should've had TBs or geocoins in them. After three days of caching, only ONE of the caches had a geocoin in it...and it was about the 16th or 17th cache we found. It's very disappointing when you're trying to do a bug trade and can't find any bugs to swap with. I left several geocoins without swapping...and many of those coins have since disappeared.

I had an 8 GB card in my 450 for a few weeks. Once when I was on a caching road trip, none of my caches would load. When I got home, the micro SD card worked fine when connected to the PC...but the 450 had problems reading the GPX files. I can't remember if I had a problem in the field requiring a battery pull. I have since installed all GPX files on the built-in memory (since I'm only using about 500 MB). I swapped the 4 GB card from the Nexus One with the 8 GB card from the 450 (so now I have room for more movies when traveling). I'll try the 4 GB card again eventually...but am trying to see if the corrupted GPX problem returns when using the internal memory

Last weekened, all of the caches disappeared from my Oregon 450. Luckily it happened after I arrived at the Cache Across America cache location. I tried removing the SD card and putting it back in and then some caches loaded...but the caches located along the drive home didn't show. I forgot to take my USB cable along with me, so I was unable to connect the Oregon to my dad's PC and copy new GPX files over. I tried using a microSD card adapter with the SD card but then my dad's PC wouldn't even boot up! When I got home, the card worked fine on my PCs. I removed the old GPX files and copied new ones over. So far so good...but I'm thinking I might stick to internal memory for a while and see if the problem goes away.

Thanks for the tip. I never knew you could send a GPX file to the phone. That would help eliminate manually entering the coordinates. Do you have any problem with accuracy when using the 5230? My 5800 didn't always point me in the right direction when I was close to some caches.

I used my Nokia 5800 to find a few caches in the beginning. I then had several weeks in a row where I wasn't able to find any caches with it. It just wasn't accurate enough to get me to the right spot. I still use my Nokia 5800 for navigation when driving. (Ovi Maps is great compared to the iPhone and Android phones since it is free, you can preload the maps and it works even when you don't have a cell phone signal.) My success rate in finding caches went way up once I switched to my Garmin Edge 305 cycling computer. It was a pain to input the coordinates, but it helped me quickly pass the 100 cache milestone. Since then, I've upgraded to the Garmin Oregon 450 and keep finding new features almost every week. Good luck with your Nokia 5800. It is possible...but it can lead to some frustration trying to input coordinates manually and writing down clues. Being able to load 1000 caches at a time via a file is SO much easier.