Improving data techniques with a Dakota
Posted: 02 July 12 9:04 pm
I'm looking for suggestions as to better use my Dakota 20. Currently I use it a fairly basic manner. I bring up a cache page, then down-load to the GPS. When we find a cache, I select "found" on the GPS and it no longer shows as a nearby cache.
There's several areas where I suspect I could improve my technique. Firstly, the down-loading. Currently I just open a whole bunch of caches in an area where we're likely to visit and work through them one by one down-loading them. I suspect I ought to be able to do them in a batch.
Secondly, the use of queries. Currently I simply use queries manually and select those caches we're interested in, using the above technique. I suspect that, again, they could be handled in bulk.
Thirdly, storage on the GPS. Currently all the caches are all mixed in together. The Dakota seems to have plenty of memory and hasn't objected so far but it seems inefficient to have a whole bunch of WA caches (from a visit earlier this year) mixed in with caches from my home state, Tasmania. Not to mention heaps of frogs, many of which don't exist any-more. Is it possible to have multiple folders on the Dakota so I can move them off to a PC when not needed?
I've got some vague ideas on the above issues but I'd be really interested in suggestions. Also any answers to the questions I haven't asked!! What I'm doing works but I feel that it could be done far better.
There's several areas where I suspect I could improve my technique. Firstly, the down-loading. Currently I just open a whole bunch of caches in an area where we're likely to visit and work through them one by one down-loading them. I suspect I ought to be able to do them in a batch.
Secondly, the use of queries. Currently I simply use queries manually and select those caches we're interested in, using the above technique. I suspect that, again, they could be handled in bulk.
Thirdly, storage on the GPS. Currently all the caches are all mixed in together. The Dakota seems to have plenty of memory and hasn't objected so far but it seems inefficient to have a whole bunch of WA caches (from a visit earlier this year) mixed in with caches from my home state, Tasmania. Not to mention heaps of frogs, many of which don't exist any-more. Is it possible to have multiple folders on the Dakota so I can move them off to a PC when not needed?
I've got some vague ideas on the above issues but I'd be really interested in suggestions. Also any answers to the questions I haven't asked!! What I'm doing works but I feel that it could be done far better.