This object is in archive!
KML import: Document/description causes error
Not a Problem
Locus isn't able to import a KML file that has
<Document>
<description>...</description>
...
</Document>
Removing the description allows the file to be imported. If nothing else, this should be documented here or somewhere, along with all other supported KML tags.
The same problem 
Good day Boris,
my teory is that Locus should be able to import every file. In case there is something, that Locus do not know (like some features in KML), it should be skipped.
So in this case, it's a bug. May you please share with me a small file that cause these troubles? So I may fix and test it, thanks.
Good day Boris,
my teory is that Locus should be able to import every file. In case there is something, that Locus do not know (like some features in KML), it should be skipped.
So in this case, it's a bug. May you please share with me a small file that cause these troubles? So I may fix and test it, thanks.
Thanks for the quick response! After a little more testing, it appears that the issue is having the tag inside the. Here's a small file (added .txt to attach here).
Thanks for the quick response! After a little more testing, it appears that the issue is having the tag inside the. Here's a small file (added .txt to attach here).
Hmm, but in this case, file is not valid! XML (GPX, KML, ...) files cannot contain some special characters like <, >, &
So it's a problem of generator of this file, that such characters appear directly in file without encoding or encapsuling into CDATA.
Hmm, but in this case, file is not valid! XML (GPX, KML, ...) files cannot contain some special characters like <, >, &
So it's a problem of generator of this file, that such characters appear directly in file without encoding or encapsuling into CDATA.
Although Google Maps can handle this format, I understand your point.
Although Google Maps can handle this format, I understand your point.
Interesting.
I have absolutely not idea how Google Maps do it, anyway every HTML text inside XML files have to be a) escaped or b) encapsuled by CDATA container. So sorry, but I cannot help here.
Interesting.
I have absolutely not idea how Google Maps do it, anyway every HTML text inside XML files have to be a) escaped or b) encapsuled by CDATA container. So sorry, but I cannot help here.
Replies have been locked on this page!