Xangxa

I do not use this macro so I can't 100% speak for Craig. However, I can tell you that the error is because you do not have a S&T saved setting called "PUSHPINS" Your are trying to run the macro command EXPORT using Settings="PUSHPINS" but the setting named "PUSHPINS" does not exists. What you need to do is go into the the S&T export and save settings under the name of "PUSHPINS". I would be very surprised if Craig has not made mention of this either in the macro or the preamble to using this macro together with his utility. What he said. You can fix it a couple of ways 1. Take out all the SETTINGS=PUSHPINS entries in the macro 2. Create a settings named PUSHPINS (see JUN 8th entry of THIS THREAD for step-by-step instructions).

More affordable alternatives are also available, such as DryPak, which can be found at Wal-Mart.com or a local boating store. If you want something hard-case, then Pelican Boxes are a more affordable version of the Otter Boxes.

PocketStreets will work with a GPS, and in fact I used it this morning to evaluate alternative routes around a 4-car pile-up. But, as you said, it doesn't do routing. Here's a cheap work-around that I've used when planning a cache run. First, I use the desktop software (MSST) to plan the route. I make each cache a stop, and then print the whole thing to a file. I use Repligo since it create nice, small, iPAQ friendly files. But if you don't have Repligo you can use PDF instead. Free tools can be found on the web and the Acrobat Reader for PPC is free from Adobe. But look into Repligo while you're at it -- it's not very expensive and very popular with PPC owners. If you want voice-prompting, it's gonna cost. If you want automatic re-routing, it's gonna cost. Those features are just too high-end to get for free. I have iNAV's iGuidance and love it, but it wasn't cheap. There are cheaper alternatives and I'm sure someone will chime in with a recommendation.

The road detail on Topo 3D is very good, and is perfect for navigation. Since I needed the topo detail, I was willing to forego the auto-routing since I can do that manually. Even though I have an expensive and fancy auto-routing package (iNAV) that even gives voice prompts ("Turn left in 200 feet"), I don't use it much since I find the maps sufficient.

I think I have a solution. I think this is controlled by the SETTINGS= parameter for each export. Try the following and see if it fixes the problem. Start GSAK and go to /File /Export /Microsoft Streets and Trips CSV file... About half-way down the dialog is a field called "Cache Description Format" Change the contents of this field to the format you desire. I'm using "%con1 %code %Name by %By (%Dif/%Ter) %datepl" (to choose/understand these special tags click the HELP button, click the "Cache Description Format" field in the help window that's displayed, and then click the "Special Tags" link. Although not related to your problem, I also changed the "Waypoint Name" field to "%drop2_%typ1%con1_%dif1a/%ter1a %notGC %code" After you've filled out the dialog how you like it, click the SAVE button and give it a short easy name (I named my settings "PushPins") Edit the export macro so that it uses the settings you just created (e.g., I edited my PushPin.txt file and ensured SETTINGS=PushPins for every EXPORT command) Optionally, you might want to play around with settings until they're just right. Before testing, set a filter so that the tests files are small and fast. Manually export, using your settings, out of GSKA to MSST format Manually import into a blank MSST map SHOW INFORMATION for a pushpin If necessary, change settings, save settings, and repeat test

