Basecamp - BirdsEye Satellite Imagery Download Question

Hope I've put this question in the correct section of the forum! - (I'm sure it will have been asked before, but I haven't been able to find a definitive answer).

I recently bought a Garmin GPSMAP64s which came bundled with a year's subscription to Birdseye Satellite Imagery.

Via Basecamp, I have been downloading (a growing collection of) Birdseye Satellite images.
All of which are "in storage, in "My Collection" within Basecamp on the computer, and some of which are copied to the GPSMAP64s itself.
(In order not to use more of the device's internal memory than necessary, I have only been copying satellite images across to the device as and when required for the specific areas involved in the current walking expedition).

I understand that once the 12 month subscription to Birdseye Satellite Imagery expires, I will no longer be able to download further images.

And I think I'm correct in my understanding that I will no longer be able to transfer any images that remain "in storage, in "My Collection", across to the GPSMAP64s.

However, I'm not sure what will happen with regards to those Birdseye Satellite Images that are actually on the GPSMAP64s internal memory, when the Birdseye Satellite Imagery subscription expires.

I would be very grateful if someone could confirm whether those satellite images that are on the GPSMAP64s internal memory when the subscription expires will still be able to be "enabled" and made use of? - or will they somehow become permanently disabled/unusable?

If Birdseye Satellite images on the GPS's internal memory remain available for use after the subscription expires, I would be looking to transfer all/most of my downloaded images to the device prior to subscription expiry date.

Kind regards,
Michael Valentine.
  • You are correct, after your subscription expires you will no longer be able to transfer the BirdsEye files via BaseCamp. They will still be usable within basecamp.

    What you can do is after transferring the BirdsEye files to your 64s, copy/move them to another location via Windows explorer. I save mine to a folder on the hard drive. Do this for all of your downloaded Birdseye files BEFORE your subscription expires. With any Birdseye files so saved, you will still be able to freely move them on and off the device via Windows and they will still function. This method has been working fine with my 64s and before that my 62s.

    The Birdseye (.jnx) files are located at UserName>AppData>Roaming>Garmin>BaseCamp>JnxFiles
    You can also access them from that folder although they have a cryptic long filename. If you copy those files, you can, by trial and error identify them and rename them to something recognizable.

    The point is, after the files have been saved outside BaseCamp and your device, you can freely to move them back and forth from your device using Windows.

    On a side note, I have greatly reduced my use of BirdsEye Images and topo as their presence on the device causes the device to display POI's even though that has been disabled in the device. I have had several "dead-end" trouble tickets open regarding this. By dead-end, Garmin has given up and ceased to continue communication even though I can easily produce this bug(?).

    Good luck and enjoy your 64s.
    John
  • Thanks for this advice John, much appreciated - It was not a possibility that I would have thought of!

    I wasn't able to find the BirdsEye .jnx image files via your suggested UserName>AppData>Roaming>Garmin>BaseCamp>JnxFiles filepath.

    I'm running Windows 10 - ( Perhaps has slightly different file path structure? ).

    However, (with the GPSMAP64s connected to the computer), I have been able to find them via this path: - This PC > Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye

    I have created a back-up folder on my hard-drive, and copied all the individual .jnx files from the GPSMAP64s across to that folder.

    I had actually renamed each of the satellite images within Basecamp, when I originally downloaded them, so that the filename had some logical meaning to the area in question.
    They appear in the "BirdsEye" folder on the GPSMAP64s with the names I gave them, and those names are retained , as would be expected, when copied across to the back-up folder. (So no cryptic filenames to deal with!).

    Looking at properties for my newly created back-up folder, it indicates that everything is exactly the same as in the "Birdseye" internal storage folder on the GPSMAP64s.

    So, hopefully I'll now be able to transfer usable copies of these back-up images across to the GPSMAP64s after the Birdseye subscription expires.

    Once again, many thanks for your help.

    Best regards,
    Mike.
  • I too use Windows 10...I think the problem is that the path I gave you is normally hidden. You will need to enable viewing of hidden folders and files.

    The path: PC > Garmin GPSMAP64s (E:) > Garmin > Birdseye is the location on the device (64s). You should also be able to see the SD card as well, if one is installed.

    Ha, ha...the E followed by colon and closed paren became a smiley!
  • Hello again,

    I just tried the following exercises to see if copying one of the .jnx files back to the GPS's internal memory worked - it didn't :(

    I had copied all the .jnx files from This PC > Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye to my back-up folder on the hard drive.
    Within Basecamp, I deleted one particular file from the internal storage of the GPSMAP64s.
    Within Windows File Explorer, I then copied the back-up file from my hard drive back-up folder, back to the Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye folder.
    At this point, and still within Windows File Explorer, the file name does appear within the Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye folder.
    And, again within Windows File Explorer, checking "free space" for the GPSMAP64s "drive", confirms that a file of that specific size has indeed been copied back to the device.

    However, in Basecamp, and on the GPS unit itself, the filename doesn't appear in the list of available satellite images, nor can any sign of the image be seen on the map-screen.
    It's as though it hasn't been properly recognised when it's been copied back onto the GPSMAP64s.

    I suspected that the problem may have been because the copied .jnx file names were showing as my re-named logical names, so I also tried the above method having re-copied all the .jnx files to another back-up folder.
    This time having enabled viewing of hidden folders and files, and backing up the cryptic .jnx filenames which ensued using the UserName>AppData>Roaming>Garmin>BaseCamp>JnxFiles filepath.
    Unfortunately, with exactly the same result - No sign of the file once copied back onto the GPSMAP64s.

    Moreover, when I then tried to reinstate the particular file onto the GPSMAP64s directly within Basecamp, by using send to "GPSMAP64s internal storage" from "My Collection", this resulted in an error message, and the image wouldn't copy back to the GPSMAP64s.

    In order to re-establish a satellite image of that particular area onto the GPS, I had to delete that image from "My Collection", and re-download another image of the area via the normal BirdsEye download process.

    Can't think what I might be doing wrong, but any suggestions would be welcome.

    Regards,
    Michael Valentine.
  • Not sure what you have going on.

    The BirdsEye jnx files sent to your device by BaseCamp have a file name that is the same as the name you give the BirdsEye within BaseCamp. You can copy/move those files from the device to your hard drive to use or not use at a later time.

    The BirdsEye files on your hard drive use the long random letter/number file name. Those files must not have their name changed and left in place. However, a copy of that file in another folder may have its name changed and in my experience, did not present any problem when copied to the device.

    I have a number of BirdsEye files saved to my hard drive. The were mostly copied from the device rather than copied from the user folder on the computer.

    Question, did you leave all the jnx files in place in the UserName>AppData>Roaming>Garmin>BaseCamp>JnxFiles folder and leave their names alone?

    I'll have to look at this some more...I have a number of "expired" BirdsEye Imagrey and Topo files that are still usable provided I copy them to the device in Windows rather than via BaseCamp. I do know that "expired" files, although usable in BaseCamp, may not be transferred to the device via BaseCamp.

    John
  • . . . Question, did you leave all the jnx files in place in the UserName>AppData>Roaming>Garmin>BaseCamp>JnxFiles folder and leave their names alone? . . . .


    Hi John,

    Yes,
    By using the UserName>AppData>Roaming>Garmin>BaseCamp>JnxFiles file-path, I simply navigated to the folder (on the computer) containing those (long-cryptic alpha numerically named) files, selected them, and copied them to the back-up folder I'd created on the hard-drive.
    The cryptic file names, file sizes, etc. etc., appeared to be exactly the same when looking in either folder. (I didn't rename, or otherwise change the files in any way).

    Previously, by using the This PC > Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye file-path, I had likewise, navigated to that folder (on the GPS unit itself), containing the ("logically renamed") .jnx files, selected them, and copied them to a separate back-up folder I'd created on the hard-drive.

    So, at this point I have back-up copies of the .jnx files from both of their original locations - one set cryptically named, and one set logically renamed.

    Forgive me if I'm being a little bit long-winded and dumb, but I'm trying to clarify things as best I can.
    (I'm doing this as much to make sense of things to myself, as well as hopefully enabling you to see where I'm at. :o ): -

    Let's now assume that the BirdsEye subscription has expired, but using the methods above, I have already copied a particular cryptically named .jnx file of (say) 47.33Mb to the back-up folder, and I've also copied a logically renamed .jnx file of exactly the same file-size to the other back-up folder.
    (I'm fairly confident in assuming that even though one is cryptically named, and one is logically named, they must both relate to the same individual Birdseye satellite image).

    Now,
    Let's say, using Basecamp, (and while the GPS is connected to the computer), I had deleted the particular Birdseye satellite image from the internal storage of the GPS, but had left it in place in "My Collection" within Basecamp.
    At this point, since we are assuming that the subscription has expired, (although it hasn't yet), I understand that I can still use the image in Basecamp, but I can't send the image back to the GPS unit.

    Which of the two .jnx back-up files should I be using to copy the image back to the GPS? - the cryptically named one?, or the logically renamed one?

    I'm assuming the back-up copy should be copied directly back to the GPS, using file-path: - Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye. ?

    If you could let me know whether I'm on the right track, and which of the two back-up .jnx files I should be using, I'll try it again and let you kow how I get on.

    Once again, many thanks for your responses - and patience!

    Best regards,
    Mike.
  • Removing the file from the device using Basecamp might be the problem.

    Instead, using a file you already have copied to the PC, use the Windows file manager to delete a Birdseye image file from the device, disconnect the device, reconnect the device and use the Windows file manager to copy the same file from the PC back to the device.

    See how that works.

    ...ken...
  • Now,
    Let's say, using Basecamp, (and while the GPS is connected to the computer), I had deleted the particular Birdseye satellite image from the internal storage of the GPS, but had left it in place in "My Collection" within Basecamp.
    At this point, since we are assuming that the subscription has expired, (although it hasn't yet), I understand that I can still use the image in Basecamp, but I can't send the image back to the GPS unit.

    Which of the two .jnx back-up files should I be using to copy the image back to the GPS? - the cryptically named one?, or the logically renamed one?

    I'm assuming the back-up copy should be copied directly back to the GPS, using file-path: - Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye. ?

    If you could let me know whether I'm on the right track, and which of the two back-up .jnx files I should be using, I'll try it again and let you kow how I get on.



    Mike,
    I just tested this whole thing, just to make sure it still works, and it still does! I'll comment on your questions and then describe what I did to test this.
    You want to leave the BE files in place in My Collection in BaseCamp.
    Yes, you cannot send expired images to the device via BaseCamp...it will notify you when you attempt!
    In the test I just did, BOTH the long cryptic filename file AND the corresponding logical filename file appeared in BC AND on the device.
    In Windows, the correct path on the device is "Garmin GPSMAP 64s (drive letter) > Garmin > BirdsEye
    You are on the right track...both files will work but, using the ones with a logical filename will be more useful to you in Windows.

    Here is a way to I.D. the .jnx with the long file name. In BaseCamp, look at the properties of the BE image... you will see the date and time of download. In the UserName>AppData>Roaming>Garmin>BaseCamp>JnxFiles folder, look for a .jnx file with a similar date/time.

    OK...my test. My 64s had no BirdsEye files for this test. All of my BirdsEye Imagery and Topo subscriptions are expired. I found a BE of interest and noted the date/time of download. I closed BC, and went to the Garmin folder containing the jnx files and located the file that was close in time to the BE of interest. I copied that file to the BE folder on the device. I disconnected the device and powered-up. I was able to enable the BE with the long filename, went to that location and could see the image. That BE appeared in the 64s menu with the long filename. I re-connected the device and opened BaseCamp. With BC, I was able to view the BE on the device.

    I closed BC, went to the BirdsEye file on the device (via Windows) and renamed it to a logical filename. That same file, re-named, still appeared on the device and in BaseCamp as well. All this time, the original BE in my BaseCamp Collection still worked as well.

    Now, I removed the "test" BE file using Windows. I then retrieved the corresponding BE file that I had saved back when my subscription was still active and copied it to the device BE folder. It also still worked on the device and was viewable via BaseCamp. By now, I have three different named versions of this same Birdseye file. All three are the same file size and the original date/time from two years ago.

    I'm not sure what is causing you to have a problem with trying this. Perhaps what I described above may help solve the problem with your procedure. At this point, all I can do is verify that this still works for ME.

    Check it out! John
  • Hello, and thanks for the further replies John & Ken.

    Success! :D - Using your latest advice I've cracked it.

    This morning I downloaded a small Birdseye Satellite image to "My Collection" via Basecamp, renamed it "Testimage", and copied it to the GPS.

    I then closed down Basecamp and switched off/unplugged the GPS from the computer. - Switching the now standalone GPS back on, the "Testimage" was enabled via Map Setup, and became visible.

    Without opening Basecamp, I reconnected the GPS to the computer, and using Windows File Explorer, (and the file-path This PC > Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye, I copied the "Testimage" file to my back-up folder on the hard-drive. - I then disconnected the GPS from the computer once again.

    Re-opening Basecamp, and reconnecting the GPS, I was able to view the "Testimage" by looking at the device's "Internal Storage", within Basecamp.

    At this point, still within Basecamp, and whilst viewing the "Testimage" on the GPS's internal storage, I right clicked on the "Testimage" and using the pop-up menu option, deleted it from the GPS.
    (Just to confirm, at this point, "Testimage was still available in "My Collection").

    I now closed down Basecamp again, and switched off/unplugged the GPS from the computer.

    Once more without opening Basecamp, I reconnected the GPS to the computer, and using Windows File Explorer, (and the file-path This PC > Garmin GPSMAP 64s ( E: ) > Garmin > BirdsEye, I then copied the "Testimage" file back to the GPS from my back-up folder on the hard-drive.

    Disconnecting the GPS from the computer, and switching it back on again revealed that the "Testimage" was now correctly back on the device and properly accessible/viewable.

    The final check of re-opening Basecamp and reconnecting the GPS confirmed that "Testimage" was now viewable once more within Basecamp, on the device's internal storage.

    I'm saving a copy of the above text as an aide memoire, so that I have the correct procedure to hand when the Birdseye subscription expires.

    Once again, thanks for your help - much appreciated.

    Best regards,
    Mike.
  • Outstanding MIke!
    Good to hear you got it resolved.
    John