Search the Community

Any body know if windows 11 can play nice with GSAK?

Members 1 Posted Monday at 05:43 PM In the past I have converted Garmin map files to Magellan files for my Magellan Explorist 210. I want to do that again now, but I don't remember how I used to do that and with which tool. Can anyone help me with that?

I also haven't had any issues with GSAK on Windows 11, other than the minor nuisance of getting it to open cache pages in the correct browser sometimes.

I know this is an old thread that's been brought back to life but I'll go ahead and chime in right quick since I'm here. I have no trouble at all using GSAK on my desktop running Windows 11. Just used it yesterday to filter for caches I thought would be more to my liking. Will admit, I haven't ran a macro in a long time or gotten into the more advanced stuff GSAK can do. Pretty basic here, load query, sort caches, and download to the old Garmin..

Yes, me too. I do all my planning and logging on the website, loading GPX files into my Garmin before I leave home for navigation. About the only time I use the app is for FTF field logs, which I then flesh out on the website when I get home.

In the past I have converted Garmin map files to Magellan files for my Magellan Explorist 210. I want to do that again now, but I don't remember how I used to do that and with which tool. Can anyone help me with that?

New to Windows 11 - GSAK will not display maps on specific geocaches or if using Get Geocaches Map.

The following data from developer tools clearly shows both problems. UTC time I logged it and dateLastLoggedUtc being the time of the first log on the lab not the last time. { "adventureId": "8d7f04c5-3224-4a70-8103-b81b3d964141", "adventureTitle": "The Beatles Liverpool Tour 2", "adventureKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/a9876136-b86e-476f-aa2d-ee690bdb9ec7", "playerLogs": [ { "id": 86068776, "stageTitle": "20 Forthlin Road", "dateLogged": "2024-05-18T23:01:59.417-07:00", "stageId": "822afc48-922c-4cf5-b0d9-da34907fbbd3", "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/771f5bbd-4dc2-4418-a267-e761ec401ec9", "isArchived": false }, { "id": 86068229, "stageTitle": "10 Admiral Grove", "dateLogged": "2024-05-18T22:48:06.247-07:00", "stageId": "9335939a-20c4-4108-98c9-df9da38d128d", "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/6e46fe92-84e2-429a-a407-5b5919bece02", "isArchived": false }, { "id": 85986086, "stageTitle": "12 Arnold Grove", "dateLogged": "2024-05-18T13:00:39.18-07:00", "stageId": "e5f35245-3f86-40d9-99b1-f6eb9504039d", "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/2e954463-0c3d-459a-855d-30b9919be612", "isArchived": false }, { "id": 77704241, "stageTitle": "The Cavern Club", "dateLogged": "2024-02-02T11:45:19.79-08:00", "stageId": "71f2fc78-0c90-47e8-9208-a97453d4d340", "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/0b92f983-f1de-4161-bf29-b198b79d5cb7", "isArchived": false }, { "id": 56201661, "stageTitle": "Ye Cracke", "dateLogged": "2023-04-22T12:43:51.91-07:00", "stageId": "51002b01-74fe-4f97-998f-a2e4c1bfd029", "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/484d68f2-dc4d-4df4-ae51-bc3c34addd68", "isArchived": false } ], "dateLastLoggedUtc": "2023-04-22T11:43:51.91-07:00" }

I have the latest version of Garmin Express downloaded, however when I try to send information to my Garmin device it keeps telling me I need to download the latest version. Is this a glitch or am I missing something. I am heading to the US on vacation soon and am trying to download geocaches to my GPS so that I don't have to use data on my phone.

Are you using an export macro? Are you certain GSAK is sending the child waypoints? I use the Garmin export macro without issue on my Montana 700. Edit to add: When loaded properly, child waypoints are available directly from each Geocache page on the Montana 7x0. See GPSrChive > Montana 7x0 > Main Menu > Geocaching > Child Waypoints for additional details. And one more thing: If you have child waypoints loaded as normal waypoints, and 'Hide Waypoints' is enabled in the Geocache Map Tab, they will not appear. Additional details available at web link above.