I'll second PDOP advice and add a bit. 1. Upgrade your MapSend to the TOPO 3D version. The NavTech street database is more accurate (except for things like fire and logging roads). Seeing the streets in relation to the cache can help with driving and parking decisions. I don't think there will ever be anything to completely solve the parking issue other than already knowing the area. 2. Use the pushpin feature of MS Streets & Trips. Then plan your cache route the day before. Turn on the POI's to identify nearby and free parking opportunities (restaurants, banks, etc.). Right-click the pushpins to jump to the online cache page and use the links to view aerial photos of the area. They can be very helpful in planning routes. Speaking of routes, use the route builder in MSST to build a route, with the caches as stops. Then print it out (or copy to a PDA). Then you'll spend more time on foot and less in the car. The routes are especially handy if you have someone to read off the directions (or you could buy an expensive voice-prompting program like iNAV's iGuidance for the solo trips)

You might be interested in this thread: Automating Microsoft Streets & Trips Pushpin Maps

You'll probably want to use a convertor, like those already mentioned, to prevent typographical, math, etc. errors. But I thought I'd answer your specific question to aid in understanding. To convert DD MM.MMM format to DD.DDD format 1. Divide the minutes by 60 2. Add the results to the degrees This is because there are 60 minutes in a degree. (FYI there are 60 seconds in a minute). The math is pretty straight forward, and every now and then I have to convert between the formats when the internet isn't handy.

If you create routes in S&T then GSAK can directly load the GPX files created by ST2GPX into the filters. Use the "Load from file" button in the set filter window. No modification required for the arc filter. Since S&T won't let you use the same point as a start and end for a route as required for the polygon filter I just copy and paste the first set of coordinates to the bottom of the list in the GSAK set filter window. Yep, that's what I do. But I'm a bit OC like Monk and like to see it as a CSV, so I can't resist using a regexp macro to whip it into symetry.

I do this, and there are a couple of approaches depending on whether the trip is ad hoc or planned. Both trip types start with Pocket Queries (PQ's) loaded into GSAK. I live in Chattanooga, but also travel to Nashville, Knoxville, and Atlanta. So I've created PQ's to cover those areas, as well as any area that I'll be vacationing in soon. I then export this single database, via filters, to smaller files (GPX files for my iPAQ PDA and WPT files for my Magellan Meridian Gold). Then, when I'm traveling in an area, I load the appropriate file and I can see them on a map and decide if I want to hunt that cache. For the ad hoc trips I fire up the Magellan or the iPAQ to see what's nearby. If something needs investigation I open the GPX in the free GPXsonar to see the details and make a decision. Both devices have maps so I can use either one to make navigational choices, although the iPAQ is better at this (with voice prompting). My laptop will do this as well, but I don't like leaving it unattended in a vehicle while I'm hunting a cache (I've had my vehicle broken into twice but luckily never when the laptop was in the vehicle). For the longer trips, I can usually plan appropriately. For planned trips I use the Polygon and Arc filters to create files that contain only caches along a route. The filters are created by drawing them in Microsoft Streets and Trips 2005. I then use the utility ST2GPX and then a text editor to load them into GSAK as the correct filter type.

For PocketPC get the free program GPXsonar which is almost like a GSAK-lite. It also has other neat features like export to PocketStreets and Magellan SD format, which I find quite handy. Field notes can be imported into GSAK.

I do NOT have a question I do NOT have a complaint I do NOT have a enhancement request (well, at least not at the moment ) I just wanted to say THANKS for such an awesome and useful program. It is worth every penny.

Any idea of when the upgrade will be completed? The FAQ says ProBoard will take 12 to 18 hours, and it has been over 24 hours already.

I think you're doing fine. I am very happy with my Meridian Gold. I load waypoints onto the SD card with a card reader, so I'm getting USB speeds. I hardly ever use the serial cable, so the USB/Serial debate is moot to me. For some people color is important, but I actually prefer the B&W screen, which is easier to read. I have a translfective color screen on my iPAQ, and it can be hard to read under bright light. As to accuracy, this past weekend I was caching with a Garmin owner. There were times when he could not get a lock, and when his accuracy was less than my Gold. Once we were between two ridges, and I expected his to do better since I heard canyon-like environments are a helix antenna's weakness. But I held a signal while he could not lock onto any birds. I can't compare the maps, but I find the Magellan maps good. I tried caching without the mapping software, but it's very handy to have all the roads and topo in one place. I really like the 3D feature on the PC. The PC interface is a bit klunky at times, but manageable.

See this PC World article

Going through withdrawals during the forum upgrade.

Because RAM can be a precious resource on a PPC, I use GSAK to slice-and-dice my cache database into smaller digestable chunks (for GPXsonar). It also makes file loading, searches, filters, exports, etc. run faster. My GSAK database has 6,700+ caches and that would choke my PPC to death. So, if I'm looking for a standard ammo can, I only have to load NBreg.GPX (Near-by Regular sized caches). The GPX files are created by a single button push (it calls a macro which sets filters and does the exports). The exports are for both GPX and Magellan waypoint files. Since I have MightySync, all the GPX files get copied to my PocketPC's SD memory card automatically. The Magellan waypoints files are manually copied to its SD memory card -- although I have used GPXsonar to do this "in the field" as well (pretty cool!). My "Nearbys" macro creates 17 different files: by radial distance (all types), type (size and style), geographic areas (using GSAK polygons), and source (i.e., TerraCaching.com caches, Benchmarks, etc.).

Under the Macro menu there is a option called "Add Button to Toolbar..." I've added a few and it works well. Or am I not understanding?

GSAK Macros can be called via a command line, so you could use "Scheduled Tasks" to call a macro that automatically does the updates. The macro could also do exports to the PDA (e.g., MightySync for PPC) and the GPS (e.g., a Magellan connected to external power to prevent battery usage).

Another vote for the Meridian Gold. I went caching with a Garmin Legend owner this past weekend, and I was getting better signal under tree cover and in narrow valleys

Yep, it's quite common. Mine's not too bad (I have to hold it close to my ear to confirm, but then I'm getting old ). I'm probably in the minority, but I consider it a feature, since I can tell when I've accidently turned it on (when I'm in bright sunlight and can't tell otherwise) -- since it drains the battery faster.

I was trying to do some cleanup in GSAK and noticed that there are some disabled caches that have been that way for as long as a year or more! A few have even been disabled since 2002 and 2003. I know up north they can be disabled throughout winter due to impassible snow, but these are all southern caches. How long should a cache be disabled before players start posting SBA's to prod their owners? Here are some examples (oldest first to older than 3 months): GC21E, GC4442, GC9EF6, GC7530, GCE65A, GCBA9A, GC27EE, GCC351, GCH18B, GCB108, GCC350, GCC34C, GCC34B, GCC34D, GCJ7GC, GCHD7R, GCG1R0, GC8F2A, GCKDBJ, GCC34E, GCKGE1, GCA84F, GCA82A, GCKNCP, GCGRNR, GC49A2, GCJWW5, GCH0R0, GCK7RG, GCG5HP, GC8627, GCG5EW, GCH2R2, GC7676, GC7819, GC9045, GCJ8E9, GCGF4X, GCHKZ0, GCGE39, GC6D4D, GCGFDE, GCD049, GCHTZX, GCKG40, GCJ04X, GCB6, GC4281, GC4BCE, GCB162

How about something cheap versus free? There are several mapping packages (e.g., Microsoft Streets & Trips) that can be found at Wal-Mart for about $30.

I use a HAiCOM CF GPS with a $10 PCMCIA adapter I got at BestBuy. It works like a charm, and the HAiCOM supports an external antenna as well. The HAiCOM can also be used in a BlueTooth Slipper so it gives you even more flexibility. I bought mine HERE

There's more than one way to skin that cat, but I'll share how I've done it. Clyde is also considering some updates to GSAK that will make this easier to track (e.g., GPX source). I have 2 databases (well, actually more than that, but for this discussion only 2 apply). I also have a TC database that only contains TerraCaches. But since I want my maps to show both GC and TC caches, I also load TerraCaches into my "Default" database. Here is how I identify which are TerraCaches. 1. Sort by code by clicking the CODE column of your grid view. This will put all the TerraCaches together. 2. Make sure USER DATA is displayed in your grid view (\View \Add/Delete Columns). 3. For each TerraCache, put in the letters "TC" (at the beginning if you already have data in these fields). I also have some "offset" coordinates so I'll put "TC ACTUAL" in those records. 4. Create a filter called "TerraCaches" and use this criteria for USER DATA: RegEx ^TC (I.e., use a regular expression that specifies records where TC is at the beginning of the USER DATA field) 5. I also change the AVAILABLE STATUS to exclude all but "Available" but that's not necessary for identifying TerraCaches specifically. 6. After you save the filter, test it to make sure it shows all the records you expected. Now with the filter built, the PushPin macro should contain these lines (drive, path, file names, and settings can be altered for your setup): CANCELFILTER FILTER name="TerraCaches" IF $_FILTERCOUNT > 0 EXPORT TYPE=SNT SETTINGS=PushPins FILE=C:\GPS\PushPins\TerraCaches.csv RUNPGM pgm="C:\GPS\PushPins\PushPinListBuild.bat" parms=TerraCaches,YYYNYYYY,C:\GPS\PushPins\PushPinList.txt WAIT=YES ENDIF