Related

Invalid LatLonBox error when importing georeferenced KML or KMZ maps from GoogleEarth into Basecamp

3605984
over 3 years ago
I GeoReferenced images of two maps in Google Earth (Idaho Area and Laos Target Echo):
Download for KML and KMZ (these are not routes - they are entire maps):
When I import any of these files into Basecamp I get the error message:
GroundOverlay : [name of map] Invalid LatLonBox
The georeferenced map doesn't appear anywhere in Basecamp.
What am I doing wrong? These same files open back up just fine in GoogleEarth.
  • 0 over 3 years ago

    I have sometimes not been able to open KMZ files in BaseCamp and have usually resolved it by opening the KMZ using the MAPC2MAPC program and then using it to write a Garmin Custom Map (KMZ) which will import into BC okay.

    I just tried this with your Idaho Area KMZ and the conversion works fine, and shows it just to the west of Hue in BC.

  • 0 over 3 years ago

    It looks like you created tracks/routes in google earth along with the map.  If so, it might be worth trying downloading the tracks/routes and the georeferenced map as separate files.

  • 0 over 3 years ago in reply to Eyelet99

    Wow, that worked!

    The question is... why did it work? Is there some reason for .KML / .KMZ files to be different and somehow not compatible across mapping software?

    Is there an open source industry standard for georeferenced map files that all apps can read out of the box (Garmin, Basecamp, OsmAnd, Google Earth, etc)?

  • 0 over 3 years ago in reply to 3605984

    That’s good to hear. A Google Earth KMZ file is simply a zipped KML file - if you change the extension to ZIP you can open it with WinZip or similar to see what KML files are inside. MAPC2MAPC was developed by John Thorn because there is no commonly agreed standard for map calibration files and map tile storage and tile sizes. Happily MAPC2MAPC can usuallly  handle them and the program is regularly updated when a new one comes out.