Ahh... this is frustrating --- I fell into the import KML trap by believing that it would actually import a KML file exported by Google Maps. How silly... We are up to 3.2.2 and its still there.
I sure would like to see a proper KML import and conversion to GPX function in BaseCamp.
[Yes, I do know about gpsbabel :) It seems to strip out the time & date data]
While we wait upon the modest possibility that BaseCamp might someday have a true KML/KMZ import feature, is someone at least working on changing that error message to tell users that the function only works with custom maps?
I realize a feature change takes time and has to move up the priority list. I have no problem with that. But there seems no excuse to not at least fix that erroneous and misleading error message in any interim patch release. A couple minutes to code a few more words into the error message text and it's done. That would save users a lot of grief in the meantime.