This is the worse possible time for this problem to be happening as I just started my trip. My GPS handheld was working fine until I removed the AA batteries for charging. As soon as I reinserted the batteries, this problem started. My Garmin GPSMAP 66S suddenly become non-functional with the message "Updating GPS firmware" and going 0% then 1% (see attached screenshot) and the message disappearing and no GPS function. Unfortunately, I don't have a laptop/computer with me as I'm out of the country. I only have an Android and iPhone with me and the Garmin app installed. I don't know how else to troubleshoot and fix the GPS unit. I tried a hard reset and the problem didn't go away. My handheld is using the latest firmware. I think it's 2.70? I recalled updating it before I left for my trip. Help?

Sorry to resurrect this thread after so long, but, I'm experiencing a possibly related issue to that of OP. Background: I'm using the official Geocaching.com app on iOS (iPhone 13 Pro). I recently received three messages from someone from whom I'd had prior interchanges with no app issue. The Unread message indicators (red dot showing "1" on the iOS GC app icon, blue dot on the sender's thread in Messages, and blue dot on the Messages icon at bottom of screen when in-app) are all showing. There are no unsent draft logs listed. Failed Solution Attempts: I have, variously, and with no change to in-app Messages Unread status: read all three of the sender's messages in-app on iPhone; read all three of the sender's messages in-browser when logged in on a Windows PC (Read status is always correct in-browser on PC); cold rebooted the iPhone; deleted the Geocaching.com app, cold rebooted the iPhone, then reinstalled and configured the app; viewed Souveniers in-app and in-browser (as noted in prior forum posts and just in case). FWIW, the in-browser Read status is still correct and does not match the in-app Read status showing "1" Unread. The three independent messages from the same sender on the same day comprised: just text; text that included a URL hyperlink to a geocaching.com page (which displays as only text in-app); and, a photo. Any other suggestions for how to remedy this iOS in-app Unread Message status appreciated.

I have been looking around the various threads at the different terms that seem to be used exclusively by geocachers. I decided to post a list of these terms which would obviously benefit from the input of others. I am certain there are hundreds of other excellent terms that can be added to the list and probably many correction that can be made as well. Is there a word for someone who is extremely skilled at geocaching? The List: Blair Witching: When GPSr readings appear to 'flip' over a desired coordinate (usually near the cache site), preventing the seeker from locating a cache. Booty Nuggets: The treasure found in the cache for trading (see also McToys, Geoswag). Chromes: "Crow Miles" describing linear distance without regarding elevation or terrain. Drive & Dump: A cache placed with little thought, usually very close to a road or parking lot. Force (The Force): The ability to instinctively know where a cache is hidden when you get within a certain proximity. The term alludes to supernatural force used by specially gifted characters in Star Wars. FTF: First to Find Garminites: Those that favor the Garmin line of GPSr units Geobasher: A person (usually a geomuggle) who derides geocachers or the act of geocaching. Geocasher: A geocacher who leaves valuable items in a cache. Geodashing: Another GPS Game involving visiting randomly generated waypoints Geomuggle: A person that is unaware of the existence of geocaching. The term alludes to Harry Potter where "muggles" refers to non-wizard humans. (see also In-Laws) Geosnatcher: A person who steals the contents of a geocache or the entire geocache itself (see also Plundered) GPSr Food: Batteries Hedwigged: E-mailed. The term alludes to Harry Potter's messenger owl, Hedwig. He-Who-Must-Not-Be-Named: The gentleman who placed the first Geocache in May 2000. The term alludes to Harry Potter's evil nemesis, a powerful wizard who must not be named. In-Laws: Unwanted geomuggles who remain at a cache location for extended periods of time, preventing discrete access to that cache. Letterboxing: Another stash-and-find game that started in the U.K. over 100 years ago. It is similar to Geocaching, but without the use of GPS and coordinates. Log and Dump: A cache carelessly replaced in its original location, often left unhidden and vulnerable to plundering. Loose Bearings: The point at which the direction on your GPSr no longer points in the correct direction, mostly because you've slowed down to a point that it doesn't know in which direction you're moving. Maggies: Those that favor the Magellan line of GPS units Markwell: To create a link to a previous, or related forum discussion of a topic. McToys: Cheap, dirty, or broken toys of little monetary value left in caches for trade. Microcache: Much smaller than a regular cache. Minicache: Between the size of a microcache and a regular cache. Minute War: Another GPS Game involving playing a "capture the flag" related game on a global scale Neocacher: An inexperienced Geocacher (see also newbie) Newbie: An inexperienced Geocacher (see also Neocacher) Plasma Bandits: Mosquitos Plundered: A cache which has had its contents stolen or the theft of the cache itself. (see also Geosnatcher) Signature Item: A specific item used and/or created by a geocacher to show that they've visited a cache. Smurfs 292: Meeting another geocacher in the woods. The term alludes to Smurfs episode #292 where the Smurfs encounter "Wild Smurf", a 150 year old loincloth-wearing Smurf who was lost as an infant and raised by squirrels. Sock Puppet: A person posting under a different handle in order to appear to have more than one person supporting the stated position. Swag: The treasure found in the cache for trading (see also McToys, Booty Nuggets) TFTC: Thanks for the Cache The "Other" Site: Navicache.com. In competition with Geocaching.com The Degree Confluence Project: Another GPS based hobby involving visiting points where the latitude and longitude are integers (e.g. N 42° 00.000 W 088° 00.000) TNLN: Took Nothing, Left Nothing TNLNSL: Took Nothing, Left Nothing, Signed Logbook TPTB: The Powers That Be (Jeremy Irish and Elias - those that control Geocaching.com) Troll: A person who posts inflammatory remarks specifically to elicit heated replies. YAPIDKA: Yet another park I didn't know about A C atom noticed that an H ion was looking depressed, "Why do you look so sad?" he asked. "I lost an electron" replied the H ion. The C atom asked "Are you sure?" To which the H ion replied, "I'm positive."

