Andronicus

OK, somehow that issue seems to have resulved itself. I don't know why... Last question. Often (more than 50% of the time) one or two of the map tiles will be incorrect, making for a garbled map. Here is an example where only one tile is mixed up. I have put a red square around it to highlight the problem tile.

Update: I was doing the import from within the app of an uncompressed gpx file. For some reason, I could't get the context menue to give me teh option for cachemaid when I would try to open the file from a file explorer. I just tried compressing the file to a .zip, then the file explorer did give me the option to open it in CacheMaid. So I did, and it worked. the import went fine. So, problem kind of fixed. However, I am still looking for a solution to the license error.

Hi onspot I have a new problem. I just got a Samsung S5 and am runnin LP. When triying ot import a GPX file from the SD card I get the following error: Error 2015-03-24 11:07:07 SAXParseException Cannot perform this operation because a nested transaction is in progress java.lang.IllegalStateException: Cannot perform this operation because a nested transaction is in progress. at com.chachemaid.lib.i.a.endElement(Unknown Source) at org.apache.harmony.xml.ExpatParser.endElement(ExpatParser.java:156) at org.apache.harmony.xml.ExpatParser.appendBytes(Native Method) at org.apache.harmony.xml.ExpatParser.parseFragment(ExpatParser.java:513) at org.apache.harmony.xml.ExpatParser.parseDocument(ExpatParser.java:474) at org.apache.harmony.xml.ExpatParser.pars(ExpatReader.java:316) at org.apache.harmony.xml.ExpatParser.parse(ExpatReader.java:294) at javax.xml.parsers.SAXParser.parse(SAXParser.jave:390) at javax.xml.parsers.SAXParser.parse(SAXParser.java:326) at com.cachemaid.lib.i.a.a(Unknown Source) at com.cachemaid.lib.i.i.a(Unknown Source) at com.cachemaid.lib.i.i.a(Unknown Source) at com.cachemaid.lib.i.i.b(Unknown Source) at com.cachemaid.lib.i.i.a(Unknown Source) at com.cachemail.lib.activities.p.run(Unknown Source) atjava.lang.Thread.run(Thread.java:818 Like previously, I am trying to import a gsak generated gpx file (found here) Also, I now have a "Not licensed! Go online to verify that you ahve bought the full version to get rid of this message!" How do I get rid of that? Where do I go online to do this? (I indeed paid for this app a year or so back. PS I am using version 4.11

I just got an S5 too, and so far I love it. And I love that is it Waterproof! I have a protective case for drop protection for when I am out and about. I bought the wireless charging setup for it too, so I don't have to keep opening the USB cover. It is easily visible in direct sunlight, has a replaceble battery. It realy meets all my needs. PS, I rooted it with ClockWorkMod, and flashed the CyanogenMod 12.0 ROM. I'm Lovin it! As for a Primuim Membership, If you are planning to find more than 1 or 2 a day, it sure help. The various approved apps will only let you load details for 3 per day with a Basic Membership. Right now, I have not been doing much caching at all, so a Basic Membership is working just fine for me. I will go back to PM next time I'm doing more caching.

If your on a budget, you can do like I did. There are rare times I would like a handheld. There are also times when I take the kids or a noob with me that I would like to had them a GPS to use. So I bought some old Garmin eTrex of of kijiji (kind of like craigslist). pay $35 or $40 max. Don't get suckered into paying more. And make sure it has an H in the part number (eg. eTrex Legend HC). That H is super importent, it is the newer much better GPS chipset.

Your phone will work fine. S4 mini is a nice unit. However, if you are going off the beaten trail and/or outside of cell coverage, you need to prepare. I have a thread that is a nice guide to help with the verious issues you will likely run into. It is a little old, but most of it is still relevent. http://forums.Groundspeak.com/GC/index.php?showtopic=241889&view=findpost&p=4224465 Edit to add: here is another good link http://forums.Groundspeak.com/GC/index.php?showtopic=305204&st=0&p=5191286entry5191286

Seems to me that the rules for this have been changing lately. Like naraD suggested, check with you local reviewer.

I think what you will find is that cell phones can use A-GPS when in cell phone coverage, allowing them to lock very quickly. Most cell phones are just as accuriate as handheld GPS, but not as sencitive. The result is poor performance under tree cover etc. That may or may not hav changed with the newer phones. My new Samsung S5 I haven't tried out in the trees yet.

Your phone GPS (in the S4) is very good. You can expect no worrs than 5m accuracy with reasonable conditions. Things that will reduce your accuracy are: Tree cover, nearby buildings (blocking the view of satellites and causing multi-path), atmospheric distortion etc. More likely, you are just new, and need more practice. First, make sure your first few caches are "Regular Size", or maybe "Small". Definatly not "Micro". Look for caches with 1, 1.5 or maybe 2 star difficulty rating. Don't search for any with a higher rating until you have found a few. When your GPS shows you reached ground zero (GZ), put it away and start looking. Your GPS will rarely pin point exacly where a cache is. Look around about a 5m radius from your GZ.

Are you using the free intro app? If so, it only shows caches that it determins are 'good' for beginner cachers.

Thanks for the pointers. Since the rescuer is a new cacher (only 2 finds, the rescue and the drop), I didn't want to confuse him/her too much, so I did what you suggested myself. All these step were done online, no physical moving or grabbing was done: Step 1) Grab the TB from GC1JC2F. Step 2) Drop it into GC3WQYC, using a Note log type, using a date prior to newbie's rescue, but after another cacher reported no TB in the cache. Step 3) Grab the TB from GC3WQYC using the date newbie resued the TB. Step 4) Drop the TB into GC1JC2F , using a Note log type, using the date newbie dropped the TB off Step 5) Delete unused cache Note logs from steps 2 and 4; Delete unused TB logs from steps 1, 3, and 4 (insuring I left the log from step 2, that is the whole point of this excersize). Step 5) Edit travel but log from step 2 with some details about what happend.

