You'll find that initially, you're using only about 1% of what GSAK can do when you create the data for your GPS units.
Here's how you can use it with your TomTom for the 'driving' part of the caching experience. It sounds like a lot of work, but since you'll have your Pocket Queries already loaded, after a 1 time configuration, it's just a matter of "Export" and copy the new file of caches to the TomTom.
In short - load your Pocket Query into GSAK, Export as TomTom POI file. Save the resulting POI (*.ov2) to your TomTom. It will automatically appear using the root of the filename you used to create it (e.g., MYPOISTUFF.OV2 will appear as a POI called MYPOISTUFF). You don't need to create the category on your TomTom. Putting the *.ov2 file on your TomTom automatically does that.
Navigating to Caches With a TomTom
Custom TomTom POI files are in a special format, and always have a filename suffix of "*.ov2". A custom POI can also have an associated icon unique to that POI type, and it comes in the form of a *.bmp" image file. The root names of *.ov2 and *.bmp files must match. So if you want to create a custom icon as well, a file called geocaches.ov2 must be accompanied by a corresponding image file called geocaches.bmp. As a reminder, TomTom icon images must be 22x22 pixels in size, and saved as 24 bit color depth *.bmp files. There are tutorials on the web for creating your own icons. If you don't need or want a custom icon, your TomTom has a selection from which you may choose.
You can create POI files from individual or Pocket Query *.gpx files acquired through the geocaching.com interface. My preferred tool for this purpose is GSAK (Geocaching Swiss Army Knife) available here -> www.gsak.net. It handles not only this task, but many others as well. Using macros, I can even take my PQ of an area and that of a friend, and compare them to see which unfound caches we have in common – a function often requested at geocaching.com, but as yet not delivered.
Premium members at geocaching.com have access to the Pocket Query system. I won't try to detail the setup and execution of a Pocket Query, but it's well worth the annual membership at geocaching.com, and is worth the entire price of the membership. Suffice it to say that you can download the results as a ZIP file, and the contents of that file are used to build your tomtom POI.
While some may consider it a bit of overkill, I build four different POI files for my tomtom units each week with new Pocket Query data. The first and most important of those is the POI list of caches in my area that I have not found. I then build a second POI file of my own caches, a third consisting of the caches I have already found, and a fourth of caches that I have found but that have subsequently been archived. Each has its own little icon on the map display to keep them straight, and I can turn each category on and off like any other POI on a TomTom. I'll place my four hand-built icons here if you wish to steal any or all of them.
.............................................................
Unfound..........Mine.................Found............Found/Archived
At a minimum, you'll want to create a POI of your unfound caches.
After loading your *.gpx file(s) into GSAK, it's a simple matter of using the GSAK "File / Export" function and selecting "TomTom POI file" as your output format type. GSAK will create the *.ov2 file with whatever root filename you specify, and the filenames can be in the 'long' format. For example, mine are geocaches.ov2, mycaches.ov2, foundcaches.ov2, archivefoundcaches.ov2. Each has one of the above *.bmp files associated with it. For basic use, all you really need is one file of your unfound caches, and calling that geocaches.ov2 keeps it easy to spot in your POI list.
The way cache information is displayed on your tomtom is in part governed by the information you supply in the "Name" field during the "File > Export > tomtom POI File ..." procedure. I recommend that you use the following string there: %drop2 %con1-%dif1a%ter1a-%last4 %name
The string above not only provides a lot of information in the cache name, it avoids certain problems that can occur in the way your tomtom interprets POI names that contain digits and special characters in various positions of the POI name. This string inserts dashes into the result to largely avoid these parsing errors. The meaning of the above are
"%drop2" is the GC code for the cache, with the initial letters "GC" removed
"%con1" is the container size, abbreviated as a single character. R=regular, L=large, M=micro, S=Small, V=Virtual, and U=unknown. If the cache type is not stated, the letter used is U.
"-%dif1a%ter1a" are the difficulty and terrain ratings, specially abbreviated to fit into a single character. 1=1, 1.5 = A, 2=2, 2.5=B, 3=3, 3.5=C, 4=4, 4.5=D, 5=5
"-%last4" are indicators of the type of the last four logs, found or not found. Found = F, Not Found = N, No log = 0. Since the field always contains four entries, the "0" indicates that there aren't that many logs available. The most recent log is always seen on the left. So "FNN0" would indicate that there are only three valid logs for this cache so far, that the first two logs are "Not Found", and the most recent is a "Found" log.
%name is the name of the cache
A typical cache listing would appear as follows on your tomtom using that string:
1WG29 R-A1-FFNF-Yet Another Cache
Another "TomTom-friendly" program that can handle conversion from *.gpx to *.ov2, but not as quickly, nor with the added features possible in GSAK, is Tyre, available here -> http://www.janboersma.nl/gett. After firing up Tyre, open your *.gpx file by selecting "File / Open" and from the "Files of type:" drop-down, select at the bottom, select "Garmin GPS Exchange Files". Once your *.gpx file is loaded, select "File / Save As" and in the "Save as type:" box, select "TomTom POI Files". Tyre will create your *.ov2 file using the name you supply.
Sadly, I know of no equivalent tools for the Mac. The above are all Windows-based applications.
Once you have your *.ov2 POI file built (and any *.bmp file you may have borrowed or created), on older models just drag and drop a copy right over into your big map folder on your TomTom and they're ready to select and use from your TomTom. Mine are all located in the folder called North_America_2GB. Newer models that use MyTomTom require that you use that application to move the *.ov2 file to your unit rather than the 'drag and drop' method.
One nice feature of the TomTom is itinerary planning (although beware – this feature is NOT available on many of the dumbed-down EasyMenu tomtom models, all of which I'd avoid for their lack of front-panel functionality. Models employing this less desirable interface at the time of writing include all of the following: Ease (Start2 in Europe), XL335SE, XL335LE, XL335LM, XL350, XL350T, XL350M, XL350TM, (XL IQRoutes2 in Europe), XXL550, XXL550T, XXL550M and XXL550TM, GO2405, GO2505. In addition, I would note that the models specified above will NOT allow you to directly enter coordinate data for navigation purposes! NOT good for caching!
You can built itineraries for your caching day using caches from your POI file. Scout out a decent route on the geocaching.com site, and you can enter each of up to 48 caches (96 on some newer models) in an itinerary and execute it. Your TomTom will take you from cache to cache. I usually delete each cache from the itinerary as I arrive since you often won't drive close enough to the actual cache location to cause it to be removed from the itinerary automatically. If you plan a monster day of more then 48 caches, just create a second (or third?!?) itinerary of 48 more.
OK! But, I have a Garmin Nuvi 200. Can I still do this?