Greetings-- Just upgraded to a GPSmap 67i from a 64st, added a 32gb microSD card, and the first thing I noticed it that when plugged into the Mac, it no longer shows up as a drive (or 2) on my desktop, thus my iCaching software doesn't see it directly for purposes of export. Garmin support told me I needed the Android File Transfer utility see the units directory and transfer files to the GPX directory. That worked, booted up and voila!. Tried to find them again the next day and nothing. Support had me verify the PQs were enabled and to use both AFT to load files to the directory, import them into BaseCamp then Xfer to the 67i. After reinstating BC (not my favorite piece of software), I was able to get the PQ loaded onto the unit. Not exactly a clean way to do so after the iCaching/GPSmap 64st combo I've used for years. Does anyone know a more efficient way to do so? I can run Windows and try GSAK, but would rather not.

Plus, a lot more than no Garmin can do.

So basically Geooh GO adds the functionality of a Garmin with trail maps loaded.

It's just inevitable, @Mineral2. If you'll think about it, you've seen this progression for decades. FAT filesystems were of the CPM and later DOS era then things were coded in assembly and for a single CPU to be reading and writing them. Imagine a filesystem on a "disk" (doesn't matter if it's a memory card or a shared buffer or punched paper or mercury tubes or whatever...) as a clay tablet (is that all I've got? We're going to overlook that a clay-tablet is write-mostly? Really? I've gotta work on my metaphors... :-) ) that always has to be internally consistent with itself in case it's suddenly disconnected from the writer. It has separate areas like an index and a table of contents and it has a list of space of what space has already been written on and what's free. With some clever chisel-work, you can make sure that this always works by having the chisel that carves out letters also updating the TOC and the free list all in the same blow of the hammer. It's atomic (unbreakable) on each hammer strike. Sure, the chisel is funny looking, but this is how filesystems work. If the writer is stricken by a diety while they're writing, the tablet is always self-consistent and there's no chance of it getting out of sync. Now, if you have TWO writers trying to hammer away on that same block, each with their own magic chisels, each may try to write into the same blank space twice, each with different data which will hose up the table of contents/index if block 1,347 could possibly contain two different entries. The wheels pretty much fall off of everything if you have TWO processors trying to write to the same filesystem. You've seen evidence of this for decades. Network operating systems work very hard so that hundreds of computers talk to IT and IT talks to the filesystems, introducing locking and such, so prevent this problem. (Remember 3Com and Novel?) Cameras (remember those?) have long had this problem. If the camera is displaying the list of photos while you're connecting to a computer and adding, deleting, and reordering photos, Bad Things happen. We introduced PTP, the Picture Tunneling Protocol to act like an NOS. The CPU on your MP3 Players (remember those?) can't index your songs and display your albums and play lists while you're connecting to a computer and reordering, adding, and removing things. So we extended PTP to become the Media Tunneling Protocol. The final entry in my walk down history lane will indeed be cell phones, notably the very Android that's mentioned when it added memory cards, introducing Android File Transfer (which has applications outside of Android, but has the advantage of being open source and widely adopted by now as well as open implementations for all the OSes that matter) to be the intermediary where everything (the big computer with a keyboard and the tiny computer with a battery) spoke a protocol to AFT and AFT spoke to the tablet, err, storage media. In all these examples, these things handled notifying the other readers/writers when a change happened, when another device connected, and so on. If you think about it, we've seen the same issues in GPSes for years.The Garmin 60CSx wouldn't let you store anything but maps on the SD card and it required a reboot to read them. The Garmin and the host couldn't both access the card at the same time. (Contrast that to the protocol-driven devices where you could watch them draw waypoints on the screen as they were added by software like mine as they transferred.) Nuvi 350, back in 2005, and before it, the i3, would basically go into a catatonic state with the local CPU doing nothing as long as the USB connection was detected. (This was annoying as hell if your charging cable happened to introduce Just Enough resistance on the pin it was supposed to leave unconnected so that your car charger would put your GPS into this flatline state.) When the USB cable disconnected, the device essentially rebooted, invalidating what it knew about the state of the clay tablet, err, filesystem, and would read them fresh. Eventually, most Nuvi mutants and later, the Drive models started using MTP or AFT to do this same thing. The handhelds at least through the Oregon 600 (which may well be my final geocaching GPS) were still essentially shutting down while connecting to USB for this same reason. USB isn't - and doesn't pretend to be - a network file system. USB mass storage actually exposes raw blocks on the device in SCSI command blocks (yes, really - and for an extra laugh, some versions of USB MSTO even exposed floppy drives as SCSI devices). So software liie AFT acts like a tiny little TFTP server that reads and writes files (not blocks, though it may allow partial writes within files, such as for appending) where everyone talks to it and it alone is responsible for actually managing the storage device. (Well, it probably delegates that to lower levels of the OS, such as the kernel's own filesystem and journaling and below that, block level management) Unlike that "DADT" model where everything talks to a server (like AFT) though, in the era of removable media, we often want to be able to take the memory card to something ELSE and read and write it there, like mounting that memory card of pictures in your TV to share with others in the room. For THAT, we can't pretend that the code below AFT has just handled everything for us and we still need everything to be able to read and write the block level jibberish that the appliacations write to the filesystem. While we've created scores of successful filesystems, none are as ubiquitous as DOS's own FAT12, FAT16, and FAT32. The relevant patents (complete with Ballmer-era shakedowns and litigations) have only very recently expired on those. So the filesystem bits (the etchings on those clay tablets) are useful to be able to read and write across devices. That's why we haven't all moved our external disks and our TiVos and whatever to EXT4, ZFS, and other, better designs. So really, Garmin's engineers have two possible stances while building a device - they either detect the edge of an insertion/removal and USB attachment/detachment and they put the host device into a catatonic state where it can no longer access the card data (else things like the map it was displaying might be removed in the middle of a frame draw) or they add something like AFT to negotiate the access of BOTH the internal and external (host computer) access to the common media. Software like GSAK has seen this train coming for years. So far, on dozens of models they've been able to turn off MTP mode and choose the "catatonic" model I've described. GSAK users have been doing this for a very long time. Again, it's a lot of words, but hopefully this explains why these things are this way. (And, yes, I did formerly engineer this sort of stuff for a living..)