Take a look at my TB T-Shirt http://coord.info/TB3MK09 I just purchased a TB, then made a QR code of the tracking number, did some editing of the QR to put the TB scarib on it, then used zazzle to get a shirt made with the QR code. I wear the shirt to events, and people can scan the QR to get the tracking code and discover it. I also use it as a personal tracking trackable, visiting it to all the caches I find. The android app CacheSense does that automaticaly for me. PS, The QR code on the TB page is not the tracking code...

I had a travle bug go missing from a cache coord.info/GC3F9QN). Soon after the cache was archived. Just a couple of days ago, a cacher found it in a cache about 500 miles away (coord.info/GC3WQYC) a year later. He has now dropped it into a different cache (coord.info/GC1JC2F). Unfortunatly, the rescuer didn't log it as having been in GC3WQYC. What is the best way to fix the problem? Could I log a earlyer dated "Note" to GC3WQYC with a drop action, or would it be best to get the rescuer to do something like that?

I blam the this childishness on the fact there are way too many challange caches out there now. This Mr.Yuck situation has me feeling disillusioned. So much so, I am taking a break from these forums for a while. I encourage anyone else feeling disillusioned to also take a break.

Can you help us help you? What app are you using? On what device are you using this app? The first things I would look at is that your phone's GPS is turned on. Then reboot your phone. Then if the problem is still there, run a GPS status app (there are lots in all the app stores), and insure your phone is locking onto the satallite signals

Guessing thats yourself then? No, Uncle Alaska has 'only' in the 2000s. There is a cache stats site that tracks all this. Google it if you are interested.

Wait, what happened to Mr Yuck (or the cacher formerly known as TheWhiteUrkel)? What? He left for good? Hmm... If that is true, looks like my 4WD thread was the last one he commented on. To stay on topic Wait, what happened to Mr Yuck (or the cacher formerly known as TheWhiteUrkel)? Yeah .... me too. He always seemed to have good words of wisdom. I have a friend that was doing some streak or other, and he just left unfound caches in the area so he could go out the days he needed a cache, and not have to go far. I thought Mr Yuck always contributed to a positive forum community experience. He was a wealth of knowledge about geocaching and forum history. Sad day. I'd sure like to know why! But anyway... to those that have posted that they see this (being concerned about deliberately logging the wrong date) there is more to it than simply cheating the system. When you do that, you are misleading both the cache owner, and future finders about the state of the cache. Agree about Mr.Yuck. I've always seen his posts as a positive contribution even during the times I disagree with his opinion. As for fudging dates, I wouldn't bat an eyelid over a day or two (though I might roll my eyes if someone brought it to my attention). But if someone finds 30 caches in a day and spreads the logs over a month, yeah, that could be very misleading. When trying to track down a missing trackable, even one day can bugger up a search.

I like CacheSense. It does everything you could imagin. It have very powerfull filtering capabilities. If you hate micro caches as much as I do, that is very good.

Well I agree on that point. You put caches out in high numbers and you think they are going to follow YOUR rules? And as for the animals messing it up. I think you got that backwards. They were there first and you messed up their homes knowing cachers will come and tromp all over. I a have never met a 37 year old coyote, so no, they weren't there first. I'll let you guys get back to getting your panties in a bunch. Glad I could be the subject of your hand wringing for a day. You will soon move on to the next issue to get you all fired up and continue to give yourselves ulcers and gray hair. LOL. Buh bye. Is this an example of how the rest of us should behave on this forum? Maybe someone should mention to elrojo14 that ulcers are not caused by stres.

Colorado is a lot like Alberta, so I figured this one is likely not 4x4 only. Sure enough, google satellite shows many hiking trails all over that area. That is a good example of BS 4x4 only geocaches.

In those cases, I wouldn't log a "Found it" for that challenge cache. Fortunately, I don't need to find every cache out there. +1

70 km is quite far. But you could do the round trip in 1 week. And you probably should pick weather that is a little cooler than 50°C Edit, Google maps shows it as 30km to a highway. Looks like Dec-Feb should provide OK weather for making this hike. That said, I can sure see why you would want to use an ORV. Turn a 3 day hike into a 1-2h drive.

This is not a downloading limit. This is a downloading via the API limit. The API is relativly new, and full access to it has always been a PM feature. PS, I am in the same situation right now. Normaly a PM, currently a Basic member. It is annoying, but considering how little caching I have been doing recently, it hasn't been a significant problem. (I use cachesence on Android) I have been able to do it in the past so I would say this limit is new. I have had GSAK for years, this is the first time I have had an issue. No, this limit is not new. I am not sure how GSAK used to work, but once the API was available, GSAK started using the API. The API has always has this limit for Basic Members. Edit: NYPaddleCacher states that V8 of GSAK started using the API. Again, the API has always (since it went public) had the basic member limit. The API didn't used to exist. I am not sure why you think that it is an integral part of the caching experience. It is only what, 4 years old? But now it is a basic right of geocachers to have full access to it?

OK, here is the guidline again Ok, I think I get it, you realised that you should not have "create(d) a hole in the ground when placing... (the) geocache." So now you have changed the hide style to Suspisious Pile Of Rocks (I would just call that a geo-pile). Good. I hope that we have all learned a valuable lesson not to make holes in the ground when hiding a geocache. Doesn't matter if it is just desert, just don't do it!

70 km is quite far. But you could do the round trip in 1 week. And you probably should pick weather that is a little cooler than 50°C Edit, Google maps shows it as 30km to a highway.