O.K. Here's my problem. I have a GSAK database with 600 caches (mainly along a route) in it for a trip that I would like to break down into (geographical) segments of 100-200 caches each to load to an iQue and possibly a magellan.

The question is....is there a simple way (readers digest condensed versions) to create export files from this one database in order to load to a device? There may be a filter method, but nothing that hasn't confused the daylights out of me so far.

Any suggestions? or, should I have just created seperate databases to begin with? If I were dividing it in half, I can see where filtering by user flags (or just including, then excluding for a mileage indicator from the nearest to center/home point) would work, though cumbersome. Otherewise, I have no clue what might work....

I know there is some really smart guy out there that has a nice simple solution.....

I would suggest making 2 or 3 DB's such as Trip1, Trip2, Trip3. You could then filter your first set of 200 based on perhaps distance, move them to Trip1 repeat for Trip2 and Trip3. This will leave you with 3 ready to upload databases that you do not need to muss with.

that sounds like a plan, but how do you move caches from database to database, and why? Or did you mean something else when you said to filter, then move to trip1?

quote:

Originally posted by geomuse:
that sounds like a plan, but how do you move caches from database to database, and why? Or did you mean something else when you said to filter, then move to trip1?

Moving/copying from DB to DB is done through the 'Database' menu and the 'copy' or 'move' and then choose which DB to go to.

Why? Depends on your needs. I've Exported 1,500 waypoints (filtered) before into a .gpx file in order to process them for my PDA. It was very slow in the processing, upload and operation of for my PDA. If you have the room and CPU power, then don't separate. Otherwise, do like Asgoroth suggests. Each may be exported in a number of formats. I've done that too. Ie: orange county, Redlands, between LA and San Diego and finally San Diego. Segments.

Thanks Joe. I would need teh main database broken down into smaller segments for two reasons. 1) - My magellan only accepts 200 waypoints into any given folder, and 2) My iQue will only map from cachemate about 150 caches at a time.

I guess my main struggle is how to effectively filter a GSAK database of 600 caches by distance into several segments (to later be moved to individual databases, or just export each filter as I create the filtered file)?

I know I can stop at a certain distance from centerpoint to include, say, 150 caches (i.e. 0 to 28.5 miles). But, then how do I resume at that same distance for the next segment of my journey (28.5 to 51 miles)?

Is there a function in the GSAK filter that does that? or, is the suggestion to move the entire first segment (once filtered)to a new database, then work with what is left, making the next closest cache the new centerpoint?

Sorry I'm slow guys, but I have not had to do this before. Just wanted to make sure I understand.

I've never done this before either, but it sounds like something useful.
There is a distance macro for GSAK that advertises: "This macro will allow you to select all caches within x miles of the currently selected cache". If you try this, please let us know how it works.

quote:

But, then how do I resume at that same distance for the next segment of my journey (28.5 to 51 miles)?

Is there a function in the GSAK filter that does that?

The Search->Filter settings let you specify a distance range. Next to "Distance" you'll see a drop down box. Pick "Between (Inclusive)". When you select that, two boxes will appear to let you enter the two distances in your range (ex: 28.5 and 51 in your example).

All AWESOME! Thanks guys! I'll give that a try tonight!

Update to my helpers:

1) I glaze over that the thought of macros. Although it sounds like a feasible idea, I just couldn't handle learning that concept so close to going out of town.

2) I looked at the "between" option and I just couldn't figure out how to maximize each segment and where the base of the radius might be. Again, devoting more time to this option would help out, but I am under a time constraint.

3) I finally re-read asgoroth's idea and realized how to execute it. It was a very simple solution. I moved each filtered subset to a new database, flagged the new "closest from home" cache, adjusted my distance until I obtained the desired number of caches, moved those out, then went to the next filter.

Easy and took me all of 5 minutes to execute.

All great suggestions, and I may explore the other options further at another time.

Again, thanks guys!

This message has been edited. Last edited by: geomuse,

I am glad I was able to provide a part of your solution. Happy caching.