Beste geocaches, Ik heb nogal slechte ervaringen met Garmin . 2 apparaten versleten in 5 jaar tijd. Garmin weigert mijn Oregon 700 van 3 jaar oud te repareren. Op internet kan ik niet echt een alternatief vinden op Garmin . Heeft iemand anders ook deze ervaringen met Garmin en weet iemand misschien een goed alternatief.

Yes, if not sent immediately, a concern is forgetting which photos go with which log. It can get a little crazy, especially if the photos are from more than one camera. Good thing I can only manage to hunt a handful of caches at a time, it's easier to keep things straight. But I also tend to not have a reliable phone connection out in the field. So I plan to do all the compiling/resizing/uploading later, which works regardless. And I save the logs as drafts and in shorthand (or in even shorter hand on my Garmin), so all of the work is delayed til I'm at a computer at home or hotel. But ya gotta do what works best for you.

That might well be true, but any averaging the phone's OS is doing would have to be reasonably short term, at most over tens of seconds, otherwise there would be an unacceptable time lag between the displayed position and where you actually are now. For example, if it was averaging over 10 minutes, that average would be centred around where it was 5 minutes ago. The suggested way of taking coordinates in the official app is to add a waypoint to an existing cache. The displayed "Current position" field when doing that doesn't update, though, it's just a static value that the app obtained when the + on the waypoints screen was tapped. I can walk around over a considerable distance while displaying that screen and the "Current location" coordinates don't change. To update it, I have to tap the back arrow and then the + to add another waypoint. To see your position in real time, you can go to the Navigate screen in compass view, which appears to update every second or so, but you can't capture the location from that screen, other than by taking a screenshot or writing it down in a notepad, I suppose. Either way, the upshot is that this recommended way of taking coordinates in the app encourages just taking a single reading, and it's not surprising that coordinates taken in this way are often a considerable distance out. By contrast, on my Garmin I can watch the drunken bee dance over a period of ten or twenty minutes and, once satisfied, can position my marker in the middle of it. Something akin to that in the app, where coordinates can be averaged over many minutes either visually or algorithmically (ideally both), would be a boon, I think.

