Announcement

Collapse
No announcement yet.

Basecamp will not transfer maps to GPS unit correctly

Collapse
X
  • Time
  • Show
Clear All
new posts

  • Basecamp will not transfer maps to GPS unit correctly

    I recently went on a motorcycle trip, beforehand transferring all the tracks, waypoints, and what I thought all the 2008 US Topo maps I needed. Once I started my trip, I tried activating the topo maps, but there was no detail, roads, topo lines, etc. Luckily I had City Navigator installed on the SD card which had a some of the roads I was riding on in the National Forest. When I got back I tried to transfer the maps again and still had the same issues. There is a lot of detail on the maps within Basecamp, but when transferring them to my Oregon 600, nothing shows up. I also downloaded custom topo maps from GPS file depot and had the same outcome. When I transfer the maps with Garmin Mapsource, everything transfers just fine, but again every time I try using Mapinstall in Basecamp the maps do NOT transfer over correctly. I'm using Basecamp verson 6.16.3 and the newest firmware on my Oregon. Any idea what is going on?

  • #2
    Which BaseCamp version? Latest is 4.7 so I'm unsure how you've got 6.16.3? If you're getting confused between BaseCamp and MapSource versions then I suspect you have 4.7, this has a bug which seems to inhibit correct map transfer.
    Last edited by SUSSAMB; 07-07-2018, 01:10 PM.
    Currently own Drive 50LMT-D, Nuvi 2508LMT-D, Nuvi 1490LMT, Nuvi 1310, Montana 650T, Etrex 20, and use Basecamp, OSM mapping
    Previously owned Etrex Legend H, Mio Navman and used Mapsource
    (please note that I am not employed by Garmin, but am a long term user of Garmin software and hardware)

    Comment


    • #3
      Ahhh, apologies. 6.16.3 is the Mapsource version, not Basecamp. Yes, I'm using Basecamp version 4.7. So Basecamp 4.7 has a bug and will not transfer maps correctly?
      Last edited by Yooperjb; 07-07-2018, 02:03 PM.

      Comment


      • #4
        Yes. If you can then revert to 4.6. You'll find instructions in this thread https://forums.garmin.com/forum/mac-...p-update/page2
        Currently own Drive 50LMT-D, Nuvi 2508LMT-D, Nuvi 1490LMT, Nuvi 1310, Montana 650T, Etrex 20, and use Basecamp, OSM mapping
        Previously owned Etrex Legend H, Mio Navman and used Mapsource
        (please note that I am not employed by Garmin, but am a long term user of Garmin software and hardware)

        Comment


        • #5
          Very well, I will revert, or use Mapsource for the time being until Basecamp bug gets resolved. Thanks for taking time to help me out.

          Comment


          • #6
            Just wanted to post that I had the same problem. BaseCamp 4.7 would not transfer OpenMapChest maps. It would say it's completed but only 332KB gets transferred. Tested it on two different computers. Downgrading to 4.62 made it work immediately.

            Comment


            • #7


              Yep. Basecamp 4.7 broke the third party map access to devices. It seems unlikely that Garmin will make a change to fix this as third party maps are not authorised, so the roll back to the old version is the workaround. It is not as if 4.7 brought anything really new to the customer.
              Last edited by SUSSAMB; 11-23-2018, 12:36 PM. Reason: Please don't quote the post directly above yours. It's unnecessary and simply clutters up the thread. Thanks

              Comment


              • #8

                Just did the rollback. So the thinking here is that Garmin will not fix this because they do not want people to be able to load 3rd party maps to Garmin devices? But that is not the direct reason for the change, correct? I think this is just a coincidence and a result of other changes since I think some types of 3rd party maps still transfer OK.

                Comment


                • #9
                  I don’t know Garmins thinking. The loss may have been made because of nessesary changes in the software or it may have intentionally broken the function. I see no benefit to speculating about it either. The fact is they are under no obligation to maintain the functionality for of non-supported uses and left us with viable workaround.

                  Comment


                  • #10
                    FWIW - I talked to Garmin support today about another BaseCamp issue I was having and also asked them about this map issue. He told me there was a ticket about the problem and that they were working on fixing it. He supposedly even added my email to the ticket so I would be notified when the issue was fixed. He made it seem like the break was inadvertent and that Garmin understood it needed to be fixed. Who knows for sure though. Understandably, I guess, he did not have any idea of a timeframe for the fix.

                    Comment

                    Working...
                    X