+Geojiggs Posted January 18, 2007 Share Posted January 18, 2007 I am thinking of tring to establish a series of Pocket Queries too submit a list of all the GC's in Wisconsin. Mainly because I am starting to travel more around the state and it would be nice to have the entire state list in my 60cx as POI's Im sure I could setup a mutitude of Queries based on zip code but I'm afraid that I will get too much overlap or miss a large section. Any ideas? Thank you Kris Quote Link to comment
+unicyclist Posted January 18, 2007 Share Posted January 18, 2007 overlap should not be a problem, it would be the same as normal as updating the queries but the problem I see is missing a section, not sure about that part. Quote Link to comment
+Stunod Posted January 18, 2007 Share Posted January 18, 2007 (edited) The secret is to break your PQ's by DATE PLACED. You will get no overlap at all. Edited January 18, 2007 by Stunod Quote Link to comment
+unicyclist Posted January 18, 2007 Share Posted January 18, 2007 oh, I am thinking a little different. When you said overlap I thought of double entries in GSAK. Which I dont think would happen because they have the same way point name. Quote Link to comment
+The Jester Posted January 18, 2007 Share Posted January 18, 2007 It's not double entries that is the problem, but the limits on PQs. With a max of 500 per PQ, Wisconsin would take at least 11 PQs (5393 caches as of right now). If you have the same cache in multiple PQs, you may need to get more PQ's to cover the state. Breaking down the caches by date, you have zero overlap and can make the most effecient use of the PQs. Quote Link to comment
+txoilgas Posted January 18, 2007 Share Posted January 18, 2007 (edited) I am thinking of tring to establish a series of Pocket Queries too submit a list of all the GC's in Wisconsin. Mainly because I am starting to travel more around the state and it would be nice to have the entire state list in my 60cx as POI's Im sure I could setup a mutitude of Queries based on zip code but I'm afraid that I will get too much overlap or miss a large section. Any ideas? Thank you Kris If you are talking about Texas, do you realize that as of right now there are 16664 caches in the state of Texas. How much memory does your GPS have? Edited January 18, 2007 by txoilgas Quote Link to comment
+Geojiggs Posted January 18, 2007 Author Share Posted January 18, 2007 The secret is to break your PQ's by DATE PLACED. You will get no overlap at all. Sorting by date work fabulous, It took 13 to cover. Now to get them all as one file, any ideas here? Quote Link to comment
+StarBrand Posted January 18, 2007 Share Posted January 18, 2007 The secret is to break your PQ's by DATE PLACED. You will get no overlap at all. Sorting by date work fabulous, It took 13 to cover. Now to get them all as one file, any ideas here? Bring them into Geocaching Swiss Army Knife (GSAK) it will combine them into one. Quote Link to comment
+Driver Carries Cache Posted January 23, 2007 Share Posted January 23, 2007 Can we get some more details on how to go about this? Sounds like a good idea. Driver Carries Cache (madmike) Quote Link to comment
+Jennifer&Dean Posted January 23, 2007 Share Posted January 23, 2007 Take the GPX files you receive and import each one into the same database in GSAK. (Get GSAK, it is wonderful!) Then you will have all the caches for a state and will be able to filter them by difficulty, terrain, distance from a centerpoint, last logs, etc. You can export the large database back to a GPX file for import into a PDA. I recommend Cachemate on a pda. Most GPSr will only hold about 1000 points, so even if you get the whole state you probably won't be able to put them all on a GPSr. Just filter for the area or difficulty you want and you will slowly get to the point where you only get the caches you will be near during the trip. -J Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.