I'm getting the same error. It was once much less complicated! The sequence I'm seeing is: In any List, attempt to Send To Garmin, and a window pops up that says: "Allow Garmin Express Your browser will ask you to open the application. Make sure to choose the option to launch Garmin Express." This is followed by no browser asking anything. Click OK, and the box closes, and is replaced by "An Error Occurred". At this point, Garmin Express has opened perfectly fine behind all other windows. And it has a box that says "Content Ready to Download". Click continue, and the requested GPX List file is placed onto the Garmin. Do the same with another List, go through that entire process again. It is working, except that there's more manual interactivity required. I don't like the additional weirdness. In your case, maybe you need to update and open Garmin Express and then try it. Or post the exact steps and errors, and your OS and Garmin Express version. Don't want to tell you how to do things, but the above is why I use Pocket Queries instead, including Lists as Pocket Queries. And if I'm "downloading" a List or PQ or a single cache, I'm "Downloading" it as a GPX, I NEVER use "Send To Garmin", because of this exact thing. It's chock full of unpleasant surprises. I'm not excited about fiddling with the bug of the day. I need to load a GPX and go. Just before I saw your post, I saved a couple of GPX files from the web site to my Oregon 750 without issue. I don't see the Garmin Express problems, because I deliberately bypass them.

If you're using Google (or pretty much another other commercially refined map) you need to be sure you're compliant with the relevant https://about.google/brand-resource-center/products-and-services/geo-guidelines/#:~:text=All%20uses%20of%20Google%20Maps,while%20the%20content%20is%20shown.license . There are many governmental agencies in many countries that can provide imagery or DEM graphs to remix in applications like this. Check with your local cartographic authorities like regional governments or universities or mapping companies. Garmin doesn't really have any competition left and has kind of left the handheld hiking business afloat for several years. Montana is bulky and expensive, but the last of their touch screens. 64, 65, 66 are so are nearly indisinguishable. When we compare the three the can be compared, we see the "65" doesn't have sesnsors - we knew that because it doesn't have an "S" in the name, which is about the only thing they've held constant. It used to be that "x" meant "expandable via SD card", but their little table doesn't show that. 65S, having a bigger number, supports more GPS constellations - but how many is "enough"? We've been successfully finding tupperware in the woods since there was only one. Sure, more SV's is "better", but it's hard to say that everything before some specific model wasn't enough. Few of us are in a position to predict war outcomes. In fact, as a moderator, I'd rather we not. Loading data without a connection ... is going to require a connection of some kind. If you want to tether your laptop to your phone to preprocess the imagery and download it to your GPS, that's up to you. None of these exactly has a cellular modem in them. Units have been big enough for many years to hold vector map data entire counties and even continents, but infinite raster storage is still out of range. I'll say only that Google Maps, for example, has an option to download map data but not to download image data. For any non-trivial area, it's HUGE (I have some relevant professional background in this area and will stick with "HUGE" as the relevant unit of measure.) Many of us have successfully navigated a couple or several countries/continents using only what our device holds, but it does require some amount of planning as we tend to not spontaneously cross oceans for most of us. I guess if you're a spy that doesn't know his or her next deployment, a pocketful of pre-generated OSM maps for your territories should be in the bag that M hands you when you receive your assignment. That might be a nudge for a unit with an "X" in the name, if it still means "expandable" - you could have multiple cards, each loaded with unique large areas. Personally, I was in the geo-imagery business for many years and still really only found it necessary while hunting geocaches a few times, but having maps not close to me WAS valuable many times. https://www.garmin.com/en-US/compare/?compareProduct=669284&compareProduct=715072&compareProduct=715085 So I'd cross off the 65 for not having "S". (I DO find the compass useful.) From the best I can tell, 64XS has expandablle memory and 65S has more radio bands. Then again, https://www.garmin.com/en-US/p/715085 says that 65S has a memory slot. So much for consistency in their naming. {shrug} I've already hinted which of those two I'd find more useful. Seems that 65 also has an extra 8GB of base memory, but unless they've upgraded their on-board USB implementation to at least USB 2 speeds (2000 - they hadn't done so as of their models from 2016 and I've quit following them because there's so little to follow) transfering 8GB over a 12Mbps connection would be torture - that was a LEADING reason to keep maps on cards in that time, in fact. Surely they've updated their USB choice by now. Surely... Then again, it looks like 65 was introduced in 2020 and I don't see much in this space since then. Maybe someone with a 64 or 65 can chime in on whether updating internal maps is torture. They never did "fix" that even in the Oregon lines unless it was the very final models, IIRC. On the battery thing, I think they pitch that their units CAN take their overpriced two-batteries-in-a-dumb-little-clip module to allow them to be recharged but CAN be run with commodity (or even Lithium) cells, if you'll forgo the in-unit charging. (Allowing charging anything they don't approve is a liability problem for them when they explode.) You can download the individual manuals to be certain, but all the doc I saw showed that the models a geocacher would consider took AAs. Their more exotic devices like the 276, that need more power than you can get from a reasonable quantity of AA's, may require non-standard cells. (I'm not testifying that this device DOES, but other low-end marine products from them in this general space did...) Finally, yes, first submissions are held by a moderator (and it's not only not me, it's not even often me just because other mods are faster on the general trigger) for review. You wouldn't believe the spam that comes through otherwise. It also catches my eye that your post doesn't mention geocaching and your profile shows no hides and no finds. This really isn't a general purpose GPS support group. I probably should have noticed that BEFORE I typed all this stuff, eh?

Where do I download maps for Garmin? Anyone have the link?

Hallo und guten Tag, meine Familie hat mir ein Garmin eTrex 20 geschenkt. Also bei geocaching.com ein Konto erstellt und fleißig gesucht - gefunden. So weit, so gut Nun meine Frage: Um ein Fund vom Gerät bei .geocaching.com zu loggen, ist der Ablauf folgender: Gerät anschalten →nachsehen welcher Fund geloggt werden soll →bei geocaching suchen-→loggen...Schweiß abwischen und das ganze Prozedere von neuen beginnen. Gibt es da eine Möglichkeit, das es eben nicht so verflixt umständlich geht? Wo alle Funde komplett geloggt werden können? Danke und Grüße von einer Anfängerin

Okay my question today is - Would you class a Smart Phone ( with access to the internet ) a T.O.T.T and use Special Tool Required, or Do you think there should be a (NEW) attribute to indicate you'll need a Mobile Phone with Internet access Me I think there is a need for a new attribute. as the game has moved on from using a PC to upload your caches via GPX files to a Garmin or other hand held GPS to now having the world at your finger tips in the way of a smart phone .