KML import for art doesn't understand folders

[marnen]

I just tried to import art from a KML file where all the Placemark elements were grouped within a Folder element. Dust's import didn't understand it, and instead treated the Folder element as if it were one Placemark. This should be fixed, and Dust should actually parse the XML enough to identify Placemark elements.

[marnen]

Actually, even when I got rid of the Folder and Document containers and put the Placemark elements directly under the root KML elements, it still didn't import. In fact, it didn't recognize any Placemark elements at all.

[damiant]

Hey @marnen , can you provide a sample KML file to import? There are all sorts of crazy things that make it into KML files depending on where they come from so I'd need a sample to work with to understand the problem.

[marnen]

Sure. If it’s OK, I’ll send it by e-mail to avoid exposing sensitive data on GitHub.

[marnen]

@damiant I should also mention that this happened even with KML exported right from Google Maps (which seems to be your canonical use case of KML).

[marnen]

@damiant OK, I've just e-mailed you some KML files.

[marnen]

I figured it out! Our GIS application was exporting <Placemark> elements with an empty <name> element within them. Once I added some text to the <name> element, Dust picked it up for import.