You will have to convert the KML file created by GE into a GPX file to import it into BaseCamp
So clearly there is a serious defect in Basecamp's import functions. Now we just need to determine what it is...
1. Is KML/KMZ import supposed to work but doesn't? If so, it should be repaired.
Or...
2. Is it that Basecamp is not intended to support KML/KMZ import? If so, then the bug is that KML/KMZ is listed as a supported format when it should not be AND Basecamp tries to import it but it should not. These should be repaired (e.g. removed) so people won't try to use a feature that was never intended to be there.
The KML/KMZ import option is to allow import of Garmin Custom Maps.
If it doesn't support KML import and, as you say, is not intended to, then it should be modified somehow to make that clear.
Possibilities are:
1. Preferred -- Change the Import menu so it doesn't show KML/KMZ as a supported file type. Instead, add a proper "Import Garmin Custom Maps" selection.
2. Less desirable -- If the import dialog can't be made clearer so we won't be fooled into trying it, then the error message should make it instantly clear that it's not intended to do what we're trying. Rather than the obscure error it's now producing, it should just say in plain English (and other languages) that it only imports Garmin custom maps.
As it is right now, there is no reason to assume it won't import any standard KML file and there is nothing more frustrating to a user than to try something that clearly should work, find it doesn't work, try everything they can think of to make it work, report the problem and discover that it was never intended to work in the first place. It makes me mad enough to want to tear my hair out ... if I had any left. :mad:
