Debugging basecamp import of kmz files

When I try and add a custom map to base camp (latest, 4.2.1) I get a message "Basecamp encountered an unexpected error while importing"

I can seek help with the specifics of the kmz file on the custom maps forum but I'm wondering if there is a debug mode for Basecamp that might give me some clues, e.g. where in the kmz file the error is encountered.

Copied directly to my Oregon 600 the unit likes the custom map. It is just Basecamp that doesn't.

Thanks!
  • Former Member
    0 Former Member over 12 years ago
    You can launch BaseCamp in debug mode by launching it with the /DEBUG parameter.

    1. Open Windows Explorer (Windows key + E).
    2. Browse to BaseCamp's installation directory (e.g. C:\Program Files (x86)\Garmin\BaseCamp)
    3. Type cmd in the Explorer's address bar and hit ENTER this will launch the command line with the above directory selected.
    4. Type "BaseCamp.exe /DEBUG" (without quotes) and hit ENTER.
    5. Now a log file will be written in BaseCamp's temp directory. For me, that is C:\Users\{username}\AppData\Local\Temp\BaseCamp\4.2.1\Debug.log
  • bingo!

    Many thanks, exactly what I was looking for and it helped solve my problem!

    The debug showed
    Message: value '357.9887498402' must be less than or equal to maxInclusive facet value '180.0'

    That corresponds to a rotation value for a LatLonBox in the kml:
    <LatLonBox>
    ....
    <rotation>357.9887498402</rotation>

    A google search led me to a Garmin kml schema document at
    http://developer.garmin.com/schemas/kml/2.1/xmlspy/index.html#Link0514D0C0

    where I found a the rotation is an "angle180"
    <minInclusive value="-180"/>
    <maxInclusive value="180"/>


    So I manually edited my kml, changing the rotations to complementary negative values (i.e. -2.0112501598) and bingo! It works :)

    Thanks again.
  • Former Member
    0 Former Member over 12 years ago
    Glad I could help and happy you got it to work!

    When there are issues with BaseCamp reading gpx or kml files, any XML validator will also help tracking down the problem.

    The particular schema isn't even a Garmin one, it's Google's kml schema. BaseCamp is very particular about kml (and gpx) files following the schema exactly. Our devices (and other software) are more forgiving.