+Mitragorz Posted July 2, 2015 Share Posted July 2, 2015 Pretty simple question, lol. What's the difference between the two formats? I use gsak's garmin macro to upload the caches. I always used GPX when uploading to the Colorado. I just started using a Montana, and was wondering if I should start using GGZ, and why? Thanks! Quote Link to comment
insig Posted July 2, 2015 Share Posted July 2, 2015 For Oregon 600/650 and GPSMAP 64, you can use GGZ for a faster initial boot time. Older devices like the Montana 600/650 do not support that file format. Quote Link to comment
+Mitragorz Posted July 2, 2015 Author Share Posted July 2, 2015 (edited) For Oregon 600/650 and GPSMAP 64, you can use GGZ for a faster initial boot time. Older devices like the Montana 600/650 do not support that file format. Ok, so I'll continue to use GPX for my Montana and start using GGZ for my fiance's Oregon. Is there any difference other than faster boot time? In other words, is there any reason to use one over the other (in the Oregon)? Edited July 2, 2015 by Mitragorz Quote Link to comment
insig Posted July 2, 2015 Share Posted July 2, 2015 GGZ is basically a ZIP compressed archive that has some metadata to help load it faster when it first indexes the caches on boot.If you throw 10,000 caches in a GPX file, it will take a lot longer on the first boot than if you throw 10,000 caches in a GGZ file. Garmin BaseCamp (last time I checked) won't read GGZ files, so that might be a reason to use GPX on the fiance's Oregon. Quote Link to comment
+Timpat Posted July 2, 2015 Share Posted July 2, 2015 This brings a question: where do you get or generate a GGZ file of caches? Quote Link to comment
+Mitragorz Posted July 2, 2015 Author Share Posted July 2, 2015 The GarminExport macro in GSAK lets you choose which format to send you your GPSr. Quote Link to comment
+Red90 Posted July 2, 2015 Share Posted July 2, 2015 This brings a question: where do you get or generate a GGZ file of caches? GSAK will do it. They needed to reverse engineer the format as Garmin did not publish specs, IIRC. Quote Link to comment
+Timpat Posted July 2, 2015 Share Posted July 2, 2015 Thanks Mitragorz and Red90! I just picked up a 64s so this will come in handy using that macro. Quote Link to comment
+Cethyn Posted July 3, 2015 Share Posted July 3, 2015 I had an issue with child waypoints if I used GGZ with my GPSMap 64s. If I used GPX I could find child waypoints on the map and when I used GGZ there were no child waypoints visible. You might want to test that before you make a long trip Quote Link to comment
+on4bam Posted July 3, 2015 Share Posted July 3, 2015 I had an issue with child waypoints if I used GGZ with my GPSMap 64s. If I used GPX I could find child waypoints on the map and when I used GGZ there were no child waypoints visible. You might want to test that before you make a long trip If exporting with Garminexport macro in GSAK you might want to export child WPs as POI's. That way POI's have their own category to select from (Parking, virtual...) and your WP list remains uncluttered. Added bonus is that you can customize the name of the WPs (i.e. WP01_cachename . Quote Link to comment
robertlipe Posted July 4, 2015 Share Posted July 4, 2015 This brings a question: where do you get or generate a GGZ file of caches? GSAK will do it. They needed to reverse engineer the format as Garmin did not publish specs, IIRC. Garmin didn't officially publish them, but they did throw some selective hints to the low number of us that actually cared. I've only very recently started implementing it in GPSBabel (and am definitely finding things that don't work quite like those specs) but Clyde, Garmin, and I did work to get their support going. It was less of a total reverse engineering exercise than in previous times that Garmin decided to go do their own thing. GGZ is basically a zip file that contains an approximation of a .loc file (coords, cache name, container, size) with a few new elements (index into gpx for corresponding wpt open and close tags) that allows Garmin's inefficient XML reader to read a tiny, simple XML for an overview (search by name, splash points on a map) and then read the "big" content (cache description, logs) only after you've expressed non-passive interest in that specific record. https://code.google.com/p/gpsbabel/source/detail?r=4994 Quote Link to comment
+BAMBOOZLE Posted July 5, 2015 Share Posted July 5, 2015 The GarminExport macro in GSAK lets you choose which format to send you your GPSr. How do I pull up that screen in GSAK ? Quote Link to comment
+on4bam Posted July 5, 2015 Share Posted July 5, 2015 The GarminExport macro in GSAK lets you choose which format to send you your GPSr. How do I pull up that screen in GSAK ? As in that post ... GarminExport macro Quote Link to comment
+BAMBOOZLE Posted July 5, 2015 Share Posted July 5, 2015 The GarminExport macro in GSAK lets you choose which format to send you your GPSr. How do I pull up that screen in GSAK ? As in that post ... GarminExport macro Is that in ver 7.7.4.36 ? Quote Link to comment
+Red90 Posted July 5, 2015 Share Posted July 5, 2015 If you choose a device that supports GGZ, GSAK will by default create a GGZ file using the normal "send waypoints" function. In fact there is no option to send as a GPX using the normal send waypoints feature. The macro above is here: http://gsak.net/board/index.php?showtopic=15866 Quote Link to comment
+on4bam Posted July 5, 2015 Share Posted July 5, 2015 Is that in ver 7.7.4.36 ? I think you'd better upgrade to V8 as GSAK is now V8.5.1.42. The macro is V1.3.59. You might find things not working as expected in the "ancient" V7.xxx as there have been a lot of changes (newer version of database, API,...) Quote Link to comment
+Red90 Posted July 5, 2015 Share Posted July 5, 2015 (edited) GGZ was added in 8.3.0 17th June, 2013. Won't work with earlier versions. Version 7 was released years before the GGZ format came into existence. Edited July 5, 2015 by Red90 Quote Link to comment
+BAMBOOZLE Posted July 6, 2015 Share Posted July 6, 2015 Is that in ver 7.7.4.36 ? I think you'd better upgrade to V8 as GSAK is now V8.5.1.42. The macro is V1.3.59. You might find things not working as expected in the "ancient" V7.xxx as there have been a lot of changes (newer version of database, API,...) Yeah, I've been wanting to but the older you get the more you don't like change.....my ver of GSAK runs perfectly. Quote Link to comment
+on4bam Posted July 6, 2015 Share Posted July 6, 2015 Yeah, I've been wanting to but the older you get the more you don't like change.....my ver of GSAK runs perfectly. I'm sure it does but V8 has a lot of improvements to make life easier. API support being just one of them. 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.