Keep KML placemarks with missing coordinates about togeojson HOT 4 CLOSED

Hi,

Thanks for the issue! I can't replicate this problem: for example, here's your example run through togeojson - https://observablehq.com/d/1c3388b177640bb7

There are 3 features in, 3 out, with one having a null geometry. Seeing the same results running the example as a testcase. As far as I can tell, this has been the case for a while - if there are no geometries in a Placemark element, then it'll output a Feature in GeoJSON with a null geometry. Are you sure you're using a recent version of this code and that the items are actually being dropped? It doesn't seem like at least the @tmcw/togeojson package, with the .kml method, has that behavior.

from togeojson.

Ping @hyperknot - is there a testcase that demonstrates this limitation that you can share?

from togeojson.

@tmcw you are right, the example I thought would be a minimal repro case does produce the null geometry correctly.

I'm looking more into the Google My Maps export, it's still not clear to me how it works. (For example it creates a totally different CSV based on how the point was created. Also their CSV is super trivally broken, the commas are not escaped, for example).

from togeojson.

Okay - closing for now, feel free to open a new issue when this gets narrowed down into a reproducible testcase!

from togeojson.